skill-author
Skill0 starsChanged 2 months agoMITView on GitHub
Write, structure, and publish a SKILL.md skill that works across every harness — Claude Code, DeepSeek Harness (dsh), Codex CLI, Gemini CLI, Copilot, Cursor — including the cross-agent gotchas generic guides miss: tier shadowing between project and user roots, discovery rules, and trigger-description design. Use when creating a new skill, fixing a skill that fails to load in some agents, or preparing a skill repo for distribution.
24 other projects use a version of this.
Adopted by
Most recently taken up by
- tailcallhq/skillstheir own version, first seen Nov 16, 2026
- himkt/cafleettheir own version, first seen Nov 12, 2026
- DylXBT/claude-orchestrator-skillstheir own version, first seen Nov 8, 2026
- pankaj-mahaur/Agent-Daemontheir own version, first seen Nov 6, 2026
- educlopez/mallardtheir own version, first seen Nov 1, 2026
- mandasTeam/skill-authortheir own version, first seen Nov 1, 2026
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- generative-computing/mellea★ 1.9ksame name
- aqm857886159/Nomi★ 550same name
- DylXBT/claude-orchestrator-skills★ 114same name
- robium-ai/robium★ 93same name
- himkt/cafleet★ 56same name
- Lethe044/agentskill-kit★ 50same name
- manusco/resonance★ 38same name
- Zhonghao1995/agentic-swmm-workflow★ 31same name
- felvieira/claude-skills-fv★ 28same name
- peter-tu-zynkr/zynkr-skill-builder★ 21same name
14 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- improve-claude-mdSkill
- show-meSkill
- claude-plugin-devSkill
- deepseek-cost-routerSkill
- deepseek-migrationSkill
- dsh-plugin-devSkill
- skill-portability-auditSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 51
Keep SKILL.md under ~500 lines: Put depth in references/*.md and link to them ("see references/schema.md").
- Very specific: line 56
Relative links must stay relative: If SKILL.md references scripts/x.py, the whole folder travels together — never link outside the skill …
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Authoring a cross-agent SKILL.md skill
A skill is a folder with a SKILL.md file inside. The file starts with a YAML
frontmatter block (name + description) followed by Markdown instructions the
agent loads on demand. Because Claude Code, DeepSeek Harness (dsh), Codex CLI,
Gemini CLI, Copilot and Cursor all read this same format, one well-authored
skill serves every agent.
Anatomy
my-skill/
├── SKILL.md # required: frontmatter + instructions
├── references/ # optional: long-form docs the model reads on demand
└── scripts/ # optional: helper scripts the skill may run---
name: my-skill
description: >-
One or two sentences: what it does AND when to use it. This is the trigger
the agent matches against the user's request — write it like a routing rule.
---
# My skill
Step-by-step instructions. Assume a competent engineer; be concrete, not vague.Rules that decide whether a skill works
namemust be kebab-case — lowercase letters, digits, hyphens; max 64 chars. Agents reject or mangle other names.aipxnormalizes for you, but ship it correct.descriptionis the trigger, not documentation. Bad: "Utilities for working with things." Good: "Summarize YouTube/Bilibili videos and podcasts from a URL. Use when the user pastes a video or audio link."- Keep SKILL.md under ~500 lines. Put depth in
references/*.mdand link to them ("see references/schema.md"). Agents load the body only when the skill triggers; huge bodies waste context and dilute behavior. - No nested skills. Discovery scans only the direct children of a skill
root —
skills/a/SKILL.mdis found,skills/a/b/SKILL.mdis not. - Relative links must stay relative. If SKILL.md references
scripts/x.py, the whole folder travels together — never link outside the skill directory.
Where skills live (user roots)
| Root | Read by |
~/.agents/skills/<name>/SKILL.md | DeepSeek Harness (dsh), Codex CLI |
~/.claude/skills/<name>/SKILL.md | Claude Code |
~/.gemini/skills/<name>/SKILL.md | Gemini CLI |
~/.copilot/skills/<name>/SKILL.md | GitHub Copilot CLI |
Project-scoped equivalents exist too (e.g. .claude/skills/, .agents/skills/
in the repo). Don't copy by hand — use aipx sync to link one copy into every
agent root.
Test before publishing
# does it parse and get discovered?
aipx install ./my-skill --dry-run
aipx install ./my-skill
aipx listThen open your agent and confirm the skill appears (Claude Code: it shows in
the skill list; dsh: / command palette → Skills group).
Publishing checklist
- Repo contains the skill folder at a stable path, e.g.
skills/my-skill/ descriptionstates trigger conditions, not just features- Works from a clean install (
aipx install owner/repo#path:/skills/my-skill) - Add GitHub topics so discovery works:
agent-skills,claude-code,dsh-plugin(if it also ships a dsh bundle),deepseek(if DS-related) - Optional: dual-target packaging — see the
dsh-plugin-devandclaude-plugin-devskills
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

