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?"

63

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 ./.claude/skills/gitnexus-impact-analysis/SKILL.md
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.

The body is highly actionable and well-structured with concrete commands and a worked example, assuming Claude's competence throughout; the only real costs are repeated command strings across sections and a validation loop not explicitly wired into the workflow steps.

DimensionReasoningScore

Conciseness

The body is lean and tool-specific with no over-explanation of concepts Claude already knows; the main trimmable cost is the full CLI fallback string being restated across Workflow, Checklist, Tools, and Example sections.

4 / 5

Actionability

Fully executable guidance throughout: concrete MCP calls with parameters, copy-paste CLI fallback commands, real READ URIs, and a worked end-to-end example covering the common case.

5 / 5

Workflow Clarity

A clear numbered workflow is reinforced by a checklist and a stale-index recovery note, but the step sequence itself lacks an explicit validate-and-retry checkpoint (the UNKNOWN "confirm with text search" guidance lives in Risk Assessment prose, not the workflow steps).

4 / 5

Progressive Disclosure

No bundle files exist and the content is well-organized into clearly headed sections (When to Use, Workflow, Checklist, Understanding Output, Risk Assessment, Tools, Example) with no content that clearly belongs in a separate file; scored on structure alone since there are no references to verify.

4 / 5

Total

17

/

20

Passed

Description

65%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 excels at explicit trigger guidance with natural user phrasing and a clear use niche, but is comparatively light on concrete capability description, framing the skill by user need rather than actions performed.

Suggestions

Add one concrete capability clause naming what the skill does, e.g. "Finds upstream dependents and computes blast radius for a symbol or diff" before the Use-when clause.

Pull one or two high-value trigger terms currently only in the body (e.g. "blast radius", "who uses this code?") into the description for fuller keyword coverage.

Keep the existing quoted examples — they are the strongest part of the description.

DimensionReasoningScore

Specificity

The description names the domain ("safety analysis before editing code", "what will break") but frames it as the user's need rather than listing concrete skill actions like finding dependents or detecting changes, so actions are minimal/generic.

2 / 5

Completeness

Both "what" (break/safety analysis) and "when" are present, with the "when" being explicit and concrete via quoted trigger phrases; the "what" is present but not a concrete capability list, keeping it just below a 5.

4 / 5

Trigger Term Quality

It quotes natural phrases users actually say ("Is it safe to change X?", "What depends on this?", "What will break?") with good synonym coverage; a few natural terms like "blast radius" or "who uses this" appear only in the body, not the description.

4 / 5

Distinctiveness Conflict Risk

The pre-change break/safety-analysis niche has distinct, specific triggers unlikely to fire for unrelated skills, with only minor overlap risk against general code-search or refactoring skills.

4 / 5

Total

14

/

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
abhigyanpatwari/GitNexus
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.