skill development
- Repo stars 487
- Author repo vibecosystem
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @vibeeval · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Skill Development Rules
When working with files in `.claude/skills/`:
## SKILL.md Structure
```yaml
```
## DO
- Keep SKILL.md concise (< 200 lines)
- Include clear "When to Use" section
- Provide copy-paste bash commands
- Reference scripts/ for MCP operations
- Add triggers to skill-rules.json
## DON'T
- Include implementation details in SKILL.md
- Duplicate content across skills
- Create skills without corresponding trigger in skill-rules.json
- Use allowed-tools that aren't needed
## MCP Wrapper Skills
For skills that wrap MCP scripts:
- Use `allowed-tools: [Bash, Read]` to restrict capabilities
- Point to the script in scripts/ directory
- Include parameter documentation
Sections and files
Listed in source order.
sections -> SKILL.md Structure → DO → DON'T → MCP Wrapper Skills
terms -> No English key terms available
files/cmd -> .claude/skills/ · allowed-tools: [Bash, Read] · .claude/skills · skill-rules.js
body sha256 -> 7506a0277c22
DO
Keep SKILL.md concise (< 200 lines) Include clear "When to Use" section Provide copy-paste bash commands Reference scripts/ for MCP operations Add triggers to skill-rules.json
DON'T
Include implementation details in SKILL.md Duplicate content across skills Create skills without corresponding trigger in skill-rules.json Use allowed-tools that aren't needed
MCP Wrapper Skills
For skills that wrap MCP scripts: Use
allowed-tools: [Bash, Read]to restrict capabilities Point to the script in scripts/ directory Include parameter documentation