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

80%

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

Quality

Content

68%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 command reference with executable blocks and flag tables for every command. Weakest on the dense, version-specific troubleshooting inline at the top and the lack of a validation checkpoint around the destructive `clean` command.

Suggestions

Move the npm 11.x / `Cannot find module` troubleshooting into the Troubleshooting section (or a dedicated old-patterns note) so the version-sensitive detail does not pad the intro and is easier to retire later.

Add an explicit validation checkpoint for `clean` — e.g. run `status` first to confirm what will be removed, and verify the repo is unregistered afterward — to satisfy the destructive-operation workflow cap.

Tighten the runner-selection paragraph in the intro; the auto-selection logic is useful but can be stated more briefly now that each command block shows the canonical invocation.

Dimension	Reasoning	Score
Conciseness	Mostly lean command reference with no padding about what GitNexus is, but the top blockquote inlines dense version-specific troubleshooting ("npm 11.x", "node.target is null", a long pnpm invocation) that could be tightened and is time-sensitive without being placed in a deprecated/old-patterns section.	3 / 5
Actionability	Every command ships as a copy-paste-ready bash block ("node .gitnexus/run.cjs analyze", etc.) with flag tables and concrete defaults ("--model <model>" default minimax/minimax-m2.5), covering the common cases fully.	5 / 5
Workflow Clarity	Per-command "When to run" guidance and an explicit verify step after indexing ("Read gitnexus://repo/{name}/context to verify the index loaded") are present, but the destructive `clean` operation has no validation/verification checkpoint, so the destructive-operation cap applies.	3 / 5
Progressive Disclosure	Well-organized into clear sections (Commands, After Indexing, Troubleshooting) with no nested references and no bundle files; content is appropriately self-contained, though it exceeds the ~50-line simple-skill threshold so it stops short of a 5.	4 / 5
	Total	15 / 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.

A strong, third-person description that concretely enumerates the CLI's commands and pairs them with natural example trigger phrases, clearly answering both what and when. Minor room only for broader synonym coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple 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 capabilities rather than vague language.	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..."), reinforced with concrete example trigger phrases.	5 / 5
Trigger Term Quality	Provides natural user phrases ("Index this repo", "Reanalyze the codebase", "Generate a wiki") plus the command verbs, but stops short of exhaustive synonyms/extensions; a few natural variations are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to a named tool ("GitNexus CLI") with command-specific triggers, giving it a clear niche and minimal overlap with other skills.	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: tslateman/spec-trace
Path: .claude/skills/gitnexus/gitnexus-cli/SKILL.md
Commit: fa5c435

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.