CtrlK
BlogDocsLog inGet started
Tessl Logo

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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-structured co-marketing playbook with strong actionability via templates, scoring rubrics, and checklists. Its main limitation is that everything is inlined in one ~290-line file rather than split into progressive reference files.

Suggestions

Move the four campaign-type tables and the partner-scoring criteria into a references/ file (e.g. references/campaign-types.md), keeping SKILL.md as an overview with one-level-deep links to reduce token load.

Add an explicit validation/checkpoint step in the workflow (e.g., confirm partner fit score ≥ threshold before drafting outreach) so the sequence has a feedback loop.

Tighten the 'Brainstorming Partner Campaigns' section — several prompts are open-ended and could be condensed into a shorter decision aid.

DimensionReasoningScore

Conciseness

Dense, practical reference material that avoids explaining concepts Claude already knows, though at ~290 lines some sections (e.g., the campaign-type tables) could be trimmed or offloaded to a reference file.

4 / 5

Actionability

Highly actionable for an instruction-only skill — scoring criteria table, copy-paste cold-outreach template, agreement outline, and checklists — with only minor gaps where sections rely on brainstorming prompts rather than concrete steps.

4 / 5

Workflow Clarity

Clear logical sequence (identify partners → score → brainstorm → approach → structure → measure) reinforced by an end-of-skill checklist; not a destructive/batch operation so no validation cap applies, but explicit checkpoints between phases are only implicit.

4 / 5

Progressive Disclosure

Well-organized into clearly signaled sections with one-level-deep external references (tools registry, related skills, product-marketing.md), though all detail lives inline in SKILL.md with no bundle files to offload the campaign-type and criteria tables.

4 / 5

Total

16

/

20

Passed

Description

95%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.

A strong, well-scoped description that pairs concrete capabilities with an explicit, keyword-rich trigger clause and clear boundary guidance against neighboring skills. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities' — but stops short of the comprehensive action coverage needed for a 5.

4 / 5

Completeness

Explicitly answers both what (find partners, plan joint campaigns, brainstorm opportunities) and when, with a concrete 'Use when the user says…' trigger clause.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and variants — 'co-marketing,' 'partner marketing,' 'joint campaign,' 'cross-promotion,' 'integration marketing,' 'co-brand,' plus the natural phrase 'who should we partner with.'

5 / 5

Distinctiveness Conflict Risk

Clear SaaS co-marketing niche with distinct triggers, plus boundary guidance ('For customer referral programs, see referrals. For launch-specific partnerships, see launch.') minimizing conflict with adjacent skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository
joshmanders/dotfiles
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.