Marketing

Skills for planning, drafting, and adapting marketing content.

14 of 14 skills

type

Review Responder
Turns customer reviews, good and bad, into on-brand public replies that defuse complaints and make promoters feel seen.
skillinstructionsworkflowreply-templatestone-calibration
by Muse Skills editors · Written for this directory
ViewInstall the "Review Responder" skill. Its full source is below. Create it at ~/workspace/skills/review-responder/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: review-responder description: Drafts on-brand public replies to customer reviews: defuses bad reviews, thanks good ones, and moves real problems offline. Trigger phrases: "draft a reply to this review", "respond to this bad review", "write review responses", "review reply". --- # Purpose Do one narrow job: turn raw customer reviews into public replies worth publishing. The skill takes the review text, the star rating, the business name, and your tone, then drafts a reply that sounds like a real human who read the review. For negative reviews it acknowledges, takes the fix offline, and never argues in public. For positive reviews it thanks specifically, names something the reviewer mentioned, and encourages a return visit. You always review and post; the skill only drafts. # Workflow 1. Collect the inputs: the review text, star rating, platform (Google, Yelp, Amazon, TripAdvisor, app store), business name, and your desired tone (warm and casual, professional, playful, formal). 2. Classify the review: praise, complaint, mixed, or spam/suspicious. Spam and policy-violating reviews get a brief factual reply plus a flag-and-report recommendation, not a full engagement. 3. For complaints: open by naming the specific issue (never a generic "sorry for your experience"), take responsibility for the part that is yours, give a private contact path (name, phone or email placeholder), and invite them to reach out. Never argue the facts in public, never admit legal fault, never promise refunds or compensation in the reply. 4. For praise: thank them by naming the specific thing they liked, add one line of personality, and invite them back. Skip the hard sell; a genuine reply earns more than a coupon. 5. For mixed reviews: acknowledge the positive, address the negative with the complaint playbook, and keep the reply shorter than the review. 6. Produce two versions: the recommended reply and a shorter alternate. Both stay under 100 words unless the platform norms differ. Ask for the business details you need before drafting. # Output Contract - The review classification (praise, complaint, mixed, or spam) - A recommended reply under 100 words, ready to copy - A shorter alternate version - A one-line note on what to fill in (contact name, phone, order details) before posting - For spam: a brief reply plus a flag-and-report recommendation # Operating Rules - Never post anything to a review site; you draft, the owner posts. - Never include private customer details in a public reply. - Never promise refunds, discounts, or compensation in a reply unless the owner told you to. - Never argue with the reviewer in public, even when they are wrong. Take it offline. - Never invent facts about what happened. If the complaint is vague, ask for context or keep the reply general and forward it to a private channel. - Match the tone the owner gave you; keep the voice human, not corporate filler.
Ad Hook Researcher
Finds the ad hooks already winning in your niche and turns them into a creative brief.
skillinstructionsworkflowbrief-template
by Muse Skills editors · Written for this directory
ViewInstall the "Ad Hook Researcher" skill. Its full source is below. Create it at ~/workspace/skills/ad-hook-researcher/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: ad-hook-researcher description: Collect winning ad hooks in a niche from a product URL into a creative brief. Trigger phrases: "research ad hooks", "find winning hooks", "build an ad hook brief". --- # Purpose Find the ad hooks already winning in your niche and hand them to you as a creative brief you can work from. You give a product URL (or a niche description), and Ad Hook Researcher returns a hook bank, the patterns behind the hooks, the angles nobody is using, and three starter hook drafts written for your product. # Workflow 1. Read the product URL or niche description. If you gave both, use the page to ground the niche read; if you gave one, start there. 2. Read the product's own landing page: headline, subhead, hero claims, pricing framing, and the promises on the page. This is the baseline the brief adapts hooks for. 3. Search the niche for active ads: public ad libraries, competitor landing pages, and ad creative roundups. Note which ads or hooks keep showing up across sources; persistence is an observed signal, not proof of performance. 4. Extract each hook: the first five to ten words plus its angle. Tag the angle: transformation, curiosity gap, direct callout, proof, offer, or contrast. 5. Cluster the hooks by angle and note which clusters dominate the niche and which angles are missing entirely. 6. Keep only hooks from ads that were actually found. Never invent ad text. Quote short hooks verbatim; summarize longer ones. 7. Write three starter hooks for the product, clearly marked as drafts, each using a different winning angle from the niche. 8. Write the creative brief in the Output Contract shape and send it. # Output Contract The creative brief, in this order: - Niche snapshot: what your page leads with today, in three lines - Hook bank: 10 to 15 hooks, each with an angle tag and the source type it was found in - Pattern notes: three to five recurring patterns across the niche - Gaps: angles the niche is not using, with one line on why each could fit - Starter hooks: three drafts for your product, marked as drafts, each using a different winning angle - Sources checked: a short list of what was actually read # Operating Rules - Read public pages and public ad libraries only. Never log in, and never work around a paywall or a bot check. - Never present persistence as proof of performance. Say what was observed. - Never invent ad copy. Every hook in the bank comes from a real page or ad that was read during the run. - Never buy media, post an ad, or contact a competitor. Research only. - If the niche is too thin to fill the hook bank, deliver what was found and say what is missing rather than padding it. - Run once per request; do not re-run on a schedule unless asked.
Lead Scorer
Scores a list of public leads against your ideal customer profile and ranks them.
skillinstructionsworkflowscoring-rubric
by Muse Skills editors · Written for this directory
ViewInstall the "Lead Scorer" skill. Its full source is below. Create it at ~/workspace/skills/lead-scorer/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: lead-scorer description: Score public leads against your ideal customer profile and rank them. Trigger phrases: "score these leads", "rank my leads", "which leads first". --- # Purpose Stop working your lead list in alphabetical order. Lead Scorer takes the list you hand it, scores each lead against the ideal customer profile you define, and returns a ranked list with the evidence behind every score. You see exactly why a lead sits at the top or the bottom, so your outreach starts with the people most likely to be a fit. # Workflow 1. The user provides the ideal customer profile: industry, company size, role titles, signals that suggest fit (hiring, funding, tech stack), and deal breakers. 2. The user provides the lead list: names plus whatever public data they have per lead (company, title, location, public posts, listing details). 3. Score each lead 0 to 100: fit signals add points, missing basics subtract, deal breakers zero the score. Record the evidence for every point. 4. Rank the list high to low. Group obvious tiers: reach out now, nurture later, skip. 5. Deliver the ranked list with one evidence line per lead, plus the rubric used, so the user can reweight it. # Output Contract Each run delivers: - The ranked lead list with 0-100 scores - One evidence line per lead showing why it scored that way - Three tiers: reach out now, nurture later, skip - The rubric, written out, so scoring stays repeatable A score is a ranking aid, not a verdict. The user reviews the evidence before acting on it. # Operating Rules - Score only public data and what the user provides. Never scrape private accounts, and never use bought or breached data. - A deal breaker zeroes the score but keeps the lead visible, flagged, with the reason shown. - Never inflate a score to be encouraging. A weak list gets weak scores, honestly. - The rubric is fixed for the whole list. Never reweight mid-list to favor one lead. - Draft no outreach and contact nobody. Scoring ends where outreach begins, and a human writes and sends every message. - Keep the user's lead list private to their workspace.
Prospect Reply Drafter
Reads a prospect's reply in the context of the thread and drafts the right next step.
skillinstructionsworkflowtemplates
by Muse Skills editors · Written for this directory
ViewInstall the "Prospect Reply Drafter" skill. Its full source is below. Create it at ~/workspace/skills/prospect-reply-drafter/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: prospect-reply-drafter description: Read a prospect's reply in the context of the thread and draft the right next step. Trigger phrases: "draft a reply to this prospect", "how should I respond", "write a follow-up for". --- # Purpose Read a prospect's latest reply together with the full thread history, figure out what the prospect is actually signaling, and draft the single best next move. It classifies the reply, an objection, a timing deferral, a referral, a polite no, or genuine interest, and writes a response matched to that signal instead of a generic follow-up. # Workflow 1. Read the full thread: your outreach, their reply, and any earlier exchanges. Ask for the offer or call to action if it is not clear from the thread. 2. Classify the reply: interested, objection, timing deferral, referral, polite no, or ambiguous. 3. Identify the signal underneath the words: what they care about, what is blocking them, what would change their mind. 4. Draft one reply: short, specific, and matched to the classification. Handle objections by addressing the block, not by arguing. 5. Give the human a send-or-edit choice: the draft plus two alternate lines for the risky spots. # Output Contract - Classification: one label plus the evidence line from the reply. - Signal read: what the prospect cares about and what blocks them, in two bullets. - Draft reply: subject or opener plus body, ready to paste, under 120 words. - Alternates: two rewrite options for the key line. # Operating Rules - Never send anything; the human reviews and sends every reply. - Never invent facts about the product, pricing, or the prospect. - Never guilt-trip, never pressure, never fake a personal connection. - If the reply is a no, draft a graceful close, not a rescue attempt.
Ad Spend Auditor
Audits an ad spend export, flags where money is burning, and suggests creative refresh angles.
Tested in Museskillinstructionsworkflowreport
by Muse Skills editors · Written for this directory
ViewInstall the "Ad Spend Auditor" skill. Its full source is below. Create it at ~/workspace/skills/ad-spend-auditor/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: ad-spend-auditor description: Audit an ad spend export for wasted spend and creative fatigue, then suggest refresh angles. Trigger phrases: "audit my ad spend", "review my ad spend", "find wasted ad spend". --- # Purpose Find the specific places where ad money is burning: campaigns with rising cost per result and no conversions, ad sets spending on narrow segments that never convert, and creative that has run so long its frequency is climbing while its click-through rate falls. Report waste first and refresh ideas second, all from one export. # Workflow 1. Read the ad spend export: a CSV or pasted table with at least campaign, ad set, ad name, spend, impressions, clicks, conversions, and the date range. Ask which platform and range if either is unclear. 2. Compute per campaign and per ad set: spend, impressions, CTR, cost per click, cost per result, and conversion count. 3. Flag spend without results: anything over the user's waste threshold (ask for one; default $50) with zero conversions. 4. Flag fatigue: ads where frequency is rising and CTR is falling across the range, or the same creative live more than 30 days with falling performance. 5. Flag overlap waste: ad sets on the same platform targeting near-identical audiences with near-identical creative. 6. For each flagged item, draft one concrete refresh angle: a new hook, a new audience slice, or a pause recommendation, grounded in the numbers. 7. Write the report in the Output Contract shape. Never adjust a budget or pause anything; analysis only. # Output Contract - Waste table: item, spend, results, and why it is flagged. - Fatigue table: creative, days live, CTR trend, frequency trend. - Refresh angles: one short line per flagged item, most spend first. - One-paragraph summary naming the single biggest burn. # Operating Rules - Never change bids, budgets, audiences, or campaign status; read-only analysis. - Never invent numbers; every figure comes from the export. - Ask for missing columns before guessing. - Keep the report short enough to act on in one sitting.
Alt-Text Writer
Writes accurate, concise alt text for any image, for accessibility and SEO.
Tested in Museskillinstructionsworkflowrules
by Muse Skills editors · Written for this directory
ViewInstall the "Alt-Text Writer" skill. Its full source is below. Create it at ~/workspace/skills/alt-text-writer/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: alt-text-writer description: Generate accurate, concise alt text for images, tuned for accessibility and SEO. This is not a caption writer: it describes the image for people who cannot see it. Trigger phrases: "write alt text for this", "alt text for this image", "describe this image for screen readers". --- # Purpose Alt-Text Writer turns an image into good alt text: a short, factual description of what the image shows, written for screen readers and search engines. Unlike a caption, which adds personality or a call to action, alt text replaces the image. It should tell a person who cannot see the image what matters in it, in plain words. # Workflow 1. Look at the image the user provides (a file, a URL, or a detailed description of what the image shows). 2. Ask what the image is for if it is not obvious: a product photo, a blog illustration, a chart, or a decorative banner. Decorative images get empty alt text, not a description. 3. Describe the essential content first: the subject, the action, and the setting. Add colors, text in the image, or data points only when they matter to understanding it. 4. Keep it under 125 characters when possible. If the image needs more (a chart, an infographic), write a short alt plus a longer text alternative the user can place next to the image. 5. Suggest a short SEO-friendly variant only when the user asks for one, with the page's focus keyword worked in naturally. # Output Contract Every result has three parts, in this order: - Alt text: the final alt attribute text, quoted and ready to paste. - Character count: the length, so the user can see it fits. - Long description (only for complex images): a fuller text alternative for charts, diagrams, or infographics. # Operating Rules - Describe only what is visible; never guess at names, places, or events that cannot be seen. - Never start with "image of" or "picture of"; screen readers already announce it is an image. - Never write alt text designed to mislead: no keyword stuffing, no claims the image does not support. - Mark decorative images with empty alt text and say why. - If the image is unclear or the request is ambiguous, ask before writing. - Keep each alt text to one sentence unless a longer alternative is genuinely needed.
Cold Outreach Drafter
Prospecting emails built from real research on the lead, not templates.
Tested in Museprompt packprompt-text
by Muse Skills editors · Written for this directory
ViewInstall the "Cold Outreach Drafter" prompt pack. Its full source is below. Save it to ~/workspace/prompts/cold-outreach-drafter.md (create the folder if needed). Then confirm it is installed and show me the full text. --- SOURCE --- This prompt pack drafts a cold outreach email from lead research. Paste it into Muse along with what you know about the lead. > Draft a cold outreach email to [name, role, company]. What I > know about them: [research notes]. Structure: subject line > under 8 words, one opening line that proves I researched them > (specific, not "I love what you're doing"), one sentence on > the problem I solve for companies like theirs, one proof > point (a result, not a claim), and one low-friction ask. > Rules: under 120 words total, no "I hope this finds you well", > no exclamation marks, no fake familiarity. If my research > notes are too thin to write a specific opener, say so and > tell me what's missing instead of faking it. Do not send; > draft only.
Testimonial Collector
Quarterly: picks happy customers and drafts the ask.
Tested in Museworkflowinstructionsworkflowschedule
by Muse Skills editors · Written for this directory
ViewSet up the "Testimonial Collector" workflow. Its full source is below. Default schedule: first Monday of each quarter at 09:00 local time. Ask me to confirm or change this time before you create the recurring job. Once I confirm, create the job. Tell me the job name and the confirmed schedule when it is set up. --- SOURCE --- name: testimonial-collector description: Quarterly testimonial collection, picks the right customers to ask, drafts each ask personally, and tracks who replied. Trigger phrases: "collect testimonials", "ask for reviews", "testimonial drive". schedule: quarterly, first Monday of Jan/Apr/Jul/Oct at 09:00 local time. Confirm the time with the user before the first scheduled run. trigger: the scheduled time, or a manual "collect testimonials" request. steps: 1. First run: ask the user for the customer list with notes on who had a good outcome, and where testimonials should go (site, Google, etc.). 2. Each quarter: pick 3-5 customers with the best outcomes who haven't been asked in the last year. 3. Draft each ask personally: reference their specific result, suggest 2-3 prompts they can answer (not "write whatever"), and keep it short enough to say yes to. 4. Track: asked, replied, published. Carry non-responders one quarter, then rotate them out. 5. Write the report in the Output shape. The user sends the asks themselves. output: - This quarter's asks: customer, why them, the drafted ask - Waiting on: asked last quarter, not yet replied - Published: newly collected testimonials to post rules: - Drafts only. Never send anything to a customer. - Every ask references a specific result. No generic "would you review us" blasts. - Don't ask the same person twice in a year. - Run only on the confirmed schedule or when asked.
Competitor Watch
Monthly: what competitors launched or posted, in one brief.
Tested in Museworkflowinstructionsworkflowschedule
by Muse Skills editors · Written for this directory
ViewSet up the "Competitor Watch" workflow. Its full source is below. Default schedule: first Monday of each month at 09:00 local time. Ask me to confirm or change this time before you create the recurring job. Once I confirm, create the job. Tell me the job name and the confirmed schedule when it is set up. --- SOURCE --- name: competitor-watch description: Monthly competitor brief: what each named competitor launched, posted, or changed, and what it means for you. Trigger phrases: "watch my competitors", "competitor update", "what did competitors do this month". schedule: monthly, first Monday at 09:00 local time. Confirm the time with the user before the first scheduled run. trigger: the scheduled time, or a manual "competitor update" request. steps: 1. First run: ask the user for the competitor list (3-8 names) and what counts as signal (launches, pricing changes, big hires, notable posts). 2. Each run: check each competitor's public pages, blog/changelog, pricing page, social accounts, for the past 30 days. 3. For each item: what happened, when, and one line on why it matters to the user. 4. Close with "so what": the 2-3 moves worth a response, and the rest as noise. 5. Write the brief in the Output shape and send it. output: - Per competitor: what happened this month, one line each with dates - So what: the moves worth responding to, and the suggested response - Noise: everything else, one line total rules: - Public pages only. Never sign up for trials, newsletters, or demos as the user. - "Why it matters" is one line, not a strategy memo. - If a competitor did nothing notable, say so. Padding is noise. - Run only on the confirmed schedule or when asked.
Launch Checklist
Product launch promo plan: announcements, posts, emails, in order.
Tested in Museskillinstructionsworkflowchecklist
by Muse Skills editors · Written for this directory
ViewInstall the "Launch Checklist" skill. Its full source is below. Create it at ~/workspace/skills/launch-checklist/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: launch-checklist description: Build an ordered launch promotion plan: announcements, posts, and emails sequenced across launch week, sized to a solo founder or small team. Trigger phrases: "plan my launch", "launch promotion checklist", "how do I announce this". --- # Purpose Launches fail quietly when the announcement plan is "post once and hope." This skill turns a launch into an ordered checklist across the week, sized for one person, not a marketing department. # Workflow 1. Ask the user for: what is launching, launch date, one sentence on who it is for, and where they already have an audience (newsletter size, social accounts, communities). 2. Build the plan in four phases: - T-7 to T-2 (tease): 2-3 short posts, one email teaser - T-1 (eve): checklist of logistics: links live, analytics on, support ready - Launch day: announcement post, email, community posts in order, with times - T+1 to T+7 (follow-through): thank-yous, first-user stories, one "how it works" post 3. Size everything to the user's actual audience. No "hire a PR firm" for a 200-subscriber newsletter. 4. Report in the Output Contract shape. # Output Contract - Launch week timeline: day by day, task by task, with the channel and the one-line point of each piece - Logistics checklist: links, analytics, support: the unglamorous half - Cut list: what a solo founder should skip, stated plainly # Operating Rules - One person can execute the whole plan in the week. If a task needs a team, it gets cut or simplified. - Every piece has a point in one line. No content for content's sake. - Never post or email anything. Drafts are the user's to approve. - The plan fits the audience they have, not the one they wish they had.
Content Calendar
Topic and cadence in; a four-week calendar of post ideas out.
Tested in Museworkflowinstructionsworkflowschedule
by Muse Skills editors · Written for this directory
ViewSet up the "Content Calendar" workflow. Its full source is below. Default schedule: first Monday of each month at 09:00 local time. Ask me to confirm or change this time before you create the recurring job. Once I confirm, create the job. Tell me the job name and the confirmed schedule when it is set up. --- SOURCE --- name: content-calendar description: Monthly content calendar: four weeks of post ideas for your topic and cadence, with hooks written. Trigger phrases: "plan next month's content", "content calendar for", "what should I post". schedule: monthly, first Monday at 09:00 local time. Confirm the time with the user before the first scheduled run. trigger: the scheduled time, or a manual "plan next month's content" request. inputs: topic, platforms, posts per week per platform, any themes or launches coming up. steps: 1. Confirm the inputs with the user the first time: topic, platforms, cadence. Remember them. 2. Build four weeks of ideas. Mix the formats: teach (how-to), show (behind the scenes), prove (results or testimonials), ask (questions and polls). 3. Every idea gets: the working title, the hook (first line), the format, and the platform. 4. Tie at least two ideas per month to something timely: a launch, a season, a trend in the topic. 5. Write the calendar in the Output shape and send it. output: - Week-by-week calendar: day, platform, working title, hook, format - Format mix summary (counts of teach / show / prove / ask) - Two "banked" backup ideas for weeks when nothing gets written rules: - Ideas, not finished posts. Hooks written, bodies left to the user. - Never invent launches, numbers, or testimonials. Mark placeholders clearly. - No posting, scheduling, or publishing. Planning only. - Run only on the confirmed schedule or when asked.
Facebook Ad Copy Drafter
Product and audience in; three ad variants with different hooks out.
Tested in Museprompt packinstructionsad-templates
by Muse Skills editors · Written for this directory
ViewInstall the "Facebook Ad Copy Drafter" prompt pack. Its full source is below. Save it at ~/workspace/prompts/facebook-ad-copy-drafter.md exactly as given, with the frontmatter (name and description) and the prompt body. Do not run it now. Then confirm it is saved and tell me the trigger phrases: "write Facebook ad copy", "draft ad variants", "create ad copy". --- SOURCE --- # Facebook Ad Copy Drafter How to use: describe the product and the audience. It returns three ad variants with different hooks, each with primary text, headline, and description, ready to paste into Ads Manager. Trigger phrases: "write Facebook ad copy", "draft ad variants", "create ad copy". Save it as a reusable prompt pack named "Facebook Ad Copy Drafter". ## The prompt Draft Facebook ad copy. I will give you: the product (what it is, price, key benefit), the audience (who they are, what they care about), and the goal (clicks, signups, purchases). 1. Write three variants, each with a different hook: - Variant A: the direct benefit ("what you get"). - Variant B: the pain point ("what's broken now"). - Variant C: social proof or specificity (a number, a testimonial shape, a concrete detail). 2. Each variant gets: primary text (under 125 characters so it doesn't truncate), headline (under 40 characters), and description (one line). 3. Match the tone to the audience, plain language for most, jargon only if the audience actually uses it. 4. End with one line per variant: who this hook is for and when to use it. Rules: no false urgency ("only 3 left!") unless it is true. No claims you can't back up. Never create or launch a campaign: drafts only.
SEO Meta Writer
Topic or URL in; title tag and meta description out, within limits.
Tested in Museprompt packinstructionsmeta-template
by Muse Skills editors · Written for this directory
ViewInstall the "SEO Meta Writer" prompt pack. Its full source is below. Save it at ~/workspace/prompts/seo-meta-writer.md exactly as given, with the frontmatter (name and description) and the prompt body. Do not run it now. Then confirm it is saved and tell me the trigger phrases: "write SEO metadata", "write a meta description", "create a title tag". --- SOURCE --- # SEO Meta Writer How to use: give a page URL or a topic plus the target keyword. It returns a title tag and meta description that fit the limits and read like a human wrote them. Trigger phrases: "write SEO metadata", "write a meta description", "create a title tag". Save it as a reusable prompt pack named "SEO Meta Writer". ## The prompt Write the SEO metadata for this page. I will give you a URL or a topic, plus the primary keyword. 1. If I give a URL, read the page first and base the copy on what it actually says. If I give a topic, ask one clarifying question only if the angle is unclear. 2. Title tag: under 60 characters, keyword near the front, written as a promise of what the page delivers. 3. Meta description: 150-160 characters, keyword included naturally, ending with the reason to click. 4. Give two options for each, labeled A and B, with different angles (one direct, one curiosity-driven). 5. Show the character count next to each. Rules: no keyword stuffing, no clickbait that the page can't deliver on. If the page is thin, say what it would need before the metadata matters.
Social Repurposer
One long post becomes an X thread, a LinkedIn post, and a caption.
Tested in Museprompt packinstructionsplatform-templates
by Muse Skills editors · Written for this directory
ViewInstall the "Social Repurposer" prompt pack. Its full source is below. Save it at ~/workspace/prompts/social-repurposer.md exactly as given, with the frontmatter (name and description) and the prompt body. Do not run it now. Then confirm it is saved and tell me the trigger phrases: "repurpose this content", "turn this into social posts", "make social versions". --- SOURCE --- # Social Repurposer How to use: paste one piece of long-form content (a blog post, a newsletter section, a thread draft). It returns platform-native versions: an X thread, a LinkedIn post, and a short-form caption. Trigger phrases: "repurpose this content", "turn this into social posts", "make social versions". Save it as a reusable prompt pack named "Social Repurposer". ## The prompt Repurpose this content for social. I will paste the source text. 1. Extract the core idea in one sentence before adapting anything. 2. X thread: 5-8 posts, each under 280 characters. First post is the hook: the most surprising or useful claim, stated plainly. Last post is the takeaway or call to action. Number them. 3. LinkedIn post: 150 words max, conversational, line breaks for readability. Open with the hook, close with a question. 4. Short-form caption (Instagram/Threads): 2-3 sentences plus up to 5 relevant hashtags. 5. Keep the author's voice, match the tone of the source, not a generic "social media voice". Rules: never invent facts not in the source. If the source is too thin for three formats, say which formats work and skip the rest. Never post anything anywhere.