CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ac-knowledge-graph

Manage knowledge graph for autonomous coding. Use when storing relationships, querying connected knowledge, building project understanding, or maintaining semantic memory.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/ac-knowledge-graph/SKILL.md

The canonical home for this skill is ac-knowledge-graph in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, well-structured overview for a simple code-backed skill: a concrete Quick Start and a correctly placed one-level reference to the implementation script. The remaining gaps are a redundant Purpose line and a Quick Start that is not fully self-contained (undefined project_dir, missing initialize() for loading existing graphs).

Suggestions

Delete or merge the Purpose section; it repeats the opening line ('Build and query knowledge graphs for project understanding') almost verbatim.

Make the Quick Start copy-paste ready: define project_dir (e.g., Path.cwd()), show an async context or note the await requirement, and mention calling initialize() to load an existing graph.

State persistence behavior in one line (e.g., 'Graph persists to .claude/knowledge-graph.json; query(entity, depth=N) traverses relations'), so users don't need to open the script for these key facts.

DimensionReasoningScore

Conciseness

The body is lean with well-chosen code and no padding, but the Purpose line 'Maintains a knowledge graph of project concepts, relationships, and learnings...' substantially duplicates the opening line 'Build and query knowledge graphs for project understanding' and the frontmatter description. That minor redundancy is exactly the level 4 anchor's 'minor instances that could be trimmed', keeping it below level 5's 'every token earns its place'.

4 / 5

Actionability

The Quick Start gives a concrete, mostly executable usage sequence (instantiate, add_entity, add_relation, query) covering the common path. It is not copy-paste ready: 'project_dir' is undefined, top-level 'await' has no async context, and 'initialize()' for loading an existing graph is never shown — minor gaps matching level 4 rather than level 5.

4 / 5

Workflow Clarity

As a simple single-purpose skill, the Quick Start's linear usage pattern is unambiguous for the happy path. However, the workflow omits how to load an existing graph (initialize()), where data persists (.claude/knowledge-graph.json), and the query depth option — minor gaps consistent with level 4 rather than a fully self-contained level 5.

4 / 5

Progressive Disclosure

The body is under 50 lines, single-task, and organized into clear sections (Purpose, Quick Start, API Reference), with a real, clearly signaled one-level-deep reference to scripts/knowledge_graph.py (verified to exist in the bundle) that appropriately holds the bulk implementation. Per the rubric's simple-skill scoring note and the level 5 anchor, this is a clear overview with well-signaled one-level references and easy navigation.

5 / 5

Total

17

/

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 description with an explicit and concrete 'Use when' clause and natural trigger keywords. Its main weakness is a generic one-verb capability statement ('Manage') rather than an enumeration of concrete actions, which limits specificity and completeness.

Suggestions

Replace the generic headline verb 'Manage' with concrete capability verbs, e.g., 'Store entities and relations in a project knowledge graph, and query connected concepts across depth levels.'

Add natural trigger synonyms users might say, such as 'entities', 'concept map', or 'linking related code', to broaden keyword coverage.

Consider naming the persistence format/location (e.g., '.claude/knowledge-graph.json') to sharpen both what the skill does and its distinctiveness.

DimensionReasoningScore

Specificity

The headline capability is the single generic verb "Manage knowledge graph for autonomous coding", matching the anchor that names the domain with limited concrete actions. Concrete actions like "storing relationships, querying connected knowledge" appear only inside the trigger clause and are semi-abstract ("building project understanding"), so it does not reach the 'several specific actions' of level 4.

3 / 5

Completeness

Both parts are present: "what" ("Manage knowledge graph for autonomous coding") and an explicit "Use when..." clause with concrete trigger phrases. The 'what' rests on one generic verb rather than comprehensively stating capabilities, so it does not clearly match the level 5 anchor.

4 / 5

Trigger Term Quality

"storing relationships", "querying connected knowledge", "semantic memory", and "knowledge graph" are natural phrases a user would plausibly say, giving good keyword coverage. A few common variations (e.g., "entities", "concept map", "linking related code") are missing, so it falls just short of comprehensive level 5.

4 / 5

Distinctiveness Conflict Risk

"knowledge graph" and "semantic memory" carve out a fairly distinct niche with domain-specific triggers. There is minor overlap risk with general memory/notes-management skills via "maintaining semantic memory", keeping it below level 5.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fernandezbaptiste/Skrillz

Path

.claude/skills/ac-knowledge-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.