Search and Install
Runtime Detection: Prefer npx skills, fall back to $CHERRY_STUDIO_BUN_PATH x skills, if neither is available prompt to install Node.js
Search: Understand the need→extract keywords→npx skills find [query]→display name/function/source
Install: Skills are third-party code with full permissions, must: display security warning→provide source link→user confirmation→npx skills add <owner/repo@skill> -y. Location: project-level .claude/skills/ or user-level ~/.claude/skills/
No Results: Inform→propose completing it directly→suggest creating a custom Skill
Create Skills
Directory Structure: skill-name/ under SKILL.md(required) + scripts/(optional) + references/(optional) + assets/(optional)
Process:
- Requirement Capture: What does the Skill do? Trigger scenarios? Output format? "Turn the process just now into a Skill"→extract from the conversation
- Write SKILL.md: frontmatter (name+description states specific trigger scenarios) + body (imperative sentences, ≤500 lines, include 1-2 examples, split large files into references/)
- Test: 2-3 use cases, run subagents in parallel comparing with-skill vs baseline
- Iterate: Modify based on tests and feedback, ensure accurate triggering
Principles: Explain why instead of piling up MUSTs, general instructions should not be tied to specific examples, organize references/ by variant for multiple domains
References: https://skills.sh/ | npx skills find/add/init