person-dossier

Build and update person dossiers from communication history. Use when a person is discussed for strategy, follow-up, opportunities, relationship context, or decisions. Automatically pull evidence from Front email, Granola meetings, memory recall, and event logs; then write/update a structured dossier in Vault/Resources/.

1.40x

Quality

88%

Does it follow best practices?

Impact

98%

1.40x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

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 strong, highly actionable skill with a well-sequenced multi-step workflow, concrete CLI commands, and thoughtful error handling. Its main weaknesses are moderate verbosity (redundant command summary section, some over-specification of obvious data structuring) and a monolithic structure that could benefit from splitting the template and command reference into separate files.

Suggestions

Remove or consolidate the 'Quick Build Command Set' section since it duplicates commands already present in the workflow steps, or move it to a separate quick-reference file.

Consider extracting the dossier template into a separate file (e.g., DOSSIER_TEMPLATE.md) and referencing it from the main skill to reduce token footprint.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy—the 'Quick Build Command Set' section repeats commands already shown in the workflow steps. The dossier template is useful but lengthy; some normalization instructions (step 7) describe obvious data structuring that Claude could infer.	2 / 3
Actionability	Every step includes concrete, executable CLI commands with specific flags and parameters. The dossier template is copy-paste ready with clear field placeholders, and the update rules are specific and unambiguous.	3 / 3
Workflow Clarity	The 10-step workflow is clearly sequenced with explicit validation (step 1 for auth, step 10 for blocker handling with fallback sources and error recording). The update rules include deduplication logic and merge strategies, and the blocker handling section provides a clear feedback loop with 'no silent partials' as a constraint.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and headers, but it's a long monolithic file (~150 lines of substantive content) with no references to external files. The dossier template and quick command set could be split into separate referenced files to reduce the main skill's footprint.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly articulates what the skill does (builds person dossiers from multiple communication sources), when to use it (when discussing a person for strategy, follow-up, opportunities, etc.), and where outputs go (Vault/Resources/). It uses third-person voice correctly, includes natural trigger terms, and occupies a distinct niche that minimizes conflict risk with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Build and update person dossiers', 'pull evidence from Front email, Granola meetings, memory recall, and event logs', 'write/update a structured dossier in Vault/Resources/'. Names specific data sources and output location.	3 / 3
Completeness	Clearly answers both 'what' (build/update person dossiers from communication history, pulling from specific sources, writing structured dossiers to a specific location) and 'when' (explicit 'Use when a person is discussed for strategy, follow-up, opportunities, relationship context, or decisions').	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'person', 'dossier', 'strategy', 'follow-up', 'opportunities', 'relationship context', 'decisions'. Also includes specific tool names (Front email, Granola meetings) and action terms (communication history) that map well to user requests.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche: person dossiers built from specific communication sources (Front, Granola) stored in a specific location (Vault/Resources/). Unlikely to conflict with other skills due to the unique combination of person-focused intelligence gathering and specific tooling.	3 / 3
	Total	12 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: joelhooks/joelclaw
Commit: 2ca3686

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