gitnexus-explorer

Index a codebase with GitNexus and serve an interactive knowledge graph via web UI + Cloudflare tunnel.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/research/gitnexus-explorer/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clearly sequenced, validated workflow, but it wastes tokens by inlining the proxy script that already ships as a bundle file and never points the reader to that bundle.

Suggestions

Replace the inlined proxy.mjs in Step 4 with a one-line reference to the bundle, e.g. 'Use the provided `scripts/proxy.mjs` (run `node $GITNEXUS_DIR/proxy.mjs ...`)', keeping only the usage invocation inline.

Reconcile the inlined copy with scripts/proxy.mjs — the bundle version has SPA-fallback and host-header fixes the inline copy lacks, so they currently diverge.

Trim justification prose such as 'same origin, no CORS issues, no sudo, no nginx' to the essential 'serves web UI and proxies /api/* to the backend'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven, but it inlines the full ~45-line proxy.mjs that already exists as a bundle file (duplication) and includes minor justifications like 'same origin, no CORS issues, no sudo, no nginx', so it could be tightened.	2 / 3
Actionability	Provides fully executable bash commands, exact file paths with before/after TypeScript patches, and a complete proxy script — copy-paste ready, matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	A clear 7-step sequence with an explicit validation checkpoint ('Verify: curl -s http://localhost:8888/api/repos should return the indexed repo(s)'), an upfront size warning, and a cleanup step — above the 'validation gaps' anchor.	3 / 3
Progressive Disclosure	Sections are well-organized, but the proxy script that belongs in the scripts/proxy.mjs bundle is inlined in the body while the bundle file is never signaled or referenced, fitting 'content that should be separate is inline' and references not clearly signaled.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 clearly states what the skill does and occupies a distinct niche, but it omits explicit 'when to use' trigger guidance and leans on product jargon over natural user phrasing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to visually explore a codebase's architecture or share an interactive knowledge/dependency graph of a repo.'

Soften jargon by adding natural synonyms users would say — 'codebase explorer', 'dependency graph', 'call graph', 'architecture visualization' — alongside 'GitNexus'.

Reorder so the natural-language trigger ('Use when ...') follows the capability sentence, mirroring the rubric's good examples.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Index a codebase', 'serve an interactive knowledge graph', 'via web UI', 'Cloudflare tunnel' — matching the anchor for listing several specific concrete actions rather than a single vague domain.	3 / 3
Completeness	The 'what' is explicit ('Index a codebase ... serve an interactive knowledge graph') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	'codebase' and 'knowledge graph' are natural user terms, but 'GitNexus' and 'Cloudflare tunnel' are product/jargon and common variations like 'explore architecture' or 'dependency graph' are missing, so it lands at 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The GitNexus knowledge-graph-visualization niche is specific and unlikely to trigger for the wrong skill, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/research/gitnexus-explorer/SKILL.md
Commit: 4c9628e

Reviewed: about 15 hours 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.