skilld
All skills
getsentry avatar

/skill-writer

@5a64b36 official
by Sentrygetsentry/skills1k stars
53

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/getsentry/skills/skill-writer

This session only. Nothing lands on disk.

referencesexample-router-skill.md

≈260 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Case Study: Router Skill Synthesis

Scenario

Goal: create a skill that classifies requests into distinct downstream paths without overloading one prompt.

Input collection approach

This case collected:

  1. examples of request categories
  2. known ambiguous cases
  3. downstream resources for each route
  4. historical misroutes and their fixes

Collection stopped only after route criteria and fallback behavior were explicit.

Coverage matrix used

Required dimensions tracked during synthesis:

  1. route categories and triggers
  2. ambiguous or overlapping cases
  3. downstream ownership per route
  4. default/fallback path
  5. misroute recovery behavior

Synthesized artifacts produced

The resulting skill references included:

  1. route-selection table
  2. one reference or script per route
  3. ambiguous-case examples
  4. fallback rule for unclear input

What made this high quality

  1. the route table was explicit
  2. every route had one clear downstream owner
  3. the skill knew what to do when classification was uncertain

Source: SKILL.md on GitHub

Third-party checks

No alerts17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    The skill is a comprehensive meta-router and workflow guide for creating, updating, and evaluating agent skills. It includes a helper python script for structural validation and standard markdown templates, presenting no security risks.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer7mo

    5/19 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 5a64b36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 months ago

Topics

  • Documentation
  • skill-authoring
  • workflow
  • specification
  • synthesis
  • iteration
  • validation
  • prompt-engineering
  • agent-skills

README badge

README badge for getsentry/skills/skill-writer

What it does

Guides AI agents through a structured workflow for creating, updating, and iterating on agent skills—instruction files that extend AI coding capabilities. Includes reference files for synthesis, authoring, validation, and skill registration following the Agent Skills specification.

Generated from the current SKILL.md.

Frequently asked

Does this skill help me write skills for Claude, or does it help Claude write skills?
This skill is loaded into Claude or another AI coding agent. It provides the agent with a standardized workflow, reference files, and decision trees for creating, updating, and iterating on skills that other agents can use.
What's the difference between create, update, synthesize, and iterate modes?
Create starts from scratch. Update modifies an existing skill. Synthesize gathers and structures source material before authoring. Iterate improves a skill based on positive, negative, or fix examples.
Do I need to read all the reference files?
No. The skill uses a step-by-step workflow that loads only the specific reference files needed for your operation. Start with mode-selection.md to determine your path, then load only the files it directs you to.
Can I use this skill to write skills for other AI providers, or only Claude?
The skill supports both provider-agnostic skills and Claude-specific mechanics. Provider-specific references are optional; the core workflow and execution shapes are portable across agents.
What does a completed skill output look like?
A skill consists of a SKILL.md file (the runtime router), optional focused reference files under references/, a SPEC.md for the maintenance contract, and optional scripts or templates. The skill-writer guides you through all artifact types and decides what belongs in each.

Generated from the current SKILL.md. These answers refresh after source changes.