Individual skill

wakewire-setup

Set up wakewire end to end — install/start 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/PRs/issues, emails) delivered into their Codex threads, or when wakewire tools report the daemon is not running.

plugins/glenncalleja/wakewire/skills/wakewire-setup/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

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.

## 0. Check the daemon

Call `wakewire_status`.

- If it errors with "daemon is not running", have the user run in a terminal:
  ```
  npm install -g wakewire
  wakewire init
  wakewire start --detach     # or: wakewire service install (starts at login)
  ```
  Then call `wakewire_status` again.
- Confirm `adapter.codexReachable` is true. If not, codex isn't on PATH for the daemon — ask the user how they installed Codex.