proposal-generation

When a founder needs to create a sales proposal, statement of work, contract, NDA, or master service agreement. Activate when the user mentions proposal, SOW, quote, contract, NDA, MSA, or needs to formalize a deal.

Quality

79%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/proposal-generation/SKILL.md

Quality

Discovery

82%

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

The description has strong trigger term coverage and good completeness with explicit activation guidance. Its main weakness is a lack of specificity about what concrete actions the skill performs beyond 'create' — it lists document types well but doesn't describe the specific capabilities (e.g., drafting from templates, pricing calculations, clause libraries). There is moderate conflict risk with other document-related skills.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Drafts sales proposals with pricing tables, generates SOW timelines, creates contract clauses from templates' rather than just listing document types.

Differentiate from generic document creation skills by specifying unique capabilities like 'includes standard legal clauses', 'auto-populates client details', or 'follows founder-friendly templates'.

Dimension	Reasoning	Score
Specificity	The description names the domain (sales/legal documents) and lists document types (sales proposal, SOW, contract, NDA, MSA), but doesn't describe concrete actions beyond 'create'. It doesn't specify what the skill actually does with these documents (e.g., draft sections, format, calculate pricing, generate templates).	2 / 3
Completeness	Clearly answers both 'what' (create sales proposals, SOWs, contracts, NDAs, MSAs) and 'when' with an explicit 'Activate when...' clause listing specific trigger terms and the scenario of needing to formalize a deal.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'proposal', 'SOW', 'quote', 'contract', 'NDA', 'MSA', 'formalize a deal', 'statement of work', 'master service agreement'. These are terms founders and salespeople naturally use.	3 / 3
Distinctiveness Conflict Risk	While the document types are fairly specific, there could be overlap with general document creation skills, legal document skills, or template generation skills. The 'founder' context helps narrow it somewhat, but 'contract' and 'proposal' are broad terms that could trigger conflicts with other skills.	2 / 3
	Total	10 / 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 domain-specific legal knowledge across multiple jurisdictions. The workflow is well-sequenced with validation steps, and the example output demonstrates exactly what good output looks like. The main weakness is that the skill is somewhat long — several reference sections (jurisdiction rules, SOW guidance, pricing strategy) could be extracted into separate files to improve progressive disclosure and reduce token cost.

Suggestions

Extract jurisdiction-specific rules and SOW-specific guidance into separate referenced files (e.g., JURISDICTIONS.md, SOW-GUIDE.md) to reduce the main skill's token footprint.

Trim the pricing presentation strategy section — the ROI advice ('Always lead with value before cost') is general sales knowledge Claude already has.

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some content that could be tightened — e.g., the pricing presentation strategy section with ROI advice and the 'Common Pitfalls' section partially restates what's already in the workflow step 6. However, most content is domain-specific legal knowledge Claude wouldn't inherently know (jurisdiction rules, BGB references), so it largely earns its place.	2 / 3
Actionability	The skill provides highly concrete guidance: specific clause options with exact values (1x/3x liability caps, 14-day cure periods), jurisdiction-specific legal references (BGB para 126, Copyright Act 101), a complete example output with realistic contract structure, and a clear deliverables table format. The example snippet is copy-paste ready with appropriate placeholders.	3 / 3
Workflow Clarity	The 7-step workflow is clearly sequenced with logical progression from requirements gathering through drafting to review and conversion. Step 6 serves as an explicit validation checkpoint reviewing common pitfalls, and step 1 flags missing items as REQUIRED. The conditional step 5 (GDPR addendum) shows appropriate branching logic.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and headers, and references related skills at the end. However, the document is quite long (~150+ lines of substantive content) with detailed jurisdiction rules, SOW guidance, and pricing strategy all inline. The jurisdiction-specific rules and SOW-specific guidance could be split into referenced files to keep the main skill leaner.	2 / 3
	Total	10 / 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: shawnpang/startup-founder-skills
Commit: 4ad31b4

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