Install

This guide gets skills from skillet.md onto your machine, the one thing the website can't do; everything else (writing, publishing, following, building kits) happens on skillet.md. Install one of these: the app (recommended for almost everyone) or the CLI (for terminal use). Both run the same sync and set up the /skillet command in your agents; you don't need both.

Install the app (recommended)

→ Download the app One page picks Mac or Windows for you and shows what the build does before anything downloads.

1. Download and open it once. Get the app →: a Mac menu-bar app or a Windows tray app. On first open it pairs with your account, checks which tools you have, and asks before it touches anything. Your skills stay on your computer.
2. Add a skill. Find one on skillet.md (Browse or Search) and click Add. It drops into your library and syncs to your tools the next time you start a chat or session. Use the caret next to Added to file it into a kit.

After setup, adding a skill is one click on the website and it lands on your machine.

Use the CLI instead

The CLI runs the same sync from the terminal. You need Node 22+ (node --version).

npx skilletmd          # run it once, or install globally:
npm install -g skilletmd && skillet

On Windows, PowerShell may refuse to run these

Windows PowerShell ships with script execution turned off, so both commands above stop before Skillet starts:

npx : File C:\...\npx.ps1 cannot be loaded because running scripts is disabled
on this system.

That is PowerShell declining to load npm's .ps1 shim. It is not a problem with the package, and nothing has been installed wrongly. Either way past it works:

• Use the .cmd shims, which the policy does not gate: npx.cmd skilletmd, or skillet.cmd sync after a global install.
• Allow local scripts once, then use the normal commands. This needs no admin rights and only affects your account:

Set-ExecutionPolicy -Scope CurrentUser RemoteSigned

RemoteSigned still requires a valid signature on anything downloaded from the internet; it only trusts scripts already on your machine. Check it took with Get-ExecutionPolicy -List, which should show RemoteSigned for CurrentUser.

PowerShell 7 (pwsh) and cmd.exe are unaffected, and so is the tray app: it bundles the CLI and needs neither Node nor npm.

1. Sign in at skillet.md. Your kits live there.
2. Connect this machine. On Settings → Devices, generate a pairing code, then run skillet connect ABCD-2345. Running bare skillet walks the whole flow (sign in, connect, sync) and can import skills you already have.
3. Sync and confirm:

skillet sync    # writes your kits into every runtime it detects
skillet list    # shows every installed skill and where it lives

Every command and flag is in the CLI reference.

ChatGPT, Claude.ai, and other no-file runtimes

Some runtimes don't read local files, so there's nothing to sync. Use your personal MCP link instead: on skillet.md, open Settings → Account, turn on MCP, and paste the link into ChatGPT or Claude.ai. Those chats then read your skills live, current with every approved update. If you'd rather have a file, use Download bundle (.zip) on the skill page (a static snapshot). Claude Desktop reads your skills live over MCP locally.

When a skill changes

An author's improvement waits in your updates as a plain diff. Nothing is applied until you approve it. See Approve updates.

Note If a skill doesn't show up in a tool, the app (or skillet sync) tells you in plain language what to check. See the FAQ.

You're set up: skills you add on the website now land on this machine. Next, add skills from people you follow.