CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

script-release-probe

Run an isolated release-component probe and report only its observed evidence.

Quality

78%

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/skills_executor/skills/script-release-probe/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an efficient, actionable, single-purpose instruction with a real bundle reference and an explicit validation guardrail. The only minor gap is the slightly abstract invocation phrasing in lieu of a full command.

DimensionReasoningScore

Conciseness

The body is lean (~7 lines), assumes Claude's competence, and does not explain concepts Claude already knows; every token earns its place. Not below 5 because there is no padding or over-explanation.

5 / 5

Actionability

It names the concrete script path (scripts/release_probe.py), the required args (--release, --component), and the expected JSON output, but the invocation mechanism ('through the available Skill script execution Action') is slightly abstract with no full copy-paste command. Not a 5 due to that minor gap.

4 / 5

Workflow Clarity

As a simple single-action skill the action is unambiguous, and it includes an explicit validation checkpoint ('Do not invent the token or claim success without a successful Action result'). Meets the simple-skill exception for a 5.

5 / 5

Progressive Disclosure

Under 50 lines, well-organized with a clear header, and the single bundle reference (scripts/release_probe.py) is one level deep and resolves to a real file. Meets the under-50-lines exception for a 5.

5 / 5

Total

19

/

20

Passed

Description

53%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 names a distinct niche, but it omits any explicit 'when to use' guidance, which caps completeness and limits trigger discoverability. It reads as a clear capability statement rather than a complete trigger description.

Suggestions

Add an explicit 'Use when…' clause naming the natural trigger phrases (e.g., 'Use when probing a release component for observed evidence, or when the task asks to run a release-component probe').

Include common user-facing synonyms or phrasings alongside the jargon (e.g., 'release check', 'component verification') to improve trigger_term_quality.

Optionally list one more concrete action (e.g., what the probe inspects) to lift specificity from a single action toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('release-component probe') and one concrete action ('Run…probe and report…observed evidence'), but coverage is not comprehensive. Not a 2 (it is more than a generic domain label) and not a 4 (only a single action is listed).

3 / 5

Completeness

It gives a clear 'what' (run an isolated probe and report evidence) but no 'Use when…' or equivalent trigger guidance, so completeness is capped at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Terms like 'release', 'component', 'probe', and 'evidence' are relevant but jargon-heavy, and common user-facing variations or synonyms are missing. Not a 2 because the keywords are domain-relevant rather than fully generic.

3 / 5

Distinctiveness Conflict Risk

'release-component probe' is a distinct niche with minimal conflict risk. Not a 5 because the trigger context is not explicit, leaving minor overlap risk with neighboring release-engineering skills.

4 / 5

Total

13

/

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

AgentEra/Agently

Path

examples/skills_executor/skills/script-release-probe/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.