CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

he-reliability-review

Review services, APIs, and multi-component systems for reliability risks including failure modes, cascading failures, resilience gaps, and SLO readiness. Use when the work involves new services, significant service changes, multiple external dependencies, or high blast-radius failure scenarios.

Quality

73%

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 ./Plugins/harness-engineering/fixtures/budget-archive/2026-04-21/deferred-store/skills/code_quality_review/he-reliability-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body delivers a concrete, well-sequenced reliability review workflow with actionable lenses, output contracts, and fail-fast validation commands, and it appropriately avoids teaching concepts Claude already knows. Its weaknesses are duplication and meta-filler that cost tokens, and a progressive-disclosure structure whose referenced bundle files are entirely absent, leaving several links dead and unsignaled.

Suggestions

Deduplicate the entrypoint: merge the overlapping 'Use' and 'When to use' sections, consolidate the subagent-routing references repeated in 'Full Context' and 'Subagent Routing', collapse the duplicate assets lines ('Assets: [./assets]' and 'Assets directory marker: `assets/`'), and remove the meta commentary in 'Progressive Disclosure Entry' and the vague 'Use this skill as normal for this Harness Engineering stage' bullet.

Fix the bundle so every referenced path exists: references/resilience-patterns.md, references/contract.yaml, references/evals.yaml, references/task-profile.json, and assets/ are all absent from the bundle, making the progressive-disclosure links dead ends.

Add a read-when signal to every reference in 'Full Context' — contract.yaml, evals.yaml, and task-profile.json are currently bare links with no guidance on when to load them, unlike resilience-patterns.md and qa-intake-routing.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient imperative bullets with no concept explanations, but contains clear tightening opportunities: 'Use' and 'When to use' sections overlap, the subagent-routing link is duplicated across 'Full Context' and 'Subagent Routing', the assets entry appears twice ('Assets: [./assets]' and 'Assets directory marker: `assets/`'), and meta-commentary like 'This entrypoint stays concise and keeps full reliability-review context in references loaded only when needed' plus the vague 'Use this skill as normal for this Harness Engineering stage' add tokens without adding instruction. This matches anchor 3 (mostly efficient but some unnecessary content could be trimmed) rather than 2, since there is no concept-teaching padding.

3 / 5

Actionability

For an instruction-only review skill, the guidance is largely executable: a 6-step ordered Procedure, concrete review lenses (timeout, retry, backoff, jitter, idempotency, circuit breaker, bulkhead), a structured output contract (severity-ranked findings with blast radius, detection gap, mitigation; 'schema_version: 1'), runnable validation commands, and example user requests. It is anchor 4 rather than 5 because some steps remain high-level with the specifics deferred to references (e.g., 'Map service boundaries and dependency failure paths' gives no concrete method inline).

4 / 5

Workflow Clarity

The Procedure is a clearly sequenced 6-step flow with ordering constraints ('Inspect resilience controls and observability evidence before assigning severity'), an upfront classification step for QA reports, and a fail-fast validation gate ('stop at the first failed gate and do not proceed') with concrete commands. This matches anchor 4 (clear sequence with most checkpoints present); it is not 5 because the findings workflow itself lacks an internal verify/feedback loop (e.g., re-checking findings against target evidence), and not 3 because the sequence, ordering rules, and fail-fast checkpoint are explicit. The review-only, non-destructive nature means the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

The intent is good — a lean entrypoint with read-when signals for the two main references — but scored against the actual bundle, every locally referenced file is missing: references/resilience-patterns.md, references/contract.yaml, references/evals.yaml, references/task-profile.json, and assets/ do not exist in the bundle, so the links are dead. Additionally, contract.yaml, evals.yaml, and task-profile.json are listed without any read-when signal, and the assets entry is duplicated with a redundant 'directory marker' line. This lands at anchor 3 (some structure, references present but not clearly signaled / could be better organized); it is not 2 because the body is well-sectioned and the primary references do carry explicit read-when conditions rather than being buried or inlined.

3 / 5

Total

14

/

20

Passed

Description

75%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 strong description that explicitly covers both what the skill does and when to use it, with a well-scoped reliability niche and mostly natural trigger terms. The main gaps are a slightly generic action verb, and the omission of common user phrasings like timeout, retry, intermittent, or outage that would strengthen trigger matching.

DimensionReasoningScore

Specificity

The description lists several concrete review targets ("failure modes, cascading failures, resilience gaps, and SLO readiness") for a named domain (services, APIs, multi-component systems), matching the 'several specific actions; minor gaps' anchor. It is not anchor 5 because 'review' is a single generic action verb and common reliability risks like timeouts, retries, and incident analysis are not covered.

4 / 5

Completeness

Both what ("Review services, APIs, and multi-component systems for reliability risks including failure modes, cascading failures, resilience gaps, and SLO readiness") and when ("Use when the work involves new services, significant service changes, multiple external dependencies, or high blast-radius failure scenarios") are explicitly present. It sits between anchors 4 and 5: the when-clause is explicit but framed around work context rather than concrete user-utterance trigger phrases, so 4 rather than 5.

4 / 5

Trigger Term Quality

The when-clause includes good natural keywords users would say: "new services", "significant service changes", "multiple external dependencies", "high blast-radius failure scenarios", plus "cascading failures" and "SLO". It falls short of anchor 5 because common user phrasings like timeout, retry, intermittent behavior, outage, or incident are missing.

4 / 5

Distinctiveness Conflict Risk

Reliability-specific triggers (cascading failures, resilience gaps, SLO readiness, blast-radius) carve a clear niche distinct from general document or data skills. It is anchor 4 rather than 5 because 'review services/APIs' could still overlap with general code-review or security-review skills in the same family when a user asks to 'review this API'.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 6 missing, 4 suspicious

Warning

referenced_paths_exist

Referenced path issues: 10 missing

Warning

Total

13

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/harness-engineering/fixtures/budget-archive/2026-04-21/deferred-store/skills/code_quality_review/he-reliability-review/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.