gitnexus-guide

Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"

Quality

83%

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

82%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 lean, highly actionable reference skill with concrete tool-call examples and a clear entry-point workflow. Structure is sound; the main opportunity is offloading the longer per-tool explanations into reference files to keep the overview tighter.

Suggestions

Move the extended per-tool explanations (e.g. the taint/PDG and staleness subsections) into separate reference files and link to them from the Tools table to tighten the overview.

Add a short validation/verification note for the cross-repo and rename operations that can produce large diff sets, so blast-radius results can be sanity-checked before acting.

Consider a brief "common pitfalls" line per hot tool (e.g. ambiguous-name disambiguation) to reduce retry loops.

Dimension	Reasoning	Score
Conciseness	Dense, table-driven reference content with minimal padding; the prose sections (staleness, taint findings) explain non-obvious behavior and earn their tokens, with only minor tightening opportunities.	4 / 5
Actionability	Provides copy-paste-ready tool invocations with concrete parameters (e.g. `trace { from: "validateUser", to: "executeQuery" }`), real JSON response shapes, and a runnable Cypher example covering common cases.	5 / 5
Workflow Clarity	The "Always Start Here" section gives a clear 3-step sequence with an explicit freshness validation checkpoint (read context, then run analyze if stale); as a reference doc rather than a destructive workflow it lacks deeper error-recovery loops.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Tools, Resources, Schema) with one-level-deep pointers to sibling skills and gitnexus:// resources; no nested references, though some tool detail could be split into bundled reference files.	4 / 5
	Total	17 / 20 Passed

Description

83%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 well-constructed description that clearly states both purpose and trigger conditions with natural example phrases. Minor room to add synonym variations and sharper action verbs.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas — "available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference" — going beyond a single action, though framed as topics the user asks about rather than actions the skill performs.	4 / 5
Completeness	Explicitly answers both "what" (a reference for tools, resources, schema) and "when" ("Use when the user asks about GitNexus itself...") with concrete example trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases and quoted examples ("What GitNexus tools are available?", "How do I use GitNexus?") map well to what a user would say, though synonym/extension coverage is limited to the GitNexus name itself.	4 / 5
Distinctiveness Conflict Risk	The "about GitNexus itself" scoping carves a clear niche distinct from sibling task skills, with minor overlap risk against the other gitnexus-* skills it references.	4 / 5
	Total	17 / 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-guide/SKILL.md
Commit: c6b2416

Reviewed: 2 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.