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/reference-architecture.md

Reference Architecture

Use this guide before adding bundled files or long sections to SKILL.md.

Router Rule

  • SKILL.md is the router.
  • References are flat lookup leaves under references/.
  • SPEC.md is the maintenance contract.
  • SOURCES.md stores provenance and decisions.

Lookup Test

Before creating a reference, finish this sentence:

  • "I need to decide X, so read ...."
  • "I need to do Y, so read ...."
  • "I need to diagnose Z, so read ...."

If the sentence sounds like "I need context" or "I need patterns", the file is too vague.

Placement Table

| Put it in... | When it belongs there | |--------------|-----------------------| | SKILL.md | every run needs it | | references/ | only some branches need it; keep runtime references as direct children | | SPEC.md | it explains maintenance, scope, or evidence policy | | SOURCES.md | it is provenance, a decision record, or a gap |

Reference Types

| Need | Shape | |------|-------| | choose a path | decision guide | | execute a procedure | task guide | | look up exact facts | reference table | | diagnose a failure | troubleshooting matrix | | imitate quality | example set | | judge completeness | validation checklist |

Naming Rules

  • Name files for the question or action they answer.
  • Good: mode-selection.md, output-contracts.md, routing-workflows.md
  • Bad: notes.md, context.md, patterns.md, research.md
  • Prefer flat filenames over nested reference folders.
  • When related references cover parallel variants of one lookup need, keep them as sibling files with a shared prefix plus an explicit differentiator.
  • List every runtime reference directly in SKILL.md.

Split Rules

Create a new reference when:

  • the content is only needed after a branch decision
  • the content has one dominant type
  • the section would make SKILL.md harder to scan
  • the file is approaching 100 lines and contains multiple lookup needs
  • the resulting file can be named as a direct child of references/ with a clear lookup reason

Keep content in SKILL.md when:

  • every invocation needs it
  • it is short
  • moving it would force unnecessary file loads

Final Checks

  1. Every runtime reference has a direct "open when..." reason in SKILL.md.
  2. The filename tells the agent why to open it.
  3. No required instruction is hidden only in an optional reference.
  4. No reference has become a second SKILL.md.
  5. No nested reference folder is introduced unless the content is non-runtime evidence or static assets.