CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 CLI reference with exact invocations, flags, and defaults throughout, plus reasonable sequencing and error-recovery guidance. Its weaknesses are verbosity in edge-case passages and missed opportunities to move dense digressions (watch behavior, provider config, storage retention) into separate reference files.

Suggestions

Trim or relocate the watch-mode internals paragraph (flag rejection list, MCP reopen throttling) and the npm 11.x install workarounds into a Troubleshooting or reference file, keeping only the one-line decision rule inline.

Move the wiki provider/model configuration table and the storage/retention env-var policy into separate one-level-deep reference files, leaving a short pointer per command section.

Give the `gitnexus auto-sync` command an actual invocation (or remove the mention), and add an explicit pre-check before the destructive `clean` command (e.g. run `status` first to confirm which index will be deleted).

DimensionReasoningScore

Conciseness

The content is tool-specific rather than explaining known concepts, but several passages are unnecessarily dense — the nine-line watch paragraph enumerates flag rejections, remote-sync semantics, and MCP reopen throttling in one block, and the npm 11.x crash note inlines four alternative install commands plus an issue link. These could be tightened or trimmed without losing actionable content.

3 / 5

Actionability

Every command is given as a copy-paste-ready invocation ("node .gitnexus/run.cjs analyze", "status", "clean", "wiki", "list") with flag tables that include defaults, env vars, and config file paths, covering all the common cases the description promises.

5 / 5

Workflow Clarity

"When to run" guidance, the numbered "After Indexing" steps ("Read gitnexus://repo/{name}/context to verify the index loaded" is an explicit validation checkpoint), and a Troubleshooting section with error-recovery advice give a clear sequence. The gap: the destructive `clean` command and the mentioned-but-never-specified `gitnexus auto-sync` lack validation or invocation detail, and some error paths (e.g. corrupt index) only imply the fix.

4 / 5

Progressive Disclosure

With no bundle files, everything is inline in one file; per-command sections, flag tables, and a troubleshooting section keep it navigable, and most content (flags, env vars) belongs next to its command. However, the 107-line body inlines digressions — watch internals, storage/retention policy, wiki provider configuration — that would fit better in one-level-deep reference files, which is a minor organization gap rather than a monolithic wall.

4 / 5

Total

16

/

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.

A strong description that clearly states capability and trigger conditions with natural example phrases and full command coverage. Its only weakness is that a couple of example triggers are generic enough to overlap with unrelated wiki-generation or code-analysis skills.

DimensionReasoningScore

Specificity

The description enumerates five concrete actions — "analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos" — which comprehensively covers the CLI's command surface rather than describing it abstractly.

5 / 5

Completeness

It explicitly answers both questions: what the skill does ("run GitNexus CLI commands like analyze/index... generate a wiki") and when to use it ("Use when the user needs to run GitNexus CLI commands"), reinforced with concrete example trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases are present and echoed verbatim ("Index this repo", "Reanalyze the codebase", "Generate a wiki"), matching how users actually phrase these requests; a few common synonyms like "reindex" or "build documentation" are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The named tool (GitNexus CLI) and its specific commands carve out a clear niche, but generic triggers like "Generate a wiki" or "Reanalyze the codebase" could plausibly fire for non-GitNexus documentation or code-analysis skills, creating minor overlap risk.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.