CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

personal-knowledge-routing

Route durable personal context and reusable knowledge between Arnesto and the personal knowledge vault. Use when the user asks to remember, persist, capture, retrieve, or organize personal knowledge; when deciding whether information belongs in rules, skills, portfolio, notes, maps, or inbox; or when using personal-knowledge-vault as a low-context reference layer.

Quality

85%

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

86%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 lean, highly actionable routing skill: exact paths, a precise decision table, explicit validation checkpoints, and concrete defaults for common requests. The only notable gaps are minor duplication between the routing table and persistence rules and the absence of an error-recovery loop for failed `make check` runs.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence, with no explanations of known concepts and exact paths throughout. A few Persistence Rules restate Routing Table entries ("Keep raw conversations out of `portfolio/`", "Put uncertain or still-evolving material in `notes/` or `inbox/` first"), which is minor duplication that keeps it below the lean score-5 anchor while well above score 3.

4 / 5

Actionability

Guidance is fully concrete for an instruction-only skill: exact repository paths, a routing table mapping each information type to a precise destination, a copy-paste command ("run `make check` from `/Users/saski/Code/personal-knowledge-vault`"), and a Good Defaults section covering common cases ("For 'remember this about me': propose a concise `portfolio/` update"). Specific examples cover the common cases, matching the score-5 anchor.

5 / 5

Workflow Clarity

A clear reading sequence ("First Files To Read" steps 1-6) and routing flow with explicit validation checkpoints ("Before writing an Obsidian wikilink, verify that the target note exists", "After vault edits, run `make check`"). It is not score 5 because there is no error-recovery feedback loop describing what to do when `make check` fails, and the vault edits are not a destructive/batch operation requiring the score-3 cap.

4 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well-organized into clear sections (Repositories, First Files To Read, Routing Table, Persistence Rules, Context Discipline, Link Discipline, Good Defaults). References to vault files ("vault/AGENT_GUIDE.md", "vault/_meta/conventions.md") are one level deep, clearly signaled, and point to an external system the skill navigates rather than nested skill content.

5 / 5

Total

18

/

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.

A strong description with explicit what/when structure and natural trigger phrases anchored to two named systems. Its main weakness is that it expresses a single routing capability rather than enumerating several concrete actions, leaving specificity below top level.

Suggestions

Enumerate the distinct capabilities as separate concrete verbs (e.g., route, promote between inbox/notes/portfolio, index navigation maps, validate vault links) instead of a single "Route..." statement, to raise specificity.

Add common natural synonyms such as "save this", "note this", or "keep this" alongside remember/persist/capture to broaden trigger term coverage.

DimensionReasoningScore

Specificity

"Route durable personal context and reusable knowledge between Arnesto and the personal knowledge vault" names the domain and one core action, with destinations enumerated, but does not list several distinct concrete capabilities. It exceeds the score-2 anchor (bare domain name) but falls short of the score-4 anchor, which expects several specific actions listed.

3 / 5

Completeness

It explicitly answers what ("Route durable personal context and reusable knowledge between Arnesto and the personal knowledge vault") and when, with three concrete trigger conditions ("Use when the user asks to remember, persist, capture, retrieve, or organize personal knowledge; when deciding whether information belongs in rules, skills, portfolio, notes, maps, or inbox; or when using personal-knowledge-vault as a low-context reference layer"). This matches the score-5 anchor pattern of explicit what AND when with concrete triggers.

5 / 5

Trigger Term Quality

"remember, persist, capture, retrieve, or organize" are natural phrases users would say, giving good keyword coverage. It is not score 5 because common synonyms such as "save this" or "note this" are missing, but it clearly exceeds the partial coverage of score 3.

4 / 5

Distinctiveness Conflict Risk

Named systems ("Arnesto", "personal-knowledge-vault") and destination-specific triggers create a clear niche with mostly distinct triggers. Not score 5 because the broad verb "remember" could fire for generic memory requests, a minor overlap risk with general memory-related skills.

4 / 5

Total

16

/

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

saski/arnesto

Path

.agents/skills/personal-knowledge-routing/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.