← ClaudeAtlas

skill-authorlisted

Author and improve robium skills. Three modes: fresh authoring from skills/_TEMPLATE, mining skills out of existing repos and apps, and hardening skills from learnings/ notes after trial runs. Enforces the robium quality bar (template compliance, trigger-surface descriptions, <500-line bodies, stated delegation posture, upstream links, no invented syntax) and runs scripts/validate_skills.py. Use when: 'write a new robium skill', 'improve robium skills', 'absorb learnings', 'harden skills', after building an app produced learnings files, or when distilling patterns from an existing robotics repo into a skill. Wraps Claude's skill-creator skill for evals and description tuning instead of reinventing it. Not for: building robot applications (use architect and the domain skills).
robium-ai/robium-plugin · ★ 0 · AI & Automation · score 73
Install: claude install-skill robium-ai/robium-plugin
# skill-author The meta-skill that governs how every other robium skill gets born, mined, and hardened. It is the repo's authoring machinery: it enforces the quality bar defined in the design spec, runs the repo-level validator, and describes the three ways skill content enters the catalog — fresh authoring, mining from existing repos, and hardening from post-trial learnings. ## When to use this skill - Creating a brand-new skill under `skills/<name>/` from the template. - Extracting reusable patterns out of an existing repo (an official demo repo, or an app built without robium) into a new or existing skill. - Consuming `learnings/YYYY-MM-DD.md` files written during app-building sessions and folding them back into the affected skills. - Auditing an existing skill against the quality bar, or running the validator before a commit. - Tuning a skill's frontmatter `description` for better trigger accuracy, or evaluating whether a skill fires on the phrasing it should. - Cross-reference: for building an actual robotics application (choosing a stack, scaffolding a repo), use the `architect` skill and the domain skills it routes to instead — this skill only edits skills, never application code. ## Key directives - **Delegation posture: embed.** This skill owns the authoring workflow outright; there is no good upstream skill for "how to write a robium skill," so the process lives here rather than being linked out. - Knowledge goes to the **lowest skill that can h