CtrlK
BlogDocsLog inGet started
Tessl Logo

gitnexus-impact-analysis

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"

68

Quality

81%

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

82%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 body with concrete tool calls, tables, and a worked example. Its main weaknesses are mild redundancy across the workflow/checklist/example sections and implicit rather than explicit validation checkpoints.

Suggestions

Collapse the duplication between the Workflow, Checklist, and Example sections — keep the numbered workflow and one worked example, reference them from the checklist instead of restating the impact() calls.

Add an explicit validation checkpoint in the workflow (e.g., 'Verify d=1 dependents are real callers before reporting risk') so the sequence has a correctness gate, not just a risk-assessment step.

Consider moving the detailed Tools parameter reference and risk-assessment tables into a reference file so SKILL.md stays a lean overview with one-level-deep navigation.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no explanations of git or impact analysis), but the Workflow, Checklist, and Example sections repeat the same impact() calls, so not every token earns its place.

4 / 5

Actionability

Provides copy-paste-ready tool calls with full parameters (target, direction, minConfidence, maxDepth, scope), concrete resource paths, a recovery command, and a worked example with realistic output covering the common case.

5 / 5

Workflow Clarity

A clear numbered sequence plus a checklist and one feedback loop ('If Index is stale → run analyze'), but validation checkpoints are implicit — step 4 'assess risk and report' is not a correctness check — leaving a minor validation gap.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections (When to Use, Workflow, Checklist, Tools, Example) with no nested references, though at ~93 lines all content is inline with no split into reference files.

4 / 5

Total

17

/

20

Passed

Description

81%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, trigger-rich description that clearly signals when to use the skill with natural user phrasings and occupies a distinct niche. It could lead with a more explicit, enumerated capability statement to lift specificity and completeness.

DimensionReasoningScore

Specificity

Names the domain (impact/safety analysis) and 1-2 actions ('know what will break', 'safety analysis before editing code'), but does not enumerate multiple concrete capabilities like 'find dependents, map blast radius, check execution flows', so it is not comprehensive.

3 / 5

Completeness

Both 'what' (safety/breakage analysis) and 'when' (explicit 'Use when...' plus concrete triggers) are present, but the capability is embedded in the trigger clause rather than led as a crisp standalone statement, slightly short of the cleanest anchor-5 form.

4 / 5

Trigger Term Quality

Includes highly natural user phrasings as explicit examples — 'Is it safe to change X?', 'What depends on this?', 'What will break?' — covering the synonyms users actually say when they need this skill.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (pre-change impact/safety analysis) with distinct triggers ('what will break', 'what depends on this') that are unlikely to fire for unrelated skills.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tslateman/praxis
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.