deal-memo-drafting

Investor-first workflow for drafting a structured deal memo, IC memo, partnership memo, or acquisition-style brief from existing diligence materials. Use for prompts like "draft a deal memo", "turn this diligence packet into a memo", or "write the IC draft". Best when you already have research findings, model review notes, meeting outputs, and supporting documents. Optional Open Brain search and capture can pull prior context and store the final memo or recommendation summary.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-structured instruction-only skill with concrete drafting rules, a clear sequenced process, and useful cross-skill navigation. It falls short on actionability (no worked examples) and workflow clarity (quality checkpoints are implicit rather than explicit validation steps with feedback loops).

Suggestions

Add a short worked example — e.g., a one-paragraph sample thesis statement carrying an explicit confidence level and a 'needs verification' note — so the guidance is demonstrated and copy-paste ready, lifting actionability.

Insert an explicit validation checkpoint in the Process: after drafting, run a gap-check confirming every section separates confirmed findings vs. inferences vs. unresolved gaps before the tightening step.

Add a brief self-review checklist just before Output (decision stated? confidence explicit? open questions listed? next verification steps given?) to make quality gates explicit rather than implicit.

Dimension	Reasoning	Score
Conciseness	The body is lean — short bullet lists and terse imperatives with no explanation of concepts Claude already knows (it never defines 'diligence', 'IC memo', or 'thesis'), so every section earns its place.	3 / 3
Actionability	Concrete rules and a defined memo spine ('Thesis, market, business, economics, risks, open questions, recommendation') give specific guidance, but there are no worked examples or sample memo excerpts to make it copy-paste ready, so it sits at the 'some concrete guidance but missing examples' anchor rather than 3.	2 / 3
Workflow Clarity	The 6-step Process is clearly sequenced and backed by checklists (Required Context, Output, Evidence and Judgment Rules), but quality checkpoints are implicit ('If a section is weak... say so') rather than explicit validation steps, and there is no validate→fix→retry feedback loop.	2 / 3
Progressive Disclosure	The skill is self-contained with no bundle files, yet well-organized into clearly navigable sections (Problem, When to Use, When Not to Use, Process, Output, Works Well With) and well-signaled one-level cross-skill pointers (e.g., 'use competitive-analysis'), with no nested references.	3 / 3
	Total	10 / 12 Passed

Description

90%

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, niche description that clearly states capability and trigger conditions with natural example prompts and good distinctiveness. Its only ding is a second-person 'you' clause that breaks the required third-person voice and costs a specificity point.

Suggestions

Rewrite in consistent third-person/imperative voice: change 'Best when you already have research findings...' to 'Best when research findings, model review notes, meeting outputs, and supporting documents are already in hand' to drop the second-person 'you' and restore the specificity point.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('drafting a structured deal memo, IC memo, partnership memo, or acquisition-style brief', 'search and capture can pull prior context and store the final memo') which would anchor at 3, but the second-person clause 'Best when you already have research findings...' violates the third-person voice rule and incurs the −1 specificity penalty.	2 / 3
Completeness	It states what the skill does (drafts structured memos from diligence) and when to use it with explicit triggers ('Use for prompts like...', 'Best when...'), satisfying the 'both what AND when' anchor.	3 / 3
Trigger Term Quality	'Use for prompts like "draft a deal memo", "turn this diligence packet into a memo", or "write the IC draft"' gives natural phrasings a user would actually say, matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	A clear niche (deal/IC/partnership memo drafting from existing diligence) with distinct triggers and a 'Best when you already have...' precondition, making it unlikely to fire for adjacent skills.	3 / 3
	Total	11 / 12 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: NateBJones-Projects/OB1
Path: skills/deal-memo-drafting/SKILL.md
Commit: 6779106

Reviewed: about 18 hours 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.