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

65%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/gitnexus/gitnexus-guide/SKILL.md

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.

The body is an efficient, well-structured reference with concrete tool-call examples and a clear entry-point workflow including a validation checkpoint, with only minor gaps in per-tool call examples and some detailed inline sections that could be split out.

Dimension	Reasoning	Score
Conciseness	The body is a lean, table-driven reference that assumes Claude's competence and avoids explaining basic concepts, though the multi-block pagination walkthrough (jsonc + text examples) could be trimmed slightly.	4 / 5
Actionability	It gives concrete, copy-paste-ready tool invocations (list_repos, explain, pdg_query, trace, cypher) for the complex tools, but several table-listed tools (query, context, impact, rename) are described functionally without call-syntax examples.	4 / 5
Workflow Clarity	The 'Always Start Here' section gives a clear 3-step sequence with an explicit staleness validation checkpoint and remediation command, missing only a fuller checklist/feedback loop for a 5.	4 / 5
Progressive Disclosure	Content is well-organized with section headers and tables, and pointers to sibling skills/resources are one level deep and clearly signaled via the Skills table; the inline deep-dive sections (taint, pdg) are borderline for an overview guide but appropriate to its purpose.	4 / 5
	Total	16 / 20 Passed

Description

55%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 has excellent natural trigger phrases and a clear niche, but it omits any explicit statement of what the skill does, leaving the 'what' half of completeness unspecified and capabilities only minimally described.

Suggestions

Add an explicit 'what' clause stating what the skill provides, e.g. 'Reference guide to GitNexus MCP tools, resources, and the knowledge graph schema.'

Replace topic nouns with concrete action verbs (e.g. 'Looks up', 'References', 'Explains') so capabilities read as actions rather than query categories.

Disambiguate "How do I use GitNexus?" from sibling skills by scoping it to meta/tool-reference questions (e.g. 'Use when the user asks about GitNexus itself — its tools, resources, or schema — not when debugging or refactoring a specific repo').

Dimension	Reasoning	Score
Specificity	The description names the GitNexus domain and several sub-topics ("available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference") but uses no concrete action verbs describing what the skill does, leaving capabilities minimal/generic.	2 / 5
Completeness	Only the 'when' is present ("Use when the user asks about GitNexus itself...") with no explicit 'what' statement of what the skill does or produces, matching the 'only when present without what' anchor.	2 / 5
Trigger Term Quality	It includes explicit natural trigger phrases users would actually say ("What GitNexus tools are available?", "How do I use GitNexus?") plus a broad topic list, giving comprehensive coverage of natural terms.	5 / 5
Distinctiveness Conflict Risk	The "asks about GitNexus itself" trigger carves a clear niche distinct from sibling skills, but "How do I use GitNexus?" has minor overlap risk with the related gitnexus-cli/exploring skills.	4 / 5
	Total	13 / 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-guide/SKILL.md
Commit: 8f0cb39

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