[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77YMEACZSHEAM2Q12JG7K2N":3,"skill-same:01M77YMEACZSHEAM2Q12JG7K2N":81},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M77YMEACZSHEAM2Q12JG7K2N","worldloops",null,"Agent Execution Guard by WorldLoops — a safe-by-default responsibility layer for AI agents that turns scattered work signals into governed open loops while preserving externalWrite:false.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fw\u002Fworldloops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: worldloops\ndescription: Agent Execution Guard by WorldLoops — a safe-by-default responsibility layer for AI agents that turns scattered work signals into governed open loops while preserving externalWrite:false.\nversion: \"1.12.0\"\nhomepage: https:\u002F\u002Fgithub.com\u002Fswit001\u002Fworldloops\nmetadata: {\"openclaw\":{\"requires\":{\"bins\":[\"node\",\"npm\"]},\"envVars\":[{\"name\":\"WORLDLOOPS_API_BASE_URL\",\"required\":false,\"description\":\"Optional WorldLoops API base URL override. Defaults to https:\u002F\u002Fapi.worldloops.ai.\"},{\"name\":\"WORLDLOOPS_API_KEY\",\"required\":false,\"description\":\"Optional bearer token for hosted WorldLoops API.\"}],\"emoji\":\"🌐\",\"homepage\":\"https:\u002F\u002Fgithub.com\u002Fswit001\u002Fworldloops\",\"skillKey\":\"worldloops\",\"tags\":[\"openclaw\",\"clawhub\",\"agentic-ai\",\"world-model\",\"executable-world\",\"open-loops\",\"open-loop-management\",\"workflow\",\"human-in-the-loop\",\"safe-by-default\",\"auditable-runtime\",\"stateful-loop-management\",\"agent-execution-guard\",\"execution-governance\",\"execution-contracts\",\"proposal-engine\",\"workflow-governance\"]}}\n---\n\n# Agent Execution Guard\n\nAgent Execution Guard is a WorldLoops skill for OpenClaw.\n\nIt turns signals from tools, messages, and workflows into governed open loops:\n\nSignal → Open Loop → Proposal → Approval → Local Transition → Receipt\n\nIt helps agents avoid unsafe or premature execution by keeping action proposals inside a safe, auditable boundary.\n\n---\n\n## Why it matters\n\nMost agents answer from a snapshot.\nWorldLoops tracks what remains unresolved.\n\nWhen an email, calendar event, Slack message, or GitHub notification implies unfinished responsibility, Agent Execution Guard surfaces it as a governed open loop — not a silent side effect.\n\nEvery proposed action requires approval before any local transition is committed.\nNo external system is changed.\n`externalWrite:false` is preserved throughout.\n\n---\n\n## Quick Start\n\n```bash\nclawhub install worldloops\ncd ~\u002F.openclaw\u002Fworkspace\u002Fskills\u002Fworldloops\nnpm run demo\n```\n\n### Optional Safety Check\n\n```bash\nnpm run doctor\n```\n\n---\n\n## Example demo output\n\n```bash\nnpm run demo\n```\n\n```\n🦞 Agent Execution Guard\n\n🚨 High — Gmail callback requested\nState: open\n\nProposal:\nReview claim context and decide whether to call back or prepare a written response. This is a local planning action only — do not initiate any call, email, or external communication without an explicit decision.\n\nAdjudication:\nrequires_approval\n\n✅ Safe\nexternalWrite:false\nNo email, draft, call, or external change made.\n```\n\n---\n\n## Safety posture\n\nAgent Execution Guard does not send emails.\nAgent Execution Guard does not post chat messages.\nAgent Execution Guard does not create calendar events.\nAgent Execution Guard does not modify external systems.\n\n```\n✅ 0 emails sent\n✅ 0 calendar events changed\n✅ 0 chat messages posted\n✅ 0 files modified\n✅ 0 project changes made\n✅ externalWrite:false enforced\n```\n\nOpenClaw reads signals.\nWorldLoops guards execution.\n\nWorldLoops does not need to own every connector.\nIf a host agent can read a signal, it can pass it to Agent Execution Guard.\n\nOpenClaw observes and interprets source signals (Gmail, Calendar, Slack, GitHub) into `ObservedSignal[]`.\nWorldLoops reads those OpenClaw-authored interpreted observations and adjudicates their lifecycle state — into active open loops, attached context, suppression receipts, and transitions.\nWorldLoops does not connect to Gmail, Calendar, or Slack directly. `externalWrite:false` is preserved throughout.\n\n---\n\n## OpenClaw Signal Handoff\n\nOpenClaw reads. Agent Execution Guard governs.\n\nNo connectors added.\nNo OAuth added.\nNo external write.\n\nA host agent (OpenClaw, gog, or any other) reads signals from Gmail, Calendar, Slack, or GitHub.\nIt places the already-read payload as a local JSON file.\nAgent Execution Guard receives that payload, normalizes it into an `AdapterSignal`, and produces a governed receipt.\n\n```\nOpenClaw \u002F gog reads Gmail \u002F Calendar \u002F Slack \u002F GitHub\n    ↓\nalready-read payload → .worldloops\u002Finbox\u002Fopenclaw-gmail-live.json\n    ↓\nnpm run guard:gmail -- --input .worldloops\u002Finbox\u002Fopenclaw-gmail-live.json --compact\n    ↓\nAgent Execution Guard\n    ↓\ngoverned open loop → proposal → receipt\nexternalWrite:false\n```\n\n### Accepted local payload formats\n\nAgent Execution Guard can consume local payloads in these forms:\n\n- **AdapterSignal JSON** — fully normalized signal with `source`, `sourceType`, `text`, `observedAt`, `externalWrite:false`\n- **OpenClaw-style handoff payloads** — already-normalized payloads from OpenClaw host agents\n- **gog-style Gmail payloads** — `{ \"messages\": [...] }` output from gog Gmail reads\n- **gog-style Calendar payloads** — `{ \"events\": [...] }` output from gog Calendar reads\n- **Slack host\u002Fplugin payloads** — `{ \"channel\": \"...\", \"messages\": [...] }` output from Slack host tools\n\ngog and OpenClaw read Gmail, Calendar, and Slack.\nAgent Execution Guard only consumes the local JSON output they produce.\nNo Gmail, Calendar, or Slack API call is made by WorldLoops.\n`externalWrite:false` is preserved throughout.\n\n### Local handoff directory\n\nHost agents should place payloads here:\n\n```\n.worldloops\u002Finbox\u002Fopenclaw-gmail-live.json\n.worldloops\u002Finbox\u002Fopenclaw-calendar-live.json\n.worldloops\u002Finbox\u002Fopenclaw-slack-live.json\n.worldloops\u002Finbox\u002Fopenclaw-github-live.json\n```\n\nThe `.worldloops\u002Finbox\u002F` directory is created automatically on first run and is gitignored by default.\n\nRedacted payload examples are in `examples\u002Fhandoff\u002F`.\n\n---\n\n## OpenClaw + WorldLoops\n\nOpenClaw is excellent at observing possible signals from user-facing queries such as \"What did I miss?\" or \"What should I do today?\"\n\nWorldLoops starts after observation.\n\nIt takes OpenClaw-observed candidate signals and adjudicates whether they are real open loops, suppressing noise such as promotional messages, FYI-only updates, duplicates, and weak evidence. Accepted signals become stateful open loops that can move through To Do, Doing, Done, Snoozed, or Escalated.\n\n### Run\n\n```bash\nnpm run openclaw:intake -- --input scripts\u002Ffixtures\u002Fopenclaw-signal-intake\u002Fmixed-observations.json\n```\n\n### OpenClaw Observation Adapter contract\n\n```\nobservedBy        \"openclaw\"\nobservationIntent new_loop | state_transition | noise | related_context | evidence\nsource            gmail | slack | calendar | github | manual\nsourceId          source-unique identifier for deduplication\ntitle             human-readable signal title\ntext              full signal text\ntimestamp         ISO 8601\nactor             sender \u002F requester (optional)\ndueAt             deadline (optional)\nevidence          source-specific fields (subject, snippet, channel, location…)\nconfidence        0.0–1.0 (optional; \u003C 0.4 → needs_review)\nrelatedContext    null | { existingLoopKey, type, note } | { observationId, type }\n```\n\n### Adjudication verdicts\n\n```\naccepted          → open loop created (todo)\nsuppressed        → receipt saved, no loop\nattached_context  → context noted, no loop\nneeds_review      → flagged, no loop\nstate_transition  → existing loop updated (done | escalated | snoozed)\n```\n\n### Morning Brief — state-management surface\n\nThe intake run produces a morning brief showing loop lifecycle:\n\n```\n- 1 loop still open\n- 1 loop closed by new evidence\n- 1 loop escalated\n- 6 observed signals suppressed as noise\n```\n\n---\n\n## Daily Brief\n\nGet a single compact summary of Gmail, Calendar, and Slack handoff payloads in one command.\n\nOpenClaw\u002Fgog\u002Fhost tools read Gmail, Calendar, and Slack.\nAgent Execution Guard reads only local payload files.\nNo Gmail, Calendar, or Slack API call is made by WorldLoops.\n`externalWrite:false` is preserved.\n\n### How it works\n\n1. Host tools (OpenClaw, gog, or Slack plugin) read your Gmail, Calendar, and Slack.\n2. They save the already-read payloads as local JSON files in `.worldloops\u002Finbox\u002F`.\n3. Agent Execution Guard reads those local files and produces one compact Daily Brief.\n\n```\n.worldloops\u002Finbox\u002Fopenclaw-gmail-live.json      ← Gmail payload\n.worldloops\u002Finbox\u002Fopenclaw-calendar-live.json   ← Calendar payload\n.worldloops\u002Finbox\u002Fopenclaw-slack-live.json      ← Slack payload\n```\n\n### Run\n\n```bash\nnpm run guard:daily\nnpm run brief:daily\n```\n\n### Preferences\n\nDefault schedule: **09:00 local time**, default delivery channel: **local**.\n\nView preferences:\n\n```bash\nnpm run brief:preferences\n```\n\nChange delivery time:\n\n```bash\nnpm run brief:preferences:set -- --time 08:30\n```\n\nSet delivery channel:\n\n```bash\nnpm run brief:preferences:set -- --channel local\nnpm run brief:preferences:set -- --channel telegram\nnpm run brief:preferences:set -- --channel slack\nnpm run brief:preferences:set -- --channel discord\nnpm run brief:preferences:set -- --channel sms\nnpm run brief:preferences:set -- --channel email\n```\n\nDaily Brief delivery channels include local, Telegram, Slack, Discord, SMS, and email.\nWhen referring only to chat-style channels: messenger channels such as Telegram, Slack, and Discord.\n\n### Delivery\n\nGenerate and deliver the brief:\n\n```bash\nnpm run brief:deliver\nnpm run brief:deliver -- --dry-run\nnpm run brief:deliver -- --channel telegram\n```\n\nDelivery notes:\n- Channel `local` prints the brief to stdout.\n- Remote channels (Telegram, Slack, Discord, SMS, email) require a host scheduler or integration to be active.\n- If no integration is active, the command exits 0 with a delivery-ready message and the brief text.\n- WorldLoops does not install cron, launchd, or background daemons.\n- A host scheduler (e.g. OpenClaw) may call `npm run brief:deliver` at the configured time.\n\n### Example output — payloads connected\n\n```\n🦞 Agent Execution Guard Daily Brief\n\nSources:\n✅ Gmail\n✅ Calendar\n✅ Slack\n\nOpen loops:\n\n⚠️ Gmail — Review requested\nFrom: Test Reviewer \u003Creviewer@example.com>\nSubject: Please review the submitted document\nWhy: review request detected\nEvidence: \"Please review the submitted document and send updates by EOD.\"\nAction: Review the submitted document or reply if needed\nAdjudication: requires_approval\n\n📅 Calendar — Important context\nEvent: Flight to Seoul (KE 24)\nWhen: May 21, 12:40 PM local time\nLocation: SFO\nReason: travel event detected, no action proposed\n\n💬 Slack — Action requested\nFrom: Dana\nChannel: #product\nWhy: review or approval request detected\nEvidence: \"Can you review this before release?\"\nAction: Review and comment\nAdjudication: requires_approval\n\n✅ Safe\nexternalWrite:false\nNo email, draft, calendar event, Slack message, or external change made.\n\nDaily Brief schedule: 09:00 local time — Delivery channel: local\nTo change: npm run brief:preferences:set -- --time HH:MM\n```\n\n### Example output — Gmail no-action with samples\n\nPromotional emails (airline offers, newsletters, discount campaigns, rewards updates) and messages with \"no action required\" are automatically suppressed and do not generate open loops:\n\n```\n📧 Gmail — No actionable loop detected\nChecked: 2 messages\nSample:\n- From: promotions@airline.example.com \u002F Subject: Earn double miles this weekend — promotion\n- From: noreply@rewards.example.com \u002F Subject: Your rewards balance: 12,450 miles\nReason: promotional or informational message; no reply, approval, review, deadline, or follow-up request detected\n```\n\nFlight and airport calendar events appear as important context without becoming approval-required tasks:\n\n```\n📅 Calendar — Important context\nEvent: Departure to ICN — Korean Air KE 24\nWhen: May 21, 12:40 PM local time\nLocation: SFO Terminal 2, Gate G1\nReason: travel event detected, no action proposed\n```\n\n### Example output — Slack not connected\n\n```\n⬜ Slack — not connected\nReason: no Slack payload found\nNext: configure OpenClaw channels.slack, then save payload to:\n.worldloops\u002Finbox\u002Fopenclaw-slack-live.json\n```\n\n### Example output — payloads not connected yet\n\n```\n🦞 Agent Execution Guard Daily Brief\n\nNo local handoff payloads found yet.\n\nAdd payloads here:\n- Gmail: .worldloops\u002Finbox\u002Fopenclaw-gmail-live.json\n- Calendar: .worldloops\u002Finbox\u002Fopenclaw-calendar-live.json\n- Slack: .worldloops\u002Finbox\u002Fopenclaw-slack-live.json\n\nThen run:\nnpm run guard:daily\n\nSource systems stay untouched.\nexternalWrite:false\n\nDaily Brief schedule: 09:00 local time — Delivery channel: local\n```\n\n---\n\n## Current commands\n\nFor everyone:\n\n```bash\nnpm run demo\nnpm run guard:demo\nnpm run wow\nnpm run doctor\n```\n\nFor Daily Brief (all sources combined):\n\n```bash\nnpm run guard:daily\nnpm run brief:daily\nnpm run guard:daily -- --details\nnpm run brief:daily -- --inbox scripts\u002Ffixtures\u002Finbox\nnpm run brief:daily -- --inbox scripts\u002Ffixtures\u002Finbox --details\nnpm run brief:preferences\nnpm run brief:preferences:set -- --time 08:30\nnpm run brief:preferences:set -- --channel telegram\nnpm run brief:deliver\nnpm run brief:deliver -- --dry-run\nnpm run brief:deliver -- --channel telegram\n```\n\nFor governed adapter invocation (already-read OpenClaw payloads):\n\n```bash\nnpm run guard:adapter -- --source gmail --input \u003Cpayload.json>\nnpm run guard:adapter -- --source gmail --input \u003Cpayload.json> --compact\nnpm run guard:gmail -- --input \u003Cpayload.json>\nnpm run guard:calendar -- --input \u003Cpayload.json>\nnpm run guard:slack -- --input \u003Cpayload.json>\nnpm run guard:github -- --input \u003Cpayload.json>\n```\n\nFor compact chat-friendly output:\n\n```bash\nnpm run doctor:mobile\n```\n\nFor developers:\n\n```bash\nnpm run wow:developer\nnpm run loop:list\nnpm run loop:transition -- \u003CloopId> doing \"started local follow-up\"\nnpm run loop:summary\nnpm run loop:review\nnpm run proposal:list\nnpm run proposal:show -- \u003CproposalId>\nnpm run proposal:decide -- \u003CproposalId> approve\nnpm run plan:list\nnpm run contract:list\nnpm run state:check\nnpm run receipts:verify\nnpm run state:repair\nnpm run capability:show\n```\n\nFor adapter developers:\n\n```bash\nnpm run adapter:validate -- examples\u002Fadapters\u002Fslack-message.json\nnpm run adapter:test -- examples\u002Fadapters\u002Fslack-message.json\nnpm run brief:reconcile -- --adapter-signal examples\u002Fadapters\u002Fslack-message.json\n```\n\nAll commands preserve `externalWrite:false` and do not write to Gmail, Calendar, Slack, GitHub, or any external system.\n\n---\n\n## Updating\n\n```\nclawhub update worldloops\n```\n\nForce reinstall:\n\n```\nclawhub install worldloops --force\n```\n\n---\n\n## Agent Runtime Instructions\n\nThe following section is for OpenClaw agents, not end users.\n\n### Daily Brief routing\n\nWhen the user asks for any of the following:\n- Daily Brief\n- morning brief\n- daily summary\n- today's open loops\n- what did I miss\n- open loops today\n- Agent Execution Guard Daily Brief\n- brief me\n\nRun immediately — do not search the workspace first:\n\n```bash\nnpm run --silent guard:daily\n```\n\nReturn only the command output. Do not narrate the command unless the user asks.\nDo not show tool search steps.\nDo not inspect package.json first for Daily Brief requests.\n\nFor fixture-based Daily Brief examples:\n\n```bash\nnpm run --silent brief:daily -- --inbox scripts\u002Ffixtures\u002Finbox\n```\n\nFor details mode (source identifiers):\n\n```bash\nnpm run --silent guard:daily -- --details\nnpm run --silent brief:daily -- --inbox scripts\u002Ffixtures\u002Finbox --details\n```\n\nFor delivery-ready checks:\n\n```bash\nnpm run --silent brief:deliver -- --channel telegram\n```\n\n### Demo routing\n\nWhen the user asks for a demo, guard demo, execution guard demo, Agent Execution Guard demo, real signal governance demo, WorldLoops guard demo, or open-loop demo, run:\n\n```bash\nnpm run --silent demo\n```\n\nReturn only the compact Agent Execution Guard output.\n\n### Runtime invocation\n\nWhen the user asks you to run this skill, do the following:\n\n1. Change into the skill directory: `{baseDir}`\n2. Run the command with `--silent`\n3. Use provided local payload files when available\n4. If no payload files are provided, use the included fixture files\n5. Return the result directly\n6. Do not modify external systems\n\nSafe default command from the skill directory:\n\n```\nnpm run --silent demo\n```\n\nFor Daily Brief (all local inbox sources combined):\n\n```\nnpm run --silent guard:daily\nnpm run --silent brief:deliver\nnpm run --silent brief:deliver -- --dry-run\nnpm run --silent brief:deliver -- --channel telegram\n```\n\nFor Daily Brief preferences:\n\n```\nnpm run --silent brief:preferences\nnpm run --silent brief:preferences:set -- --time HH:MM\nnpm run --silent brief:preferences:set -- --channel \u003Cchannel>\n```\n\nFor local payload handoff:\n\n```\nnpm run --silent guard:gmail -- --input \u003Cpayload.json> --compact\nnpm run --silent guard:calendar -- --input \u003Cpayload.json> --compact\nnpm run --silent guard:slack -- --input \u003Cpayload.json> --compact\nnpm run --silent guard:github -- --input \u003Cpayload.json> --compact\n```\n\n### OpenClaw observation write-back\n\nWhen the user asks any of the following — or anything with the same intent:\n- \"What should I do today?\"\n- \"What did I miss?\"\n- \"Any follow-ups I'm missing?\"\n- daily brief, morning brief, open loops check\n\nPerform your normal high-quality observation: read full message content, search memory for existing open loops, resolve actor identities, extract deadlines from natural language, and prioritize what matters to the user.\n\nAfter surfacing candidates, write them as `ObservedSignal[]` to:\n\n```\n.worldloops\u002Finbox\u002Fopenclaw-observations.json\n```\n\nThis is a local workspace file write only. No external system is called.\n\n**Do not tell WorldLoops to reinterpret raw Gmail, Calendar, or Slack payloads.** WorldLoops adjudicates the interpreted observations you write here — it does not re-read source inboxes.\n\n**Shape of each item (`ObservedSignal`):**\n\n```json\n{\n  \"id\": \"openclaw-\u003Csource>-\u003CsourceId>\",\n  \"source\": \"gmail\" | \"slack\" | \"calendar\" | \"github\" | \"manual\",\n  \"sourceId\": \"\u003Cmessage or event ID from the source>\",\n  \"observedBy\": \"openclaw\",\n  \"userQuery\": \"\u003Cthe question the user asked>\",\n  \"observationIntent\": \"new_loop\" | \"state_transition\" | \"noise\" | \"related_context\" | \"evidence\",\n  \"title\": \"\u003Cyour interpreted action title — not a copy of the raw subject line>\",\n  \"text\": \"\u003Cone-sentence synthesis of why this matters to the user>\",\n  \"timestamp\": \"\u003CISO 8601>\",\n  \"actor\": \"\u003Cresolved name or email — not a raw Slack user ID>\",\n  \"dueAt\": \"\u003CISO 8601 deadline extracted from natural language, else omit>\",\n  \"evidence\": {\n    \"\u003Craw field from source>\": \"\u003Cvalue>\"\n  },\n  \"confidence\": 0.0–1.0,\n  \"relatedContext\": null\n}\n```\n\nFor `state_transition` intent, set `relatedContext`:\n\n```json\n\"relatedContext\": {\n  \"existingLoopKey\": \"openclaw-\u003Csource>-\u003CsourceId of existing loop>\",\n  \"proposedTransition\": \"done\" | \"escalated\" | \"snoozed\",\n  \"note\": \"\u003Cwhy this closes or escalates the loop>\"\n}\n```\n\n**What you must decide before writing — your interpretation, not shallow heuristics:**\n- `observationIntent`: classify using full message content, your memory of open loops, and conversation context\n- `title`: a human-readable action title synthesized from the full message — not a copy of the subject line\n- `text`: one sentence on why this matters to the user right now\n- `dueAt`: extract from natural language (\"by Friday\" → ISO date of that Friday at 17:00 local)\n- `actor`: resolve Slack user IDs and display names to real identities where known\n- `confidence`: your assessed certainty given full context, not field presence\n- `relatedContext.existingLoopKey`: search memory for existing open loops before marking `state_transition`\n\n**Include noise explicitly.** Promotional email, automated notifications, and informational-only items should be written with `observationIntent: \"noise\"` rather than omitted — WorldLoops records suppression receipts for them.\n\nTo write and validate observations, use the helper command from the skill directory:\n\n```bash\nnpm run observations:write -- --input \u003Cpath\u002Fto\u002Fyour-observations.json>\n```\n\nThis validates the `ObservedSignal[]` shape, creates `.worldloops\u002Finbox\u002F` if needed, and writes to `.worldloops\u002Finbox\u002Fopenclaw-observations.json`. It will refuse invalid JSON or missing required fields and exit non-zero on error.\n\nAfter writing, WorldLoops `openclaw:intake` handles all lifecycle management: deduplication, open loop creation, state transitions, suppression receipts.\n\n### Default API\n\nBy default, WorldLoops uses:\n\n```\nhttps:\u002F\u002Fapi.worldloops.ai\n```\n\nYou do not need to set `WORLDLOOPS_API_BASE_URL` for the default demo flow.\n\nTo use a different backend, set:\n\n```\nWORLDLOOPS_API_BASE_URL=https:\u002F\u002Fyour-worldloops-api.example.com\n```\n\nOptional:\n\n```\nWORLDLOOPS_API_KEY=your_api_key\n```\n\n### Output\n\nDefault output is compact, messenger-friendly Agent Execution Guard output.\nStructured JSON remains available through developer-oriented commands where supported.\n\n### Important rules\n\nDo not invent missing source data.\nDo not send messages.\nDo not send emails.\nDo not create drafts.\nDo not create or update calendar events.\nDo not write to Slack, Gmail, Calendar, GitHub, SMS, or push channels.\nDo not implement background daemons.\nDo not auto-install cron or launchd.\n\nReturn the result directly.\n","# Agent Execution Guard\n\nAgent Execution Guard is a WorldLoops skill for OpenClaw.\n\nIt turns signals from tools, messages, and workflows into governed open loops:\n\nSignal → Open Loop → Proposal → Approval → Local Transition → Receipt\n\nIt helps agents avoid unsafe or premature execution by keeping action proposals inside a safe, auditable boundary.\n\n---\n\n## Why it matters\n\nMost agents answer from a snapshot.\nWorldLoops tracks what remains unresolved.\n\nWhen an email, calendar event, Slack message, or GitHub notification implies unfinished responsibility, Agent Execution Guard surfaces it as a governed open loop — not a silent side effect.\n\nEvery proposed action requires approval before any local transition is committed.\nNo external system is changed.\n`externalWrite:false` is preserved throughout.\n\n---\n\n## Quick Start\n\n```bash\nclawhub install worldloops\ncd ~\u002F.openclaw\u002Fworkspace\u002Fskills\u002Fworldloops\nnpm run demo\n```\n\n### Optional Safety Check\n\n```bash\nnpm run doctor\n```\n\n---\n\n## Example demo output\n\n```bash\nnpm run demo\n```\n\n```\n🦞 Agent Execution Guard\n\n🚨 High — Gmail callback requested\nState: open\n\nProposal:\nReview claim context and decide whether to call back or prepare a written response. This is a local planning action only — do not initiate any call, email, or external communication without an explicit decision.\n\nAdjudication:\nrequires_approval\n\n✅ Safe\nexternalWrite:false\nNo email, draft, call, or external change made.\n```\n\n---\n\n## Safety posture\n\nAgent Execution Guard does not send emails.\nAgent Execution Guard does not post chat messages.\nAgent Execution Guard does not create calendar events.\nAgent Execution Guard does not modify external systems.\n\n```\n✅ 0 emails sent\n✅ 0 calendar events changed\n✅ 0 chat messages posted\n✅ 0 files modified\n✅ 0 project changes made\n✅ externalWrite:false enforced\n```\n\nOpenClaw reads signals.\nWorldLoops guards execution.\n\nWorldLoops does not need to own every connector.\nIf a host agent can read a signal, it can pass it to Agent Execution Guard.\n\nOpenClaw observes and interprets source signals (Gmail, Calendar, Slack, GitHub) into `ObservedSignal[]`.\nWorldLoops reads those OpenClaw-authored interpreted observations and adjudicates their lifecycle state — into active open loops, attached context, suppression receipts, and transitions.\nWorldLoops does not connect to Gmail, Calendar, or Slack directly. `externalWrite:false` is preserved throughout.\n\n---\n\n## OpenClaw Signal Handoff\n\nOpenClaw reads. Agent Execution Guard governs.\n\nNo connectors added.\nNo OAuth added.\nNo external write.\n\nA host agent (OpenClaw, gog, or any other) reads signals from Gmail, Calendar, Slack, or GitHub.\nIt places the already-read payload as a local JSON file.\nAgent Execution Guard receives that payload, normalizes it into an `AdapterSignal`, and produces a governed receipt.\n\n```\nOpenClaw \u002F gog reads Gmail \u002F Calendar \u002F Slack \u002F GitHub\n    ↓\nalready-read payload → .worldloops\u002Finbox\u002Fopenclaw-gmail-live.json\n    ↓\nnpm run guard:gmail -- --input .worldloops\u002Finbox\u002Fopenclaw-gmail-live.json --compact\n    ↓\nAgent Execution Guard\n    ↓\ngoverned open loop → proposal → receipt\nexternalWrite:false\n```\n\n### Accepted local payload formats\n\nAgent Execution Guard can consume local payloads in these forms:\n\n- **AdapterSignal JSON** — fully normalized signal with `source`, `sourceType`, `text`, `observedAt`, `externalWrite:false`\n- **OpenClaw-style handoff payloads** — already-normalized payloads from OpenClaw host agents\n- **gog-style Gmail payloads** — `{ \"messages\": [...] }` output from gog Gmail reads\n- **gog-style Calendar payloads** — `{ \"events\": [...] }` output from gog Calendar reads\n- **Slack host\u002Fplugin payloads** — `{ \"channel\": \"...\", \"messages\": [...] }` output from Slack host tools\n\ngog and OpenClaw read Gmail, Calendar, and Slack.\nAgent Execution Guard only consumes the local JSON output they produce.\nNo Gmail, Calendar, or Slack API call is made by WorldLoops.\n`externalWrite:false` is preserved throughout.\n\n### Local handoff directory\n\nHost agents should place payloads here:\n\n```\n.worldloops\u002Finbox\u002Fopenclaw-gmail-live.json\n.worldloops\u002Finbox\u002Fopenclaw-calendar-live.json\n.worldloops\u002Finbox\u002Fopenclaw-slack-live.json\n.worldloops\u002Finbox\u002Fopenclaw-github-live.json\n```\n\nThe `.worldloops\u002Finbox\u002F` directory is created automatically on first run and is gitignored by default.\n\nRedacted payload examples are in `examples\u002Fhandoff\u002F`.\n\n---\n\n## OpenClaw + WorldLoops\n\nOpenClaw is excellent at observing possible signals from user-facing queries such as \"What did I miss?\" or \"What should I do today?\"\n\nWorldLoops starts after observation.\n\nIt takes OpenClaw-observed candidate signals and adjudicates whether they are real open loops, suppressing noise such as promotional messages, FYI-only updates, duplicates, and weak evidence. Accepted signals become stateful open loops that can move through To Do, Doing, Done, Snoozed, or Escalated.\n\n### Run\n\n```bash\nnpm run openclaw:intake -- --input scripts\u002Ffixtures\u002Fopenclaw-signal-intake\u002Fmixed-observations.json\n```\n\n### OpenClaw Observation Adapter contract\n\n```\nobservedBy        \"openclaw\"\nobservationIntent new_loop | state_transition | noise | related_context | evidence\nsource            gmail | slack | calendar | github | manual\nsourceId          source-unique identifier for deduplication\ntitle             human-readable signal title\ntext              full signal text\ntimestamp         ISO 8601\nactor             sender \u002F requester (optional)\ndueAt             deadline (optional)\nevidence          source-specific fields (subject, snippet, channel, location…)\nconfidence        0.0–1.0 (optional; \u003C 0.4 → needs_review)\nrelatedContext    null | { existingLoopKey, type, note } | { observationId, type }\n```\n\n### Adjudication verdicts\n\n```\naccepted          → open loop created (todo)\nsuppressed        → receipt saved, no loop\nattached_context  → context noted, no loop\nneeds_review      → flagged, no loop\nstate_transition  → existing loop updated (done | escalated | snoozed)\n```\n\n### Morning Brief — state-management surface\n\nThe intake run produces a morning brief showing loop lifecycle:\n\n```\n- 1 loop still open\n- 1 loop closed by new evidence\n- 1 loop escalated\n- 6 observed signals suppressed as noise\n```\n\n---\n\n## Daily Brief\n\nGet a single compact summary of Gmail, Calendar, and Slack handoff payloads in one command.\n\nOpenClaw\u002Fgog\u002Fhost tools read Gmail, Calendar, and Slack.\nAgent Execution Guard reads only local payload files.\nNo Gmail, Calendar, or Slack API call is made by WorldLoops.\n`externalWrite:false` is preserved.\n\n### How it works\n\n1. Host tools (OpenClaw, gog, or Slack plugin) read your Gmail, Calendar, and Slack.\n2. They save the already-read payloads as local JSON files in `.worldloops\u002Finbox\u002F`.\n3. Agent Execution Guard reads those local files and produces one compact Daily Brief.\n\n```\n.worldloops\u002Finbox\u002Fopenclaw-gmail-live.json      ← Gmail payload\n.worldloops\u002Finbox\u002Fopenclaw-calendar-live.json   ← Calendar payload\n.worldloops\u002Finbox\u002Fopenclaw-slack-live.json      ← Slack payload\n```\n\n### Run\n\n```bash\nnpm run guard:daily\nnpm run brief:daily\n```\n\n### Preferences\n\nDefault schedule: **09:00 local time**, default delivery channel: **local**.\n\nView preferences:\n\n```bash\nnpm run brief:preferences\n```\n\nChange delivery time:\n\n```bash\nnpm run brief:preferences:set -- --time 08:30\n```\n\nSet delivery channel:\n\n```bash\nnpm run brief:preferences:set -- --channel local\nnpm run brief:preferences:set -- --channel telegram\nnpm run brief:preferences:set -- --channel slack\nnpm run brief:preferences:set -- --channel discord\nnpm run brief:preferences:set -- --channel sms\nnpm run brief:preferences:set -- --channel email\n```\n\nDaily Brief delivery channels include local, Telegram, Slack, Discord, SMS, and email.\nWhen referring only to chat-style channels: messenger channels such as Telegram, Slack, and Discord.\n\n### Delivery\n\nGenerate and deliver the brief:\n\n```bash\nnpm run brief:deliver\nnpm run brief:deliver -- --dry-run\nnpm run brief:deliver -- --channel telegram\n```\n\nDelivery notes:\n- Channel `local` prints the brief to stdout.\n- Remote channels (Telegram, Slack, Discord, SMS, email) require a host scheduler or integration to be active.\n- If no integration is active, the command exits 0 with a delivery-ready message and the brief text.\n- WorldLoops does not install cron, launchd, or background daemons.\n- A host scheduler (e.g. OpenClaw) may call `npm run brief:deliver` at the configured time.\n\n### Example output — payloads connected\n\n```\n🦞 Agent Execution Guard Daily Brief\n\nSources:\n✅ Gmail\n✅ Calendar\n✅ Slack\n\nOpen loops:\n\n⚠️ Gmail — Review requested\nFrom: Test Reviewer \u003Creviewer@example.com>\nSubject: Please review the submitted document\nWhy: review request detected\nEvidence: \"Please review the submitted document and send updates by EOD.\"\nAction: Review the submitted document or reply if needed\nAdjudication: requires_approval\n\n📅 Calendar — Important context\nEvent: Flight to Seoul (KE 24)\nWhen: May 21, 12:40 PM local time\nLocation: SFO\nReason: travel event detected, no action proposed\n\n💬 Slack — Action requested\nFrom: Dana\nChannel: #product\nWhy: review or approval request detected\nEvidence: \"Can you review this before release?\"\nAction: Review and comment\nAdjudication: requires_approval\n\n✅ Safe\nexternalWrite:false\nNo email, draft, calendar event, Slack message, or external change made.\n\nDaily Brief schedule: 09:00 local time — Delivery channel: local\nTo change: npm run brief:preferences:set -- --time HH:MM\n```\n\n### Example output — Gmail no-action with samples\n\nPromotional emails (airline offers, newsletters, discount campaigns, rewards updates) and messages with \"no action required\" are automatically suppressed and do not generate open loops:\n\n```\n📧 Gmail — No actionable loop detected\nChecked: 2 messages\nSample:\n- From: promotions@airline.example.com \u002F Subject: Earn double miles this weekend — promotion\n- From: noreply@rewards.example.com \u002F Subject: Your rewards balance: 12,450 miles\nReason: promotional or informational message; no reply, approval, review, deadline, or follow-up request detected\n```\n\nFlight and airport calendar events appear as important context without becoming approval-required tasks:\n\n```\n📅 Calendar — Important context\nEvent: Departure to ICN — Korean Air KE 24\nWhen: May 21, 12:40 PM local time\nLocation: SFO Terminal 2, Gate G1\nReason: travel event detected, no action proposed\n```\n\n### Example output — Slack not connected\n\n```\n⬜ Slack — not connected\nReason: no Slack payload found\nNext: configure OpenClaw channels.slack, then save payload to:\n.worldloops\u002Finbox\u002Fopenclaw-slack-live.json\n```\n\n### Example output — payloads not connected yet\n\n```\n🦞 Agent Execution Guard Daily Brief\n\nNo local handoff payloads found yet.\n\nAdd payloads here:\n- Gmail: .worldloops\u002Finbox\u002Fopenclaw-gmail-live.json\n- Calendar: .worldloops\u002Finbox\u002Fopenclaw-calendar-live.json\n- Slack: .worldloops\u002Finbox\u002Fopenclaw-slack-live.json\n\nThen run:\nnpm run guard:daily\n\nSource systems stay untouched.\nexternalWrite:false\n\nDaily Brief schedule: 09:00 local time — Delivery channel: local\n```\n\n---\n\n## Current commands\n\nFor everyone:\n\n```bash\nnpm run demo\nnpm run guard:demo\nnpm run wow\nnpm run doctor\n```\n\nFor Daily Brief (all sources combined):\n\n```bash\nnpm run guard:daily\nnpm run brief:daily\nnpm run guard:daily -- --details\nnpm run brief:daily -- --inbox scripts\u002Ffixtures\u002Finbox\nnpm run brief:daily -- --inbox scripts\u002Ffixtures\u002Finbox --details\nnpm run brief:preferences\nnpm run brief:preferences:set -- --time 08:30\nnpm run brief:preferences:set -- --channel telegram\nnpm run brief:deliver\nnpm run brief:deliver -- --dry-run\nnpm run brief:deliver -- --channel telegram\n```\n\nFor governed adapter invocation (already-read OpenClaw payloads):\n\n```bash\nnpm run guard:adapter -- --source gmail --input \u003Cpayload.json>\nnpm run guard:adapter -- --source gmail --input \u003Cpayload.json> --compact\nnpm run guard:gmail -- --input \u003Cpayload.json>\nnpm run guard:calendar -- --input \u003Cpayload.json>\nnpm run guard:slack -- --input \u003Cpayload.json>\nnpm run guard:github -- --input \u003Cpayload.json>\n```\n\nFor compact chat-friendly output:\n\n```bash\nnpm run doctor:mobile\n```\n\nFor developers:\n\n```bash\nnpm run wow:developer\nnpm run loop:list\nnpm run loop:transition -- \u003CloopId> doing \"started local follow-up\"\nnpm run loop:summary\nnpm run loop:review\nnpm run proposal:list\nnpm run proposal:show -- \u003CproposalId>\nnpm run proposal:decide -- \u003CproposalId> approve\nnpm run plan:list\nnpm run contract:list\nnpm run state:check\nnpm run receipts:verify\nnpm run state:repair\nnpm run capability:show\n```\n\nFor adapter developers:\n\n```bash\nnpm run adapter:validate -- examples\u002Fadapters\u002Fslack-message.json\nnpm run adapter:test -- examples\u002Fadapters\u002Fslack-message.json\nnpm run brief:reconcile -- --adapter-signal examples\u002Fadapters\u002Fslack-message.json\n```\n\nAll commands preserve `externalWrite:false` and do not write to Gmail, Calendar, Slack, GitHub, or any external system.\n\n---\n\n## Updating\n\n```\nclawhub update worldloops\n```\n\nForce reinstall:\n\n```\nclawhub install worldloops --force\n```\n\n---\n\n## Agent Runtime Instructions\n\nThe following section is for OpenClaw agents, not end users.\n\n### Daily Brief routing\n\nWhen the user asks for any of the following:\n- Daily Brief\n- morning brief\n- daily summary\n- today's open loops\n- what did I miss\n- open loops today\n- Agent Execution Guard Daily Brief\n- brief me\n\nRun immediately — do not search the workspace first:\n\n```bash\nnpm run --silent guard:daily\n```\n\nReturn only the command output. Do not narrate the command unless the user asks.\nDo not show tool search steps.\nDo not inspect package.json first for Daily Brief requests.\n\nFor fixture-based Daily Brief examples:\n\n```bash\nnpm run --silent brief:daily -- --inbox scripts\u002Ffixtures\u002Finbox\n```\n\nFor details mode (source identifiers):\n\n```bash\nnpm run --silent guard:daily -- --details\nnpm run --silent brief:daily -- --inbox scripts\u002Ffixtures\u002Finbox --details\n```\n\nFor delivery-ready checks:\n\n```bash\nnpm run --silent brief:deliver -- --channel telegram\n```\n\n### Demo routing\n\nWhen the user asks for a demo, guard demo, execution guard demo, Agent Execution Guard demo, real signal governance demo, WorldLoops guard demo, or open-loop demo, run:\n\n```bash\nnpm run --silent demo\n```\n\nReturn only the compact Agent Execution Guard output.\n\n### Runtime invocation\n\nWhen the user asks you to run this skill, do the following:\n\n1. Change into the skill directory: `{baseDir}`\n2. Run the command with `--silent`\n3. Use provided local payload files when available\n4. If no payload files are provided, use the included fixture files\n5. Return the result directly\n6. Do not modify external systems\n\nSafe default command from the skill directory:\n\n```\nnpm run --silent demo\n```\n\nFor Daily Brief (all local inbox sources combined):\n\n```\nnpm run --silent guard:daily\nnpm run --silent brief:deliver\nnpm run --silent brief:deliver -- --dry-run\nnpm run --silent brief:deliver -- --channel telegram\n```\n\nFor Daily Brief preferences:\n\n```\nnpm run --silent brief:preferences\nnpm run --silent brief:preferences:set -- --time HH:MM\nnpm run --silent brief:preferences:set -- --channel \u003Cchannel>\n```\n\nFor local payload handoff:\n\n```\nnpm run --silent guard:gmail -- --input \u003Cpayload.json> --compact\nnpm run --silent guard:calendar -- --input \u003Cpayload.json> --compact\nnpm run --silent guard:slack -- --input \u003Cpayload.json> --compact\nnpm run --silent guard:github -- --input \u003Cpayload.json> --compact\n```\n\n### OpenClaw observation write-back\n\nWhen the user asks any of the following — or anything with the same intent:\n- \"What should I do today?\"\n- \"What did I miss?\"\n- \"Any follow-ups I'm missing?\"\n- daily brief, morning brief, open loops check\n\nPerform your normal high-quality observation: read full message content, search memory for existing open loops, resolve actor identities, extract deadlines from natural language, and prioritize what matters to the user.\n\nAfter surfacing candidates, write them as `ObservedSignal[]` to:\n\n```\n.worldloops\u002Finbox\u002Fopenclaw-observations.json\n```\n\nThis is a local workspace file write only. No external system is called.\n\n**Do not tell WorldLoops to reinterpret raw Gmail, Calendar, or Slack payloads.** WorldLoops adjudicates the interpreted observations you write here — it does not re-read source inboxes.\n\n**Shape of each item (`ObservedSignal`):**\n\n```json\n{\n  \"id\": \"openclaw-\u003Csource>-\u003CsourceId>\",\n  \"source\": \"gmail\" | \"slack\" | \"calendar\" | \"github\" | \"manual\",\n  \"sourceId\": \"\u003Cmessage or event ID from the source>\",\n  \"observedBy\": \"openclaw\",\n  \"userQuery\": \"\u003Cthe question the user asked>\",\n  \"observationIntent\": \"new_loop\" | \"state_transition\" | \"noise\" | \"related_context\" | \"evidence\",\n  \"title\": \"\u003Cyour interpreted action title — not a copy of the raw subject line>\",\n  \"text\": \"\u003Cone-sentence synthesis of why this matters to the user>\",\n  \"timestamp\": \"\u003CISO 8601>\",\n  \"actor\": \"\u003Cresolved name or email — not a raw Slack user ID>\",\n  \"dueAt\": \"\u003CISO 8601 deadline extracted from natural language, else omit>\",\n  \"evidence\": {\n    \"\u003Craw field from source>\": \"\u003Cvalue>\"\n  },\n  \"confidence\": 0.0–1.0,\n  \"relatedContext\": null\n}\n```\n\nFor `state_transition` intent, set `relatedContext`:\n\n```json\n\"relatedContext\": {\n  \"existingLoopKey\": \"openclaw-\u003Csource>-\u003CsourceId of existing loop>\",\n  \"proposedTransition\": \"done\" | \"escalated\" | \"snoozed\",\n  \"note\": \"\u003Cwhy this closes or escalates the loop>\"\n}\n```\n\n**What you must decide before writing — your interpretation, not shallow heuristics:**\n- `observationIntent`: classify using full message content, your memory of open loops, and conversation context\n- `title`: a human-readable action title synthesized from the full message — not a copy of the subject line\n- `text`: one sentence on why this matters to the user right now\n- `dueAt`: extract from natural language (\"by Friday\" → ISO date of that Friday at 17:00 local)\n- `actor`: resolve Slack user IDs and display names to real identities where known\n- `confidence`: your assessed certainty given full context, not field presence\n- `relatedContext.existingLoopKey`: search memory for existing open loops before marking `state_transition`\n\n**Include noise explicitly.** Promotional email, automated notifications, and informational-only items should be written with `observationIntent: \"noise\"` rather than omitted — WorldLoops records suppression receipts for them.\n\nTo write and validate observations, use the helper command from the skill directory:\n\n```bash\nnpm run observations:write -- --input \u003Cpath\u002Fto\u002Fyour-observations.json>\n```\n\nThis validates the `ObservedSignal[]` shape, creates `.worldloops\u002Finbox\u002F` if needed, and writes to `.worldloops\u002Finbox\u002Fopenclaw-observations.json`. It will refuse invalid JSON or missing required fields and exit non-zero on error.\n\nAfter writing, WorldLoops `openclaw:intake` handles all lifecycle management: deduplication, open loop creation, state transitions, suppression receipts.\n\n### Default API\n\nBy default, WorldLoops uses:\n\n```\nhttps:\u002F\u002Fapi.worldloops.ai\n```\n\nYou do not need to set `WORLDLOOPS_API_BASE_URL` for the default demo flow.\n\nTo use a different backend, set:\n\n```\nWORLDLOOPS_API_BASE_URL=https:\u002F\u002Fyour-worldloops-api.example.com\n```\n\nOptional:\n\n```\nWORLDLOOPS_API_KEY=your_api_key\n```\n\n### Output\n\nDefault output is compact, messenger-friendly Agent Execution Guard output.\nStructured JSON remains available through developer-oriented commands where supported.\n\n### Important rules\n\nDo not invent missing source data.\nDo not send messages.\nDo not send emails.\nDo not create drafts.\nDo not create or update calendar events.\nDo not write to Slack, Gmail, Calendar, GitHub, SMS, or push channels.\nDo not implement background daemons.\nDo not auto-install cron or launchd.\n\nReturn the result directly.\n",{"name":5,"version":24,"homepage":25,"metadata":26,"description":7},"1.12.0","https:\u002F\u002Fgithub.com\u002Fswit001\u002Fworldloops",{"openclaw":27},{"tags":28,"emoji":46,"envVars":47,"homepage":25,"requires":54,"skillKey":5},[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"openclaw","clawhub","agentic-ai","world-model","executable-world","open-loops","open-loop-management","workflow","human-in-the-loop","safe-by-default","auditable-runtime","stateful-loop-management","agent-execution-guard","execution-governance","execution-contracts","proposal-engine","workflow-governance","🌐",[48,51],{"name":49,"required":20,"description":50},"WORLDLOOPS_API_BASE_URL","Optional WorldLoops API base URL override. Defaults to https:\u002F\u002Fapi.worldloops.ai.",{"name":52,"required":20,"description":53},"WORLDLOOPS_API_KEY","Optional bearer token for hosted WorldLoops API.",{"bins":55},[56,57],"node","npm","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fw\u002Fworldloops",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill worldloops",{"tool":73,"command":74},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill worldloops",{"tool":76,"command":77},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill worldloops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fw\u002Fworldloops\u002FSKILL.md",true,[],[82,89,96,103,110,117],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\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":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]