Markdown behaviors for hakoCLAW and hako. Drop a folder, name it, and the agent loads it.

_{site catalog  ·  SKILL.md spec  ·  hakoCLAW  ·  hako}

_{—— I ——}

Catalog

— 01 —	corp A company in a folder. CEO · DEV · DESIGN · QA · ARCH. Routes tasks by domain. Markdown only, no runtime.
— 02 —	your skill here Open a PR. Folder name becomes the invocation.

_{—— II ——}

Install into claw

git clone https://github.com/mithraeums/skills /tmp/skills_tmp
cp -r /tmp/skills_tmp/<skill> ~/.hakoc/skills/
rm -rf /tmp/skills_tmp
hakoc                  # "loaded 1 skill(s)"

claw loads any folder containing a SKILL.md at startup. Inner files are pulled on demand via the read_skill(skill, path) tool.

Install into hako

cp -r <skill> ~/.hako/skills/

Hako loads ~/.hako/skills/*.md and ~/.hako/skills/*/SKILL.md into the Rei panel's system prompt at launch.

_{—— III ——}

Format

Every skill is a folder:

<skill-name>/
├── SKILL.md          dispatcher: frontmatter + intro + agent map
└── (any *.md, agents/, helpers, assets)

SKILL.md frontmatter:

---
name: <skill-name>
description: >
  One-paragraph summary. When to load. What it solves.
  Include trigger phrases.
---

Inside SKILL.md: keep it dispatcher-shaped — orient the model, list which inner files exist, hand off. Under 50 lines is the goal. If a skill needs more, split it into agents.

_{—— IV ——}

Compatibility

Tool	Path	Status
hakoCLAW	~/.hakoc/skills/	native, read_skill tool
hako (Rei panel)	~/.hako/skills/	native, system-prompt inject
Claude Code	.claude/skills/	drop-in
Codex CLI · Cursor · Gemini CLI · OpenCode · Windsurf	varies	markdown is markdown

_{—— V ——}

Contribute

git clone https://github.com/mithraeums/skills
git checkout -b add/your-skill
# add your-skill/SKILL.md (+ any agents/helpers)
git push origin add/your-skill
# open PR

Keep skills referential, not prescriptive. Token budget first. The dispatcher orients — the model reasons.

_{— deus sol invictus mithras —}