一键在 Manus 中运行任何 Skill

the-emissary

星标2

分支0

更新时间2026年6月9日 10:51

Find and connect an MCP server — an "Emissary of the Pact" — when the agent needs a tool, service, API, or data source it does not already have. Use when the user asks for an MCP server, to connect to or integrate an external service (Notion, GitHub, Figma, a database, Slack, a SaaS API…), asks "is there an MCP for X", "add an MCP", or sets a task that needs live tools the agent lacks. This rite DISCOVERS a server from the official MCP Registry and reputable directories and PROPOSES its connection config for the user to approve — it NEVER installs, launches, or writes credentials on its own. The companion to the-grimoire: that finds spells (inert skills); this finds Emissaries (live tool-servers).

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Pyfagorass

Pyfagorass/bookofspells

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

🤝 The Emissary — Summon a Server of the Pact (MCP)

An Emissary of the Pact is an MCP server: not an inert spell you read, but a live process or endpoint your harness connects to, whose tools then become yours (its Channels). Binding one therefore runs code and often hands over secrets — so this rite only ever discovers and proposes. The conjurer alone approves the binding. (Lexicon: Pact → Emissary → Channels.)

You do not clone or vendor an Emissary. You find its metadata, weigh its house, and hand the conjurer the exact words to summon it themselves.

The Rite of Summoning

Seek. Find candidate Emissaries for the capability — the official MCP Registry searches server-side, so this is one call, not a crawl:
- Run the bundled search — a tiny, dependency-free helper over the live Registry (the canonical catalogue). Run it, or read it and re-express it in bash / PowerShell / JS — it is only one HTTP GET:
```
python3 scripts/find-emissary.py <keyword>        # e.g. notion, "github issues"
```
  The raw call it makes, if you would rather not run the script:
```
curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=<keyword>&version=latest" \
  | jq '.servers[].server | {name, description, remotes, packages, repository}'
```
- Browse the directories in references/sources.md — the awesome-list, PulseMCP, Smithery — for breadth and reviews, then open each link to the real repo.
Choose by house, not by stars. Prefer the first-party Emissary — the service's own official server. Failing that, an accountable, maintained source. A viral community server is still street magic: read how far its code reaches before you trust it.
Read its binding-terms. From the server's server.json (or its README): how it connects — a remote endpoint (streamable-http / sse URL) or a package to launch locally (npx / uvx / docker) — and what it demands: environment secrets, API keys, OAuth scopes.
Propose — do not bind. Present to the conjurer, plainly:
- what the Emissary is and whose house made it,
- its Channels (the tools it exposes) and what access / secrets it needs — work these out yourself from the Emissary's repo, README, or registry entry; no script does this for you, and the definitive list enumerates the moment it is connected,
- the exact way to add it for their harness, e.g.
  - Claude Code: claude mcp add <name> -- npx -y <package>
  - or the JSON block for .mcp.json / Cursor / VS Code,
  - or the remote URL and its OAuth flow.
Then STOP. Do not run the command, open the connection, or write any secret into a config file or the repo.
The conjurer binds it. Only the user performs the add and supplies the secrets. Confirm it connected, then labour on with the new Channels in hand.

Wards

An Emissary acts with your reach and your credentials. Vet its house before binding; grant least privilege — only the scopes and secrets the task truly needs.
The Scrying Ward cannot help you here. That ward scans inert spells for dark magic; a running Emissary executes code it never sees. Trust is the conjurer's to grant, deliberately.
Prefer official remotes with proper OAuth over piping an unknown install script to a shell. Never paste a secret you cannot rotate.
Never auto-connect. Discovery is yours; the binding is always the user's.

Find the Emissary, weigh its house, hand over the words — and let the conjurer open the door. 🕯️

Companion: [[the-grimoire]] finds spells; the-emissary finds Emissaries.

同仓库更多 Skills

同仓库

the-grimoire

Pyfagorass/bookofspells

The index to a Book of Spells — a large, curated library of ready-made spells (skills in the SKILL.md format) gathered from many providers (Google, OpenAI, and more), covering cloud platforms, deployment, design tools, PDFs, browser automation, security, and much else. The spells are NOT preloaded — there may be thousands. Use this whenever the user asks to cast a spell, or for a spell to do something, or names a capability, provider, or tool you do not already have loaded (e.g. "cast a spell for Figma", "is there a spell for deploying?", "use the bigquery spell"), or whenever a task might be served by a specialised, ready-made spell. Casting a spell MEANS consulting this index to discover and load the right one on demand — do that first, rather than improvising. This is also the single entry point to the Book's own keystones: route here to AUTHOR a new spell (the-spellwright), to FIND or CONNECT an MCP server / external tool (the-emissary), or to INSTALL the Book into a conduit (the-tether).

