Reusable AI-assistant skills, authored locally and published from GitHub.
Install agent-skills-setup through the current agent's own Skill manager or
ClawHub. The repository does not provide a cross-agent installer. Installation
only makes the references and migration script available to that agent.
Installation has no IDE target: --source, --target, --objects, and
--workspace belong to a later migration command run by the agent.
skills-repo/
├── docs/ # active maintainer guidance
├── scripts/ # repository tooling
└── skills/agent-skills-setup/ # canonical publishable skill
├── SKILL.md
├── references/
└── scripts/
Scoped migration of selected assistant context between supported IDEs and agents. It handles documented skills, rules, prompts, and MCP objects; whole IDE configuration and opaque project trees stay manual. See the IDE registry for the 44 script-supported identifiers and documented manual-only surfaces.
The runtime package contains references plus one migration command. It does not install IDEs or runtimes, create symlinks, maintain registry locks, or copy itself into agent directories. Global migrations default to Skills only; project-backed objects use an explicit workspace. Before a Skill directory is copied, all source text is scanned; a likely literal credential or link outside the Skill rejects that Skill without changing its source or existing target. The Skill metadata declares only local file-read, file-write, and shell capabilities, and its trigger describes migration between two named supported products. Project rules and prompt targets use the selected conflict strategy, defaulting to a backup before copy.
- Edit
skills/agent-skills-setup/, never the generated rootSKILL.md. - Run
bash validate-all.sh. - Regenerate the root mirror after canonical-skill edits:
bash scripts/sync-root-mirror.sh. - Merge only after validation.
To review an external skill, use bash scripts/import-agent-skill.sh <source-dir> <skill-name> in a branch.
GitHub is canonical; ClawHub and Awesome Copilot are distribution channels. Before release, run the full suite and security scan, push and verify the GitHub commit, then require a successful ClawHub dry run before publishing. See the release checklist.