CtrlK
BlogDocsLog inGet started
Tessl Logo

gitnexus-plan

Use when you need a deep, implementation-ready engineering plan for a code change — built from GitNexus graph intelligence, statement-level PDG analysis, and targeted source verification, compact enough that an implementation agent can start without re-investigating. Also strengthens existing plans via Deepen mode. Examples: "/gitnexus-plan Add retry support to the ingestion pipeline", "/gitnexus-plan deepen docs/plans/<plan>.md", "plan this change using the knowledge graph".

73

Quality

90%

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

92%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 content is a well-structured, highly actionable planning workflow with explicit validation and feedback loops and clean progressive disclosure into verified reference files. Its only weakness is minor verbosity from repeated helper-invocation prose and a dense configuration table.

DimensionReasoningScore

Conciseness

The body is dense operational guidance that assumes Claude's competence with no basic-concept padding, but the evidence-provenance helper invocation is repeated across Hard rules, Phase 4, Phase 5, and Deepen, and the Configuration 'Meaning' column is verbose — minor trims are available.

4 / 5

Actionability

Concrete analyzer-runner commands, exact tool-call signatures (query, context, impact, trace), normalized plan-path formats, and helper subcommands (write-plan, read-plan) give copy-paste-ready, executable guidance across the common cases.

5 / 5

Workflow Clarity

A clearly sequenced Phase 0–5 plus Deepen workflow carries explicit validation checkpoints (freshness gate, analyzer provenance check, source verification) and feedback loops (graph/source disagreement, safe-write failure, stale-analyzer limitation); the skill is non-destructive and guards its only state changes.

5 / 5

Progressive Disclosure

The overview body points to one-level-deep references (context-ledger, pdg-slice, plan-template, context-pack, evidence-provenance) and the evidence-provenance script, all of which exist as real files with clearly signaled relative paths, keeping detail appropriately split out.

5 / 5

Total

19

/

20

Passed

Description

87%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 strong: it explicitly answers what and when with concrete trigger examples and occupies a distinct, tool-specific niche. The main gap is trigger-term breadth — heavy on specialized jargon that a user may not naturally say.

DimensionReasoningScore

Specificity

Lists concrete actions (produce an implementation-ready plan; strengthen existing plans via Deepen mode) plus named methods (graph intelligence, PDG analysis, source verification), but is methodology-heavy rather than a comprehensive set of distinct user-facing capabilities.

4 / 5

Completeness

An explicit 'Use when…' clause states when to invoke it, the body states what it produces (deep implementation-ready plan plus Deepen-mode strengthening), and concrete trigger examples make both halves explicit.

5 / 5

Trigger Term Quality

Examples supply natural phrasings ('plan this change using the knowledge graph', 'Add retry support to the ingestion pipeline') alongside 'engineering plan' and 'code change', but the description leans on specialized jargon (PDG, GitNexus) and lacks synonym or file-extension breadth.

4 / 5

Distinctiveness Conflict Risk

It is bound to a specific tool (GitNexus) and command (/gitnexus-plan) with distinct triggers ('knowledge graph', 'deepen'), giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

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.