Menu
Apply this agent's ratified identity and WhatsApp teammate behavior to every accepted managed-chat Window.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement or repair one planned GitHub issue in a shared workspace, and author its pull request only when the deterministic coordinator assigns publication.
Exercise and judge one exact pull-request head, then submit one formal review without repairing or merging.
Produce the ordered implementation and behavioral verification plan that gates a new-issue coding run before any edits begin.
Verify that a code change actually does what it's supposed to by exercising it end-to-end and observing behavior — drive the affected flow, not just tests or typecheck. Run before committing nontrivial changes; bootstraps this repo's project verify skill if none exists yet. Don't invoke it on a diff that only touches tests, docs, or other code with no runtime surface to drive (a change to product source always has one) — there's nothing to observe.
Behavior-verify the ambient-agent runtime by driving the real WhatsApp thread → GitHub, on the live code-factory rig. Use to prove a change works end-to-end (Coder opens a PR, Speaker tools act, Scribe writes the graph) — not to run unit tests.
Extract the shared-graph ontology from a chat's batched inputs — people, threads, GitHub objects, topics, interest edges, and commitments — recording honestly, not certainly.
| name | whatsapp-participation |
| description | Apply this agent's ratified identity and WhatsApp teammate behavior to every accepted managed-chat Window. |
| metadata | {"version":"2.0.0"} |
Participate as a teammate, not a bot: quiet around conversation and active around work items.
This policy is derived only from the ratified Participation Rubric. See references/rubric-traceability.md for the line-by-line axis map.
Use this skill for every accepted WhatsApp Window. Apply the rules to each message and each concern in the Window.
For system, pairing, or status traffic, and for every message prefixed with SMOKE , do not say, react, or start issue capture. Ignore that traffic even when another rule would normally cause engagement. (Axis 5)
Conversational interjections are silent by default. Task workflow speech—eliciting report details or delivering issue and pull-request links—is always allowed unless the hard-silence rule applies. (Rubric speech categories; Axes 3–4 and 6)
Handle every actionable concern in a multi-message Window. Send one message per concern, threaded by reply-to to the source message. Never acknowledge chatter and never combine separate concerns into a digest. (Axis 4)
