Muse skills for business

The short answer

A Muse skill is a document of instructions, saved as a file called SKILL.md, that you paste into a Muse chat so Muse works the way the document describes. There is no app store for skills and, as of October 2026, no permanent install. You paste the document into a chat, Muse follows it for that conversation, and a new chat starts clean until you paste it again. Business owners are sharing these documents the way they once shared spreadsheet templates, and a pack of marketing skills is currently moving from owner to owner on X. This guide explains what a skill really is, the pack people are running, how to use one step by step, how to write your own, and where the limits honestly sit.

What a skill actually is

Strip the jargon away and a skill is a written brief. It tells Muse who to be for this job, what the job is, what information to work from, what rules to follow, and what the finished work should look like. Anyone who has ever written a good brief for a freelancer has written the ancestor of a SKILL.md file. The difference is that the freelancer on the other end is an AI agent, and it reads the brief at the start of the conversation and works to it.

The format is plain text with light structure, usually written in the markdown style that gives the file its .md ending. A typical skill names the role in its first lines, then lays out the inputs it expects, the steps it follows, the standards it holds, and the shape of the output it produces. Because it is a document rather than a program, you can read every word of a skill before you use it, edit the parts you dislike, and keep your own copy. Nothing about it is hidden inside an app.

That plainness is also why skills spread so easily. A skill that works for one owner can be copied, pasted, and adapted by the next in minutes. The sharing is the distribution: a creator posts a skill that saves them an hour a week, other owners try it, improve it, and pass their version on. No marketplace takes a cut and no approval queue slows it down, which is exactly why the quality varies as much as it does.

The install question, answered plainly

The single most common question about skills is some version of this: how do I install it in Muse for good? The honest answer, confirmed by hands on testing, is that you cannot. When the AI Agents Library ran its Facebook workflow test on Muse, it asked directly whether you can install your own AI skills in Muse, and the answer it found was no, not as a permanent install. The working method is to paste the SKILL.md into a chat.

It helps to understand why. A skill is not software that plugs into the app. It is context for a conversation. Muse reads documents the way it reads anything you paste into a chat, and it follows the instructions it finds there. When the conversation ends, that context ends with it. Owners who understand this stop asking for an install button and start treating their skills as documents they keep, version, and paste with intent. Owners who miss it spend frustrating weeks wondering where their setup went.

Meta may well build a proper skill library into Muse one day, and the connector directory shows the company is comfortable with marketplaces. As of October 2026 there is no announcement of one, so everything in this guide works with the paste method that exists today.

The pack owners are actually running

The clearest snapshot of skills in the wild comes from X, where creators who use Muse for marketing have been sharing the packs they run. One widely shared post told Muse users to bookmark ten marketing skills, and the names in that post will be familiar to anyone who has ever hired for a small marketing team. The pack, as shared, includes:

• Content Strategist. Plans what to publish, where, and why, instead of posting at random.
• Copywriter. Drafts posts, pages, and captions in the voice you feed it.
• SEO Specialist. Works on search angles, titles, and the structure of pages.
• Paid Ads Specialist. Shapes campaign ideas and ad copy for the ad accounts Muse can reach.
• Market Researcher. Reads competitors, reviews, and conversations, then reports back.
• Email Marketer. Drafts campaigns and sequences, and audits the flows you already run.
• Conversion Optimizer. Looks at a page or a funnel and argues for what to fix first.

Read that list again and notice what it is: a job description collection. Each skill turns Muse from a general assistant into a named specialist with a defined desk. That is the whole trick, and it is a good one. A general chat asked to do marketing produces general output. A chat that opens with a tight specialist brief, your business details, and examples of your voice produces work that needs editing rather than rescuing.

Notice also what the pack is not. It is not seven apps, seven subscriptions, or seven integrations. It is seven documents. The owners sharing them are not selling software; they are lending each other their best written instructions, which is a very old small business habit wearing new clothes.

How to use a skill, step by step

1. Get the whole document. Creators share skills as posts, files, or pasted text. Copy the complete SKILL.md, not a screenshot of part of it. A skill with its rules section missing is a different, worse skill.
2. Connect what the skill needs to read. A Copywriter skill can work from what you tell it. An analytics or ads skill needs your accounts connected first, through the connectors in Muse settings. Our Small Business setup guide covers that order of operations.
3. Open a fresh chat and paste the document. Fresh matters. The skill sets the frame for the conversation, and it works best as the first serious thing Muse reads.
4. Tell Muse to work to it. Say plainly that it should follow the skill for this job. The sharing posts describe exactly this: paste the SKILL.md into a chat and ask Muse to follow it.
5. Feed the inputs. Give it your product, your audience, your offer, and examples of work you like. If the skill reads connected accounts, point it at the right Page, store, or inbox.
6. Judge the first output like a first draft. Specialist framing improves the start; it does not remove the need for your eye. Correct what is off, in the chat, specifically.
7. Fold the corrections back into your copy. This is the step that separates owners who improve from owners who repeat themselves. Your edits apply to this chat only, so save the improved version of the document as your own.

Writing your own SKILL.md

The best skill for your business is usually the one you write, because it carries your standards instead of a stranger's. You do not need to be technical. You need to be specific. A working SKILL.md contains seven things:

