← ClaudeAtlas

skill-authorlisted

How to create or update a somora skill correctly — always use the somora skill CLI, never write SKILL.md directly.
thenaxon/somora_agent · ★ 4 · AI & Automation · score 80
Install: claude install-skill thenaxon/somora_agent
# Authoring somora skills When the user asks you to create a new 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 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>" ``` ## 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`, repo `openclaw/clawhub`) is OpenClaw's public skill registry. Pass any `clawhub.ai/<owner>/<slug>` web URL directly — somora detects it, downloads the ZIP via ClawHub's public API, extracts sub-resources, and translates `metadata.openclaw.*` frontmatter to `metadata.somora.*` automatically. ``` somora skill add github --from-url https://clawhub.ai/steipete/github ``` If ClawHub has the skill flagged as malware-blocked, the install refuses with a precise reason. Rate-limit errors (429) surface the `Retry-After` value so the user knows when to retry. If lint fails, **do not** work around it by writing the file