CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/sensei/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill has excellent workflow clarity with a well-defined iterative loop, clear validation checkpoints, and strong actionability with concrete commands throughout. However, it suffers significantly from verbosity — key warnings and concepts are repeated multiple times, the ASCII help box duplicates content, and detailed information that belongs in reference files is inlined. The skill would benefit greatly from aggressive deduplication and moving detailed content to its referenced files.

Suggestions

Deduplicate the 'DO NOT USE FOR' risk explanation — it appears three times with nearly identical content. Consolidate into one brief mention with a reference to SCORING.md for details.

Move the detailed scoring criteria table and frontmatter template to SCORING.md, keeping only a one-line summary with a link in the main SKILL.md.

Reduce the ASCII help box to essential usage patterns only, or remove it entirely since the same information is covered in the 'Invocation Modes' and 'The Ralph Loop' sections.

Consolidate the GEPA explanation — it's described in both 'Invocation Modes' and 'The Ralph Loop' step 5b. Keep the detailed explanation in one place only.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~250+ lines. It repeats the same information multiple times (e.g., 'DO NOT USE FOR' risk is explained three separate times with nearly identical content, scoring criteria appears in both the help box and a dedicated section, GEPA is explained in both invocation modes and the loop steps). The large ASCII art help box alone consumes significant tokens. Much of this content could be consolidated or moved to reference files.

1 / 3

Actionability

The skill provides concrete, executable commands throughout: specific CLI invocations ('Run sensei on azure-deploy'), exact bash commands for scaffolding ('cp -r tests/_template tests/{skill-name}'), test commands ('cd tests && npm test -- --testPathPatterns={skill-name}'), GEPA script paths, and commit message formats. The 12-step loop is fully specified with actionable instructions at each step.

3 / 3

Workflow Clarity

The Ralph loop is clearly sequenced with 12 numbered steps, explicit validation checkpoints (step 7: VERIFY tests, step 8: VALIDATE REFERENCES), a feedback loop (step 12: REPEAT, max 5 iterations), clear exit conditions (score >= Medium-High AND tests pass), and a user decision point (Commit, Create Issue, or Skip). The workflow handles both normal and GEPA modes with clear branching.

3 / 3

Progressive Disclosure

The skill references four external files (SCORING.md, LOOP.md, EXAMPLES.md, TOKEN-INTEGRATION.md) which is good progressive disclosure structure, but the main SKILL.md itself contains too much inline detail that should be in those reference files (e.g., the full scoring criteria table, the detailed GEPA explanation, the repeated DO NOT USE FOR warnings). The help box duplicates the loop steps. No bundle files were provided to verify references exist.

2 / 3

Total

9

/

12

Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-structured skill description with excellent trigger term coverage and clear completeness. The explicit WHEN clause with multiple natural trigger phrases and the disambiguation note for single operations are strong points. The main weakness is that the core capability description could be more specific about what concrete actions the skill performs beyond 'iteratively improve frontmatter compliance'.

Suggestions

Add more specific concrete actions to the capability description, e.g., 'validates frontmatter fields, counts tokens, checks compliance scores, suggests fixes, and commits improvements' rather than the abstract 'iteratively improve skill frontmatter compliance'.

DimensionReasoningScore

Specificity

Names the domain (skill frontmatter compliance) and mentions some actions like 'improve', 'audit', 'score', 'check tokens', but doesn't list multiple concrete specific actions in detail — 'iteratively improve skill frontmatter compliance using the Ralph loop pattern' is somewhat abstract.

2 / 3

Completeness

Clearly answers both 'what' (iteratively improve skill frontmatter compliance using the Ralph loop pattern) and 'when' (explicit WHEN clause with trigger phrases). Also includes an INVOKES section and a disambiguation note for single operations.

3 / 3

Trigger Term Quality

Includes a strong set of natural trigger terms that users would actually say: 'run sensei', 'sensei help', 'improve skill', 'fix frontmatter', 'skill compliance', 'frontmatter audit', 'score skill', 'check skill tokens'. These cover multiple natural variations.

3 / 3

Distinctiveness Conflict Risk

Very specific niche — skill frontmatter compliance and the 'Ralph loop pattern' with distinct trigger terms like 'run sensei' and 'sensei help' make this highly unlikely to conflict with other skills. The disambiguation note ('FOR SINGLE OPERATIONS: use token CLI directly') further reduces conflict risk.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/github-copilot-for-azure
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.