build-graph

Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.

Quality

75%

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 ./skills/build-graph/SKILL.md

Quality

Content

87%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 content is a tight, actionable, well-structured guide with concrete MCP calls and a clear sequence; its only meaningful gap is the absence of an error-recovery feedback loop around the batch build operation.

Suggestions

Add a feedback loop after the verify step, e.g., 'If errors are reported, address the failing files/patterns and re-run build_or_update_graph_tool() until list_graph_stats_tool reports no errors.'

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: concrete tool calls, parameters, and a short Notes section with no padding or explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	It gives fully executable, copy-paste-ready MCP tool calls with exact parameters for both the full build and incremental cases, plus a concrete verification call, covering the common scenarios.	5 / 5
Workflow Clarity	The three steps are clearly sequenced with a status-based branch and an explicit verify step, but a full graph build is a batch operation and the workflow lacks a feedback loop (no 'if errors, fix and re-run' guidance), which the rubric caps at 3.	3 / 5
Progressive Disclosure	At under 50 lines with no need for external references, the skill is well-organized into Steps / When to Use / Notes sections, qualifying for the top score under the simple-skill exception.	5 / 5
	Total	18 / 20 Passed

Description

62%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 clearly states what the skill does and gives a usable initialization trigger, but its trigger-term coverage is narrow and the 'when' guidance only addresses first-time setup rather than the broader use cases the body describes.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers (e.g., 'Use when setting up review for a new repo, after major refactoring, or when the graph is stale').

Include natural synonyms users might say ('code graph', 'review index', 'rebuild the graph') alongside 'knowledge graph' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('code review knowledge graph') and two core actions ('Build or update'), matching the anchor for 1-2 concrete actions without comprehensive coverage; the initialize/hooks phrases are usage modes rather than distinct capabilities.	3 / 5
Completeness	A clear 'what' ('Build or update the code review knowledge graph') is paired with an explicit 'when' ('Run this first to initialize'), but the when covers only initialization and could be more explicit about other trigger situations.	4 / 5
Trigger Term Quality	Relevant terms ('build', 'update', 'knowledge graph', 'initialize') appear but are somewhat technical and lack common synonyms or variations a user might naturally say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'code review knowledge graph' niche is specific and largely distinct, with only minor overlap risk against general code-indexing skills, fitting the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: tirth8205/code-review-graph
Path: skills/build-graph/SKILL.md
Commit: b586687

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.