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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

80%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 highly actionable with copy-paste-ready commands and well-organized into a clean single-file structure. The main weakness is workflow clarity: destructive (clean) and batch (analyze) operations lack explicit validation checkpoints, which the rubric caps at 3.

Suggestions

Add an explicit validation step to the clean workflow (e.g., run `status` before/after to confirm the index was removed) and to analyze (e.g., run `status` or read `gitnexus://repo/{name}/context` to verify the rebuild succeeded).

Tighten the npm 11.x troubleshooting parenthetical — the version-specific fallback commands are useful but the surrounding clause is dense; consider a compact "If npx crashes on npm 11.x" sub-bullet.

Consider a short ordered workflow at the top (status → analyze → verify context → use exploring/debugging skills) so the relationship between commands is explicit rather than implied across sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — command blocks, flag tables, and "When to run" notes that assume Claude's competence — but the dense npm 11.x troubleshooting parenthetical and a few explanatory clauses could be trimmed slightly, keeping it just below the score-5 anchor.	4 / 5
Actionability	Every command is a copy-paste-ready `node .gitnexus/run.cjs <command>` block and flags are documented in tables with concrete effects, covering all common cases (analyze, status, clean, wiki, list), matching the score-5 anchor.	5 / 5
Workflow Clarity	The destructive `clean` command (deletes the index) and the long batch `analyze` operation lack explicit validation checkpoints tying the workflow together; per the rubric, missing validation for destructive/batch operations caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The skill is self-contained with no bundle files, well-organized into clear sections (Commands, After Indexing, Troubleshooting), and single-purpose, so the well-organized-sections exception applies and it scores 5.	5 / 5
	Total	17 / 20 Passed

Description

92%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 specific, complete, and distinctive — it names concrete actions, provides explicit "Use when" trigger guidance with natural example phrases, and targets a clear tool niche. The only minor gap is trigger-term synonym coverage, which keeps trigger_term_quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions — "analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos" — giving comprehensive coverage of the CLI's command set, matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers both what ("run GitNexus CLI commands like analyze/index...") and when ("Use when the user needs to run GitNexus CLI commands...") with concrete trigger example phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ("Index this repo", "Reanalyze the codebase", "Generate a wiki") that users would actually say, but synonym coverage is good rather than exhaustive, placing it just below the score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	"GitNexus CLI" carves a clear niche with tool-specific triggers ("Index this repo", "Reanalyze the codebase") and minimal overlap risk with other skills, matching the score-5 anchor.	5 / 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: mindfold-ai/Trellis
Path: .claude/skills/gitnexus/gitnexus-cli/SKILL.md
Commit: 64e6636

Reviewed: 5 days 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.