skill-creator
When to Create a Skill
Create a skill when:
- A pattern is used repeatedly and AI needs guidance
- Project-specific conventions differ from generic best practices
- Complex workflows need step-by-step instructions
- Decision trees help AI choose the right approach
Don't create a skill when:
- Documentation already exists (create a reference instead)
- Pattern is trivial or self-explanatory
- It's a one-off task
Skill Structure
More from phar-dev/phardev.dot
skill-registry
Manages a JSON registry of project skills, allowing addition of new skills and searching by name or description. Works with skill-creator to automatically register new skills.
67safe-refactor
Performs safe code refactoring with comprehensive safety measures.
10git-master
MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with delegate_task(category='quick', load_skills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
7skill-finder
Helps the agent find and recommend the most appropriate skill for a given task or user query by searching the skill-registry.
6command-creator
Creates new opencode command files with proper structure, templates, and validation. Generates .md files in .opencode/commands/ with YAML frontmatter and actionable templates.
6