personal-crm

How to work in a Personal CRM project (the `entity-vault` starter pack, GBrain-compatible): a typed-entity vault of people, companies, meetings, and concepts, each a dossier with a rewritable summary plus an append-only timeline. Read when the project has these folders, OR when asked to capture notes about a person or company, log a meeting, prep for an upcoming meeting, or answer who someone is and what was last said. Carries the dossier convention and entity-extraction behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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 well-crafted, information-dense body: every section carries novel project-specific convention rather than general knowledge, and the guidance is copy-paste concrete. The only improvements are trimming the duplicated platform-skill statements and framing the brokenLinks catch as an explicit validation loop.

Suggestions

Consolidate the duplicated platform-skill relationship: the intro paragraph and the blockquote both state that the /open-knowledge skill governs underlying operations — keep one, ideally the blockquote.

Frame the brokenLinks response as an explicit validate-fix-retry loop in the Links section (e.g. 'If brokenLinks reports a wrong-depth path, fix the ../ depth and re-run the write') rather than only noting it catches errors.

State what to do when an entity mention in a meeting note is ambiguous (e.g. two people with the same name) so the extract-and-append behavior has a defined fallback.

Dimension	Reasoning	Score
Conciseness	Dense and project-specific with no padding of concepts Claude already knows, but it restates the platform-skill relationship twice (intro paragraph plus the blockquote) and repeats the GBrain-compatible framing, so minor trimming is possible — anchor 4 rather than 5's 'every token earns its place'.	4 / 5
Actionability	Fully concrete guidance: exact separator ('--- timeline ---'), a copy-paste timeline bullet form ('- YYYY-MM-DD \| source \| @author — evidence. Confidence: …'), exact addressing scheme ('meetings/<source>-<source_meeting_id>'), required frontmatter fields, and concrete link examples — executable without placeholders, matching anchor 5.	5 / 5
Workflow Clarity	The ingest → write-note → extract-entities → append-timeline → stub-new-entities sequence is clear, with an explicit routing rule and the brokenLinks response cited as a safety net, but there is no explicit validate-fix-retry loop (e.g. how to respond when brokenLinks flags a link) — anchor 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist and the body is under 50 lines with well-organized sections (dossier convention, folders, links, behaviors, CLI, templates) and no need for external references, so per the simple-skill guideline it scores 5 on organization alone.	5 / 5
	Total	18 / 20 Passed

Description

92%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: concrete, third-person, with an explicit 'Read when…' trigger clause covering natural user phrasings and an explicit boundary against the closely-related platform skill. The only gap is a couple of missing natural synonyms (contacts, relationship management) for the Personal CRM domain.

Dimension	Reasoning	Score
Specificity	Names the domain ('typed-entity vault of people, companies, meetings, and concepts, each a dossier with a rewritable summary plus an append-only timeline') and lists multiple concrete actions — capture notes about a person or company, log a meeting, prep for an upcoming meeting, answer who someone is and what was last said — covering the skill's full scope comprehensively, matching the anchor 5 rather than 4 (no minor gaps in coverage).	5 / 5
Completeness	Explicitly answers both what ('a typed-entity vault of people, companies, meetings, and concepts, each a dossier with a rewritable summary plus an append-only timeline' plus entity-extraction behaviors) and when ('Read when the project has these folders, OR when asked to capture notes… log a meeting, prep for an upcoming meeting, or answer who someone is'), with concrete trigger phrases matching anchor 5.	5 / 5
Trigger Term Quality	Includes natural phrases users would actually say — 'capture notes about a person or company', 'log a meeting', 'prep for an upcoming meeting', 'who someone is and what was last said', 'Personal CRM' — but a few natural synonyms are missing (e.g. 'contacts', 'relationship management'), fitting anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Personal CRM entity-vault) with distinct triggers, and it explicitly manages the one overlap risk: 'Complements the platform `open-knowledge` skill; does not replace it.' Minimal conflict risk, matching anchor 5.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 1 missing, 3 suspicious	Warning

	Total	14 / 16 Passed

Repository: inkeep/open-knowledge
Path: packages/server/assets/skills/packs/entity-vault/SKILL.md
Commit: e84b75f

Reviewed: 2 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.