CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

68

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

67%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 well-structured strategy skill with concrete tables, templates, checklists, and a properly signaled single reference file. Main weaknesses are token efficiency — the adjacent partnership-type digression and symmetric filler tables — and inlining of detail that belongs in reference files.

Suggestions

Move the partnership-types detail (flagship stats like HubSpot's $100M ARR, standout moves) into references/partnership-types.md, keeping only the 5-type table and the pointer inline.

Delete or compress the 'Unique Assets Each Brings' table — it enumerates trivially symmetric pairs that add no decision value.

Add threshold guidance to the partner scoring criteria (e.g., what a 4+ total or per-criterion score means for proceeding to outreach) so the scoring step drives a go/no-go decision.

DimensionReasoningScore

Conciseness

The body is mostly tight, table-driven content, but the Partnership Types section spends ~15 lines on adjacent-type knowledge and flagship stats ("HubSpot's partner program = $100M ARR, ~40% of revenue, 3,400+ partners"), and the "Unique Assets Each Brings" table is trivially symmetric padding ("Your audience size/engagement | Their audience size/engagement"). Anchor 3 fits: mostly efficient with some unnecessary explanation that could be trimmed — not 4 given the size of the taxonomy digression, not 2 since most sections are lean and useful.

3 / 5

Actionability

Concrete, usable guidance throughout: a copy-paste cold outreach template, a 6-criteria partner scoring table, checklists, an 8-point agreement outline, and specific tool pointers (Crossbeam/Reveal). Minor gaps keep it below anchor 5: the 1-5 partner scoring has no thresholds or interpretation guidance, and the success-metrics section lists metrics without benchmarks or targets.

4 / 5

Workflow Clarity

The Co-Marketing Checklist explicitly sequences Identification → Campaign Planning → Execution → Post-Campaign, and "Before Starting" adds an entry checkpoint (read product-marketing context before asking questions). Not anchor 5: no explicit go/no-go decision points (e.g., minimum partner score before outreach), and no verification of campaign prerequisites before launch; not anchor 3 since the sequence is explicit rather than implicit.

4 / 5

Progressive Disclosure

The partnership-types taxonomy is summarized inline with a clear one-level-deep pointer to references/partnership-types.md (which exists), and external tool guides are clearly linked. However, ~300 lines of campaign-format tables, agreement outline, and metrics detail are inlined in SKILL.md where some could be split into references — anchor 4's "minor organization gaps," short of anchor 5's lean overview with fully appropriate splitting.

4 / 5

Total

15

/

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 description: concrete capabilities, comprehensive natural trigger phrases, an explicit 'Use when' clause, and explicit boundary routing to sibling skills. The only weakness is that it omits a few capabilities the body covers (structuring agreements, measuring success).

DimensionReasoningScore

Specificity

Lists three concrete actions ("find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities"), but the body also covers structuring agreements, approaching partners, and measuring success, which the description omits. Anchor 4 fits: several specific actions with minor coverage gaps — not 5 (not comprehensive), not 3 (well beyond 1-2 actions).

4 / 5

Completeness

Explicitly answers both what ("find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities") and when ("Use when the user says 'co-marketing,' 'partner marketing,' ...") with concrete trigger phrases — exactly anchor 5, and far above the anchor 3 case where 'when' is only weakly implied.

5 / 5

Trigger Term Quality

Nine natural trigger phrases including synonyms ("co-marketing," "partner marketing," "cross-promotion," "co-brand") and a natural user question ("who should we partner with"). This is comprehensive natural-term coverage matching anchor 5, clearly above anchor 4's "a few natural terms missing."

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche with distinct triggers, and closes with explicit boundary routing ("For customer referral programs, see referrals. For launch-specific partnerships, see launch."), minimizing conflict with adjacent skills. Matches anchor 5; anchor 4's "minor overlap risk" understates the deliberate disambiguation.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/co-marketing/SKILL.md

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.