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

78%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/server/assets/skills/packs/entity-vault/SKILL.md

Quality

Content

68%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 dense, specific, and largely actionable, carrying the dossier convention and exact formats Claude needs without padding. Its main weakness is workflow validation: the append-only timeline step — an irreversible batch write — has no explicit verification checkpoint before commit.

Suggestions

Add an explicit validation checkpoint to the entity-extraction workflow (e.g. verify referenced dossier filenames resolve via brokenLinks before appending timeline bullets) so the append-only write is checked before commit.

Provide one complete minimal dossier example (compiled truth + `--- timeline ---` + a dated bullet) so the convention is copy-paste concrete rather than described.

Link templates and root files (USER.md, SOUL.md, etc.) as one-level file references rather than prose mentions to tighten progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly lean and load-bearing; the GBrain link deltas and frontmatter/timeline formats are non-obvious specifics that earn their tokens, with only minor over-explanation in the Links section that could be trimmed.	4 / 5
Actionability	Concrete and executable — exact frontmatter fields, filename patterns, the timeline bullet shape, link forms, and commands (`ok seed`, `write({document:{template}})`, `gbrain import`) — though no full copy-paste example of a complete dossier is provided.	4 / 5
Workflow Clarity	The ingest→extract→append-timeline sequence is clear and the brokenLinks/dedup-key checkpoints validate links and duplicates, but the central append-only timeline workflow (an irreversible/batch operation) lacks an explicit validate-before-append verification step, capping the score per the batch-operation rule.	3 / 5
Progressive Disclosure	Well-organized into clear sections (dossier convention, Folders, Links, Agent behaviors, gbrain CLI, Templates) with no nested references; templates and root files are signaled but referenced in prose rather than as clean one-level file links, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

87%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: it states what the vault is and gives multiple concrete, natural-language triggers for when to read it, while explicitly delimiting its scope against the platform skill. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Names concrete actions — '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' — plus a typed-entity dossier structure, giving several specific capabilities with only minor framing gaps.	4 / 5
Completeness	Explicitly answers both 'what' ('a typed-entity vault of people, companies, meetings, and concepts, each a dossier...') and 'when' ('Read when the project has these folders, OR when asked to...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases a user 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') give good keyword coverage, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Personal-CRM/dossier niche with distinct triggers and explicitly boundaries itself ('Complements the platform open-knowledge skill; does not replace it'), minimizing overlap risk.	5 / 5
	Total	18 / 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: 60997a2

Reviewed: 1 day 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.