1f70264e73
- create-skill: superseded by native /skill command and official docs - orchestrator: superseded by native Agent Teams (/agent-teams) - notediscovery: redundant with cognitive-memory MCP (superior local-first implementation) All moved to _archive/ for historical reference. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
56 lines
1.1 KiB
Markdown
56 lines
1.1 KiB
Markdown
# Update Existing Skill Workflow
|
|
|
|
## Trigger
|
|
User says: "update skill", "improve skill", "modify skill"
|
|
|
|
## Purpose
|
|
Update an existing skill with new capabilities or improved structure.
|
|
|
|
## Workflow
|
|
|
|
### 1. Review Current Skill
|
|
- Read SKILL.md
|
|
- Check existing workflows
|
|
- Identify what needs updating
|
|
|
|
### 2. Determine Update Type
|
|
|
|
**Content Update:**
|
|
- Add new information
|
|
- Update examples
|
|
- Refine instructions
|
|
|
|
**Structure Update:**
|
|
- Add workflows/ if simple → complex
|
|
- Reorganize sections
|
|
- Improve routing logic
|
|
|
|
**Capability Update:**
|
|
- Add new tools/commands
|
|
- Integrate new APIs
|
|
- Add new workflows
|
|
|
|
### 3. Make Changes
|
|
- Update SKILL.md description/triggers
|
|
- Add/modify workflow files
|
|
- Update routing logic
|
|
|
|
### 4. Test Changes
|
|
- Verify triggers still work
|
|
- Test new workflows
|
|
- Check backward compatibility
|
|
|
|
### 5. Document Updates
|
|
- Note what changed
|
|
- Update examples if needed
|
|
- Test activation
|
|
|
|
## Best Practices
|
|
- Maintain existing functionality
|
|
- Test trigger phrases
|
|
- Keep changes focused
|
|
- Document major changes
|
|
|
|
## Reference
|
|
See main create-skill SKILL.md for detailed guidelines.
|