Explore: Create a failure-mode-to-skill index #73

Closed
opened 2026-07-08 11:55:00 -04:00 by jasper · 0 comments
Contributor

This repo has 30+ skills covering a broad range of domains and capabilities. The hardest part of using them isn't executing any single skill — it's knowing which one to reach for. There's currently no lightweight index that maps situations, pain signals, or problem types to the right skill.

Pocock has ask-matt, a dedicated router skill. Rather than a full router (which would add complexity), a simple failure-mode-to-skill index table could help an agent navigate the collection.

What to explore

  1. What the index should look like — a markdown file with columns: problem pattern / signs / load this skill
  2. Whether this should be a standalone reference file or embedded in an existing skill
  3. How to handle skills that apply to multiple problem patterns
  4. Whether the index should be agent-facing only or user-facing too
  5. How to maintain it as new skills are added — a CLAUDE.md rule similar to Pocock's ask-matt maintenance rule?
  6. Whether this overlaps with the specialist-delegation skill in the Hermes workflow

Relationship to existing work

The specialist-delegation skill already maps problem types to Hermes profiles. This index would be the agent-skills equivalent — mapping problem types to skills in this repo.

This repo has 30+ skills covering a broad range of domains and capabilities. The hardest part of using them isn't executing any single skill — it's knowing which one to reach for. There's currently no lightweight index that maps situations, pain signals, or problem types to the right skill. Pocock has ask-matt, a dedicated router skill. Rather than a full router (which would add complexity), a simple failure-mode-to-skill index table could help an agent navigate the collection. ## What to explore 1. What the index should look like — a markdown file with columns: problem pattern / signs / load this skill 2. Whether this should be a standalone reference file or embedded in an existing skill 3. How to handle skills that apply to multiple problem patterns 4. Whether the index should be agent-facing only or user-facing too 5. How to maintain it as new skills are added — a CLAUDE.md rule similar to Pocock's ask-matt maintenance rule? 6. Whether this overlaps with the specialist-delegation skill in the Hermes workflow ## Relationship to existing work The specialist-delegation skill already maps problem types to Hermes profiles. This index would be the agent-skills equivalent — mapping problem types to skills in this repo.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
magnus/agent-skills#73
No description provided.