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

Passed

No findings from the security scan

Quality

Content

83%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 a tight, command-driven reference: each subcommand is shown with executable syntax and a flag table, plus clear when-to-run notes, an after-indexing checklist, and troubleshooting. It earns high marks on actionability and structure, with only minor conciseness padding and a small validation gap around the destructive clean operation.

Dimension	Reasoning	Score
Conciseness	Mostly lean command tables and short notes that assume Claude's competence, with minor over-explanation such as the lengthy npm 11.x / pnpm fallback paragraph and the trailing troubleshooting bullets that could be trimmed.	4 / 5
Actionability	Every command is given as a copy-paste-ready bash invocation (e.g. `node .gitnexus/run.cjs analyze`) with per-flag effect tables, fully executable guidance.	5 / 5
Workflow Clarity	Commands are clearly sequenced with an "After Indexing" checklist and troubleshooting section, and validation is addressed via status freshness checks; however the `clean` destructive operation has a `--force` skip but no explicit validate-before-clean checkpoint, leaving a minor gap.	4 / 5
Progressive Disclosure	Well-organized into command sections with flag tables and a separate After Indexing / Troubleshooting structure; for a self-contained skill with no bundle files this is good organization, though no one-level-deep external references are used.	4 / 5
	Total	17 / 20 Passed

Description

88%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 concise yet comprehensive: it names five concrete operations, gives third-person voice, and includes a clear "Use when..." clause with three example trigger phrases. It is well above the midpoint on every dimension, with only minor room to add synonyms 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"—mapping to actual commands, giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (the five CLI operations) and when (a clear "Use when..." clause with concrete example trigger phrases).	5 / 5
Trigger Term Quality	Natural trigger phrases like "Index this repo", "Reanalyze the codebase", "Generate a wiki" are good, but lacks synonyms and only surfaces three example phrasings, leaving some common variations uncovered.	4 / 5
Distinctiveness Conflict Risk	Scoped to a named tool (GitNexus CLI) with distinct trigger phrases, making overlap with unrelated skills minimal.	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/praxis
Path: .claude/skills/gitnexus/gitnexus-cli/SKILL.md
Commit: 8f0cb39

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.