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/example-router-skill.md

Case Study: Router Skill Synthesis

Scenario

Goal: create a skill that classifies requests into distinct downstream paths without overloading one prompt.

Input collection approach

This case collected:

  1. examples of request categories
  2. known ambiguous cases
  3. downstream resources for each route
  4. historical misroutes and their fixes

Collection stopped only after route criteria and fallback behavior were explicit.

Coverage matrix used

Required dimensions tracked during synthesis:

  1. route categories and triggers
  2. ambiguous or overlapping cases
  3. downstream ownership per route
  4. default/fallback path
  5. misroute recovery behavior

Synthesized artifacts produced

The resulting skill references included:

  1. route-selection table
  2. one reference or script per route
  3. ambiguous-case examples
  4. fallback rule for unclear input

What made this high quality

  1. the route table was explicit
  2. every route had one clear downstream owner
  3. the skill knew what to do when classification was uncertain