CtrlK
BlogDocsLog inGet started
Tessl Logo

review-skill-instruction-integrity

Review a change to an agent-facing skill for whether an agent following it reaches the outcome the skill describes. Use as one lens in a code review run.

63

Quality

74%

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 ./review-lenses/review-skill-instruction-integrity/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a tight, well-structured instruction lens with no padding and clear scope/threshold/reporting sections. It is actionable and well-sequenced, falling just short of full marks only on the absence of a worked defect example and explicit validation loops.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — 'A skill is executable instruction. An agent reads it and acts, with no author to ask.' — with no padding or explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

It gives concrete, executable procedure ('Start from what the change asserts, then find every other place the same skill speaks about it') and a specific reporting format, but lacks a worked example of an actual defect, leaving a minor gap versus fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

The Method section lays out a clear ordered sequence (assertions → cross-references → follow as agent → check each step) and the Threshold section acts as a report/don't-report decision checklist, but there are no explicit validation feedback loops, fitting the 4 anchor.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and no need for external references, the body is well-organized into clearly labeled sections (Scope, Method, Threshold, Reporting), meeting the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

62%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 states what the skill does and gives an explicit use context, with a distinct niche. It is somewhat limited on trigger-term variety and lists only one concrete action, which keeps it mid-range rather than top.

Suggestions

Add concrete trigger phrases users would naturally say (e.g. 'Use when reviewing a skill change, auditing agent instructions, or checking that a skill still does what it claims').

Expand the 'what' with one or two more specific actions (e.g. 'finds contradictions, substituted outcomes, and unprovable claims') to lift specificity.

DimensionReasoningScore

Specificity

It names the domain ('Review a change to an agent-facing skill') and one concrete action ('whether an agent following it reaches the outcome the skill describes'), but lists only a single action rather than several, matching the 1-2 concrete actions anchor rather than the comprehensive 4-5.

3 / 5

Completeness

Both 'what' (review a skill change for outcome integrity) and 'when' ('Use as one lens in a code review run') are present; the when-clause is explicit but could be more specific with concrete trigger phrases, matching the 4 anchor.

4 / 5

Trigger Term Quality

Relevant keywords appear ('review', 'skill', 'code review run'), but natural user phrasings and synonyms are limited and lack common variations a user would actually say, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct (instruction-integrity review of agent-facing skills) with minor overlap risk against other code-review lenses, fitting 'mostly distinct; minor overlap risk' rather than the fully conflict-free 5.

4 / 5

Total

14

/

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
tesslio/product-plugins
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.