Create a new mode-specific project skill to standardize a workflow in one mode. Confirm scope and name Target path is ./.roo/skills-<mode>/<skill-name>/SKILL.md and the name is spec-compliant Create folder and SKILL.md with required frontmatter and clear sections Skill is discoverable and has actionable instructions Validate name/description constraints and directory-name match Spec-compliant frontmatter Create a project skill that includes an entrypoint SKILL.md plus reference material and a validation script. The goal is progressive disclosure: only read references when needed, and execute scripts for deterministic checks. Choose structure based on fragility and size Use SKILL.md as the entrypoint, references/ for long-lived guidance, and scripts/ for validation/automation. Draft SKILL.md as navigation (not a dumping ground) SKILL.md contains: - Frontmatter (name/description) - When to use / When NOT to use - A numbered workflow with explicit "read this file when..." pointers - A "Files" section that links one level deep: - references/SCHEMA.md (read when needing field definitions) - references/TROUBLESHOOTING.md (read when validation fails) - scripts/validate_input.(sh|js|py) (execute to validate intermediate outputs) Create references with table-of-contents style headings Each references/*.md file starts with a short contents list so the agent can jump to relevant sections. Make script intent explicit SKILL.md clearly states whether the script should be executed (preferred) or read as reference. The script produces verifiable output (e.g., JSON report or "OK"/error list) to support feedback loops. Edit an existing global skill used across multiple projects. Locate the global skill path and read SKILL.md Exact file to change is known Apply the minimal edit and re-check frontmatter constraints Global skill updated safely and remains spec-compliant