[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGKMJ7C0RR7MQQH4S7MPKT":3,"skill-same:01M6MGKMJ7C0RR7MQQH4S7MPKT":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6MGKMJ7C0RR7MQQH4S7MPKT","wakewire-setup",null,"Set up wakewire end to end — install\u002Fstart the local daemon, wire a first GitHub or Gmail route into a Codex thread, and verify with a test delivery. Use when the user wants external events (GitHub pushes\u002FPRs\u002Fissues, emails) delivered into their Codex threads, or when wakewire tools report the daemon is not running.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fglenncalleja\u002Fwakewire\u002Fskills\u002Fwakewire-setup\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"setup","wakewire setup","running","gmail","when","prs","thread","threads","daemon","events","end","emails","local","delivery","route","up","use","install","Tools","SET","start","issues","2026-11-10 10:12:30",false,"---\nname: wakewire-setup\ndescription: Set up wakewire end to end — install\u002Fstart the local daemon, wire a first GitHub or Gmail route into a Codex thread, and verify with a test delivery. Use when the user wants external events (GitHub pushes\u002FPRs\u002Fissues, emails) delivered into their Codex threads, or when wakewire tools report the daemon is not running.\n---\n\nYou are configuring wakewire, a local daemon that pushes external events into Codex threads. Configuration happens through the `wakewire_*` MCP tools; this skill is the runbook.\n\n## 0. Check the daemon\n\nCall `wakewire_status`.\n\n- If it errors with \"daemon is not running\", have the user run in a terminal:\n  ```\n  npm install -g wakewire\n  wakewire init\n  wakewire start --detach     # or: wakewire service install (starts at login)\n  ```\n  Then call `wakewire_status` again.\n- Confirm `adapter.codexReachable` is true. If not, codex isn't on PATH for the daemon — ask the user how they installed Codex.\n\n## 1. Resolve the target thread\n\nMost users want events delivered \"into this thread\". MCP tools cannot see the current thread id, but shell commands can:\n\n1. Run this shell command: `echo \"$CODEX_THREAD_ID\"`\n2. Use that value as `target: {\"type\":\"thread\",\"threadId\":\"\u003Cvalue>\"}`.\n\nIf the user prefers fresh threads per event (e.g. \"spawn a worktree and investigate each failure\"), use `target: {\"type\":\"new-thread\",\"cwd\":\"\u003Cabs repo path>\",\"worktree\":true}` instead.\n\n## 2. Set up the source\n\n### GitHub\n1. Call `wakewire_source_setup_github` with the repo (e.g. `{\"repo\":\"acme\u002Fapi\"}`). It creates a smee.io relay channel and returns a webhook URL, a secret, and step-by-step instructions.\n2. Relay those instructions to the user verbatim — they add the webhook in the repo settings. Warn them: smee.io is a public relay; payloads transit it, which is why wakewire verifies HMAC signatures and why private-repo users may prefer `{\"mode\":\"listen\"}` with their own tunnel.\n3. GitHub sends a `ping` on creation; `wakewire_status` should show the source received it.\n\n### Gmail\n1. Ask which Gmail label to watch (never watch everything — a label is required) and the Gmail address.\n2. Ask which auth they prefer:\n   - **App password** (simpler): call `wakewire_source_setup_gmail` with `{label, user, authKind: \"imap-password\"}`. The user creates an app password at https:\u002F\u002Fmyaccount.google.com\u002Fapppasswords (needs 2-Step Verification) and runs `wakewire auth imap` in a terminal to store it. Also works for non-Gmail IMAP servers via `host`\u002F`port`.\n   - **OAuth**: call `wakewire_source_setup_gmail` with `{label, user}`. The user creates their own Google OAuth client (Desktop type) and runs `wakewire auth gmail` in a terminal to complete consent.\n3. Relay the returned instructions verbatim either way.\n\n### Slack\n1. Call `wakewire_source_setup_slack` (optionally with `{team: \"workspace-name\"}`). It returns the one-time Slack app setup: create an app, enable Socket Mode (app-level token, `connections:write`), add bot scopes (`app_mentions:read`, `channels:history`, `channels:read`, `users:read`), subscribe to bot events (`app_mention`, `message.channels`), install, invite the bot to channels.\n2. Relay those steps verbatim, then have the user run `wakewire auth slack` in a terminal — both tokens go in via hidden prompts, never through this conversation.\n3. Slack routes match `app_mention` by default (any channel the bot is in); matching plain `message` events requires naming channels. Bot-posted messages are skipped by default.\n\n### Any other provider (Sentry, Grafana, Linear, ClickUp, Stripe, CI, custom)\nUse the generic webhook source. The loop:\n1. `wakewire_source_setup_webhook` with `name` and `verification` only (check the provider's docs for its signature header; hmac-sha256 + header name covers most). Relay the returned URL + secret. The next 3 events are captured raw.\n2. Ask the user to trigger a test event, then read it with `wakewire_source_captures`.\n3. Author the mapping from the real payload — `deliveryId`\u002F`kind`\u002F`occurredAt` paths, a `summary` template, and `fields` (alias → dot.path). Only mapped fields reach the model, so map what routes and prompts need, nothing more.\n4. Re-run `wakewire_source_setup_webhook` with the mapping (the secret and relay URL are preserved).\n5. Route with `source: \"webhook\"`, `match: {\"provider\": \"\u003Cname>\", \"where\": [...]}`.\nKnown-provider presets (ClickUp, Linear, Sentry) are in the package's recipes\u002F directory.\n\n## 3. Create the route\n\nCall `wakewire_route_add`. Examples:\n\n- Pushes to main into this thread:\n  ```json\n  {\n    \"name\": \"api main pushes\",\n    \"source\": \"github\",\n    \"match\": {\"repo\": \"acme\u002Fapi\", \"events\": [\"push\"], \"branches\": [\"main\"]},\n    \"target\": {\"type\": \"thread\", \"threadId\": \"\u003Cresolved id>\"},\n    \"promptTemplate\": \"Summarize this push to {{repo}}:{{branch}} and flag anything risky.\"\n  }\n  ```\n- Labeled email into this thread: `match: {\"label\": \"agent-inbox\"}`.\n\nPrompt templates may interpolate only whitelisted summary fields ({{summary}}, {{repo}}, {{branch}}, {{kind}}, {{subject}}, {{from}}, …). Event payloads are always delivered as fenced untrusted data — remind the user that email\u002Fcommit content must be treated as data, not instructions.\n\nSandbox: default is read-only. Only set `\"sandbox\": \"workspace-write\"` for GitHub routes if the user explicitly wants the injected turns to edit files. Gmail routes are always read-only.\n\n## 4. Verify\n\n1. Ask the user to trigger a real event (push a commit, or send + label an email), or replay one: `wakewire_deliveries` → pick a delivery id → `wakewire_replay`.\n2. Confirm with `wakewire_deliveries` that the delivery status is `delivered` and the turn arrived in the target thread.\n3. If something is off, switch to the $wakewire-inspect skill.\n","You are configuring wakewire, a local daemon that pushes external events into Codex threads. Configuration happens through the `wakewire_*` MCP tools; this skill is the runbook.\n\n## 0. Check the daemon\n\nCall `wakewire_status`.\n\n- If it errors with \"daemon is not running\", have the user run in a terminal:\n  ```\n  npm install -g wakewire\n  wakewire init\n  wakewire start --detach     # or: wakewire service install (starts at login)\n  ```\n  Then call `wakewire_status` again.\n- Confirm `adapter.codexReachable` is true. If not, codex isn't on PATH for the daemon — ask the user how they installed Codex.\n\n## 1. Resolve the target thread\n\nMost users want events delivered \"into this thread\". MCP tools cannot see the current thread id, but shell commands can:\n\n1. Run this shell command: `echo \"$CODEX_THREAD_ID\"`\n2. Use that value as `target: {\"type\":\"thread\",\"threadId\":\"\u003Cvalue>\"}`.\n\nIf the user prefers fresh threads per event (e.g. \"spawn a worktree and investigate each failure\"), use `target: {\"type\":\"new-thread\",\"cwd\":\"\u003Cabs repo path>\",\"worktree\":true}` instead.\n\n## 2. Set up the source\n\n### GitHub\n1. Call `wakewire_source_setup_github` with the repo (e.g. `{\"repo\":\"acme\u002Fapi\"}`). It creates a smee.io relay channel and returns a webhook URL, a secret, and step-by-step instructions.\n2. Relay those instructions to the user verbatim — they add the webhook in the repo settings. Warn them: smee.io is a public relay; payloads transit it, which is why wakewire verifies HMAC signatures and why private-repo users may prefer `{\"mode\":\"listen\"}` with their own tunnel.\n3. GitHub sends a `ping` on creation; `wakewire_status` should show the source received it.\n\n### Gmail\n1. Ask which Gmail label to watch (never watch everything — a label is required) and the Gmail address.\n2. Ask which auth they prefer:\n   - **App password** (simpler): call `wakewire_source_setup_gmail` with `{label, user, authKind: \"imap-password\"}`. The user creates an app password at https:\u002F\u002Fmyaccount.google.com\u002Fapppasswords (needs 2-Step Verification) and runs `wakewire auth imap` in a terminal to store it. Also works for non-Gmail IMAP servers via `host`\u002F`port`.\n   - **OAuth**: call `wakewire_source_setup_gmail` with `{label, user}`. The user creates their own Google OAuth client (Desktop type) and runs `wakewire auth gmail` in a terminal to complete consent.\n3. Relay the returned instructions verbatim either way.\n\n### Slack\n1. Call `wakewire_source_setup_slack` (optionally with `{team: \"workspace-name\"}`). It returns the one-time Slack app setup: create an app, enable Socket Mode (app-level token, `connections:write`), add bot scopes (`app_mentions:read`, `channels:history`, `channels:read`, `users:read`), subscribe to bot events (`app_mention`, `message.channels`), install, invite the bot to channels.\n2. Relay those steps verbatim, then have the user run `wakewire auth slack` in a terminal — both tokens go in via hidden prompts, never through this conversation.\n3. Slack routes match `app_mention` by default (any channel the bot is in); matching plain `message` events requires naming channels. Bot-posted messages are skipped by default.\n\n### Any other provider (Sentry, Grafana, Linear, ClickUp, Stripe, CI, custom)\nUse the generic webhook source. The loop:\n1. `wakewire_source_setup_webhook` with `name` and `verification` only (check the provider's docs for its signature header; hmac-sha256 + header name covers most). Relay the returned URL + secret. The next 3 events are captured raw.\n2. Ask the user to trigger a test event, then read it with `wakewire_source_captures`.\n3. Author the mapping from the real payload — `deliveryId`\u002F`kind`\u002F`occurredAt` paths, a `summary` template, and `fields` (alias → dot.path). Only mapped fields reach the model, so map what routes and prompts need, nothing more.\n4. Re-run `wakewire_source_setup_webhook` with the mapping (the secret and relay URL are preserved).\n5. Route with `source: \"webhook\"`, `match: {\"provider\": \"\u003Cname>\", \"where\": [...]}`.\nKnown-provider presets (ClickUp, Linear, Sentry) are in the package's recipes\u002F directory.\n\n## 3. Create the route\n\nCall `wakewire_route_add`. Examples:\n\n- Pushes to main into this thread:\n  ```json\n  {\n    \"name\": \"api main pushes\",\n    \"source\": \"github\",\n    \"match\": {\"repo\": \"acme\u002Fapi\", \"events\": [\"push\"], \"branches\": [\"main\"]},\n    \"target\": {\"type\": \"thread\", \"threadId\": \"\u003Cresolved id>\"},\n    \"promptTemplate\": \"Summarize this push to {{repo}}:{{branch}} and flag anything risky.\"\n  }\n  ```\n- Labeled email into this thread: `match: {\"label\": \"agent-inbox\"}`.\n\nPrompt templates may interpolate only whitelisted summary fields ({{summary}}, {{repo}}, {{branch}}, {{kind}}, {{subject}}, {{from}}, …). Event payloads are always delivered as fenced untrusted data — remind the user that email\u002Fcommit content must be treated as data, not instructions.\n\nSandbox: default is read-only. Only set `\"sandbox\": \"workspace-write\"` for GitHub routes if the user explicitly wants the injected turns to edit files. Gmail routes are always read-only.\n\n## 4. Verify\n\n1. Ask the user to trigger a real event (push a commit, or send + label an email), or replay one: `wakewire_deliveries` → pick a delivery id → `wakewire_replay`.\n2. Confirm with `wakewire_deliveries` that the delivery status is `delivered` and the turn arrived in the target thread.\n3. If something is off, switch to the $wakewire-inspect skill.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fglenncalleja\u002Fwakewire\u002Fskills\u002Fwakewire-setup",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill wakewire-setup",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill wakewire-setup",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill wakewire-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fglenncalleja\u002Fwakewire\u002Fskills\u002Fwakewire-setup\u002FSKILL.md",true,[],[71,81,89,97,105,113],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":76,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":80},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":80},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":80},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":80},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":80},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]