CtrlK
BlogDocsLog inGet started
Tessl Logo

sensei

Iteratively improve skill frontmatter to achieve good routing test coverage. WHEN: run sensei, sensei help, improve skill routing

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%Weight 40%Scale 1-5

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

The body is well-structured with an explicit, checkpointed loop and good file separation, but the decorative ASCII help box wastes tokens and duplicates the Main Loop. Actionability and workflow clarity are solid; conciseness is the main drag.

Suggestions

Replace the space-padded ASCII box with a compact markdown list; fold the non-duplicated parts of "WHAT IT DOES" into the Main Loop to remove redundancy.

Tighten the TEST step from "suggest fixes" to an explicit apply-and-re-test gate to strengthen the validation checkpoint.

Inline a one-line example of a scaffolded routing test prompt so the SCAFFOLD step is executable without requiring the vally-eval skill lookup.

DimensionReasoningScore

Conciseness

The large ASCII art box uses extensive space padding and its "WHAT IT DOES" section duplicates the Main Loop, making it noticeably padded rather than merely efficient.

2 / 5

Actionability

Concrete file paths like `plugins/{plugin}/skills/{skill-name}/SKILL.md` and `evals/{skill-name}/*.yaml` plus an explicit CONVENTIONS.md reference give mostly executable guidance, with minor gaps from deferring to vally-eval.

4 / 5

Workflow Clarity

Eight clearly sequenced steps include VERIFY and TEST checkpoints plus a REPEAT feedback loop with an iteration cap, though "suggest fixes" is softer than a hard validation gate.

4 / 5

Progressive Disclosure

The body is an overview with detailed conventions split into the real, one-level-deep references/CONVENTIONS.md and vally-eval clearly signaled, giving easy navigation.

5 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

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

The description clearly answers both what and when with concrete WHEN triggers and a distinctive name, but the capability list is narrow and trigger synonyms are limited. It is strong on completeness but could enumerate more concrete actions.

Suggestions

Add 1-2 more concrete actions (e.g., scaffold routing tests, verify frontmatter against conventions) to lift specificity beyond a single stated action.

Broaden trigger coverage with natural synonyms such as "skill routing tests", "fix skill frontmatter", or "skill compliance".

Consider a more distinctive trigger than the generic "improve skill routing" to reduce overlap with general skill-authoring skills.

DimensionReasoningScore

Specificity

"Iteratively improve skill frontmatter to achieve good routing test coverage" names the domain and one concrete action but is not comprehensive, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

It explicitly states what it does (improve skill frontmatter for routing test coverage) and gives concrete WHEN triggers, satisfying both what and when clearly.

5 / 5

Trigger Term Quality

"WHEN: run sensei, sensei help, improve skill routing" provides natural invocation phrases with good coverage, though synonyms/extra variations are missing.

4 / 5

Distinctiveness Conflict Risk

The distinctive name "sensei" and frontmatter/routing niche make it mostly distinct, though "improve skill routing" could overlap with general skill-authoring skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

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.