CtrlK
BlogDocsLog inGet started
Tessl Logo

triage

Review file-based todo findings into ready, skipped, customized, or blocked states. Use this skill when pending todo files need approval.

64

Quality

77%

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 ./Skills/agent-ops/triage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, mostly lean process skill with a clear sequenced workflow and fail-fast validation loop. The main weakness is progressive disclosure: the body references an archived path absent from the bundle and never links the bundle files that actually exist.

Suggestions

Deduplicate the Avoid and Anti-Patterns sections, which repeat the same three bullets verbatim, to recover token budget.

Reference the real bundle files (contract.yaml, evals.yaml, task-profile.json) from the body, or correct the archived-context path so signaled references resolve to existing files.

Make validation concrete by listing the exact Plugin Eval / strict audit commands rather than only naming the procedures.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the Avoid and Anti-Patterns sections are near-verbatim duplicates and the 'Fail fast' guidance is repeated across Constraints and Validation, which could be tightened.

4 / 5

Actionability

Concrete workflow steps ('Apply one decision: ready, skipped, customized, or blocked'; 'Update filename, frontmatter, and work-log state together') give mostly executable guidance, with a minor gap in that exact validation commands are named but not specified.

4 / 5

Workflow Clarity

A clear six-step sequence is paired with an explicit fail-fast validation feedback loop ('stop at the first failed gate, fix it, and rerun'), though per-item checklists for the batch triage are only implicit.

4 / 5

Progressive Disclosure

The body is well sectioned and points outward to archived context, but the referenced path 'Infrastructure/references/deferred-skill-context/agent-ops-triage/' is not present in the bundle while the actual bundle files (contract.yaml, evals.yaml, task-profile.json) are never referenced from the body.

3 / 5

Total

15

/

20

Passed

Description

83%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 that cleanly states both the capability and its trigger condition. It enumerates concrete outcome states and uses natural trigger language, with only minor room for more synonyms.

DimensionReasoningScore

Specificity

The description names the domain ('file-based todo findings') and enumerates four concrete outcome states ('ready, skipped, customized, or blocked'), giving several specific actions/outcomes with only minor coverage gaps.

4 / 5

Completeness

It explicitly answers both what ('Review file-based todo findings into ready, skipped, customized, or blocked states') and when ('Use this skill when pending todo files need approval') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Natural terms like 'pending todo files', 'findings', and 'approval' match what users would say, with good though not exhaustive coverage of synonyms or file extensions.

4 / 5

Distinctiveness Conflict Risk

The file-based todo/approval niche is fairly distinct with mostly specific triggers, though there is minor overlap risk with general review or backlog skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
jscraik/Agent-Skills
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.