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/spec-template.md

SPEC.md Template

Use this guide to create or update a root-level SPEC.md.

Use SPEC.md For

  • intent
  • scope
  • trigger context
  • evidence model
  • validation expectations
  • limitations
  • maintenance rules

Do not put runtime instructions or full provenance tables here.

Update SPEC.md When

  • intent or scope changes
  • trigger strategy changes
  • evidence sources or storage policy changes
  • reference architecture changes
  • validation gates change
  • privacy, security, or data-handling assumptions change

For tiny wording-only fixes, update SOURCES.md changelog instead.

Relationship To Other Files

| File | Purpose | |------|---------| | SKILL.md | runtime activation and execution | | SPEC.md | maintenance contract | | SOURCES.md | source inventory, decisions, gaps, changelog | | references/ | runtime-loadable depth | | references/evidence/ | persistent iteration examples |

Template

# <Skill Name> Specification

## Intent

<1-2 short paragraphs>

## Scope

In scope:
- ...

Out of scope:
- ...

## Users And Trigger Context

- Primary users:
- Common user requests:
- Should not trigger for:

## Runtime Contract

- Required first actions:
- Required outputs:
- Non-negotiable constraints:
- Expected bundled files loaded at runtime:

## Source And Evidence Model

Authoritative sources:
- ...

Useful improvement sources:
- positive examples:
- negative examples:
- commit logs/changelogs:
- issue or PR feedback:
- validation results:

Data that must not be stored:
- secrets
- customer data
- private URLs or identifiers not needed for reproduction

## Reference Architecture

- `SKILL.md` contains:
- `references/` contains:
- `references/evidence/` contains:
- `scripts/` contains:
- `assets/` contains:

## Validation

- Lightweight validation:
- Deeper validation:
- Holdout examples:
- Acceptance gates:

## Known Limitations

- ...

## Maintenance Notes

- When to update `SKILL.md`:
- When to update `SOURCES.md`:
- When to update `references/evidence/`:

Design Rules

  1. Keep SPEC.md concise.
  2. Link to SOURCES.md or refs instead of duplicating them.
  3. Keep raw examples in references/evidence/.
  4. Keep sensitive data redacted.