using-vibekit
Use when starting any conversation: establishes the auto-trigger discipline so guardrail skills fire instead of being silently skipped.
Skill by rizukirr
Chalk Labs
Need help deploying using-vibekit?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/rizukirr-using-vibekit
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/using-vibekit
What's inside
- Skill name
using-vibekit- Description
- Use when starting any conversation: establishes the auto-trigger discipline so guardrail skills fire instead of being silently skipped.
- License
- MIT
- Instructions
- 35 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# using-vibekit If there is even a 1% chance a vibekit skill applies to what you are about to do, invoke it. This is not negotiable. "The task is too small", "I already know the answer" and "it would be faster to just do it" are the rationalisations this plugin exists to stop. A guardrail you talked yourself out of is a guardrail that was never there. If a skill turns out to be wrong for the situation, you do not have to follow it, but you do have to check. ## If you are a subagent If you were dispatched to execute a specific task, skip this and follow your brief. The orchestration discipline belongs to the session that dispatched you. ## Instruction priority 1. **The user's explicit instructions**: highest. If they say "skip the design step", skip it. 2. **vibekit skills**: these override default behaviour where they conflict. 3. **The default system prompt**: lowest. ## Finding the right skill Every skill declares its own trigger, and the auto-trigger table in `CLAUDE.md` is generated from those declarations, so it is never out of date. Read the table, not a copy of it. A skill whose row says `hard` is a gate. Respect it regardless of how simple the task looks. Simple tasks are where unexamined assumptions cost the most. ## Always on Some skills are modifiers rather than steps: they say so in their own descriptions, which end "Stays on after." The trigger table lists them like any other skill. Nothing here enumerates them, because a count kept by hand goes stale the moment one is added. Invoke each **once**, at the first moment its trigger applies, then keep applying it for the rest of the session without invoking it again. A modifier you never invoke is a modifier whose content you never read: the description line alone is not the skill. ## How to invoke Use the `Skill` tool. The skill's content loads and you follow it directly. Never read a skill file as a substitute for invoking it: reading gives you the text without the commitment.
From rizukirr/vibekit, MIT.
More from rizukirr/vibekit
- 0.644score
plan
rizukirr
Use when a spec is approved and implementation has not started: turns it into a task-by-task plan with exact paths and checkable verification.
SkillAFreshness: A★ 20Claude Code +9 - 0.644score
quick
rizukirr
Use when the user types /vibekit:quick: writes the change immediately under lazy's ladder, no spec, no plan, no subagents.
SkillAFreshness: A★ 20Claude Code +9 - 0.644score
exec
rizukirr
Use when a plan is approved and implementation has not started: dispatches one fresh subagent per task, runs each task's verify clause, and routes failures…
SkillAFreshness: A★ 20Claude Code +9 - 0.644score
debug
rizukirr
Use when a check fails: a red test, a broken build, a failed clause, or a bug you can point at.
SkillAFreshness: A★ 20Claude Code +9 - 0.644score
plain
rizukirr
Use before writing any text, in chat or into a file.
SkillAFreshness: A★ 20Claude Code +9 - 0.641score
brainstorm
rizukirr
Use before any creative or implementation work: features, components, behavior changes.
SkillAFreshness: A★ 20Claude Code +9 - 0.641score
lazy
rizukirr
Use at the start of any coding work: writing, adding, refactoring, fixing, designing.
SkillAFreshness: A★ 20Claude Code +9 - 0.641score
terse
rizukirr
Use at the start of every session.
SkillAFreshness: A★ 20Claude Code +9 - 0.641score
verify
rizukirr
Use before claiming a change is done, fixed or passing: checks the whole change against its spec, runs the checks no single task could, hunts for the bugs the…
SkillAFreshness: A★ 20Claude Code +9 - 0.633score
vibe
rizukirr
Run a short intent through the pipeline.
SkillAFreshness: A★ 20Claude Code +9
Signals
- Stars
- 20
- Forks
- 1
- Open issues
- 0
- Last commit (this folder)
- Aug 25, 2026 (2 months ago)
- Last release
- Oct 10, 2026 (20 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/rizukirr/vibekit
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from rizukirr
- 0.644score
plan
rizukirr
Use when a spec is approved and implementation has not started: turns it into a task-by-task plan with exact paths and checkable verification.
SkillAFreshness: A★ 20Claude Code +9 - 0.644score
quick
rizukirr
Use when the user types /vibekit:quick: writes the change immediately under lazy's ladder, no spec, no plan, no subagents.
SkillAFreshness: A★ 20Claude Code +9 - 0.644score
exec
rizukirr
Use when a plan is approved and implementation has not started: dispatches one fresh subagent per task, runs each task's verify clause, and routes failures…
SkillAFreshness: A★ 20Claude Code +9 - 0.644score
debug
rizukirr
Use when a check fails: a red test, a broken build, a failed clause, or a bug you can point at.
SkillAFreshness: A★ 20Claude Code +9 - 0.644score
plain
rizukirr
Use before writing any text, in chat or into a file.
SkillAFreshness: A★ 20Claude Code +9 - 0.641score
brainstorm
rizukirr
Use before any creative or implementation work: features, components, behavior changes.
SkillAFreshness: A★ 20Claude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get using-vibekit running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
using-vibekit skill. Agent Mart. https://agentmart.dev/skills/rizukirr-using-vibekit (last updated 2026-10-24)