• The role and the job. One or two lines: who Muse is being, and what done looks like.
• Your business in brief. What you sell, who buys it, and the facts Muse must never get wrong, such as prices, locations, and policies.
• The inputs to gather first. Tell it what to ask you, or which connected account to read, before it starts work.
• The rules. Your voice, the claims you never make, the words you avoid, and the lines it must not cross. Remember that nothing publishes, sends, or spends without your approval, and write the skill so drafts come to you rather than going out.
• The output format. Length, structure, and shape. If you want three caption options with the strongest first, say so.
• Examples of good. Two or three pieces of your own past work that hit the mark. Examples teach faster than adjectives.
• What to do when unsure. Instruct it to ask you rather than invent. A skill that permits guessing will eventually guess about a price, a date, or a promise.

Keep the document tight. A skill is a working brief, not a book, and every line in it competes for attention with the actual job. Write the first version in twenty minutes, use it twice, and then improve the parts that produced weak output. That loop, used honestly, is how the shared packs got good in the first place.

Skills beyond marketing

Marketing got the attention because marketers share in public, but the pattern works anywhere a job repeats with a stable standard. Owners are applying the same document trick to the rest of the week:

• Sales research. A skill that takes an ideal customer description and returns researched prospects with reasons, the same workflow our sales research guide walks through, captured once as a brief instead of retyped each time.
• Support replies. A skill that reads a customer thread, drafts the reply in your voice, and holds it for your approval. The standard it enforces is tone: patient, specific, and never promising what the business cannot do.
• Review analysis. A skill that sorts customer reviews into strengths, complaints, and fixes, on the pattern of our review analysis guide, so a month of feedback becomes a one page brief.
• The morning brief. A skill that triages inbox, calendar, and news into a priority list, the job Meta itself uses to demonstrate the business offer.

The test for whether a job deserves a skill is simple. If you have explained the same job the same way twice, write it down once, properly, and stop explaining.

A skill is not a connector

These two words get mixed up constantly, and the confusion wastes real time. A skill changes how Muse works: the role it takes, the steps it follows, the standard it aims at. A connector changes what Muse can reach: your Page, your store, your books, your inbox. A Copywriter skill cannot see your Page numbers until the Page is connected, and connecting a Page does not teach Muse your voice. Serious setups use both, skills for the standard and connectors for the reach. Our connectors list tracks what can be connected and which announced connectors are actually live.

There is a third thing nearby that is neither: the custom connector route, where you hand Muse the documentation for a tool it does not know and it builds its own integration. That is about reach, not instructions, and Meta does not review what you build that way. Skills sit at the opposite pole: nothing to approve, nothing to integrate, just a document you control completely.

The honest limits

You paste it every time. There is no permanent install, so every new chat starts without your skill until you add it. Owners build the paste into their routine, the way they once opened the same spreadsheet every morning.

The document is the ceiling. A vague skill produces vague work, delivered confidently. When output disappoints, the fix is almost never a better prompt in the moment; it is a better document.

Corrections do not carry over. What you teach Muse inside one chat stays inside that chat. The only memory a skill has is the copy you keep, which is why step seven of the method above matters.

Skills grant no access and skip no approvals. A skill cannot open a tool you have not connected, and it does not loosen the rule that publishing, sending, and spending wait for your approval. It makes the drafts better. You remain the gate.

Length is a budget. The document lives inside the conversation it guides, so a bloated skill leaves less room for the work itself. Tight beats thorough.

Get started

Frequently asked questions

Can I install a skill in Muse permanently?

No, not as of October 2026. Hands on testing of Muse found no permanent install for your own skills. The working method is to paste the SKILL.md document into a chat and ask Muse to follow it. The skill guides that conversation, and a new chat starts clean until you paste it again.

Where do I get skills?

Owners and creators share them in public, most visibly on X, where a pack of marketing skills covering content strategy, copywriting, SEO, paid ads, market research, email, and conversion work has been circulating. You can also write your own, and for most businesses the skill you write yourself, carrying your own standards, ends up the most useful one.

How do I use a skill once I have it?

Copy the complete document, open a fresh Muse chat, paste it in, and tell Muse to follow it for the job at hand. Then feed it the inputs it needs: your product, your audience, your examples, or the connected accounts it should read. Judge the first output as a draft, correct it in the chat, and save the improved document as your copy.

What should a good SKILL.md contain?

Seven things: the role and the job, your business in brief with the facts it must never get wrong, the inputs to gather first, your rules for voice and claims, the output format you want, examples of your good work, and an instruction to ask you rather than invent when something is missing. Tight beats long.

Is a skill the same as a connector?

No. A skill changes how Muse works: the role, the steps, the standard. A connector changes what Muse can reach: your Page, your store, your books, your inbox. A copywriting skill cannot see your Page numbers until the Page is connected, and connecting the Page does not teach Muse your voice. Most serious setups use both.

Why does Muse forget my skill in a new chat?

Because there is no permanent install, each conversation carries only what you put into it. Corrections you make while working live and die inside that chat. The fix is unglamorous and effective: fold what you taught it back into your saved copy of the document, so the next paste starts smarter.

Built with Muse is an independent community project. Not affiliated with or endorsed by Meta.