AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

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, precision passes, authoring, registration, and validation.

Original source
getsentry
License
Apache-2.0
Pinned revision
d12f250460ffd961f549dbebf7eeb0cf4afd4c2e

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read getsentry--skill-writer at revision d12f250460ffd961f549dbebf7eeb0cf4afd4c2e, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 41

references/iteration-path.md

Iteration Path

Use this path when improving a skill based on outcomes and examples.

Example intake

Read references/iteration-evidence.md when examples should be persisted across future skill revisions.

Capture example records with:

  • label (positive or negative)
  • example kind (true-positive, false-positive, fix, regression, edge-case)
  • evidence origin (human-verified, mixed, synthetic)
  • anonymized content
  • source provenance pointer (where the example came from)

Replay and Review

  1. Review behavior against working set.
  2. Review behavior against holdout set.
  3. Record improved/unchanged/regressed outcomes.
  4. Confirm both positive and negative behavior changed in the expected direction.

Improvement rules

  1. Prioritize fixes for repeated negative patterns.
  2. Preserve behavior that consistently succeeds on positives.
  3. Update transformed examples when guidance changes.
  4. Record deltas in SOURCES.md changelog.
  5. Expand input collection when failures indicate coverage gaps.
  6. Store durable positive/negative examples in references/evidence/ instead of overloading SKILL.md, SOURCES.md, or a generic reference file.
  7. Keep holdout examples separate from working examples until validation is complete.
  8. Update SPEC.md when iteration changes the skill's intended scope, evidence model, validation expectations, or known limitations.

Required output

  • Example intake summary
  • Behavior deltas
  • Updated artifacts
  • Replay summary