CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

build-graph

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

Quality

88%

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

93%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 body is a tight, executable guide with concrete tool calls and a clear conditional workflow. The only gap is an explicit error-recovery loop in the reporting step.

DimensionReasoningScore

Conciseness

The ~27-line body is lean and assumes Claude's competence, with concrete tool calls and no padding or explanation of known concepts, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Provides fully executable, copy-paste-ready tool calls with exact arguments (e.g., build_or_update_graph_tool(full_rebuild=True)) covering first build, full, and incremental cases, matching the 5 anchor.

5 / 5

Workflow Clarity

Steps are clearly sequenced with a state check and status report (ok/partial/error) as a checkpoint, but no explicit error-recovery feedback loop, fitting the 4 anchor rather than the validate-and-retry 5.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and well-organized into Steps, When to Use, and Notes sections, satisfying the simple-skill exception for a 5.

5 / 5

Total

19

/

20

Passed

Description

78%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 concisely communicates a specific niche and both what the skill does and when to use it. Trigger phrases are present but could be made more explicit with a 'Use when...' formulation.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when setting up code review for a repository or after a large refactor') to lift completeness toward 5.

Include a synonym or extension-style trigger term (e.g., 'knowledge graph', 'code map') to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names several concrete actions — 'Build or update the code review knowledge graph' and 'Run this first to initialize' — with only minor gaps in coverage, fitting the 'lists several specific actions' anchor rather than the comprehensive 5.

4 / 5

Completeness

Clearly states what ('Build or update the code review knowledge graph') and when ('Run this first to initialize, or let hooks keep it updated automatically'), but the trigger guidance could be more explicit, matching the 4 anchor rather than a concrete 'Use when...' 5.

4 / 5

Trigger Term Quality

Good keyword coverage ('code review knowledge graph', 'initialize', 'hooks') but missing common synonyms or file extensions, so it sits below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche ('code review knowledge graph') with distinct triggers and minimal overlap risk with other skills, matching the 5 anchor.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.