CtrlK
BlogDocsLog inGet started
Tessl Logo

gitnexus-exploring

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exceptionally tight, action-oriented body: executable tool calls and resource URIs, an explicit staleness validation loop, and a worked example, all with no filler. Progressive disclosure is appropriately handled inline given the skill's modest size and absence of bundle files.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence throughout, with no padding or explanation of basic concepts; every section (workflow, checklist, resources, tools, example) earns its place with concrete syntax.

5 / 5

Actionability

Guidance is fully executable: real tool calls (list_repos, query, context), real resource URIs (gitnexus://repo/{name}/process/{name}), a concrete re-analyze command, and a worked end-to-end example with actual symbol names.

5 / 5

Workflow Clarity

A numbered workflow, a checkpoint checklist, an explicit staleness validation/decision rule ('Re-analyze only for behind or diverged'), and a fallback (stop and ask when the repo is ambiguous) provide clear sequencing with feedback loops for error recovery.

5 / 5

Progressive Disclosure

No bundle files exist; the skill is under 100 lines and well-organized into clearly headed sections (When to Use, Workflow, Checklist, Resources, Tools, Example) with no nested references, fitting the simple-skill exception for a 5.

5 / 5

Total

20

/

20

Passed

Description

70%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 solid, well-structured description with explicit 'Use when' guidance and concrete example trigger phrases. It is slightly thin on enumerating specific concrete actions and has minor overlap risk with general code-comprehension skills.

DimensionReasoningScore

Specificity

Description names the domain (codebase exploration) and one concrete action ('explore unfamiliar parts of the codebase') with execution-flow tracing implied, but coverage of concrete actions is limited rather than comprehensive.

3 / 5

Completeness

Clearly answers 'what' (understand architecture, trace execution flows, explore codebase) and provides an explicit 'Use when...' trigger with concrete example phrases; 'when' is explicit and concrete.

4 / 5

Trigger Term Quality

Includes natural user phrasings via direct examples ('How does X work?', 'What calls this function?', 'Show me the auth flow') covering common query forms, missing only a few synonyms.

4 / 5

Distinctiveness Conflict Risk

The gitnexus-specific framing and execution-flow/caller tracing examples give it a clear niche with mostly distinct triggers, though generic 'how does X work' phrasing has minor overlap with general code skills.

4 / 5

Total

15

/

20

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
abhigyanpatwari/GitNexus
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.