CtrlK
BlogDocsLog inGet started
Tessl Logo

pinned-release-checklist

Minimal guidance-only Skill used by release-pinned compatibility examples.

40

Quality

40%

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 ./examples/release_pinned_usage/skills/pinned-release-checklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is lean and well-organized for a deliberately minimal, capability-free skill, earning high conciseness and progressive-disclosure marks. Its weakness is that a skill named 'checklist' provides no actual checklist items or steps, leaving actionability and workflow clarity incomplete.

Suggestions

Add the actual checklist items or concrete install/inspect/select steps so the 'checklist' name is earned and actionability rises above 2.

Include a brief explicit sequence (e.g., install -> inspect -> confirm pinned revision) with a verification checkpoint to lift workflow_clarity toward 3.

DimensionReasoningScore

Conciseness

The ~7-line body is lean and every sentence states a specific fact about the skill (guidance-only, no side effects, exists to prove installation/revision binding) with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It gives a concrete selection trigger ("Use this Skill when a release check needs...that can be installed, inspected, and explicitly selected") and a clear capability boundary, but despite being named a 'checklist' it provides no checklist items or executable steps, so it is 'some concrete guidance but incomplete' rather than fully actionable.

2 / 3

Workflow Clarity

The selection guidance is present, but the skill named 'Pinned Release Checklist' defines no checklist steps or sequence, so the post-selection action is implicit; for a simple skill the single action is not fully unambiguous, capping this at the 'sequence present but checkpoints/steps missing' level.

2 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references (none exist), and is organized into a clear heading plus two coherent paragraphs, meeting the simple-skill allowance of scoring 3 with well-organized sections alone.

3 / 3

Total

10

/

12

Passed

Description

7%

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 identifies the skill as an internal test fixture rather than describing user-facing capabilities: it names no concrete actions, omits any 'Use when...' trigger guidance, and relies on internal jargon no user would naturally say. Distinctiveness is the only dimension above 1, and only because the niche is narrowly internal.

Suggestions

Add concrete actions describing what the skill does (e.g., 'Inspects installed Skills and verifies exact revision binding') to lift specificity above 1.

Add an explicit 'Use when...' trigger clause with natural user-facing vocabulary (e.g., 'Use when verifying that a pinned Skill revision is installed and selectable without a model call') to address the missing 'when' in completeness.

Replace internal jargon ('release-pinned compatibility examples') with terms a user would actually say to improve trigger_term_quality and reduce conflict ambiguity.

DimensionReasoningScore

Specificity

The description is a noun phrase ("Minimal guidance-only Skill used by release-pinned compatibility examples") that names a domain but lists no concrete actions the skill performs, matching the 'vague or no actions' anchor rather than score 2 which requires naming some actions.

1 / 3

Completeness

The 'what' is very weak ("minimal guidance-only Skill" states no capability) and the 'when' is entirely absent with no 'Use when...' clause, matching 'missing what OR when, or both very weak'; the cap-at-2 rule does not rescue it because the 'what' is also near-empty.

1 / 3

Trigger Term Quality

"release-pinned compatibility examples" is internal testing jargon a user would never naturally say, fitting the 'no natural keywords; technical jargon' anchor and falling below score 2 which needs some natural relevant keywords.

1 / 3

Distinctiveness Conflict Risk

The niche is specific enough (release-pinned compatibility) to avoid accidental triggering, but there are no distinct user-facing triggers, so it sits at 'somewhat specific but could overlap' rather than the distinct-trigger bar of score 3.

2 / 3

Total

5

/

12

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
AgentEra/Agently
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.