Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sensei
**WORKFLOW SKILL** — Iteratively improve skill frontmatter compliance using the Ralph loop pattern. WHEN: \"run sensei\", \"sensei help\", \"improve skill\", \"fix frontmatter\", \"skill compliance\", \"frontmatter audit\", \"score skill\", \"check skill tokens\". INVOKES: token counting tools, test runners, git commands. FOR SINGLE OPERATIONS: use token CLI directly for counts/checks.
Passed 15 of 20 test cases with the skill, and 3 of 20 without it.
and 10 more in the full report
13 fixed3 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
In sensei, if frontmatter checks or routing tests keep failing repeatedly for a given skill, what is the maximum number of correction iterations allowed before stopping?
| Checked | Without skill | With skill |
|---|---|---|
| The maximum iteration cap per skill is 5. | Missed | Passed |
The instructions your model reads when the skill loads.
When user says "sensei help" or asks how to use sensei, show this:
╔══════════════════════════════════════════════════════════════════╗
║ SENSEI - Skill Frontmatter Compliance Improver ║
╠══════════════════════════════════════════════════════════════════╣
║ ║
║ USAGE: ║
║ Run sensei on <skill-name> # Single skill ║
║ Run sensei on <skill1>, <skill2>, ... # Multiple skills ║
║ Run sensei on all skills # All skills ║
║ ║
║ EXAMPLES: ║
║ Run sensei on appinsights-instrumentation ║
║ Run sensei on azure-ai, azure-compute ║
║ ║
║ WHAT IT DOES: ║
║ 1. READ - Load skill's SKILL.md and tests ║
║ 2. VERIFY - Compare skill frontmatter with convention ║
║ 3. SCAFFOLD - Create tests from frontmatter if missing ║
║ 4. IMPROVE - Add WHEN: triggers ║
║ 5. TEST - Run tests, fix if needed ║
║ 6. SUMMARY - Show before/after with suggestions ║
║ 7. PROMPT - Ask: Commit, Create Issue, or Skip? ║
║ 8. REPEAT - Until routing tests pass ║
╚══════════════════════════════════════════════════════════════════╝
For each skill, execute this loop until the frontmatter aligns with convention, have thorough routing tests AND routing tests pass:
plugins/{plugin}/skills/{skill-name}/SKILL.md, and vally eval suites in evals/{skill-name}/*.yaml.evals/{skill-name}/ doesn't exist, follow instructions in vally-eval skill to scaffold a set of routing tests. The routing tests test if the skill can be invoked for target user prompts. Generate user prompts that match the target scenario of the skill's description.vally-eval skill to run the routing tests. If there are failed tests, suggest fixes.test cases passed, vs 3 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.