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

81%

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-guide in abhigyanpatwari/GitNexus

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 well-structured, actionable reference guide that earns its length with GitNexus-specific tool behavior and concrete invocations. It is efficient but not fully lean, and a few detailed subsections could be offloaded to bundled files for tighter progressive disclosure.

Suggestions

Tighten the longest prose paragraphs (the `explain` caveats and `list_repos` pagination notes) into terse bullet points so every sentence earns its place.

Move the detailed `trace` and pagination walkthroughs into a bundled reference file, keeping SKILL.md as a lean overview with one-line summaries and a clear link.

Replace placeholder `target: "..."` arguments in example invocations with realistic concrete values so examples are copy-paste ready.

Dimension	Reasoning	Score
Conciseness	A dense, mostly lean reference that avoids explaining concepts Claude already knows, but a few long prose sentences (e.g., the explain caveats and the pagination notes) could be tightened without losing information.	4 / 5
Actionability	Provides concrete, parameterized invocations (e.g., `trace { from: "validateUser", to: "executeQuery" }`, `pdg_query { mode: "controls", target: "..." }`) and a runnable Cypher example, with minor gaps from placeholder `"..."` targets that are not copy-paste ready.	4 / 5
Workflow Clarity	The "Always Start Here" 3-step sequence with a staleness check (run `analyze` if the index is stale) gives a clear navigation flow with a checkpoint; not a 5 because the recovery loop is implicit rather than a validate-fix-retry cycle.	4 / 5
Progressive Disclosure	Well-organized into clearly signaled sections with one-level references (skill files in the routing table, `gitnexus://repo/{name}/schema`, and a pointer to the `gitnexus-pdg-query` skill), though some detailed subsections (trace, pagination) are inlined where a separate file could carry the bulk.	4 / 5
	Total	16 / 20 Passed

Description

87%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 pairs an explicit Use-when trigger with concrete example queries and a well-scoped GitNexus niche. The only soft spot is framing coverage as topics rather than explicit actions.

Dimension	Reasoning	Score
Specificity	Names the GitNexus domain and lists several concrete capability areas ("available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference"), though framed as topics the user asks about rather than verbs the skill performs, leaving a minor gap versus the most action-explicit anchor.	4 / 5
Completeness	Explicitly answers both what (the five reference areas) and when via a "Use when the user asks about..." clause with concrete example trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural keyword coverage ("GitNexus", "available tools", "query the knowledge graph", "MCP resources", "graph schema") plus two verbatim user-style example queries, though a few synonymous phrasings a user might say are not enumerated.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to "GitNexus itself" with tool-specific triggers, giving it a clear niche and minimal overlap with other skills.	5 / 5
	Total	18 / 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-guide/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.