skill-author

# Authoring & installing somora skills When the user asks you to create or install a skill, **always use the somora skill CLI**. Do not write SKILL.md files directly with the Write tool — the CLI pre-flights the lint that would otherwise reject your file at load time. ## Create a new skill from scratch (conversational path) Pick a template based on what the skill does: - `cli-wrapper` — orchestrates an installed command-line tool (e.g. wraps `gh`, `op`, `gog`) - `api-wrapper` — calls an HTTP API - `default` — everything else Then run: ``` somora skill add <slug> --template <template-name> --description "<one-line>" ``` Fill in the body, then **declare what the skill needs** (next section) and finish with the setup checklist below. ## Install a skill from a URL ### Direct markdown URL ``` somora skill add <slug> --from-url <https-url-to-raw-SKILL.md> ``` The CLI downloads, sniffs for HTML (rejects landing pages), lints, and only writes if everything passes. ### ClawHub marketplace ClawHub (`https://clawhub.ai`) is OpenClaw's public skill registry. Pass the web URL directly — somora detects it, downloads the ZIP via ClawHub's public API, extracts sub-resources, and translates the frontmatter (`metadata.openclaw.*`, legacy `clawdbot`/`clawdis` too) to `metadata.somora.*` automatically. **Prefer the owner-qualified URL** — slugs are not unique across owners: ``` somora skill add gog --from-url https://clawhub.ai/steipete/skills/gog ``` A bare-slug URL of a contest...