Two-tier dealflow evaluation: research dossier (15-25 pages) and executive memo (5-7 pages) with anti-bias MoE layer, True Potential Council, and arithmetic verification
67
84%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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, well-crafted description that clearly communicates specific deliverables, proprietary frameworks, and explicit trigger conditions. It occupies a distinct niche (VC/startup due diligence) with rich natural trigger terms. The description is comprehensive yet concise, covering both what the skill produces and when it should be used.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and deliverables: two-tier evaluation (research dossier and executive memo), team assessment, market analysis, competitive landscape, True Potential Council, Anti-Bias MoE layer, IASV scorecard, and PASS/INVESTIGATE/INVEST signal. Very detailed about what is produced. | 3 / 3 |
Completeness | Clearly answers both 'what' (produces two-tier evaluation with specific components) and 'when' (explicit 'Use for due diligence, deal analysis, VC memo generation, startup assessment, or founder evaluation at pre-seed and seed stage'). The 'Use for...' clause serves as an explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'due diligence', 'deal analysis', 'VC memo', 'startup assessment', 'founder evaluation', 'pre-seed', 'seed stage'. These cover the natural vocabulary of the target user (VC investors/analysts). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — VC due diligence and startup evaluation at pre-seed/seed stage with specific proprietary frameworks (True Potential Council, Anti-Bias MoE layer, IASV scorecard). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured complex workflow skill with clear sequencing, good use of tables, and appropriate separation of concerns between research dossier and executive memo outputs. Its main weaknesses are moderate verbosity (repeated explanations of the two-tier architecture, inline stakeholder quotes), incomplete actionability due to missing referenced files containing critical scoring rubrics and prompts, and the gap between referenced and available materials. The workflow clarity is strong with explicit validation steps and a comprehensive completion checklist.
Suggestions
Remove or condense the version changelog and 'Problem/Solution' framing — state the two-tier architecture once concisely rather than explaining the rationale multiple times across sections.
Include the referenced files (TRUE-POTENTIAL-COUNCIL.md, ANTI-BIAS-MOE.md, VERIFICATION-CHECKLIST.md) in the bundle, or inline the essential scoring rubrics and thresholds so the skill is actionable standalone.
Make the parallel analysis steps more concrete — specify exact WebSearch query patterns, expected data formats, and how to handle conflicting sources rather than describing the process abstractly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity — the inline Ed quotes, the 'Problem/Solution' framing for two-tier output, and repeated explanations of the dossier vs memo distinction across multiple sections. The version changelog at the top also consumes tokens on context Claude doesn't need. However, most content is functional and tables are used effectively. | 2 / 3 |
Actionability | The skill provides clear invocation commands and structured output templates, but the core analysis steps (market researcher, biographical researcher, etc.) are described at a process level rather than with executable specifics. Key details like scoring rubrics, council prompts, and verification checklists are deferred to referenced files that aren't provided, making the skill incomplete as a standalone guide. | 2 / 3 |
Workflow Clarity | The five-step workflow is clearly sequenced with explicit validation (Step 5 arithmetic verification is mandatory with a 7-point checklist), parallel execution is well-defined in Step 2, and the completion checklist at the end serves as a comprehensive verification gate. The failure handling table provides error recovery guidance for common issues. | 3 / 3 |
Progressive Disclosure | The skill references three external files (TRUE-POTENTIAL-COUNCIL.md, ANTI-BIAS-MOE.md, VERIFICATION-CHECKLIST.md) which is good progressive disclosure design, but none of these bundle files are provided, meaning critical scoring rubrics, council prompts, and verification details are inaccessible. The main document also includes substantial inline detail (full dossier/memo templates, scorecard table) that could arguably be split out, while the referenced files that should contain the most important operational details are missing. | 2 / 3 |
Total | 9 / 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 | |
Reviewed
Table of Contents