skill usage
- Repo stars 551
- Author repo a-evolve
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @A-EVO-Lab · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- Python
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Skill Usage Guide
Skills are modular instruction packages placed in the container to help you solve tasks. Using them effectively is the single most important factor for success.
## Skill locations
Skills are copied to multiple well-known paths inside the container:
- `/root/.agents/skills/`
- `/root/.claude/skills/`
- `/root/.codex/skills/`
All paths contain the same skills. Use whichever is available.
## Skill structure
Each skill is a folder:
```
skill-name/
├── SKILL.md # Main instructions (YAML frontmatter + markdown body)
├── scripts/ # Optional helper scripts (Python, Bash)
└── references/ # Optional reference documentation
```
## How to use skills
1. **Always list skills first** — call `list_skills` at the start of every task
2. **Load relevant skills** — if a skill name matches the task domain, call `load_skill` with the skill name
3. **Follow skill instructions** — skills contain domain-specific procedures, parameter values, or code patterns that are essential
4. **Run helper scripts** — if the skill has `scripts/`, execute them (they often automate tedious steps)
5. **Consult references** — check `references/` for API docs or formula sheets
## Common skill patterns
- **Data format skills** (e.g., xlsx, csv): Teach how to read/write specific formats
- **Domain skills** (e.g., pid-control, seismic): Contain domain formulas and constants
- **Tool skills** (e.g., libreoffice, ffmpeg): Show correct CLI flags and workflows
- **Framework skills** (e.g., react, spring-boot): Guide migration or debugging patterns
## Anti-patterns
- Do NOT ignore skills — they exist specifically for the task at hand
- Do NOT reinvent what a skill script already automates
- Do NOT skip reading the full SKILL.md — summaries miss critical details
Sections and files
Listed in source order.
sections -> Skill locations → Skill structure → How to use skills → Common skill patterns → Anti-patterns
terms -> Always list skills first · Load relevant skills · Follow skill instructions · Run helper scripts · Consult references · Data format skills · Domain skills · Tool skills
files/cmd -> /root/.agents/skills/ · /root/.claude/skills/ · /root/.codex/skills/ · list_skills · load_skill · scripts/ · references/
body sha256 -> df67a3446ce3
Skill locations
Skills are copied to multiple well-known paths inside the container:
/root/.agents/skills//root/.claude/skills//root/.codex/skills/All paths contain the same skills. Use whichever is available.Skill structure
Each skill is a folder:
How to use skills
Always list skills first — call
list_skillsat the start of every task Load relevant skills — if a skill name matches the task domain, callload_skillwith the skill name Follow skill instructions — skills contain domain-specific procedures, parameter values, or code patterns that are essential Run helper scripts — if the skill hasscripts/, execute them (they often automate tedious steps) Consult references — checkreferences/for API docs or formula sheetsCommon skill patterns
Data format skills (e.g., xlsx, csv): Teach how to read/write specific formats Domain skills (e.g., pid-control, seismic): Contain domain formulas and constants Tool skills (e.g., libreoffice, ffmpeg): Show correct CLI flags and workflows Framework skills (e.g., react, spring-boot): Guide migration or debugging patterns
Anti-patterns
Do NOT ignore skills — they exist specifically for the task at hand Do NOT reinvent what a skill script already automates Do NOT skip reading the full SKILL.md — summaries miss critical details