CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl/default-skill-review

The default Tessl review rubric. An agentic reviewer that reads a SKILL.md and scores it against rubrics for its description and its content, the same reviewer tessl review uses out of the box. Use it as the reference reviewer to score skills, or as the base to fork a custom rubric from.

68

Quality

86%

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

Overview
Quality
Evals
Security
Files

Quality

Content

82%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 content is a well-structured, highly actionable workflow with concrete commands and exact output schemas. It loses a little on conciseness (minor repetition) and workflow clarity (no explicit validate-fix-retry loop).

Suggestions

Trim the repeated 'Important reminders' section, which restates constraints already covered in Steps 2-5, to tighten conciseness toward a 5.

Add an explicit validation/verification checkpoint in Step 5 (e.g., 'Validate results.json against schemas/results.schema.json before finishing; if invalid, fix and re-validate') to close the workflow-clarity feedback-loop gap.

DimensionReasoningScore

Conciseness

The body is dense and instructional with exact file paths, formulas, and JSON templates; minor repetition in the closing reminders and a few over-explained asides ('Do not load all bundle file contents into memory') keep it just below the lean anchor 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready guidance: concrete shell operations ('List all .json files in ./rubrics/', 'Read ./config.json'), exact scoring formulas, and complete JSON output templates covering the common cases.

5 / 5

Workflow Clarity

A clear five-step sequence (Read → Discover → Run judges → Compute → Write) with an implicit validation checkpoint ('results.json must conform to schemas/results.schema.json'), but no explicit error-recovery feedback loop, so it sits below anchor 5.

4 / 5

Progressive Disclosure

Body is organized into well-signaled sections and points to real one-level-deep references (./rubrics/, ./config.json, schemas/results.schema.json, confirmed present in ./references/), with only minor organization gaps versus the ideal anchor 5.

4 / 5

Total

17

/

20

Passed

Description

83%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 is strong: it clearly states what the skill does and when to use it, with concrete actions and natural trigger phrases. Its only weakness is slight overlap risk with broader review skills and a few missing synonym triggers.

DimensionReasoningScore

Specificity

Names the domain ('Evaluate a SKILL.md for quality') and several concrete actions — 'dynamically discovers the rubric files', 'scores the skill against each', 'producing one result per rubric' — beyond the 1-2 of anchor 3 but with minor coverage gaps versus the fully comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both what ('Evaluate a SKILL.md for quality... scores the skill against each, producing one result per rubric') and when ('Use when running a skill review workflow or testing skill quality against configurable rubrics') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('skill review workflow', 'testing skill quality', 'configurable rubrics', 'SKILL.md') with good coverage, though a few common synonyms/variations are absent.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (rubric-based skill-quality evaluation) with distinct triggers, but minor overlap risk with general code-review or quality-check skills keeps it just below the minimal-conflict anchor 5.

4 / 5

Total

17

/

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.

Reviewed

Table of Contents