> skill-writer
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, depth gates, authoring, registration, and validation.
curl "https://skillshub.wtf/getsentry/skills/skill-writer?format=md"Skill Writer
Use this as the single canonical workflow for skill creation and improvement. Primary success condition: maximize high-value input coverage before authoring so the resulting skill has minimal blind spots.
Load only the path(s) required for the task:
| Task | Read |
|---|---|
| Set skill class and required dimensions | references/mode-selection.md |
| Apply writing constraints for depth vs concision | references/design-principles.md |
| Select structure pattern for this skill | references/skill-patterns.md |
| Select workflow orchestration pattern for process-heavy skills | references/workflow-patterns.md |
| Select output format pattern for deterministic quality | references/output-patterns.md |
| Choose workflow path and required outputs | references/mode-selection.md |
| Load representative synthesis examples by skill type | references/examples/*.md |
| Synthesize external/local sources with depth gates | references/synthesis-path.md |
| Author or update SKILL.md and supporting files | references/authoring-path.md |
| Optimize skill description and trigger precision | references/description-optimization.md |
| Iterate using positive/negative/fix examples | references/iteration-path.md |
| Evaluate behavior and compare baseline vs with-skill (opt-in quantitative) | references/evaluation-path.md |
| Register and validate skill changes | references/registration-validation.md |
Step 1: Resolve target and path
- Resolve target skill root and intended operation (
create,update,synthesize,iterate). - Distinguish skill-internal paths from repo registration paths:
- inside a skill, reference bundled files relative to that skill root (for example
references/foo.md,scripts/check.py) - for repository registration edits, use the repository's actual canonical files/locations after inspecting the workspace
- inside a skill, reference bundled files relative to that skill root (for example
- Read
references/mode-selection.mdand select the required path(s). - Classify the skill (
workflow-process,integration-documentation,security-review,skill-authoring,generic). - Ask one direct question if class or depth requirements are ambiguous; otherwise state explicit assumptions.
Step 2: Run synthesis when needed
Read references/synthesis-path.md.
- Collect and score relevant sources with provenance.
- Apply trust and safety rules when ingesting external content.
- Produce source-backed decisions and coverage/gap status.
- Load one or more profiles from
references/examples/*.mdwhen the skill is hybrid. - Enforce baseline source pack for skill-authoring workflows.
- Enforce depth gates before moving to authoring.
Step 3: Run iteration first when improving from outcomes/examples
Read references/iteration-path.md first when selected path includes iteration (for example operation iterate).
- Capture and anonymize examples with provenance.
- Re-evaluate skill behavior against working and holdout slices.
- Propose improvements from positive/negative/fix evidence.
- Carry concrete behavior deltas into authoring.
Skip this step when selected path does not include iteration.
Step 4: Author or update skill artifacts
Read references/authoring-path.md.
- Write or update
SKILL.mdin imperative voice with trigger-rich description. - Create focused reference files and scripts only when justified.
- Follow
references/skill-patterns.md,references/workflow-patterns.md, andreferences/output-patterns.mdfor structure and output determinism. - For authoring/generator skills, include transformed examples in references:
- happy-path
- secure/robust variant
- anti-pattern + corrected version
Step 5: Optimize description quality
Read references/description-optimization.md.
- Validate should-trigger and should-not-trigger query sets.
- Reduce false positives and false negatives with targeted description edits.
- Keep trigger language generic across providers unless the skill is intentionally provider-specific.
Step 6: Evaluate outcomes
Read references/evaluation-path.md.
- Run a lightweight qualitative check by default (recommended).
- For integration/documentation and skill-authoring skills, include the concise depth rubric from
references/evaluation-path.md. - Run deeper eval playbook and quantitative baseline-vs-with-skill only when requested or risk warrants it.
- Record outcomes and unresolved risks.
Step 7: Register and validate
Read references/registration-validation.md.
- Apply repository registration steps for the active layout you verified in the workspace.
- Run quick validation with strict depth gates.
- Reject shallow outputs that fail depth gates or required artifact checks.
Output format
Return:
SummaryChanges MadeValidation ResultsOpen Gaps
> related_skills --same-repo
> skill-creator
Alias for sentry-skills:skill-writer. Use when users explicitly ask for "skill-creator" or reference the legacy skill name. Redirects to the canonical skill authoring workflow.
> security-review
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
> doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
> code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.