CtrlK
BlogDocsLog inGet started
Tessl Logo

triage-block

Marks a single auto-triage work-item as BLOCKED on its OWN tracker when a run hit something it could not overcome (permission denial, broken environment, timeout, unrecoverable error). Applies the `triage-blocked` label, returns the item to the queue (Todo), and comments the reason — so it leaves the auto-queue until a human resolves the cause and clears the label. Tracker- and project-agnostic: reuses the triage config + tracker binding (Linear, GitHub, …), never assumes one. The daemon calls it after DETERMINISTICALLY detecting a block; also usable as `triage-block <ITEM-ID> -- <reason>`.

68

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 concise, highly actionable single-purpose skill body with a clear sequenced procedure and exact output contracts; the only gap is the absence of an explicit validation checkpoint and reliance on cross-skill references.

Suggestions

Add an explicit verification step (e.g. confirm the label is present and state is QUEUED before emitting the final JSON) to strengthen the workflow's feedback loop.

If the referenced tracker-binding and work-item-schema files are part of this skill's contract, vendor them under ./references/ so the skill is self-contained and the references are verifiable.

DimensionReasoningScore

Conciseness

Lean ~40-line body with no padding or explanation of concepts Claude already knows; the brief framing ('detection lives in the scheduler, not here') is load-bearing rather than fluff.

5 / 5

Actionability

Provides the exact comment string, exact JSON output format, and concrete per-step examples (Linear 'Todo', 'gh label create', setState→QUEUED), making the guidance copy-paste ready.

5 / 5

Workflow Clarity

A clear 5-step procedure with edge-case handling ('{"blocked": null}' when not found), but lacks an explicit validate-then-retry checkpoint; the operation is single-item and non-destructive so the batch/destructive cap does not bind.

4 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled 'Read first' reference list one level deep; references point to the sibling triage skill's bundle rather than a local bundle, which is appropriate but not verifiable here.

4 / 5

Total

18

/

20

Passed

Description

72%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 specific, well-scoped description that names concrete actions and an explicit invocation trigger, with only minor weaknesses in natural trigger phrasing and overlap with the sibling triage skill.

Suggestions

Add a 'Use when…' clause with user-facing trigger phrasing (e.g. 'Use when an auto-triage run is blocked by a permission denial, timeout, or broken environment') to lift completeness and trigger-term quality.

Include common synonyms a user might say ('blocked', 'stuck', 'cannot proceed') alongside the technical terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Marks a single auto-triage work-item as BLOCKED', 'Applies the triage-blocked label', 'returns the item to the queue (Todo)', 'comments the reason' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Clearly states the 'what' and gives an explicit 'when' ('when a run hit something it could not overcome…' / 'The daemon calls it after DETERMINISTICALLY detecting a block'), though the trigger is mechanistic rather than user-need-framed.

4 / 5

Trigger Term Quality

Domain terms like 'BLOCKED', 'permission denial', 'timeout', and 'triage-block' are present, but the language is jargon-heavy and daemon-oriented, missing the natural synonyms a user would say.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (tracker-side block recording) with distinct triggers, but shares the triage family and config with the sibling 'triage' skill, creating minor overlap risk.

4 / 5

Total

16

/

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
MrToxy/claude-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.