CtrlK
BlogDocsLog inGet started
Tessl Logo

gitnexus-pdg-query

Use when querying or extending GitNexus's PDG control/data-dependence surface (the `pdg_query` MCP tool, CDG/REACHING_DEF edges), or reasoning about "what controls X" / "where does Y flow" / guard clauses. Examples: "what guards this statement?", "trace this variable within the function", "why is the pdg_query result empty?", "add a CDG query".

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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 dense, actionable reference that gives copy-paste Cypher, exact tool signatures, and the specific off-by-one and edge-table gotchas a maintainer needs. It loses a point only on workflow_clarity and progressive_disclosure because it is a single-file read-only reference rather than a multi-step workflow with external references.

DimensionReasoningScore

Conciseness

Dense, expert-grade prose that assumes competence — references "Ferrante control dependence (post-dominators)", "GEN/KILL def→use", and WAL/meta-probe internals with no boilerplate explanation of what a graph or dependency is; every line is load-bearing.

5 / 5

Actionability

Provides a copy-paste-ready Cypher query, concrete `pdg_query({ mode: 'controls', target })` / `{ mode: 'flows', target, variable? }` invocations, exact source file (`gitnexus/src/mcp/local/local-backend.ts`, `_pdgQueryImpl`), and precise off-by-one corrections (1-based block vs 0-based symbol lines, `+1` on both bounds).

5 / 5

Workflow Clarity

Clear structure — build order (L1/L2/L5), the two modes, the corrected guard-clause Cypher, and a load-bearing gotchas list — but it is a read-only query reference rather than a multi-step destructive workflow, so explicit validation checkpoints do not apply; the no-layer "note, not an error" handling is the closest thing to a verification step.

4 / 5

Progressive Disclosure

A single self-contained, well-sectioned SKILL.md (~85 lines) with clear headers and no external bundle files; content is appropriately kept inline for a focused reference, sitting just above the under-50-line simple-skill threshold so it does not quite reach a 5.

4 / 5

Total

18

/

20

Passed

Description

95%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 tightly-scoped, trigger-rich description that clearly states both capability and invocation conditions using natural user phrasing. Its only minor gap is that the action list is good but not exhaustively comprehensive.

DimensionReasoningScore

Specificity

Names the domain ("PDG control/data-dependence surface", "the `pdg_query` MCP tool", "CDG/REACHING_DEF edges") and several concrete actions ("querying or extending", "reasoning about... guard clauses"), but stops just short of the comprehensive multi-action list of a 5.

4 / 5

Completeness

Explicitly answers both what (querying/extending the PDG control/data-dependence surface via pdg_query, CDG/REACHING_DEF edges) and when ("Use when..." with concrete trigger examples), matching the anchor for a clear what-and-when with trigger phrases.

5 / 5

Trigger Term Quality

Embeds the exact natural phrases a user would say — "what guards this statement?", "trace this variable within the function", "why is the pdg_query result empty?", "add a CDG query" — plus the generic "what controls X" / "where does Y flow" forms.

5 / 5

Distinctiveness Conflict Risk

Scoped to GitNexus's PDG/CDG/REACHING_DEF niche with highly specific trigger phrases, making overlap with unrelated skills minimal.

5 / 5

Total

19

/

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.