57 lines
1.6 KiB
Markdown
57 lines
1.6 KiB
Markdown
# create-skills
|
|
|
|
Used when you notice patterns or workflows that could improve efficiency but have no skill covering them.
|
|
|
|
## Principle
|
|
|
|
Not every repetitive task needs to become a skill. Ask first: is this pattern general enough to warrant abstraction?
|
|
|
|
## Process
|
|
|
|
### 1. Identify the Pattern
|
|
|
|
- Record the repeating sequence of operations
|
|
- Analyze: what are you doing repeatedly across tasks?
|
|
- Evaluate: is this operation general-purpose or a one-off特例?
|
|
|
|
### 2. Assess Whether It's Worth Making a Skill
|
|
|
|
**Worth doing when:**
|
|
- The same operation recurs across different agents/workspaces
|
|
- The steps are fixed, results are predictable
|
|
- Involves external system calls (git, keycloak, file ops, etc.)
|
|
|
|
**Not worth doing when:**
|
|
- One-off task
|
|
- Steps vary depending on context
|
|
- Purely conversational/analytical work
|
|
|
|
### 3. Design the Skill
|
|
|
|
- **Name:** `{action}-{target}` (e.g., `git-clone-repo`, `keycloak-create-user`)
|
|
- **SKILL.md contents:**
|
|
- Description: what this skill does
|
|
- Use cases: when to use it
|
|
- Scripts: all related scripts and how to call them
|
|
- **Scripts:**
|
|
- Place under `scripts/`
|
|
- Each script has a single responsibility
|
|
- Provide `--help` or `-h` support
|
|
|
|
### 4. Implement
|
|
|
|
- Write the scripts, verify they work
|
|
- Write the SKILL.md
|
|
- Test locally
|
|
|
|
### 5. Submit
|
|
|
|
- Follow promote-improvements to push to your branch
|
|
- Commit message includes: skill name, what it does, usage example
|
|
- Notify hang with the new skill's purpose
|
|
|
|
### 6. Ship
|
|
|
|
- hang merges it; skill enters the official ClawSkills list
|
|
- Other agents pull it automatically via learn.sh
|