Name: gitnexus-cli
Rating: 72.8 (1 reviews)
Author: abhigyanpatwari

gitnexus-cli

Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is gitnexus-cli in abhigyanpatwari/GitNexus

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 highly actionable, well-organized command reference with copy-paste commands and concrete flags throughout. It is slightly verbose in a few edge-case passages and lacks explicit validation for the destructive clean operation.

Suggestions

Tighten the long blockquote (npm 11.x crash workarounds) and the --watch rejected-flags list in the analyze section; move detailed version-specific fallbacks to a troubleshooting sub-section or external reference to improve conciseness.

Add an explicit validation step after 'clean' (e.g., run 'status' to confirm the index is gone) and state a numbered 're-run analyze if the context check fails' loop to strengthen workflow_clarity for the destructive/batch operations.

Consider splitting the npm/bun troubleshooting edge cases into a references file so SKILL.md stays a lean overview, lifting progressive_disclosure toward the one-level-deep-reference ideal.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational with no basic-concept padding, but the npm 11.x crash blockquote and the long --watch flag-rejection list are verbose edge-case passages that could be trimmed.	4 / 5
Actionability	Every command has a copy-paste-ready bash snippet ('node .gitnexus/run.cjs analyze', 'status', 'clean', 'wiki', 'list') plus concrete flag tables covering the common cases.	5 / 5
Workflow Clarity	The 'After Indexing' sequence (run analyze -> read context to verify loaded -> use other skills) has an explicit verify checkpoint and troubleshooting covers stale-index recovery, but there is no explicit post-clean verify step or numbered re-run loop.	4 / 5
Progressive Disclosure	Clear section headers (Commands, After Indexing, Troubleshooting) with per-command subsections give easy navigation; no bundle files exist so there are no one-level-deep references, and the npm-11.x troubleshooting block could arguably live in its own file.	4 / 5
	Total	17 / 20 Passed

Description

96%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, well-constructed description that clearly states both what the skill does and when to use it, with concrete action verbs and natural example trigger phrases. The only soft spot is minor overlap risk with the related GitNexus skill family.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions ('analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos') with no gaps relative to the documented command set, matching the comprehensive-coverage anchor.	5 / 5
Completeness	An explicit 'Use when...' clause answers 'when', the enumerated commands answer 'what', and the 'Examples:' trigger phrases make both concrete, matching the top anchor.	5 / 5
Trigger Term Quality	Includes synonyms ('analyze/index') and explicit natural trigger phrases ('Index this repo', 'Reanalyze the codebase', 'Generate a wiki') that a user would actually say, satisfying comprehensive natural-term coverage.	5 / 5
Distinctiveness Conflict Risk	The GitNexus CLI niche and management verbs (index/clean/status/wiki/list) are distinct from the sibling GitNexus skills, but a closely related skill family exists and 'Reanalyze the codebase' sits adjacent to debugging/refactoring language, leaving minor overlap risk.	4 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: abhigyanpatwari/GitNexus
Path: .claude/skills/gitnexus-cli/SKILL.md
Commit: 4e51213

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.