JasonColapietro/suede-creator-skills / skills/suede-co-marketing
suede-co-marketing
VerifiedSuede Co-Marketing Skills. Use when asked to "find co-marketing partners" or plan a joint campaign: evidence-backed fit, reciprocal value, format, roles, consent, shared KPIs and content. NOT FOR: affiliate/referral programs (suede-referrals), software release packaging (suede-launch-packaging), or partner-facing sales collateral (suede-sales-enablement).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.3 KB |
| SKILL.md | skill md | 12.8 KB |
| agents/openai.yaml | config | 539 B |
| evals/evals.json | config | 6.8 KB |
| references/campaign-formats.md | markdown | 2.7 KB |
| references/output-templates.md | markdown | 2.0 KB |
| references/worked-contract.md | markdown | 1.8 KB |
references/campaign-formats.md
View on GitHub# Co-Marketing Campaign Formats
Read this when selecting the format for a joint campaign: the output skeleton
requires the selected format to be named from one of the four families below.
## Content Partnerships
| Format | Effort | Lead Sharing | Best For |
|--------|--------|--------------|----------|
| **Co-authored blog post** | Low | Shared byline, link exchange | Thought leadership, SEO |
| **Joint ebook/guide** | Medium | Gated, split leads | Lead gen, deeper topic |
| **Research report** | High | Gated, split leads | Authority, PR |
| **Guest newsletter swap** | Low | Each keeps own leads | Audience exposure |
| **Podcast guest exchange** | Low | Each keeps own leads | Relationship building |
## Webinars & Events
| Format | Effort | Lead Sharing | Best For |
|--------|--------|--------------|----------|
| **Joint webinar** | Medium | Gated, split leads | Lead gen, product education |
| **Virtual summit panel** | Medium | Host keeps registrations | Multi-partner exposure |
| **Co-hosted workshop** | High | Gated, split leads | Hands-on education, deeper engagement |
| **Conference booth sharing** | Medium | Each keeps own scans | Cost splitting, audience overlap |
| **Joint happy hour/dinner** | Low | Each keeps own leads | Relationship building at events |
## Product & Integration Marketing
| Format | Effort | Lead Sharing | Best For |
|--------|--------|--------------|----------|
| **Integration launch** | Medium | Each keeps own signups | Existing integration partners |
| **Joint case study** | Medium | Each keeps own leads | Shared customers |
| **"Better together" landing page** | Low | Split by form owner | Integration discovery |
| **Bundle or discount** | Medium | Split by purchase path | Conversion boost, cross-sell |
| **In-app cross-promotion** | Medium | Each keeps own users | User activation |
## Community & Social
| Format | Effort | Lead Sharing | Best For |
|--------|--------|--------------|----------|
| **Social media takeover** | Low | Each keeps own followers | Audience exposure |
| **Joint giveaway/contest** | Low | Gated, split entries | List building, engagement |
| **Slack/Discord community collab** | Low | Each keeps own members | Community building |
| **Joint AMA or Twitter Space** | Low | Each keeps own leads | Thought leadership |
## Lead-sharing shorthand
Two arrangements cover almost every format above, and the campaign plan must
state which one applies:
- **Gated / split**: one shared form, leads delivered to both parties under an
agreed split. Requires a written data-handling and consent arrangement.
- **Each keeps own**: no shared list; each side keeps whoever it brought.
Simpler, and the default when the parties have not agreed data terms.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |