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/layout-reference-backed-skill.md

Reference-Backed Skill Layout

Use this layout when the skill needs deep knowledge, but most runs only need one branch or subset of that knowledge.

Choose this layout when

  • SKILL.md can act as a router
  • bundled references can stay focused by lookup need
  • the complexity is optional knowledge, not heavy automation

File layout

my-skill/
├── SKILL.md
└── references/
    ├── focused-topic-a.md
    ├── focused-topic-b.md
    └── troubleshooting.md

Keep reference files as direct children of references/. For related variant-specific leaves, use a shared filename prefix and list each file directly from SKILL.md.

Required contract

  1. SKILL.md tells the agent exactly when to open each reference.
  2. Reference filenames predict their contents.
  3. No reference mixes routing, troubleshooting, examples, and source notes without a clear reason.
  4. Large references include navigation or are split further.
  5. Runtime references stay flat unless there is a non-runtime evidence or asset reason to use a subfolder.

Avoid this layout when

  • the skill is small enough to stay inline
  • scripts or validators are central to execution
  • the references would only exist as vague topic buckets