Name: gitnexus-cli
Rating: 72 (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

88%

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

76%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.

An actionable, well-structured CLI command reference with concrete commands and flag tables. Its main weaknesses are a verbose `--watch`/troubleshooting section and the lack of an explicit validation checkpoint before the destructive `clean` operation.

Suggestions

Add an explicit verification step before `clean` (e.g., run `status` first and confirm with the user) so the destructive operation has a validation checkpoint.

Trim the `--watch` paragraph by moving the inline list of rejected flags into a small table, and condense the npm 11.x workaround alternatives.

Consider splitting the per-command flag tables and troubleshooting into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concept over-explanation, but the dense `--watch` paragraph (inline list of rejected flags) and the npm 11.x troubleshooting with multiple alternative install commands could be tightened.	4 / 5
Actionability	Provides concrete copy-paste commands (`node .gitnexus/run.cjs analyze`) plus complete flag and environment-variable tables, covering the common cases directly.	5 / 5
Workflow Clarity	A verify step exists in "After Indexing" (read context to confirm the index loaded), but the destructive `clean` command has no explicit validation checkpoint before deletion, capping this dimension.	3 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized into clear sections (Commands, Index storage, After Indexing, Troubleshooting) with no nested references, though the long flag tables and troubleshooting could live in separate reference files.	4 / 5
	Total	16 / 20 Passed

Description

100%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 names concrete actions, includes natural trigger examples, and explicitly covers both what the skill does and when to use it. It is concise without padding and clearly distinguishable from other skills.

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.	5 / 5
Completeness	Explicitly answers both what (run GitNexus CLI commands) and when ("Use when the user needs to run GitNexus CLI commands like…") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrasings appear in the examples ("Index this repo", "Reanalyze the codebase", "Generate a wiki") alongside command-verb synonyms ("analyze/index"), matching how a user would actually ask.	5 / 5
Distinctiveness Conflict Risk	Scoped to a named tool (GitNexus CLI) with tool-specific triggers, occupying a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	20 / 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: 5be80b1

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.