robo-engineer-skill-authoring

Write the SKILL.md with write_file to skills/<category>/<name>/ or optional-skills/<category>/<name>/, validate the frontmatter locally, add a pytest file under tests/skills/, regenerate the docs, then git add, commit, and open a PR.

The validator requires name and description, but the repo standard also expects version, author, license, platforms, and metadata.robo with tags and related_skills. The file must start with --- at byte zero and close the frontmatter before a non-empty body.

Bundled skills/ is for daily-driver behavior useful across many user types, justified by 5+ sessions per month. Niche, vertical-specific, or heavy skills belong in optional-skills/. When in doubt, choose optional since promoting later is easier than demoting.

skill_manage(action='create') writes to the user-local ~/.robo/skills/ directory, not the repository tree. For committed in-repo skills, use write_file to create the SKILL.md and git add to stage it.

The repo hardline is 60 characters, one sentence, ending with a period, even though the validator allows up to 1024. The system prompt skill index truncates at 57 characters, so the trigger must be self-contained in that window.

The skill loader is initialized at session start and cached, so skill_view and skills_list will not see a newly added skill until a new session begins. This is expected behavior, not a bug.