partnership-outreach

When a founder needs to write partnership or BD emails, craft integration pitches, or create co-marketing proposals. Activate when the user mentions partnerships, business development, integration proposals, co-marketing, channel partnerships, or strategic alliances.

Quality

73%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/partnership-outreach/SKILL.md

Quality

Content

64%

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

This is a comprehensive and highly actionable partnership outreach skill with excellent concrete examples, scoring frameworks, and email templates. Its main weaknesses are verbosity (some sections explain things Claude already knows) and a monolithic structure that could benefit from splitting detailed frameworks into referenced files. The workflow would also benefit from explicit validation checkpoints between stages.

Suggestions

Split the detailed frameworks (Co-Marketing Proposal Structure, Integration Pitch Framework, Partner Evaluation Framework) into separate referenced files to reduce the main skill's token footprint and improve progressive disclosure.

Add explicit validation checkpoints to the workflow, e.g., 'Verify partner evaluation score is 15+ before drafting outreach' and 'Review outreach draft against Email Principles checklist before sending.'

Trim explanatory sentences that state the obvious to Claude, such as 'Partnership emails differ from sales emails. You are proposing a collaboration, not selling a product' and 'The tone should be peer-to-peer and the value proposition must be bilateral.'

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~200+ lines) with some sections that explain concepts Claude already understands (e.g., 'Partnership emails differ from sales emails. You are proposing a collaboration, not selling a product.'). The frameworks and tables are useful but some principles sections are verbose and could be tightened. However, most content is instructional rather than explanatory.	2 / 3
Actionability	The skill provides highly concrete, copy-paste-ready frameworks: a scoring rubric with specific dimensions, email structure with a complete example output, follow-up timing sequences, and specific proposal structures. The example outreach email is realistic and directly usable as a template.	3 / 3
Workflow Clarity	The 7-step workflow is clearly sequenced and logical, but it lacks validation checkpoints. There's no explicit step to verify the partner evaluation score before proceeding, no feedback loop for iterating on outreach drafts, and no checkpoint between outreach and proposal stages. For a multi-step process involving external communication, validation steps would strengthen this.	2 / 3
Progressive Disclosure	The skill references related skills (`cold-outreach`, `proposal-generation`) which is good, but the main file is monolithic — all frameworks, tables, principles, and examples are inline. The co-marketing proposal structure, integration pitch framework, and detailed email principles could be split into referenced files to keep the main skill leaner.	2 / 3
	Total	9 / 12 Passed

Description

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.

This is a solid description that clearly communicates both what the skill does and when to use it, with good trigger term coverage for the partnership/BD domain. Its main weakness is moderate specificity in the actions listed and some potential overlap with general email or proposal writing skills. The description uses appropriate third-person framing and avoids vague language.

Suggestions

Add more specific concrete actions to increase specificity, e.g., 'draft partner outreach sequences, structure revenue-sharing proposals, write API integration pitch decks'

Differentiate more clearly from general email/proposal skills by emphasizing the partnership-specific elements, e.g., mentioning mutual value propositions, partner tiers, or integration technical details

Dimension	Reasoning	Score
Specificity	Names the domain (partnership/BD) and some actions ('write partnership or BD emails, craft integration pitches, create co-marketing proposals'), but the actions are somewhat general categories rather than deeply specific concrete operations.	2 / 3
Completeness	Clearly answers both 'what' (write partnership emails, craft integration pitches, create co-marketing proposals) and 'when' with an explicit 'Activate when...' clause listing specific trigger scenarios.	3 / 3
Trigger Term Quality	Includes a strong set of natural keywords users would say: 'partnerships', 'business development', 'integration proposals', 'co-marketing', 'channel partnerships', 'strategic alliances'. These cover common variations well.	3 / 3
Distinctiveness Conflict Risk	While it targets a specific niche (partnership/BD communications), there could be overlap with general email writing skills or broader sales/marketing skills. The terms 'emails' and 'proposals' are fairly common across multiple skill types.	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: 3 months 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.