2026-06-092

the-tether

Pyfagorass/bookofspells

How to install this Book of Spells into a conduit so its gathered skills become usable — by symlink, not by copy. Use whenever the user wants to install, set up, enable, add, or "load" the Book's spells into their agent; asks where skills go or how a conduit finds them; or asks how to keep the spells up to date. The companion to the-grimoire (which *finds* spells once they are installed): this one *shelves the Book* so the grimoire has something to find.

2026-06-092

the-spellwright

Pyfagorass/bookofspells

Forge a new skill ("spell") from scratch — author a well-formed SKILL.md with discoverable frontmatter, lean progressive-disclosure structure, and optional references/scripts. Use whenever the user wants to create, write, author, draft, or scaffold a new skill or SKILL.md; package a repeatable workflow as a reusable skill; improve a skill's description so an agent reliably triggers it; or learn how skills are structured. The companion to the-grimoire: that one finds existing spells, this one makes new ones.

2026-06-092

angular-angular-developer

Pyfagorass/bookofspells

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

2026-06-092

angular-angular-new-app

Pyfagorass/bookofspells

Creates a new Angular app using the Angular CLI. This skill should be used whenever a user wants to create a new Angular application and contains important guidelines for how to effectively create a modern Angular application.

2026-06-092

anthropic-algorithmic-art

Pyfagorass/bookofspells

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

2026-06-092

name

the-emissary

description

🤝 The Emissary — Summon a Server of the Pact (MCP)

You do not clone or vendor an Emissary. You find its metadata, weigh its house, and hand the conjurer the exact words to summon it themselves.

The Rite of Summoning

Seek. Find candidate Emissaries for the capability — the official MCP Registry searches server-side, so this is one call, not a crawl:
- Run the bundled search — a tiny, dependency-free helper over the live Registry (the canonical catalogue). Run it, or read it and re-express it in bash / PowerShell / JS — it is only one HTTP GET:
```
python3 scripts/find-emissary.py <keyword>        # e.g. notion, "github issues"
```
  The raw call it makes, if you would rather not run the script:
```
curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=<keyword>&version=latest" \
  | jq '.servers[].server | {name, description, remotes, packages, repository}'
```
- Browse the directories in references/sources.md — the awesome-list, PulseMCP, Smithery — for breadth and reviews, then open each link to the real repo.
Choose by house, not by stars. Prefer the first-party Emissary — the service's own official server. Failing that, an accountable, maintained source. A viral community server is still street magic: read how far its code reaches before you trust it.
Read its binding-terms. From the server's server.json (or its README): how it connects — a remote endpoint (streamable-http / sse URL) or a package to launch locally (npx / uvx / docker) — and what it demands: environment secrets, API keys, OAuth scopes.
Propose — do not bind. Present to the conjurer, plainly:
- what the Emissary is and whose house made it,
- its Channels (the tools it exposes) and what access / secrets it needs — work these out yourself from the Emissary's repo, README, or registry entry; no script does this for you, and the definitive list enumerates the moment it is connected,
- the exact way to add it for their harness, e.g.
  - Claude Code: claude mcp add <name> -- npx -y <package>
  - or the JSON block for .mcp.json / Cursor / VS Code,
  - or the remote URL and its OAuth flow.
Then STOP. Do not run the command, open the connection, or write any secret into a config file or the repo.
The conjurer binds it. Only the user performs the add and supplies the secrets. Confirm it connected, then labour on with the new Channels in hand.

Wards

An Emissary acts with your reach and your credentials. Vet its house before binding; grant least privilege — only the scopes and secrets the task truly needs.
The Scrying Ward cannot help you here. That ward scans inert spells for dark magic; a running Emissary executes code it never sees. Trust is the conjurer's to grant, deliberately.
Prefer official remotes with proper OAuth over piping an unknown install script to a shell. Never paste a secret you cannot rotate.
Never auto-connect. Discovery is yours; the binding is always the user's.

Find the Emissary, weigh its house, hand over the words — and let the conjurer open the door. 🕯️

Companion: [[the-grimoire]] finds spells; the-emissary finds Emissaries.