skill development

Other Community

Skill notes

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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
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.

Author source file SKILL.md

# 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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.