oma-skill-creation

# OMA Skill Authoring ## Scheduling ### Goal Create or revise a usable OMA skill with clear routing, one execution path, domain-specific recovery, and proportionate context. ### Intent signature - Create, update, audit, or normalize an OMA skill, its resources, or the SSL-lite format. - Decide whether content belongs inline, in a conditional resource, or should be removed. ### When to use - Authoring `.agents/skills/{name}/SKILL.md` and supporting resources. - Reviewing skill routing, execution contracts, reference loading, or duplicated instructions. ### When NOT to use - Installing third-party skills -> skill installer; creating a Codex plugin -> plugin tooling. - Application implementation -> the owning specialist; project requirements -> `oma-pm`. ### Expected inputs Skill purpose, triggers, boundaries, execution model, and existing commands/resources or user edits to preserve. ### Expected outputs A four-section SKILL.md, only necessary supporting resources, and validation results with unresolved limitations. ### Dependencies `resources/ssl-lite-template.md` for the skeleton and `resources/validation-checklist.md` for acceptance criteria. Use native file tools and available `oma skill` validators. Follow repository rules for source ownership and generated copies. ## Structural Flow ### Transitions - New skill: compare 1–3 analogous skills, then use the template. - Existing skill: preserve working domain detail and change only the requested scope. - Repeated ins...