2.1 KiB
name, description
| name | description |
|---|---|
| claw-skills | ClawSkills management and collaboration suite — scripts and workflows for using and improving skills. |
claw-skills
ClawSkills management and collaboration suite — scripts and workflows for using and improving skills.
All skill-related documentation must be written in English. When creating, improving, or correcting skills, always use English for all documentation, descriptions, and guides.
For additional guidance, see {baseDir}/docs/standard.md.
Skill Structure
A skill is a directory with the following layout:
{skill-name}/SKILL.md # Required — skill description and usage
{skill-name}/scripts/ # Optional — executable scripts
{skill-name}/workflows/ # Optional — process guides
{skill-name}/docs/ # Optional — supplementary documentation
Writing Requirements
SKILL.md should be concise. It serves as a table of contents for workflows — list each workflow file path with the scenario that triggers it. For supplementary documentation, use docs/.
Scripts
update-skills
Pull latest ClawSkills from git-hangman-lab, then run learn.sh to install/update skills to {AGENT_WORKSPACE}/skills.
claw-skills/scripts/update-skills
promote-improvements
Create and force-push a branch named after the agent (via ego-mgr get name) from {AGENT_WORKSPACE}.
claw-skills/scripts/promote-improvements
Workflows
fix-skills
When a skill or its scripts fail to produce expected results, or throw errors:
Do not resort to workarounds lightly. Follow
{baseDir}/workflows/fix-skills.md— identify the root cause first, then fix properly.
improve-skills
When using a skill and you find:
- Misleading or ambiguous descriptions
- Missing coverage for your use case
- Suboptimal or confusing behavior
Follow
{baseDir}/workflows/improve-skills.mdto improve it.
create-skills
When you notice patterns or workflows that could improve efficiency but have no skill covering them:
Follow
{baseDir}/workflows/create-skills.mdto create a new skill.