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.

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

This session only. Nothing lands on disk.

SOURCES.md

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

Sources

This file tracks source material synthesized into skill-writer, plus iterative changes over time.

Current source inventory

Source Type Trust tier Retrieved Confidence Contribution Usage constraints Notes
SKILL.md local canonical canonical 2026-05-01 high Baseline orchestration, path model, and runtime contract local active skill root Primary source of current behavior
references/*.md local canonical canonical 2026-05-05 high Detailed path guidance, examples, routed leaf references, and validation requirements local active skill root Flat runtime reference files listed directly from SKILL.md
SPEC.md local canonical canonical 2026-05-05 high Canonical maintenance contract for intent, scope, evidence model, validation, and limitations local active skill root Updated to treat skill-writer as a meta-router
https://agentskills.io/specification external canonical spec canonical 2026-05-01 high Portable skill structure, frontmatter, progressive disclosure, optional directories, and file-reference rules spec-level constraints take precedence over local preferences Cross-agent compatibility baseline
https://agentskills.io/skill-creation/evaluating-skills external official docs canonical 2026-06-30 high Evaluation guidance: run isolated task cases, compare outputs to a baseline, and judge invocation plus output quality skill-authoring evaluation guidance, not a deterministic validator spec Informed EVAL.md
https://platform.openai.com/docs/guides/evals external official docs canonical 2026-06-30 high Behavior-driven eval structure, test inputs, testing criteria, result analysis, and iteration loop Evals platform is deprecated; retain general evaluation principles only Informed EVAL.md
https://platform.openai.com/docs/guides/graders external official docs canonical 2026-06-30 high Deterministic graders, model graders, evidence-bearing grading, smooth scores, and reward-hacking cautions Graders product path is deprecated; retain judge design principles only Informed LLM judge guidance
https://github.com/anthropics/skills/tree/main/skills/skill-creator external official/adjacent skill secondary 2026-06-30 high Skill-eval loop with baseline runs, assertions after first outputs, timing capture, benchmark aggregation, human review, and blind comparison Adapt concepts to this repo's Codex workflow rather than copying Claude-specific mechanics Informed EVAL.md and eval case criteria
https://axis.run/ external eval tooling secondary 2026-06-30 high Open source coding-agent eval harness with scenarios, built-in Codex support, isolated workspaces, judge checks, reports, artifacts, and baselines use for skill evals that must run real coding agents through Codex; avoid custom runners unless AXIS cannot express the case Informed prescriptive eval framework
https://www.promptfoo.dev/docs/providers/openrouter/ external eval tooling secondary 2026-06-30 medium First-class OpenRouter provider syntax and API key/base URL configuration rejected for skill evals because it does not exercise the Codex harness without custom glue Preserved as research provenance only
Codex manual: noninteractive mode, SDK, and Record & Replay external official docs canonical 2026-06-30 high codex exec --json, --output-schema, sandbox, final-message output, SDK orchestration option, and skill recording guidance Codex harness requirements are satisfied through AXIS's Codex adapter for repeatable skill evals Informed AXIS requirement checks
local codex exec --help local tooling canonical 2026-06-30 high Installed CLI flag availability for ephemeral runs, output schemas, and working directory selection local CLI behavior may vary by installed Codex version Cross-checked manual guidance
https://agentskills.io/skill-creation/best-practices external official docs canonical 2026-05-01 high Coherent unit design, moderate detail, progressive disclosure, defaults over menus, validation loops, plan-validate-execute skill-authoring guidance, not provider-specific runtime semantics Informed shape-selection and workflow guidance
https://agentskills.io/skill-creation/using-scripts external official docs canonical 2026-05-01 high Script bundling, non-interactive requirements, --help, structured output, and safe script interfaces script examples are illustrative, adapt to local tooling Informed script-backed workflow requirements
https://code.claude.com/docs/en/skills external official docs canonical 2026-05-01 high Current Claude Code skill lifecycle, frontmatter fields, argument features, context: fork, allowed-tools, and hooks-in-skills support provider-specific; do not generalize to portable Agent Skills behavior Replaced stale local assumptions about Claude-specific fields
https://code.claude.com/docs/en/sub-agents external official docs canonical 2026-05-01 high Automatic delegation, focused subagents, explicit invocation modes, and subagent lifecycle integration provider-specific Informed subagent-fork shape guidance
https://code.claude.com/docs/en/hooks external official docs canonical 2026-05-01 high Hook lifecycle, hooks in skills and agents, async constraints, and security requirements provider-specific and security-sensitive Informed hook-backed shape guidance and safety notes
https://www.anthropic.com/engineering/building-effective-agents external official engineering guidance canonical 2026-05-01 high Simplicity-first design and workflow taxonomy such as prompt chaining, routing, parallelization, and orchestrator-workers conceptual guidance; adapt to skill authoring rather than full app orchestration Core source for execution-shape taxonomy
https://developers.openai.com/api/docs/guides/reasoning-best-practices external official docs canonical 2026-05-01 high Planner/doer distinction, reasoning-vs-GPT model tradeoffs, and avoiding explicit chain-of-thought prompting provider-specific model guidance; use only as general orchestration input unless exact product syntax matters Informed reasoning-model notes
https://openai.com/business/guides-and-resources/a-practical-guide-to-building-ai-agents/ external official guidance canonical 2026-05-01 high Maximize a single agent first, use multi-agent only when needed, manager-vs-handoff split, layered guardrails product-level guidance, not a skills standard Informed simplicity rule and advanced-shape escalation criteria
https://openai.github.io/openai-agents-python/agents/ external official SDK docs canonical 2026-05-01 medium Manager-vs-handoff distinction and structured-output support SDK-specific implementation details Informed router/orchestrator language and contract expectations
https://openai.github.io/openai-agents-python/handoffs/ external official SDK docs canonical 2026-05-01 medium Handoff metadata, input filters, and receiving-agent history control SDK-specific implementation details Informed route/handoff contract guidance
https://huggingface.co/docs/hub/model-cards external documentation pattern secondary 2026-04-26 high Model-card sections for intended use, data, limitations, and reproducibility adapted as documentation prior art, not a skill standard Inspired SPEC.md maintenance contract shape
https://huggingface.co/docs/hub/en/model-card-annotated external documentation pattern secondary 2026-04-26 high Annotated intended-use, out-of-scope, risks, and limitations sections adapted as documentation prior art, not a skill standard Informed SPEC scope and limitations sections
https://cacm.acm.org/research/datasheets-for-datasets/ research/documentation pattern secondary 2026-04-26 high Data provenance, collection, composition, intended use, and maintenance transparency adapted from dataset documentation to skill evidence documentation Informed source/evidence model and privacy rules
https://diataxis.fr/ documentation framework secondary 2026-04-26 high User-need-centered documentation types: tutorial, how-to, reference, explanation adapted as information architecture prior art, not a skill standard Informed reference files as lookup needs rather than topic buckets
https://dita-lang.org/ documentation standard secondary 2026-04-26 high Topic-oriented technical content patterns: task, concept, reference, troubleshooting adapted as documentation architecture prior art Informed reference type table and troubleshooting matrix guidance
https://www.writethedocs.org/guide/writing/docs-principles/ documentation guidance secondary 2026-04-26 medium Documentation should be structured for findability, reuse, and user participation general writing guidance Cross-check for reference architecture usability
AGENTS.md repo convention canonical 2026-05-01 high Repository-specific workflow requirements and registration checklist repository-local policy Registration + validator expectations
README.md repo convention canonical 2026-05-01 high Skill table format and authoring conventions repository-local policy Registration and discoverability source

Decisions

  1. skill-writer is a meta-router: it must choose both a skill class and an execution shape before authoring.
  2. Default to the simplest adequate shape. Advanced mechanics require evidence and an explicit reason simpler shapes were rejected.
  3. Skill class and execution shape are independent axes. Class drives coverage requirements; shape drives runtime mechanics and artifact layout.
  4. SKILL.md remains the orchestration/index layer; references, scripts, assets, hooks, and subagents are leaves selected by that router.
  5. Provider-specific Claude Code features are valuable but not default. Use them only when justified and record portability implications.
  6. Claude-specific frontmatter guidance should track the current code.claude.com/docs/en/skills fields, including when_to_use, arguments, effort, paths, shell, context, agent, and hooks.
  7. Router, parallel/orchestrator, subagent-fork, and hook-backed shapes each require explicit contracts, not just prose.
  8. Hooks are deterministic enforcement and need narrow scope plus security notes because command hooks run with full user permissions.
  9. Multi-agent guidance should distinguish manager/orchestrator, handoff, and isolated subagent execution instead of collapsing them into one pattern.
  10. Reasoning-model guidance is a design option, not a universal default: planner/doer splits are useful when complexity warrants them.
  11. Architectural choices are reviewed qualitatively during authoring, not inferred by validator heuristics.
  12. Reference files remain split by lookup need rather than topic buckets, even as the set of supported shapes expands.
  13. Runtime references stay flat under references/; related leaves use filename prefixes, and every bundled reference is directly discoverable from SKILL.md.
  14. The validator should enforce durable structural guarantees and required fields, but should not hardcode name style, path-portability scans, skill classes, source-coverage schemas, SPEC headings, trigger-quality heuristics, or provider-specific optional frontmatter keys.
  15. skill-writer should default to dense structures such as tables, checklists, templates, and I/O examples, and should cut explanatory prose unless it prevents a concrete mistake.
  16. SKILL.md should stay a thin router; repeated policy belongs in routed references rather than always-loaded step prose.
  17. Validation stays lightweight and structural; qualitative precision remains an authoring judgment.
  18. Missing referenced bundled files are structural failures because they break runtime loading.
  19. Generated skill quality should be evaluated with repo-level repeatable task cases, baseline comparison, and a rubric rather than by adding semantic heuristics to quick_validate.py.
  20. Eval cases for skill-writer itself belong outside runtime SKILL.md routing so they do not affect normal skill use.
  21. The prescriptive default for skill evals is AXIS with agents: ["codex"] when the eval must exercise Codex; AXIS uses the Codex codex exec --json harness while adding scenarios, artifacts, reports, judge checks, and baselines.
  22. Promptfoo is not part of the prescribed skill-eval path; AXIS is the only framework choice for skill evals in this repo.
  23. skill-writer needs runtime guidance for authoring evals for other skills, but its own maintainer eval files must stay out of SKILL.md routing.
  24. Skill evals should combine deterministic assertions with LLM-as-judge for qualitative dimensions and require concrete evidence for every grade.

Coverage matrix

Dimension Coverage status Evidence
SKILL.md vs references placement complete Agent Skills spec, local reference architecture
Reference splitting heuristics complete Agent Skills best practices, Diataxis, DITA, local reference architecture and artifact-layout guidance
Long reference navigation complete local design principles
Source discovery beyond docs complete local synthesis coverage checks, repository history practices
Commit log as source material complete local source-discovery guidance
Positive/negative evidence storage complete local iteration path, prior validation guidance
Skill maintenance specification complete model cards, datasheets, local SPEC.md reference implementation
Shape-selection framework complete Anthropic effective agents, OpenAI practical guide, local execution-shapes guidance
Router/orchestrator patterns complete Anthropic effective agents, OpenAI agent guides, local workflow-mechanics guidance
Current Claude skill frontmatter and lifecycle mechanics complete Claude Code skills docs
Subagent-fork guidance complete Claude Code skills docs, subagents docs
Hook-backed guidance and security constraints complete Claude Code hooks docs
Script-backed workflow design complete Agent Skills using scripts guide
Skill-output evaluation complete Agent Skills evaluating skills guide, local iteration evidence model
Planner/doer reasoning guidance complete OpenAI reasoning best practices
Lookup-oriented reference architecture complete Diataxis user needs, DITA topic types, local reference architecture
Flat reference routing complete local reference architecture, user feedback on generator simplicity

Open gaps

  1. Advanced-shape contracts still rely on author judgment and review rather than deterministic validation.
  2. This repository still has few real shipped examples using hooks, context: fork, when_to_use, arguments, paths, or effort.
  3. Public repo docs outside skill-writer may need follow-up updates to fully reflect the current Claude-specific skill fields.
  4. The initial skill-writer eval cases are synthetic; they should be replaced or expanded with real generated-output regressions over time.
  5. AXIS is now the eval harness, but the initial scenarios are still synthetic and should be calibrated against real generated-output regressions.

Changelog

  • 2026-03-05: Initialized SOURCES.md with baseline source pack (local canonical, Codex upstream, Claude upstream, spec, and repo conventions).
  • 2026-03-19: Clarified path-resolution guidance so bundled skill references stay skill-root-relative while registration steps are resolved from the repository's active layout.
  • 2026-03-19: Made portability a default authoring rule and emphasized avoiding host-specific absolute filesystem paths.
  • 2026-04-19: Updated path guidance to preserve repository-standard root variables such as ${CLAUDE_SKILL_ROOT} instead of banning them outright.
  • 2026-05-09: Replaced ${CLAUDE_SKILL_ROOT} guidance with skill-root-relative paths. Environment variable path prefixes cause permission friction and runtime failures in Claude Code.
  • 2026-04-19: Restored .agents/skills as the default authoring target and kept repository-specific layouts as an inspected override rather than the default.
  • 2026-04-19: Added explicit prior-art inspection and user-confirmation guidance when the correct skill root is unclear.
  • 2026-04-26: Added reference architecture, source discovery, and iteration evidence guidance; updated synthesis, authoring, and iteration paths to prevent overloaded SKILL.md and catch-all reference files.
  • 2026-04-26: Added SPEC.md as the canonical skill-writer maintenance specification and added references/spec-template.md for future skills.
  • 2026-04-26: Removed fixed integration reference filename validation and added length-based reference warnings.
  • 2026-04-26: Reworked reference architecture around concrete lookup needs instead of generic topic buckets.
  • 2026-05-01: Reworked skill-writer around explicit execution-shape routing, added shape-specific example profiles, refreshed Claude Code provider mechanics from current official docs, and added source guidance for routing, delegation, and hooks.
  • 2026-05-01: Replaced generic pattern bucket references with routed leaf files and made SKILL.md enumerate every bundled reference file with a direct open-when reason.
  • 2026-05-01: Removed the validator's hardcoded optional frontmatter allowlist so provider-specific field drift does not create noisy false warnings.
  • 2026-05-01: Reduced prose-heavy guidance in skill-writer, rewrote the main runtime refs into denser tables/checklists, and made compact runtime guidance an explicit contract.
  • 2026-05-01: Thinned SKILL.md back toward a true router and removed duplicated execution-shape detail from mode-selection.md.
  • 2026-05-05: Flattened runtime reference files under references/, kept SKILL.md as the complete material index, removed unused runbooks, added source-adaptation guidance, and made precision passes part of every skill create/update flow while keeping validation lightweight.
  • 2026-05-05: Removed validator skill-class inference, integration coverage parsing, SPEC heading checks, SOURCES schema checks, and description-style heuristics.
  • 2026-05-05: Removed validator name-style checks and machine-specific path scanning; kept only format, required fields, directory-name match, referenced-file existence, and a high-threshold size warning.
  • 2026-06-30: Added skills/skill-writer/EVAL.md, evals/axis.config.json, and AXIS scenarios with baseline comparison guidance, working/holdout cases, artifact capture, judge checks, and semantic grading that stays out of the structural validator and runtime SKILL.md.
  • 2026-06-30: Replaced framework-first and custom-runner eval guidance with AXIS as the prescriptive open source skill-eval harness. AXIS satisfies the Codex-harness requirement through its built-in codex adapter while adding reports, artifacts, transcripts, and baselines.
  • 2026-06-30: Added references/skill-evals.md so skill-writer can author skill-specific eval playbooks and cases without routing its own maintainer evals.

Source: SKILL.md on GitHub

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

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
  • Documentation
  • skill-authoring
  • workflow
  • specification
  • synthesis
  • iteration
  • validation
  • prompt-engineering
  • agent-skills

README badge

README badge for getsentry/skills/skill-writer

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.

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.