CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-reviewer

Review skill PRs with structured severity-rated feedback covering token budgets, routing conflicts, and repo conventions. WHEN: "review skill", "review skill PR", "review skill changes", "check skill quality", "skill PR feedback".

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A well-organized instruction-only skill body with a clear sequenced workflow, concrete error remediation, and excellent progressive disclosure via real reference files. Minor conciseness redundancy from duplicated links and delegated detail keep most dimensions at 4.

Suggestions

Remove the standalone References section or the inline links in the Review Workflow to eliminate the duplicated reference listing and save tokens.

Inline one or two concrete examples of severity classification or a sample finding line so the skill is actionable without always loading a reference.

Add a brief validate→fix→retry note for the Draft/Validate steps (e.g., re-check file/line references when a suggested fix is found to be inaccurate) to strengthen the feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explaining what a PR or skill is), but the four reference links are duplicated between the Review Workflow steps and the References section, a minor redundancy that could be trimmed.

4 / 5

Actionability

Each workflow step points to a specific reference file with concrete remediation in the error table ('Estimate at ~4 chars per token'), giving mostly executable guidance, though detail is delegated to references rather than given inline.

4 / 5

Workflow Clarity

A clear six-step sequence (Collect → Check → Classify → Analyze Routing → Draft → Validate) with an explicit Validate checkpoint and an error-handling table, but no true validate→fix→retry feedback loop (acceptable for a non-destructive review skill).

4 / 5

Progressive Disclosure

SKILL.md is a concise overview pointing to four one-level-deep, clearly signaled reference files (all verified to exist), with content appropriately split and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

95%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.

A strong, well-structured description that explicitly covers what and when with natural trigger phrases and a distinct niche. The only minor gap is that specificity is framed as one review action with broad coverage rather than multiple discrete actions.

DimensionReasoningScore

Specificity

Names the domain ('Review skill PRs with structured severity-rated feedback') and enumerates concrete coverage areas — 'token budgets, routing conflicts, required sections, and repo conventions' — but frames them as scope of a single review action rather than multiple distinct actions, leaving it just short of comprehensive.

4 / 5

Completeness

Clearly answers both 'what' (severity-rated structured feedback on token budgets, routing, sections, conventions) and 'when' via an explicit WHEN clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Five natural trigger phrases users would actually say ('review skill', 'review skill PR', 'review skill changes', 'check skill quality', 'skill PR feedback') give comprehensive coverage with synonyms and phrasing variants.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche — reviewing skill PRs — with distinct skill-specific triggers, giving minimal overlap risk with unrelated skills.

5 / 5

Total

19

/

20

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.

Validation16 / 16 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.