CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-aw-reliability

Validate GitHub Agentic Workflow contracts through compiled artifacts and realistic mutations

60

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 ./.github/skills/gh-aw-reliability/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.

The body is a lean, well-organized instruction set with strong validation emphasis and concrete test-file exemplars; its main gap is that guidance stays at the directive level without exact commands or an explicitly numbered workflow sequence.

DimensionReasoningScore

Conciseness

The ~25-line body is lean and assumes Claude's competence: no padding, no explanation of concepts Claude already knows, and every directive earns its place, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Guidance is concrete and domain-specific ('Strict-compile the workflow and inspect the emitted artifact', 'Test a realistic mutation ... and prove the relevant gate fails') with real test-file examples, but it stops short of copy-paste commands, sitting at 'mostly executable guidance with minor gaps' rather than fully executable.

4 / 5

Workflow Clarity

Validation is present and emphasized ('a zero exit code alone is not enough', 'Fail closed when ... unavailable', 'prove the relevant gate fails'), avoiding the destructive/batch cap, but the patterns are principles rather than an explicitly numbered sequence with checkpoints, fitting just below the 5 anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, requires no external bundle references (none provided), and is organized into clear Context / Patterns / Examples / Anti-Patterns sections, qualifying for the top anchor under the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

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

The description is specific to a well-defined niche and states a clear capability, but it lacks an explicit 'Use when' trigger clause and offers only one or two concrete actions, capping completeness and trigger quality at mid-range.

Suggestions

Add a 'Use when ...' clause naming concrete trigger situations, e.g. 'Use when creating or modifying Squad GitHub Agentic Workflow sources, safe outputs, authorization, or prompt inputs.'

Expand the action list beyond a single 'Validate' verb to enumerate specific concrete actions (e.g. strict-compile, inspect the emitted artifact, run realistic mutations and assert gate failures).

Include a natural-language synonym or two (e.g. 'GitHub Agentic Workflow gates' or 'compiled workflow contracts') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('GitHub Agentic Workflow contracts') and one action ('Validate') carried out via two methods ('compiled artifacts and realistic mutations'), but does not enumerate several distinct concrete actions, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

The 'what' is clear ('Validate ... contracts through compiled artifacts and realistic mutations'), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

It includes relevant niche terms ('GitHub Agentic Workflow', 'contracts', 'compiled artifacts') a practitioner in this domain would say, but it leans technical and omits common variations or synonyms; not a comprehensive spread of natural terms.

3 / 5

Distinctiveness Conflict Risk

The domain is a clear, narrow niche unlikely to trigger the wrong skill, but the absence of explicit trigger phrases and the technical phrasing leave minor overlap risk with general validation/testing skills, so it sits just below the 5 anchor.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
bradygaster/squad
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.