JasonColapietro/suede-creator-skills / skills/suede-influencer-outreach
suede-influencer-outreach
VerifiedUse when asked "pitch this creator" or to repair an influencer or B2B creator-program first touch. Suede grounds one message in a named audience fact, states real compensation and one ask, fits the published contact route and stops the two-follow-up plan at a positive reply. NOT FOR: affiliate mechanics (use suede-referrals), brand partnerships (use suede-co-marketing), cold B2B email (use suede-cold-email), or journalist pitches (use suede-public-relations).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.8 KB |
| SKILL.md | skill md | 11.0 KB |
| agents/openai.yaml | config | 571 B |
| evals/evals.json | config | 3.8 KB |
| references/channel-and-manager.md | markdown | 2.7 KB |
| references/examples.md | markdown | 4.4 KB |
| references/follow-up-cadence.md | markdown | 2.3 KB |
| references/pitch-anatomy.md | markdown | 6.5 KB |
| references/usage-contract.md | markdown | 896 B |
evals/evals.json
View on GitHub{
"skill_name": "suede-influencer-outreach",
"evals": [
{
"id": 1,
"prompt": "Pitch @plantsbypriya for our ceramic planter launch. She's vetted, 48k on Instagram, lists a business email in her bio. Offer is a free planter plus 15% commission, 30-day attribution, paid monthly.",
"expected_output": "Should check for product-marketing.md first. Should ask for the missing inputs one at a time (fit evidence or a specific post, brand voice, signer, which CTA the brand can honor) rather than drafting immediately. Should propose two or three angles with a recommendation and wait for a pick. The eventual email should open on a verifiable creator-specific fact framed as audience fit, state 15%, 30 days, monthly payout, and a rough per-sale figure, carry exactly one low-friction ask, and include a Personalization source line. Should not include contract, exclusivity, or disclosure terms.",
"assertions": [
"Checks for product-marketing.md",
"Asks for fit evidence instead of inventing a post",
"Asks one question per message",
"Proposes 2-3 angles with a recommendation before drafting",
"Routes to the listed business email, not a DM",
"States commission rate, attribution window, and payout schedule",
"Exactly one CTA",
"Includes a Personalization source line",
"No contract, exclusivity, or disclosure language in the pitch"
],
"files": []
},
{
"id": 2,
"prompt": "Write the first-touch email to the DevOps newsletter writer from our shortlist. $2,000 for a sponsored deep-dive issue. Her issue last week on alert fatigue is why we picked her. She lists a partnerships email. Sign it from Sam, Head of Partnerships.",
"expected_output": "Should treat this as B2B and frame the pitch around a business problem her readers have, using the alert-fatigue issue as the opener. Should name the flat fee and budget without a rate card. Deliverable stays a one-line sketch. One low-friction ask. Signed by Sam. Should output the full package with a two-follow-up plan in which each follow-up is one or two sentences and carries a new angle.",
"assertions": [
"Frames the pitch around the audience's business need",
"Opens on the alert-fatigue issue as audience fit",
"Names the $2,000 flat fee without a rate card",
"Deliverable is a one-line sketch",
"Exactly one CTA",
"Signed by a named person",
"Follow-up plan has two follow-ups, each one or two sentences with a new angle",
"No follow-up says 'just checking in' or 'bumping this'"
],
"files": []
},
{
"id": 3,
"prompt": "This creator lists a talent manager but I'd rather just DM her directly since DMs get faster replies. Write me the DM. Gifted product only, a skincare set.",
"expected_output": "Should flag once that the creator lists a manager and recommend pitching the manager, since going around a listed manager can end the conversation. The recommendation is advisory: the skill should not refuse the user's choice. It should offer the manager version and, if the user keeps the DM, write the DM to the 2-4 sentence, no-links rules. Should never plan both a manager pitch and a DM in parallel. Should state plainly that the offer is gifted product with no payment implied, and ask for or flag the missing fit evidence rather than inventing it.",
"assertions": [
"Flags the listed manager once and recommends that route",
"Does not refuse the user's choice to DM",
"Never plans a manager pitch and a DM in parallel",
"States plainly the offer is gifted product, with no payment implied",
"Does not invent a post or fit evidence",
"Exactly one CTA"
],
"files": []
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |