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/.
91
88%
Does it follow best practices?
Impact
98%
1.40xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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 communication history), when to use it (when discussing a person for strategy, follow-up, etc.), and how it works (pulling from specific named sources and writing to a specific location). It uses third person voice throughout and provides enough specificity to be easily distinguishable from 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 tools and output locations. | 3 / 3 |
Completeness | Clearly answers both what ('Build and update person dossiers from communication history... pull evidence... write/update a structured dossier') and when ('Use when a person is discussed for strategy, follow-up, opportunities, relationship context, or decisions') with explicit trigger guidance. | 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 source names (Front email, Granola meetings) that users would reference. Good coverage of when someone is discussing a person in a business context. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: person dossiers built from specific sources (Front email, Granola meetings) stored in a specific location (Vault/Resources/). The combination of person-focused intelligence gathering from named tools makes this unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 excellent workflow clarity and concrete commands for every step. Its main weaknesses are minor redundancy (the Quick Build Command Set duplicates workflow commands) and the monolithic structure that could benefit from splitting the template and reference commands into separate files. The evidence provenance requirements and blocker handling are particularly well done.
Suggestions
Remove or consolidate the 'Quick Build Command Set' section since it duplicates commands already present in the workflow steps, or reframe it as the sole command reference and remove inline commands from workflow steps.
Consider extracting the Dossier Template into a separate referenced file (e.g., DOSSIER_TEMPLATE.md) to reduce the main skill's length and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but has some redundancy—the 'Quick Build Command Set' at the end repeats commands already shown in the workflow steps. Some sections like 'Resolve identifiers' and 'Normalize extracted data' could be tighter. However, it avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Provides fully concrete, copy-paste-ready bash commands for every data source (Front, Granola, memory, events), specific flags and parameters, a complete markdown template for the output, and explicit update rules with deduplication logic. Very little is left ambiguous. | 3 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced with explicit validation (step 1 checks auth/secrets), blocker handling with fallback strategies (step 10), update rules that prevent data loss (step 8), and evidence/confidence labeling requirements (step 9). The feedback loop for blocked states is well-defined with 'no silent partials' as a clear constraint. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a fairly long monolithic file (~150 lines of content). The dossier template, quick command set, and detailed workflow steps could potentially be split into referenced files. However, for a single skill file the organization is reasonable. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
825972c
- 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.