Skill Overview
In a nutshell: a Skill is a small capability package installed locally on a Claw host. You do not need to learn install commands β just ask the General Assistant Agent to install whatever Skill you want.
What a Skill is
- A directory with a
SKILL.mddescribing what the capability does. - It only takes effect on the Claw host where it is installed.
- The Agent sees it automatically during a session and loads the full instructions when needed.
Where Skills live
All Skills live in this local directory on the target Claw host:
text~/.myclaws/claw/data/skills/
You do not have to maintain this path yourself β when Claw starts it scans the directory and injects each installed Skill's description into the current session's system prompt.
Installing a new Skill
Just ask the General Assistant. For example:
- "Install a code-review Skill for me."
- "Add the git Skill to this Claw."
- "List the Skills installed on this Claw."
- "Remove the xxx Skill."
The General Assistant uses the built-in skill-installer / skill-creator tools to install, create, or remove Skills β you never have to remember command-line arguments.
Notes
Skills are host-local and do not auto-sync across machines
To have the same Skill on every Claw, ask each host's General Assistant to install it.
Built-in Skills cannot be uninstalled
codex, claude-code, cron-task, skill-creator, skill-installer are platform built-ins.
When to use MCP instead
If you want to plug in an "external system as a tool" (database, internal service, third-party API), prefer MCP. Skills are better for "reusable workflow scripts".