sensei

Audit and improve SKILL.md frontmatter to prevent routing conflicts.

2|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/PlagueHO/plagueho.learn --skill sensei-plagueho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sensei
Source: https://github.com/PlagueHO/plagueho.learn/tree/main/.github/skills/sensei
Command: npx skills add https://github.com/PlagueHO/plagueho.learn --skill sensei-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Frontmatter quality is essential for reliable skill routing; many skills ship with short, non-specific descriptions and missing triggers that cause misrouting. Sensei audits SKILL.md and iteratively improves frontmatter using a Ralph loop to reduce collisions.

Core Features & Use Cases

  • Iterative frontmatter improvement: read, score, scaffold tests, improve frontmatter, verify, and repeat until Medium-High.
  • Supports explicit triggers (WHEN:, USE FOR:), anti-triggers (DO NOT USE FOR:), and routing cues (INVOKES:, FOR SINGLE OPERATIONS:).
  • Token-budget aware; keeps SKILL.md lean; scaffolds test frameworks when needed; documents MCP integration points.
  • Suitable for teams shipping multiple skills with overlapping domains.

Quick Start

Run Sensei on your skill to start the Ralph loop and iteratively improve its frontmatter.

Frequently Asked Questions about sensei

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent skill routing collisions and misactivations in SKILL.md?

To prevent skill routing collisions, you must improve frontmatter quality with explicit triggers, anti-triggers, and routing cues. Sensei audits SKILL.md files and iteratively refines these metadata fields to eliminate misrouting.

How does the Ralph loop improve skill frontmatter iteratively?

The Ralph loop improves skill frontmatter by cycling through up to five iterations of reading, scoring, scaffolding missing tests, improving triggers, and verifying results until the frontmatter reaches a Medium-High quality score.

What frontmatter fields are needed to avoid overlapping skill activations?

To avoid overlapping activations, frontmatter needs explicit triggers like WHEN: and USE FOR:, anti-triggers like DO NOT USE FOR:, and routing cues like INVOKES: and FOR SINGLE OPERATIONS: to precisely define routing boundaries.

How do I keep SKILL.md files lean while improving trigger specificity?

You keep SKILL.md files lean by enforcing token budgets during frontmatter evaluation. Sensei analyzes triggers and routing cues while maintaining a strict token budget to prevent file bloat during the improvement process.

Can I automate frontmatter evaluation for teams shipping multiple skills?

Yes, you can automate frontmatter evaluation for teams shipping multiple skills with overlapping domains. Sensei reads each SKILL.md, scaffolds test frameworks when missing, and reports before and after results for review.

What should I do when my skill tests are missing during frontmatter improvement?

When skill tests are missing during frontmatter improvement, the evaluation loop scaffolds the necessary test frameworks automatically. This ensures that routing changes are verified before the iterative cycle completes.