Skip to content
Skills Library
AI & agents · Planning

using-vibekit

/using-vibekit

Use when starting any conversation: establishes the auto-trigger discipline so guardrail skills fire instead of being silently skipped.

Repository
vibekit ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when starting any conversation: establishes the auto-trigger discipline so guardrail skills fire instead of being silently skipped.

Original author description

Use when starting any conversation: establishes the auto-trigger discipline so guardrail skills fire instead of being silently skipped.

How it works

  1. If you are a subagent
  2. Instruction priority
  3. Finding the right skill
  4. Always on
  5. How to invoke
Original SKILL.md headings · 35 lines, 349 words
SKILL.md preview
---
name: using-vibekit
description: "Use when starting any conversation: establishes the auto-trigger discipline so guardrail skills fire instead of being silently skipped."
trigger: Session start
gate: none
---

# 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.

Versions

The database has no other skills named using-vibekit.

Database snapshot: 13.11.2026 · package version a3f7c6323a37 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100use-vibekit
    Operate VibeKit inside projects created or configured by `vibekit new` and `vibekit init`. Use for VibeKit CLI and MCP tools, project setup, LocalNet, accounts, signing, network selection, deployment, transactions, and troubleshooting. Load before any on-chain action in a…
  • 100vibekit
    Add @randroids-dojo/vibekit as a tag-pinned dependency and apply its per-module integration patterns. Use when a project needs VibeKit installation, dependency-ledger guidance, or cookbook help for its client and server modules.
  • 100using-superjawn
    Establishes how to find and use skills before any response or action. Use when starting any conversation.
  • 100build-on-vibekit
    Extend VibeKit from its source workspace. Use when defining VibeKit tools, building a ToolPlugin package, composing a deployment, or exposing a custom deployment through stdio or HTTP MCP. Covers the current packages/vibekit/examples and packages/vibekit/src/plugins/* patterns.…
  • 90using-superpowers
    Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
  • 100using-groundwork
    This skill should be used when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.