CtrlK
BlogDocsLog inGet started
Tessl Logo

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?"

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A compact, well-structured reference skill with a clear entry workflow and tidy progressive disclosure. Its main gap is actionability: tool and resource tables describe outputs rather than showing how to call them.

Suggestions

Add a short "how to call" example for at least the core tools (e.g., a one-line `query` invocation with its key arguments) so guidance is copy-paste ready rather than descriptive.

Show one concrete `context` or `impact` resource/tool call alongside the Cypher example to lift actionability from descriptive to executable.

Consider noting required vs. optional tool parameters in the Tools Reference table so Claude can construct correct calls without external docs.

DimensionReasoningScore

Conciseness

Lean tables and tight one-line descriptions with no concept padding or explanations Claude already knows; every section earns its tokens. It does not reach a higher tier because the scale maxes at 3.

3 / 3

Actionability

Offers concrete references and one executable Cypher block plus a CLI command, but tool/resource rows summarize what each gives rather than full call signatures, leaving key usage details incomplete.

2 / 3

Workflow Clarity

The "Always Start Here" section gives a clear numbered sequence with an explicit validation checkpoint (index-freshness warning → run analyze), appropriate for this simple reference skill.

3 / 3

Progressive Disclosure

Under 50 lines with well-organized sections and no external bundle files needed; sibling-skill pointers are single-level and clearly signaled, matching the simple-skill guidance.

3 / 3

Total

11

/

12

Passed

Description

100%

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-crafted description that is specific, trigger-rich, complete, and distinctive. It cleanly answers what the skill covers and when Claude should invoke it using natural user language.

DimensionReasoningScore

Specificity

Names multiple concrete capability areas — "available tools", "how to query the knowledge graph", "MCP resources", "graph schema", "workflow reference" — matching the anchor for listing several specific actions.

3 / 3

Completeness

Explicitly answers both what it is (reference for GitNexus tools/resources/schema) and when to use it via an explicit "Use when..." clause, satisfying the top anchor.

3 / 3

Trigger Term Quality

Includes natural user phrasings ("What GitNexus tools are available?", "How do I use GitNexus?") and a plain "Use when the user asks about GitNexus itself" trigger, covering terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to "GitNexus itself" with product-specific triggers, giving it a clear niche unlikely to conflict with other skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mindfold-ai/Trellis
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.