CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

79%

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.

An exemplarily lean instruction-only skill: a clear scope taxonomy, a sequenced review method, explicit report/don't-report thresholds, and a concrete reporting format. The only meaningful gap is the absence of a worked example showing one finding in the prescribed reporting format.

DimensionReasoningScore

Conciseness

The body is lean with no padding and no explanation of concepts Claude already knows; every section (Scope, Method, Threshold, Reporting) carries distinct operational weight, matching the 'every token earns its place' anchor.

5 / 5

Actionability

The guidance is concrete for an instruction-only skill: four named defect categories ("Internal agreement", "Substituted outcomes", etc.), a sequenced method, and a reporting format ("Name the instruction ... Quote the statement it disagrees with, and its file"). It stops short of the 5 anchor because no worked example of a finding is given to anchor the reporting format.

4 / 5

Workflow Clarity

The Method section sequences the review clearly ("Start from what the change asserts ... Then follow the changed instruction as an agent would, in order") and the Threshold section supplies explicit include/exclude checkpoints plus a boundary handoff to "Copyable Snippets". It lacks the explicit validation/feedback loop of the 5 anchor, though no destructive-operation cap applies.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references; its four well-organized sections (Scope, Method, Threshold, Reporting) fully satisfy the simple-skill exception for a top progressive-disclosure 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.

A concise, third-person description with an explicit when-clause and a well-defined niche. Its main weakness is trigger coverage: it uses one narrow invocation phrase and few natural synonyms, and it names only one concrete action rather than enumerating the review's capabilities.

Suggestions

Enumerate the concrete checks the review performs (e.g., contradictions between statements, fallbacks that substitute outcomes, unprovable claims, unreferenced bundle files) so the 'what' is more than a single action.

Broaden the when-clause with natural trigger phrases users would actually say, e.g., "Use when reviewing or editing a SKILL.md, changing skill instructions, or auditing whether a skill does what it claims."

Add synonymous trigger terms such as "skill instructions", "SKILL.md change", or "instruction integrity" to reduce missed invocations.

DimensionReasoningScore

Specificity

The description names its domain ("agent-facing skill", "code review") and one concrete action ("Review a change ... for whether an agent following it reaches the outcome the skill describes"), but does not list several distinct actions, matching the '1-2 concrete actions, not comprehensive' anchor rather than the more comprehensive 4 or 5 anchors.

3 / 5

Completeness

Both parts are explicitly present: what ("Review a change to an agent-facing skill for whether an agent following it reaches the outcome the skill describes") and when ("Use as one lens in a code review run"). The when-clause is explicit but narrow and could carry more concrete trigger phrasing, so it sits at anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Relevant keywords are present ("review", "change", "skill", "code review run"), but common natural variations a user might say (e.g., "check a skill", "skill instructions wrong", "does my skill work") are missing, which fits the 'some relevant keywords but missing common variations' anchor better than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

The niche is clear (instruction integrity of agent-facing skills within code review) with mostly distinct triggers; minor overlap risk remains because "code review run" is a broad phrase that could match generic review requests, so it does not reach the minimal-conflict 5 anchor.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tesslio/product-plugins

Path

review-lenses/review-skill-instruction-integrity/SKILL.md

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.