Skills & MCP Gallery

Teach your AI reusable skills in the same SKILL.md format as Claude Code and Codex, and connect MCP servers for live tools and data.

πŸ’¬

Create a skill in chat

Describe the task once. Swipeer writes the SKILL.md and saves it after you approve.

β€œCreate a skill for my weekly status report: …”
πŸ“₯

Copy an existing skill

Paste a GitHub folder link or a local path such as ~/.claude/skills/…. Skills from Claude Code and Codex work unchanged.

β€œCopy this skill: https://github.com/anthropics/skills/tree/main/skills/internal-comms”
⚑

Used when it fits

The AI only sees each skill's name and description and loads the full instructions when a request matches. Turn on Use skills and tools in the chat. Bundled scripts run only after your approval, in a sandbox by default. Manage everything in Settings βž” Skills.

πŸ”
🧠 Find more skills Any folder with a SKILL.md works, for example from anthropics/skills, your own ~/.claude/skills or a Codex skills folder. Paste the link in chat or use Settings βž” Skills βž” Import folder. Check each skill's license before you use it, and note that some bundled scripts need Python packages installed on your computer.

πŸ›  Build Your Own

Your own skill

A skill is a folder with a SKILL.md: a short frontmatter with a name and a description that says when to use it, followed by the instructions in Markdown. Scripts, references and templates can sit next to it.

---
name: meeting-notes
description: Use when the user wants structured notes or a follow-up email from a meeting.
---

# Meeting notes

1. Collect decisions, owners and due dates.
2. Run `python scripts/format.py notes.txt` to build the table.
3. End with a short follow-up email draft.
  • name: lowercase letters, digits and hyphens, at most 64 characters.
  • description: when the AI should use the skill, at most 1024 characters.
  • Scripts: .py needs Python 3, .js runs on Swipeer's built-in Node.js, .sh runs in bash.
  • Easiest way: describe the task in chat and say β€œCreate a skill for this”.
πŸ”’ Safe by default Saving or importing a skill never runs anything. Scripts run only when the AI calls them and you approve. On macOS and Linux they run in a sandbox that can only write to the working folder, without network unless you allow it. Windows has no sandbox, so scripts there always need your approval to run without one. Scripts never see Swipeer's API keys.

Your own local MCP server

A local MCP server is a script that communicates using JSON-RPC 2.0 over standard input and output (stdin/stdout). Use it when the AI needs tools that run continuously or keep a connection open, for example to a local database.

  1. Save your script, for example as ~/swipeer-tools/my-tool.js.
  2. Open Settings βž” Integrations βž” MCP Servers and click +.
  3. Choose Local (command), enter a name, the command node and the argument swipeer-tools/my-tool.js.
  4. Click Test Connection, then Add Server.

Relative paths start in your home folder; absolute paths work as well. A full template is in the docs.

πŸ’‘ Zero Setup Node.js Environment Swipeer runs node scripts with its built-in runtime and provides @modelcontextprotocol/sdk via NODE_PATH. You do not need to run npm install in your script folderβ€”simply require the classes and it works!
βš™οΈ NPX Requirement Swipeer's built-in Local Files and Web Browser tools do not require Node.js. For third-party packages that use npx (for example -y @remotion/mcp@latest), you must have Node.js installed globally on your machine.

βš–οΈ Skill or MCP Server?

Skill MCP Server
What it is Instructions in a SKILL.md, optionally with scripts and files A running program or URL that offers tools
Best for Workflows, formats, checklists and small helper scripts Live data and services such as databases, n8n or a browser
How to add In chat, or Settings βž” Skills Settings βž” Integrations βž” MCP Servers
Runs Only when needed, scripts after approval in a sandbox While connected; local servers run with your user permissions