CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage

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

Quality

70%

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

57%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 compact, well-structured instruction-only skill with a clear philosophy, decision states, and safety constraints. Its weaknesses are duplicated Avoid/Anti-Patterns content, missing operational specifics (state-marking conventions, schemas, exact validation commands), no in-workflow validation checkpoint for batch state updates, and a broken progressive-disclosure reference path that ignores the real bundle files.

Suggestions

Add an explicit validation checkpoint to the workflow (e.g., after step 5: verify each updated todo file passes the output schema before summarizing), since the skill modifies files in batch-capable mode.

Specify the state-marking mechanics: the filename convention, the frontmatter fields to set, and where the output schema lives, so the core operation is executable rather than implied.

Fix the 'Progressive Disclosure' reference to point at files that actually exist in the bundle (e.g., references/contract.yaml and references/evals.yaml) instead of the nonexistent 'Infrastructure/references/deferred-skill-context/agent-ops-triage/' path, and delete the verbatim-duplicate 'Anti-Patterns' section.

DimensionReasoningScore

Conciseness

The body is lean, well-sectioned, assumes Claude's competence, and explains no background concepts; every section carries operational content. Not a 5 because the 'Avoid' and 'Anti-Patterns' sections are verbatim duplicates of the same three bullets, and 'Fail fast' guidance is repeated in both 'Constraints' and 'Validation' — trimmable redundancy.

4 / 5

Actionability

The workflow enumerates concrete decision states and a step order ('Apply one decision: ready, skipped, customized, or blocked'), but key execution details are missing: no filename convention or frontmatter fields for marking state, no schema example for the 'schema-bound outputs', and no exact validation commands despite 'Report exact validation commands'. This matches the anchor for concrete-but-incomplete guidance with missing key details.

3 / 5

Workflow Clarity

The six-step sequence is clearly ordered, but this skill modifies todo files and supports batch mode ('Present one item at a time unless batch mode is requested') without an explicit validate-after-update checkpoint inside the workflow — the 'Validation' section only covers editing the skill itself. Per the rubric, batch/destructive-adjacent workflows without validation are capped at 3.

3 / 5

Progressive Disclosure

Sections are clearly organized with a See Also table, but the 'Progressive Disclosure' section points to 'Infrastructure/references/deferred-skill-context/agent-ops-triage/' which does not exist in the bundle, while the actual bundle files (references/contract.yaml, references/evals.yaml, references/task-profile.json) are never referenced from the body. This is a dangling reference path plus unnavigable bundle content — structure present but references not correctly signaled.

3 / 5

Total

13

/

20

Passed

Description

70%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 solid description that clearly states a concrete capability and an explicit trigger condition in third-person voice with no fluff. Its main gaps are the single narrow 'when' condition, sparse synonym coverage, and no boundary signals distinguishing it from adjacent task-management skills.

Suggestions

Broaden the 'when' clause with additional concrete trigger phrasings, e.g. 'Use when pending todo files need approval, when findings must become explicit ready/skipped/blocked states, or when the user mentions triaging todos.'

Add a boundary qualifier such as 'for file-based todos only' to reduce conflict risk with Linear/GitHub/product-backlog triage skills.

DimensionReasoningScore

Specificity

The description names the domain ('file-based todo findings') and one concrete action with four enumerated outcome states ('ready, skipped, customized, or blocked'), matching the anchor for naming a domain with 1-2 concrete actions. It is not a 4 because there is only a single action verb ('Review... into states') rather than several distinct specific actions.

3 / 5

Completeness

Both parts are explicitly present: the 'what' ('Review file-based todo findings into ready, skipped, customized, or blocked states') and the 'when' ('Use this skill when pending todo files need approval'). Not a 5 because the 'when' clause offers only a single narrow trigger condition, whereas the top anchor expects multiple concrete trigger phrasings covering common variations.

4 / 5

Trigger Term Quality

Natural terms like 'todo files', 'pending todo files', 'findings', and 'approval' are terms a user would plausibly say when needing this skill. Not a 5 because common synonyms and variations ('triage', 'backlog', 'queue', 'review findings') are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — file-based todo findings triage with named terminal states — so overlap risk with unrelated skills is low. Not a 5 because the description omits boundary guidance (e.g., excluding Linear/GitHub/product backlog triage), leaving mild overlap risk with generic task-management skills.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/agent-ops/triage/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.