Meta’s Muse AI has built-in skills — reusable workflow packs that turn one-off requests into repeatable routines. On 29 September 2026, Meta framed the feature set of Muse for Small Business as “a collection of new skills and connectors inside Muse to help people run their businesses”, and Meta’s own public Muse documentation now describes built-in Skills. But there is still no upload-your-own-skill button, so the community solved it the simple way: paste-to-install. Below are 8 original, free copy-paste skill packs for Muse — for email, meetings, money, content, research and travel — written so you can drop them into a Muse chat today.
What is a Muse skill?
A skill is a portable set of written instructions that teaches an AI assistant a reusable workflow: when to trigger it, what steps to follow, and what good output looks like. The community has standardised on the open Agent Skills format — a SKILL.md markdown file with YAML frontmatter (name + description) followed by plain instructions — so the same skill text works across assistants that support the format, including Meta’s Muse. Think of it as the difference between a prompt (one question) and a skill (a whole job you can rerun).
Built-in skills vs community skills: what Muse actually has today
The honest picture, as of October 2026:
| Built-in skills (Meta) | Community skills (paste-to-install) | |
|---|---|---|
| Where they live | Inside Muse, shipped by Meta — e.g. the small-business skill set announced 29 Sep 2026 (advertising, sales, social media, finance, creative work, customer communication) | GitHub repos and skill libraries on the open web, as SKILL.md text |
| How you install | Automatic — they ship with Muse (US and Canada, iOS/Android/muse.ai at the 29 Sep announcement) | Copy-paste: open the skill text, paste it into a Muse chat, and ask Muse to “use this skill whenever I ask about <topic> and remember it for our future conversations” |
| Upload flow | Not applicable | Not announced. Meta has said more of its own Skills are coming but has not announced a way to upload yours. Muse Code (the developer tool) already reads standard SKILL.md files, so these files are ready if uploads open. |
| Approval line | “Nothing publishes, sends, or spends without your approval” — Meta’s stated rule | Same approvals apply — a skill is just text instructions; Muse still asks before important actions |
Our take: the paste-to-install workaround is not a hack — it is how skills work by design. A skill is instructions, and Muse follows instructions in context. When Meta ships a native install flow, every skill below is already in the right format to move over.
How to install any skill in Muse (the 60-second method)
- Copy the skill block — each pack below is formatted like a
SKILL.md: name, when it triggers, and the steps. - Paste it into a Muse chat (Muse runs inside the Meta AI app, iOS/Android/muse.ai) and add one line: “Please use this skill whenever I ask about <topic>. Remember it for our future conversations.”
- That’s it. From then on, asking “give me my morning briefing” runs the whole workflow instead of a fresh one-off answer.
Meta’s own writing tips apply here: give context (who it’s for, what good looks like), set boundaries (“only search my email, not my texts”), and correct it as you go (“too long” works, and Muse learns your preferences).
8 free copy-paste Muse skill packs
These 8 packs are original, desk-written for this guide (not copied from any library — see Sources and Methodology), grouped work → money → life. Each follows the same mini-format: trigger (when to ask) and the skill text to paste.
1. Morning Briefing
Trigger: “Give me my morning briefing.”
--- name: morning-briefing description: Runs each morning as a 5-minute workday startup routine. --- 1. Check my calendar for today: list meetings with time, attendees, and prep needed. 2. Scan my unread email from overnight: flag only what needs a reply today, sorted urgent first. 3. Give me the 3 things that matter most today in priority order, one line each. 4. End with one question: "What is the single most important outcome for today?" Rules: keep it under 250 words. Never invent calendar events or emails.
2. Inbox Triage
Trigger: “Triage my inbox.”
--- name: inbox-triage description: Sorts an unread inbox into action buckets with reply drafts. --- 1. Group unread messages into: Reply today / FYI / Can wait / Likely spam. 2. For "Reply today": draft a short reply for each (my voice: direct, warm, under 80 words each). 3. For "Likely spam": say so plainly with the reason, don't delete anything yourself. 4. Summarise: counts per bucket + the single email I should answer first. Rules: nothing sends without my explicit approval on each draft.
3. Meeting Prep Pack
Trigger: “Prep me for my 2pm with [name].”
--- name: meeting-prep-pack description: Builds a 5-minute pre-read before any meeting. --- 1. Pull the meeting's invite details: title, attendees, time. 2. Search my email/notes for recent threads with each attendee. 3. Produce a pre-read: (a) why this meeting exists, (b) 3 questions I should ask, (c) 1 fact to drop that shows I did homework. 4. After I confirm, offer a 3-line follow-up email draft for when the meeting ends. Rules: cite where each fact came from (email/calendar/note). Flag anything unconfirmed as unconfirmed.
4. Expense Guard (money)
Trigger: “Run my weekly expense check.”
--- name: expense-guard description: Weekly personal spending review with a savings nudge. --- 1. Ask me to paste or upload this week's transactions (or list them verbally). 2. Categorise into: fixed / flexible / fun. 3. Report: total spent vs my stated weekly budget, the single biggest leak, and one concrete cut that saves money next week. 4. Keep a running note of my monthly average and compare this week to it. Rules: this is spending analysis, not financial advice. Never guess missing numbers — ask.
5. Social Crosspost Pack (content)
Trigger: “Turn this into a crosspost pack: [topic + photo/draft].”
--- name: social-crosspost-pack description: One idea becomes a caption pack, one per platform. --- 1. Take my topic (and any photo or draft I give) and write: one idea per platform. 2. Instagram: caption + hook first line + hashtags. TikTok/Shorts: spoken script under 60 seconds. X: thread of 3 short posts. Facebook: longer caption with a question ending. 3. Keep one brand voice across all four (ask me for my voice rules the first time and save them). Rules: stage drafts only — nothing posts. One post per platform, never the same text pasted everywhere.
6. Research Digester
Trigger: “Digest this research: [link or pasted text].”
--- name: research-digester description: Turns any report or article into a decision-ready brief. --- 1. Read the material I provide (link or pasted text). 2. Output: (a) the 3 key claims, each with the evidence it rests on; (b) what the author wants me to believe vs what is actually proven; (c) a 2-line "so what" for my work. 3. End with 3 follow-up questions I should investigate. Rules: label vendor-reported figures as vendor-reported. If a claim lacks evidence in the text, say so.
7. Trip Planner (travel)
Trigger: “Plan my 3-day trip to [city].”
--- name: trip-planner description: Builds a day-by-day trip plan from a destination and dates. --- 1. Ask: dates, budget per day, who is travelling, interests (food / sights / rest). 2. Build a day-by-day plan: morning / afternoon / evening blocks with one anchor activity each. 3. Add practicals: rough cost estimate, 2 booking links to verify, 1 backup plan for bad weather. 4. Keep the plan editable — "swap day 2 morning" should re-plan just that block. Rules: prices are estimates unless from a checked source. Say which is which.
8. Weekly Review
Trigger: “Run my weekly review.”
--- name: weekly-review description: 10-minute Friday review: wins, misses, next week's plan. --- 1. Ask me for: 3 wins, 3 misses, and anything unfinished from this week. 2. For each miss: one concrete fix, under 20 words, assigned to a specific day next week. 3. Draft next week's top-3 priorities from my wins/misses pattern. 4. Close with one encouraging line and the review saved as a dated note I can ask for later. Rules: stay honest and direct, no fluff. Never rewrite my wins into bigger claims than I made.
Skills vs prompts vs connectors: the 60-second distinction
- Prompt: one question, one answer. Disposable.
- Skill: a written method Muse reuses every time — the trigger phrase runs the whole workflow. This guide’s 8 packs live here.
- Connector: a live data pipe into Muse (Gmail, Calendar, QuickBooks, Shopify… — Meta named Asana, Box, Canva, Dropbox, Figma, Granola, HighLevel, Intuit QuickBooks, Klaviyo, Lovable, Notion, Shopify, Slack, Stripe and Zoom on 29 Sep 2026, with Zapier reaching 9,000+ apps). A skill tells Muse how; a connector gives it where.
Skills and connectors stack: the Morning Briefing skill gets dramatically more useful once Muse is connected to your calendar and email. Our earlier guide on 12 copy-paste Muse prompts covers single-shot requests; the 8 packs above are their repeatable upgrades.
Safety rules before you install skills
- Skills are instructions, not software. They can’t do anything Muse can’t already do — and Muse still asks before anything important. Community skill repos are unreviewed by Meta; read a skill before pasting it, just like you’d read a prompt.
- Keep the approval line. Meta’s rule stands: nothing publishes, sends, or spends without your approval. If a skill ever tries to shortcut that, the problem is the skill text — delete it from the conversation.
- Start narrow, then widen. Give a new skill a bounded test (“triage my last 5 emails”) before trusting it with a whole inbox.
- One trigger, one skill. Two skills fighting over the same trigger phrase (“plan my trip” vs “plan my weekend”) will confuse the routing. Name triggers distinctly.
Frequently Asked Questions
Are Meta Muse skills free?
Built-in skills ship with Muse itself — Muse’s tiers run free, Power ($20/month) and Maximum ($100/month) per Meta’s own pricing. Community skills are text files on the open web (MIT and similar licences) that cost nothing to copy and paste; some libraries sell downloadable packs or all-access bundles, but the individual skill texts in the free catalogs are free to use.
Can I upload my own skill file to Muse?
Not as of October 2026. Meta has not announced an upload flow for your own skill files. The working method is paste-to-install: paste the skill’s instructions into a chat and ask Muse to remember them. Meta’s developer tool, Muse Code, already reads standard SKILL.md files, which suggests uploads could arrive for the personal assistant too.
Do these skills work in other AI assistants?
Yes, by design. The Agent Skills format (YAML frontmatter + markdown instructions) is open, so the same skill text works across assistants that support it — the community repos explicitly list Muse, Claude, ChatGPT and Gemini among supported targets. Availability varies by assistant.
Is paste-to-install safe?
As safe as any prompt you paste. A skill can’t grant itself abilities Muse doesn’t have, and Muse’s approval step still gates publishing, sending and spending. The real risk is a badly written skill giving sloppy instructions — read the text before pasting, the same way you’d review code before running it.
Sources and Methodology
This article rests on: Meta’s Muse for Small Business announcement (29 Sep 2026, skills-and-connectors framing; reported via Unite.AI), the AI Agents Library’s free Meta Muse skills page (updated Oct 2026 — the paste-to-install method and the “no upload flow yet” status), the awesome-muse-skills community catalog on GitHub (2,384 skills across 31 categories, claim verified from the repo README on 15 Oct 2026), and Meta’s own usage tips quoted on the AI Agents Library how-to page. The 8 skill packs are original to this article — desk-written for Muse’s copy-paste workflow, not copied from any library — and desk-validated, not hands-on tested (skill behaviour can vary with Muse’s rolling updates; test each pack with a small task first). All claims verified 15 October 2026.
Govind Dheda covers AI tools, guides and prompts for OpenAIMaster — what is new, what is worth using, and how to put AI to work.
Feel free to email us at contact@openaimaster.ai — we are happy to help!


