CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conditional-resource-guide

Choose supporting materials for release preparation and incident analysis.

Quality

76%

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/conditional-resource-guide/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 a tightly written conditional resource guide that cleanly maps each phase to a specific, real reference file and splits detail into one-level-deep bundle files. It is lean, well-structured, and unambiguous, with only minor abstraction in the defer-reading line.

DimensionReasoningScore

Conciseness

The four-line body is lean and efficient, assumes Claude knows what release handoffs and incident investigations are, and adds no concept padding; every line advances the conditional-reading guidance.

5 / 5

Actionability

Concrete, executable file-per-phase instructions ('read references/primary.md before drafting the handoff', 'read references/secondary.md instead') cover the common cases, but the 'defer detailed reading' line is slightly more abstract than a direct file directive.

4 / 5

Workflow Clarity

This is a simple, non-destructive conditional-selection skill where the single action is unambiguous across three mapped cases (handoff -> primary, incident -> secondary, outline -> neither), satisfying the simple-skill exception without needing validation checkpoints.

5 / 5

Progressive Disclosure

The body is a clear overview that signals one-level-deep references to the verified, existing files references/primary.md and references/secondary.md, with detailed checklist content appropriately split into those files.

5 / 5

Total

19

/

20

Passed

Description

48%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 names its two target domains and a clear action, but the action is generic and it lacks an explicit 'Use when...' trigger, capping completeness and trigger coverage. It is reasonably distinct but would benefit from concrete trigger phrases.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers, e.g. 'Use when preparing a release handoff or investigating an incident.'

Replace the generic verb 'Choose supporting materials' with specific actions like 'Select and read the matching checklist for release handoffs or incident investigations.'

Include natural synonyms users might say, such as 'release handoff', 'incident response', or 'postmortem', to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The verb 'Choose supporting materials' is a single, generic action even though two domains ('release preparation', 'incident analysis') are named, matching the anchor where the domain is named but actions are minimal or generic.

2 / 5

Completeness

The 'what' is clear (choose supporting materials for two named scenarios) but there is no explicit 'Use when...' trigger clause, so 'when' is only weakly implied and completeness is capped at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

'release preparation' and 'incident analysis' are relevant natural keywords, but common synonyms and variations (e.g., 'release handoff', 'incident response', 'postmortem') are missing.

3 / 5

Distinctiveness Conflict Risk

The two named scenarios give the skill a clear niche with mostly distinct triggers, though the generic action 'Choose supporting materials' leaves minor overlap risk with related release/incident skills.

4 / 5

Total

12

/

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/conditional-resource-guide/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.