domains / families / agent-tooling / skill-writer

skill-writer

combined

Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs and registration". Handles source capture, precision passes, authoring, registration, and validation. Create and improve agent skills following the Agent Skills specification. Use when asked to create, write, or update skills.

When to use

• Use this skill when tackling tasks related to its primary domain or functionality as described above.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

Both copies describe the same canonical workflow for creating and improving agent skills, but they disagree on the reference architecture and the required steps. The getsentry copy is a router that defers to many specific reference files (execution-shapes, reference-architecture, source-discovery, source-adaptation, iteration-evidence, output-contracts, skill-evals, structure-troubleshooting, artifact-layout, workflow-mechanic, and Claude-specific references) and does not prescribe a fixed multi-step sequence beyond Step 1. The sickn33 copy prescribes a fixed 7-step sequence (Resolve, Synthesis, Iteration, Author, Optimize Description, Evaluate, Register/Validate), uses a different set of reference files (skill-patterns, workflow-patterns, output-patterns, evaluation-path, examples/*.md), and adds explicit output format, limitations, and risk metadata. Crowning one would hide the other's real alternative structure and steps.