CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blast-radius

Before and after changing anything shared — a function's return value, a signature, a schema, a label set, a config default, a constant, a file format — find every consumer and actually run them. Catches the change that looks purely additive but silently breaks a contract in a file you never opened. Use when editing shared code, adding a field/column/return element, renaming, changing units or defaults, or touching a pipeline that produces reported numbers.

Quality

76%

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 ./.agents/skills/blast-radius/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 tightly written redirect shim: lean, well-structured, and dense with sensible portability guidance for non-Claude-Code agents. Its weakness is architectural — it contains none of the skill's actual procedure, and every reference points outside the bundle to files that are not shipped, so as a standalone artifact it is not navigable or executable.

Suggestions

Inline the actual blast-radius procedure (find consumers, run them before the change, apply the change, run them after, compare results) in the body instead of redirecting through '../../../.claude/skills/blast-radius/SKILL.md', whose relative path escapes the bundle and breaks when the file is distributed standalone.

Ship the referenced files (the source SKILL.md, AGENTS.md, and any .claude/agents/* files) inside the bundle, or restructure so references are one level deep and resolve within it — currently every link is dangling.

Add a brief in-file summary of what the skill does and its validation checkpoints so a reader has actionable guidance and gating rules without chasing nested references.

DimensionReasoningScore

Conciseness

The body is ~25 lines of purely imperative content: every bullet (Arguments, Claude Code agents, Fresh context, Claude Code settings, Guards) carries distinct, non-redundant instruction, and nothing explains concepts the reader already knows. Not 4 because no specific passage of over-explanation or padding can be identified to trim.

5 / 5

Actionability

Some concrete guidance is present (exact paths, 'Agent or Task tool', '/commit', '/verify-claims', specific frontmatter fields to ignore), but the executable procedure for the skill's actual task is entirely absent from the body, deferred to an external file that does not resolve within the bundle. Not 2 because what is written is specific rather than high-level hints; not 4 because the missing task steps are a major gap.

3 / 5

Workflow Clarity

A clear reading sequence exists ('Read AGENTS.md first' then 'Read that file now and follow it') and gating is preserved ('A step that gates what follows still gates it'), with a verification fallback ('mark every result it produced not independently verified'). However, the actual multi-step procedure and its checkpoints are not in this body, and the skill involves running batches of consumers with no visible validation steps, consistent with a cap of 3.

3 / 5

Progressive Disclosure

The bundle ships only SKILL.md, and both references ('../../../.claude/skills/blast-radius/SKILL.md' and '../../../AGENTS.md') escape the bundle and do not resolve; reaching any content requires 2+ levels of indirection (shim, then source skill, then 'the files it points to'), matching the nested-reference anti-pattern. Not 1 because the file itself is well-structured with prominently signaled links; not 2-below or 3 because no content is split at this level at all and the links dangle as shipped.

2 / 5

Total

13

/

20

Passed

Description

83%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: it states a concrete, distinctive capability (enumerate and run every consumer of a shared contract before and after a change), explains the failure mode it prevents, and closes with an explicit, multi-trigger 'Use when' clause full of natural developer phrasing. The only gaps are minor missing trigger synonyms and slight breadth in 'editing shared code'.

DimensionReasoningScore

Specificity

The core action 'find every consumer and actually run them' is concrete, and the enumeration 'a function's return value, a signature, a schema, a label set, a config default, a constant, a file format' gives specific coverage of shared-contract types. It is not 3 because the enumeration provides breadth beyond 1-2 generic actions, and not 5 because it describes essentially one procedure (find consumers, run them) rather than multiple distinct concrete actions.

4 / 5

Completeness

Explicitly answers both: what ('find every consumer and actually run them' before and after changing anything shared, to catch changes that 'silently break a contract') and when ('Use when editing shared code, adding a field/column/return element, renaming, changing units or defaults, or touching a pipeline that produces reported numbers'). This matches the anchor-5 pattern of concrete what plus multi-trigger when; not 4 because the when-clause is explicit and specific rather than merely present. Voice is third person, so no penalty applies.

5 / 5

Trigger Term Quality

'editing shared code', 'adding a field/column/return element', 'renaming', 'changing units or defaults', and 'touching a pipeline that produces reported numbers' are phrases developers naturally say. It is not 5 because common variations like 'refactoring', 'removing a field', or 'breaking change' are absent, and not 3 because coverage goes well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

The niche (consumer/contract impact analysis for shared code) is distinct, with specific triggers like 'a label set', 'changing units', and 'a config default' unlikely to fire for unrelated skills. Not 5 because the trigger 'editing shared code' is broad and could overlap with generic code-review or testing skills; not 3 because the contract-change framing is clearly differentiated.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

pedrohcgs/claude-code-my-workflow

Path

.agents/skills/blast-radius/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.