CtrlK
BlogDocsLog inGet started
Tessl Logo

pinned-release-checklist

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

48

Quality

51%

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

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.

The body is appropriately lean and well-structured for a deliberately minimal, single-purpose guidance-only skill, with a clear trigger and rationale. Its only real weakness is actionability: it tells Claude when to select the skill but not what a release check concretely involves.

Suggestions

Add one or two concrete examples of a 'release check' scenario so the selection trigger is unambiguous in practice.

Optionally list the inspectable properties (installable, inspectable, explicitly selectable, no model call) as a short bulleted checklist to make the guidance more actionable.

DimensionReasoningScore

Conciseness

The six-line body is lean and assumes Claude's competence, with every line earning its place; the rationale sentence is purposeful rather than padded.

5 / 5

Actionability

It gives a clear selection trigger ("Use this Skill when a release check needs a deterministic guidance-only Skill that can be installed, inspected, and explicitly selected") but lacks concrete examples or specifics of what such a release check entails.

3 / 5

Workflow Clarity

As a single-purpose guidance-only skill the single action (select this skill for deterministic release checks) is unambiguous, but there is no sequencing or checkpoint to push it to a 5.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, the body is well-organized with a clear heading and grouped rationale — the simple-skill exception applies.

5 / 5

Total

17

/

20

Passed

Description

25%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 concise and occupies a distinct niche, but it reads as internal plumbing language: it states a vague category rather than concrete capabilities and omits any natural trigger or "Use when" guidance. It would rarely surface for a real user request.

Suggestions

Rewrite the description in third person with concrete verbs describing what the skill does (e.g., 'Provides a deterministic, no-side-effect checklist for verifying release-pinned compatibility').

Add an explicit 'Use when...' clause with natural trigger phrases such as 'release checks', 'pinned dependency verification', or 'compatibility smoke tests'.

Replace jargon ('guidance-only Skill', 'release-pinned compatibility examples') with user-facing terms so the description is recognizable from a natural query.

DimensionReasoningScore

Specificity

The description names a domain ("guidance-only Skill", "release-pinned compatibility examples") but provides no concrete actions — "Minimal guidance-only Skill used by..." is a category label rather than a verb-driven capability list.

2 / 5

Completeness

It offers only a vague "what" (a minimal guidance-only skill) and no "when"/Use-when clause, so it fails to answer when Claude should invoke it; the missing trigger guidance caps completeness well below the midpoint.

2 / 5

Trigger Term Quality

The phrasing relies on internal plumbing jargon ("guidance-only Skill", "release-pinned compatibility examples") rather than natural terms a user would actually say, offering no recognizable trigger keywords.

1 / 5

Distinctiveness Conflict Risk

The narrow niche (release-pinned compatibility examples, deterministic guidance-only selection) makes it largely distinct with only minor overlap risk against other release-related skills.

4 / 5

Total

9

/

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