CtrlK
BlogDocsLog inGet started
Tessl Logo

loop-triage

Triage recent changes, CI failures, issues, and conversations. Produces a concise, actionable findings report suitable for a loop to consume. Writes structured output to a state file or Linear board.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/loop-triage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-structured instruction skill with a clear output template and example invocation, but the triage procedure itself is under-specified and lacks a validation step. Adding a short sequenced method and a self-check would lift actionability and workflow clarity.

Suggestions

Add a brief sequenced triage procedure (e.g. gather inputs → dedupe against state file → classify by impact → assign to High-Priority/Watch/Noise) so the action is unambiguous.

Include a validation/self-check step, such as confirming every High-Priority item has an impact rationale and a suggested next action before emitting the report.

Give one concrete worked example of a triaged item across all four output sections to anchor the abstract format.

DimensionReasoningScore

Conciseness

The body is lean and well-organized into Inputs, Output Format, Rules, and Example Invocation, with no explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

The output template and the example invocation command are concrete, but the actual triage methodology — how to gather, deduplicate, and prioritize the inputs — is left abstract, so guidance is incomplete.

2 / 3

Workflow Clarity

The output sections (1–4) are clearly laid out, but there is no sequenced process for performing the triage itself and no validation checkpoint confirming the report is complete and honest.

2 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clearly labeled sections, satisfying the simple-skill allowance for a top score.

3 / 3

Total

10

/

12

Passed

Description

60%

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 specific and action-oriented with a clear loop-consumer niche, but it lacks an explicit 'when to use' trigger clause and natural trigger-term coverage is incomplete. Adding a 'Use when...' sentence with common trigger phrasings would raise the completeness and trigger scores.

Suggestions

Append a 'Use when...' trigger clause, e.g. 'Use when the loop needs to triage recent CI failures, open issues, or team conversations into a prioritized action list.'

Broaden trigger-term coverage with natural variations users would say, such as 'flaky tests', 'broken builds', 'open tickets', or 'standup threads'.

Sharpen distinctiveness by naming the consumer explicitly, e.g. 'for an automated opencode loop to act on' rather than the generic 'a loop'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Triage recent changes, CI failures, issues, and conversations', 'Produces a concise, actionable findings report', 'Writes structured output to a state file or issue tracker' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

It clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

Relevant keywords like 'CI failures', 'issues', and 'conversations' appear, but common variations and natural trigger phrasings are missing, so it sits at the 'some relevant keywords' anchor rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The loop-triage framing is somewhat specific, but 'triage' of CI failures and issues could overlap with general debugging or review skills, so it is not yet a clearly non-conflicting niche.

2 / 3

Total

9

/

12

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
cobusgreyling/loop-engineering
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.