菜单
Use when the user says 'set up a webhook', 'connect X service to Pantheon', 'receive notifications from Y', or any request to bring external events into the Pantheon. Produces a webhook integration config and rule, saved to ~/pantheon/conductor/webhooks/ and ~/pantheon/conductor/rules/.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | conductor-design-webhook |
| description | Use when the user says 'set up a webhook', 'connect X service to Pantheon', 'receive notifications from Y', or any request to bring external events into the Pantheon. Produces a webhook integration config and rule, saved to ~/pantheon/conductor/webhooks/ and ~/pantheon/conductor/rules/. |
| version | 1.0.0 |
| author | Thoth & Hermes (Pantheon) |
| license | MIT |
| metadata | {"hermes":{"tags":["conductor","webhook","integration","external","event"],"related_skills":["conductor-design-rule","conductor-design-workflow"]}} |
Load this skill when the user wants to connect an external service to the Pantheon event system. Keywords: "webhook," "connect X," "receive from," "monitor Y," "set up integration for."
Ask:
| Method | When | Example |
|---|---|---|
| Native webhook | Service sends HTTP POST to a URL | GitHub, Stripe, Jira |
| Polling | Cron job checks API periodically | Reddit, YouTube, RSS feeds |
| NATS bridge | Tallon's instance forwards via Relay-7 | Cross-Pantheon events |
If native webhook, Conductor will need a webhook endpoint URL. Ask if the user has:
Same as rule designer — walk through the modes:
| Mode | Best For |
|---|---|
log_only | Reddit mentions, YouTube uploads, passive monitoring |
notify | Low-priority FYI alerts |
approval_required | Actionable events (PR review request, deploy request) |
route_on_approval | Known actionable events with predictable routing |
Ask: "What fields from the webhook payload matter?"
Two files:
~/pantheon/conductor/webhooks/{service}-{purpose}.yaml
~/pantheon/conductor/rules/{service}-{purpose}.yaml
If the service needs a webhook URL registered (GitHub repo settings, Stripe dashboard, etc.), note that as a manual step for the user.
Summarize:
Use when the user says 'set up a report', 'create a digest', 'I want a daily/weekly summary of', 'monitor X and report on Y', or any request for scheduled information synthesis. Produces a Conductor workflow + rules for scheduled reports and digests.
Use when the user says 'when X happens, do Y', 'set up a rule for', 'react to', or any request to define an event-driven trigger. Produces a Conductor reaction rule YAML and saves it to ~/pantheon/conductor/rules/.
Use when the user says 'set up a pipeline', 'create a workflow', 'I need a multi-god process', or any request to chain multiple gods into a repeatable sequence. Produces a Conductor workflow YAML and saves it to ~/pantheon/conductor/workflows/.
Conductor handoff and acknowledgement protocol for Pantheon gods
Use after a design spec is written, before any implementation begins. Runs a structured assessment of holes, risks, pros/cons, system conflicts, overhead, and a go/no-go verdict. Must be completed before build handoff.
Use when the user says 'build Amber a skill', 'she needs something for X at the conference', 'make her a skill that does Y', 'package this up for her', 'design a skill for Amber', or any request to design, build, and ship a custom skill for Amber. The output is a fully packaged skill (zip file) ready to attach to Telegram and send to her agent for install. Designed to be invoked repeatedly as new conference needs come up.