dispatch-authoringlisted

Matcher-aware authoring and troubleshooting knowledge for the full dispatch authoring surface — trigger frontmatter, applicable_agents, applicable_skills, routable, and description: phrase-matching. Loaded by any agent (router, code-writer, doc-writer, project-planner, etc.) when the user wants to write, improve, troubleshoot, or understand dispatch configuration. Trigger this skill whenever the user types /dispatch-authoring, asks "how do I write triggers", "how do I make frontmatter for my agent", "what's a good keyword weight", "set up triggers", or says "my agent isn't being dispatched", "this skill never matches", "my frontmatter isn't working", "dispatch isn't picking up", or similar authoring or troubleshooting requests around dispatch configuration. Covers the matcher's seven-decision ladder, scoring math, weight ladder {0.25, 0.5, 1.0}, symmetric Porter2 stemming and the no_stem opt-out, fnmatch path-glob footguns, conflict-pair detection, and the audit-catalog CLI pointer.
glitchwerks/claude-wayfinder · ★ 1 · AI & Automation · score 67

Install: claude install-skill glitchwerks/claude-wayfinder

# Frontmatter Authoring Guide This skill covers everything you need to write, improve, and troubleshoot trigger frontmatter for claude-wayfinder agents and skills. It explains what fields the matcher reads, how scoring works, the seven routing decisions the matcher can produce, and the most common mistakes that cause an entry to match poorly or never match at all. --- ## 1. What the Matcher Consumes ### Source precedence The catalog generator accepts trigger configuration from two places: inline frontmatter inside the agent or skill file itself, and a **sidecar file** placed next to the main file. The sidecar always wins when both are present. The current sidecar format is **v6**. Under v6: - A **skill** stores its trigger configuration in a file named `triggers.yml` placed in the same directory as `SKILL.md`: ``` skills/python/SKILL.md skills/python/triggers.yml ← authoritative trigger config ``` Per issue #150, a colocated `<name>.triggers.yml` next to `SKILL.md` (owned and project agent sidecars) overrides inline frontmatter. The `SKILL.md` file itself should not contain `triggers:`, `applicable_agents:`, or `applicable_skills:` keys; the generator emits a warning and ignores them if they appear there. - A **plugin-shipped agent** stores its trigger override at `triggers/<plugin>/agents/<name>.yml` (per issue #142). This file activates a dormant plugin agent that would otherwise score zero. For the canonical field reference see `docs/sc