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-hook-backed-skill.md

Case Study: Hook-Backed Skill Synthesis

Scenario

Goal: create a skill that enforces a deterministic check at a specific lifecycle or tool boundary.

Input collection approach

This case collected:

  1. official hook lifecycle and schema docs
  2. security guidance for shell-executed hooks
  3. examples of narrow matchers vs over-broad hooks
  4. fallback behavior for environments without hooks

Coverage matrix used

Required dimensions tracked during synthesis:

  1. event and matcher scope
  2. decision behavior
  3. security boundaries
  4. fallback behavior
  5. portability constraints

Synthesized artifacts produced

The resulting skill references included:

  1. hook configuration example
  2. safety checklist
  3. fallback path without hooks
  4. anti-pattern showing over-broad or unsafe hook scope

What made this high quality

  1. the hook scope was narrow and auditable
  2. security assumptions were explicit
  3. the skill still described what to do when hooks were unavailable