CtrlK
BlogDocsLog inGet started
Tessl Logo

diagnose-a-red-run

Test is red, typecheck failed, CI job failed, flaky, timed out, was this already broken. Use to classify any failing check before changing code or calling it pre-existing.

65

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 ./.opencode/skills/diagnose-a-red-run/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An efficient, well-structured diagnostic skill that assumes Claude's competence and centers a clean-control validation gate. It is held just below 5 on actionability and workflow clarity because portions of the guidance are directives rather than fully executable steps with explicit retry loops.

Suggestions

Convert key directives into concrete commands where possible (e.g., give the actual port-kill command instead of 'Kill by port') to push actionability toward 5.

Add an explicit validate→retry loop for the non-reproducing case ('repeat both sides; if still divergent, label flaky') to reach anchor-5 workflow clarity.

DimensionReasoningScore

Conciseness

Terse, dense bullets with no padding and no explanation of concepts Claude already knows; every line carries project-specific signal ('Kill by port, not process name').

5 / 5

Actionability

Provides copy-paste-ready bash (git worktree control) and concrete per-signature responses, but a meaningful share of the guidance is directive ('Quote the...', 'Classify as...') rather than executable commands.

4 / 5

Workflow Clarity

Clear sequence (capture → clean control → classify → forensics) with the clean control acting as an explicit validation gate and branch logic, but it lacks the formatted validate→fix→retry feedback loop of anchor 5.

4 / 5

Progressive Disclosure

A single well-organized SKILL.md with four clear section headers and no nested or buried references; no external files are needed, matching the simple-skill exception.

5 / 5

Total

18

/

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 tight, trigger-rich description that clearly signals when to use the skill and carves out a distinct niche. It is slightly thin on enumerating multiple concrete actions, which keeps specificity and completeness at the 4-level rather than 5.

Suggestions

Add one or two more concrete actions beyond 'classify' (e.g., 'reproduce on a clean checkout, then label') to lift specificity toward 5.

Separate the 'when' trigger from the 'what' so the use-condition reads as a standalone 'Use when ...' clause.

DimensionReasoningScore

Specificity

Names the domain (failing checks) and one concrete action ('classify any failing check') with concrete check types, but does not list multiple distinct actions, so it stops short of anchor 4.

3 / 5

Completeness

Provides both a 'what' (classify failing checks) and an explicit 'Use to ... before changing code or calling it pre-existing' trigger clause, though the 'when' blends into the 'what' rather than standing alone.

4 / 5

Trigger Term Quality

Opens with natural phrases a user would say ('Test is red, typecheck failed, CI job failed, flaky, timed out, was this already broken') — strong coverage, just shy of fully comprehensive synonyms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (diagnosing red CI/check runs) with distinct triggers, with only minor overlap risk against general debugging skills.

4 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
different-ai/openwork
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.