contacts

Add, enrich, and manage contacts in Joel's Vault. Fire the Inngest enrichment pipeline for full multi-source dossiers, or create quick contacts manually. Use when: 'add a contact', 'enrich this person', 'who is X', 'VIP contact', 'update contact', or any task involving the Vault/Contacts directory.

Quality

85%

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

65%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 dense, actionable single-file skill with concrete code and a clear VIP enrichment playbook, but it lacks validation checkpoints for its batch/file-write operations and inlines substantial content that would benefit from being split into reference files.

Suggestions

Add an explicit validation/verification step after the Typesense batch upsert and after writing contact files (e.g., query the collection to confirm upsert counts, or re-read the vault file to confirm frontmatter parsed) so the batch/destructive workflows clear the workflow_clarity cap.

Move the date-bound details out of the main flow — replace the hardcoded 'egghead-2026-01-19-13-09-38.edn' filename with a glob/variable, and relocate the 'Feb 26, 2026' Kent C. Dodds example and the 'Bun v1.3.9' bug note into a notes/deprecated section so they don't rot the concise core.

Extract the VIP Deep Enrichment Playbook and the Roam Research Enrichment section into reference files under references/ (e.g., references/vip-playbook.md, references/roam-enrichment.md) and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly lean and Joel-specific with no padding of concepts Claude already knows, but it carries time-sensitive detail (hardcoded 'egghead-2026-01-19-13-09-38.edn', 'Feb 26, 2026', 'Bun v1.3.9') that is not isolated in a deprecated section and will rot.	4 / 5
Actionability	Provides copy-paste-ready curl payloads, Python regex scripts, and frontmatter templates covering the common cases, with only minor gaps such as the invalid-JSON 'ts: EPOCH_MS' placeholder in the curl example.	4 / 5
Workflow Clarity	Options and the 9-step VIP playbook are clearly sequenced, but the batch Typesense upsert and vault file writes have no validation/verification checkpoint, which caps workflow clarity at 3 per the destructive/batch cap.	3 / 5
Progressive Disclosure	Well-sectioned with signaled pointers to the example contact, the ADR, and related skills, but it is a ~150-line single file with no bundle references, and large blocks (VIP playbook, Roam enrichment) that could live in separate reference files are inlined.	3 / 5
	Total	14 / 20 Passed

Description

100%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, third-person description that concretely states capabilities and pairs them with natural, exhaustive trigger phrases. It cleanly answers both what the skill does and when to invoke it, and is tightly scoped to Joel's Vault contacts niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Add, enrich, and manage contacts', 'Fire the Inngest enrichment pipeline for full multi-source dossiers', 'create quick contacts manually' — giving comprehensive coverage rather than vague abstractions.	5 / 5
Completeness	Explicitly answers both what (add/enrich/manage, fire pipeline, manual create) and when (a 'Use when:' clause with concrete trigger phrases), matching the anchor for full completeness.	5 / 5
Trigger Term Quality	Natural trigger phrases a user would actually say — 'add a contact', 'enrich this person', 'who is X', 'VIP contact', 'update contact' — plus the directory reference, covering synonyms and variations.	5 / 5
Distinctiveness Conflict Risk	Scoped to 'Joel's Vault' and the 'Vault/Contacts directory' with Inngest-pipeline-specific triggers, giving it a clear niche with minimal overlap risk against generic skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: joelhooks/joelclaw
Path: skills/contacts/SKILL.md
Commit: aa0116c

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