CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

impact-map

Builds an impact-first view of a GitHub PR: a verdict with expandable What/Risk/Ask rows, one diagram colored new/changed/removed, at most three decisions with linked lines, and what is already settled. Every claim is checked against code, tests, and docs first. --comment or --body posts it to the PR with light and dark PNGs. Triggers on "impact map", "visualize this PR", "/impact-map".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

As writing, the body is excellent — lean, dense with executable commands, and sequenced with explicit validation gates and feedback loops. As a bundle, it fails its own architecture: it is explicitly a thin index whose per-phase rules and page template are not shipped, so the progressive-disclosure structure it advertises cannot be followed.

Suggestions

Ship the referenced files — rules/analysis.md, rules/diagram.md, rules/outputs.md, and templates/page.html — or inline the phase procedures into SKILL.md if the bundle is meant to be self-contained; a thin index pointing at absent files is the skill's dominant defect.

State the consent rule once (Core rules) and reference it from the Arguments and stack sections instead of restating it four times, trimming the long --findings table cell to just the pointer into rules/diagram.md.

Add natural trigger variations ('PR overview', 'summarize this PR', 'impact analysis') to the description's trigger clause so the skill is discoverable before the user knows its name.

DimensionReasoningScore

Conciseness

The body is dense and load-bearing — no explanation of concepts Claude already knows, compact wrong/right contrast blocks instead of prose, and exact commands rather than descriptions. It is not 5 because of repetition that could be trimmed: the GitHub-write consent rule is stated four times (Arguments prose, stack step 3, the ✗/✓ block, and Core rule 5), and the long --findings table cell re-states procedure detail that is also delegated to rules/diagram.md.

4 / 5

Actionability

Concrete and executable where it speaks directly: exact script invocations ("node scripts/line-link.mjs locate pr.diff <path> '<regex>'"), gh commands ("gh pr diff <n>", "gh pr list --base <head>"), a complete flag table, a literal report template, and per-phase gates like "≤ 3 decisions, each What / Risk / Ask and ≤ 3 linked lines". It is not 5 because the procedures for phases 0–4 are delegated to rules/*.md files that are not present in the bundle, so a reader cannot execute the core analysis from what actually ships alongside this index.

4 / 5

Workflow Clarity

The Workflow table sequences seven named phases (Fetch → Candidates → Verify → Decide → Diagram → Page → Post), each with an explicit gate that functions as a validation checkpoint: "Every candidate classified open / settled / wrong, with evidence", "PNGs rendered and looked at", and "PNGs uploaded, posted, read back clean" — the last two being feedback loops for error recovery. Risky operations carry their own checks (consent verified before the undeletable image upload; the no-Chrome fallback is specified), so the destructive/batch cap does not apply. Not 4 because checkpoints are not merely 'most' present but explicit at every phase.

5 / 5

Progressive Disclosure

The design intent is exemplary — "This SKILL.md is a thin index", one-level-deep per-phase rule files, and an on-demand reference that self-describes as "Read on demand; nothing here is needed to run the skill" — but scored against the actual bundle, 5 of the 6 referenced paths are broken: rules/analysis.md, rules/diagram.md, rules/outputs.md (the workflow table's core targets) and templates/page.html do not exist in the bundle; only references/design-rationale.md and the two scripts are present. Navigation is clearly signaled but leads nowhere for the procedural content, which is the failure this dimension exists to catch. Not 3 because the missing files are the skill's substance, not an organization nicety; not 1 because the in-body structure and the one real reference are well organized and only one level deep.

2 / 5

Total

15

/

20

Passed

Description

85%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: concrete, comprehensive, third-person, with an explicit quoted trigger clause that satisfies the completeness requirement outright. The only real weakness is trigger breadth — two natural phrases plus the slash command misses the synonyms and variations ("PR overview", "summarize this PR", "impact analysis") a user might say before learning the skill's name.

Suggestions

Extend the trigger list with natural variations users would say before knowing the skill's name, e.g. 'PR overview', 'summarize this PR', 'impact analysis', or 'what do I need to review in this PR'.

Consider naming the domain words 'pull request' / 'PR' in the trigger clause itself so matching does not depend on the abbreviated form.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage: "Builds an impact-first view of a GitHub PR: a verdict with expandable What/Risk/Ask rows, one diagram colored new/changed/removed, at most three decisions with linked lines, and what is already settled", plus "Every claim is checked against code, tests, and docs first" and "--comment or --body posts it to the PR with light and dark PNGs". It covers build, verify, and post phases in third-person voice with no vague filler. Not 4 because the action list spans the skill's full capability set rather than having minor gaps.

5 / 5

Completeness

Both questions are answered explicitly: 'what' is the concrete build/verify/post capability list, and 'when' is the closing "Triggers on 'impact map', 'visualize this PR', '/impact-map'" with concrete trigger phrases. This matches the anchor-5 example structure (full capability list followed by an explicit use-when clause with quoted triggers). Not 4 because the 'when' is not merely present but given as exact quoted phrases.

5 / 5

Trigger Term Quality

Trigger guidance is explicit — "Triggers on 'impact map', 'visualize this PR', '/impact-map'" — and each phrase is natural, but coverage is thin: effectively two natural phrases plus the slash command. Common variations a user would actually say ("PR overview", "summarize this PR", "impact analysis", "PR risk") are missing, which matches anchor 3 ('relevant keywords but missing common variations or synonyms'). Not 4 because the natural-term set is too small to count as good coverage; not 2 because the terms given are genuinely natural, not generic.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche — impact-first PR review views with a bounded output format (verdict rows, one diagram, ≤3 decisions) — and its triggers are the skill's own name and slash command plus one PR-specific verb phrase, so overlap with generic review or visualization skills is minimal. Not 4 because no closely related skill would plausibly claim these triggers; "visualize this PR" is anchored to the PR context the description establishes throughout.

5 / 5

Total

18

/

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_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 9 missing

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/quality/impact-map/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.