knowledge-graph
Three-Layer Memory System — automatic fact extraction, entity-based knowledge graph, and weekly synthesis. Manages life/areas/ entities with atomic facts and living summaries.
Install with Tessl CLI
npx tessl i github:jdrhyne/agent-skills --skill knowledge-graph56
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
17%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 explains the technical architecture of a memory system but fails to communicate when Claude should use it or what user requests would trigger it. It uses internal/technical terminology rather than natural language users would employ, making skill selection difficult.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms like 'remember this', 'what do I know about', 'track information about [person/project]', 'personal notes'
Replace technical jargon with user-facing actions: instead of 'atomic facts and living summaries', say 'stores facts about people, projects, and topics; generates periodic summaries'
Include natural keywords users would say: 'remember', 'recall', 'notes', 'personal knowledge', 'track', 'information about'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (memory system) and some actions (fact extraction, knowledge graph, weekly synthesis), but the actions are somewhat abstract rather than concrete user-facing operations like 'create', 'update', 'query'. | 2 / 3 |
Completeness | Describes what the system is (three-layer memory) but lacks any explicit 'Use when...' clause or trigger guidance. The 'when' is entirely missing. | 1 / 3 |
Trigger Term Quality | Uses technical jargon ('entity-based knowledge graph', 'atomic facts', 'living summaries') that users would not naturally say. Missing natural terms like 'remember', 'notes', 'track', 'personal information'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'life/areas/ entities' path and 'three-layer' structure provide some distinctiveness, but 'memory system' and 'knowledge graph' could overlap with other note-taking or knowledge management skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflows and concrete examples. The main weakness is length—it includes motivational explanations and inline configuration blocks that could be externalized. The fact schema and task procedures are excellent, providing copy-paste ready implementations.
Suggestions
Move the AGENTS.md and HEARTBEAT.md snippet blocks to a separate SETUP.md or TEMPLATES.md file to reduce main skill length
Remove the 'Why This Matters' section and 'The Compounding Flywheel' ASCII diagram—these explain benefits Claude can infer
Consider moving the full cron YAML configuration to a separate reference file, keeping only a brief mention in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanations (e.g., 'Every conversation makes your agent smarter' motivational text, the 'Why This Matters' section explaining obvious benefits). The architecture overview could be tighter. | 2 / 3 |
Actionability | Provides fully executable bash commands, complete JSON schemas, and copy-paste ready code blocks for creating entities, setting up directories, and configuring cron jobs. The fact schema and task procedures are concrete and specific. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly numbered with explicit sequences. The fact extraction and weekly synthesis tasks have clear step-by-step workflows. The supersession pattern includes explicit validation (check existing facts, mark old as superseded). | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (~200 lines) and could benefit from splitting detailed setup instructions or the full AGENTS.md blocks into separate reference files. The inline YAML and markdown blocks add bulk. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- 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.