CtrlK
BlogDocsLog inGet started
Tessl Logo

dossier

Decision-grade entity research skill — produces a hypothesis-tested dossier on a specific company, person, nonprofit, or government org, not a generic profile. Forcing intake makes the user state their hypothesis upfront (what they already believe and want to verify or disprove) so the dossier tests it rather than confirms it. Output is an editable Word document (.docx) with verdict on the hypothesis, identity facts, 12-month activity timeline, network and reputation signals, red flags, conversation hooks tied to specific findings, and source-provenance audit log. Uses WebSearch + WebFetch + free APIs (SEC EDGAR, GitHub, ProPublica) as workhorses; optional BYOK MCPs enhance coverage. Use when the user asks for background research, diligence, or meeting prep on a specific entity (e.g., 'prep me for a meeting with [person/company]', 'due diligence on [company]'). Honors sensitivity exclusions for journalism + personal-vetting contexts.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 thorough, well-sequenced research skill with excellent workflow clarity, concrete tooling, and clean one-level references. Its main weaknesses are mild verbosity from repeated differentiator framing and inlining of detail (notably the full DOCX section spec) that could live in references.

Suggestions

Deduplicate the 'non-generic anchor / Wikipedia summary' framing — state it once in the Differentiator section and let the Anti-Patterns entry reference it rather than re-explaining at lines ~28, ~91, and ~302.

Move the full 9-section DOCX specification (Phase 9) into a references file (e.g. references/docx_generation.md), keeping only the section list and styling summary inline, to deepen progressive disclosure and shorten SKILL.md.

Provide a complete executable Node + docx generation script (or a scripts/ entry) for Phase 9 rather than only the ExternalHyperlink snippet and styling spec, so the highest-complexity step is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is well-organized and mostly tight, but repeats the 'non-generic anchor / Wikipedia summary' framing three times and carries verbose '*Why I'm asking*' rationale blocks that could be trimmed. It sits above the mostly-efficient anchor but short of fully lean.

4 / 5

Actionability

Strong concrete guidance throughout — named scripts, a copy-paste zip-integrity validation command, file-naming convention, the ≥30% disconfirming threshold, and a hyperlink JS snippet — but the core DOCX-generation step is specified via sections/styling rather than a complete executable Node script, leaving minor gaps.

4 / 5

Workflow Clarity

Ten phases are clearly sequenced with an intake stop-condition, a disambiguation gate, explicit Phase 10 validation (zip integrity + required-sections check), an error-handling table with recovery behaviors, and an anti-patterns checklist — matching the explicit-validation-with-feedback-loops anchor.

5 / 5

Progressive Disclosure

Three one-level-deep references (all verified to exist, well-signaled 'for the canon') plus three scripts listed in a Tooling table give good navigation, but the full 9-section DOCX spec and source matrices are inlined in SKILL.md rather than split out, a minor organization gap.

4 / 5

Total

17

/

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.

An exemplary description: concrete capabilities, natural trigger phrases with synonyms and a file extension, explicit what-and-when guidance, and a clearly differentiated niche, all in third-person voice. It does not over-claim or pad.

DimensionReasoningScore

Specificity

Lists multiple concrete output actions — 'verdict on the hypothesis, identity facts, 12-month activity timeline, network and reputation signals, red flags, conversation hooks… and source-provenance audit log' — giving comprehensive coverage of what the skill produces.

5 / 5

Completeness

Explicitly answers both 'what' (hypothesis-tested dossier with named sections) and 'when' via a concrete 'Use when the user asks for background research, diligence, or meeting prep on a specific entity' clause with example triggers.

5 / 5

Trigger Term Quality

Natural user phrases are present with synonyms ('background research', 'diligence', 'due diligence on [company]', 'meeting prep', 'prep me for a meeting with [person/company]') plus a file extension (.docx), matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

A clear niche — 'decision-grade entity research with hypothesis-testing' on typed subjects (company/person/nonprofit/gov), explicitly 'not a generic profile' — yields distinct triggers with minimal overlap risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.