[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M9FV9M49465ERDXBNDJ5P9":3,"skill-same:01M6M9FV9M49465ERDXBNDJ5P9":69},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6M9FV9M49465ERDXBNDJ5P9","autonomous-loop",null,"How Cavekit's autonomous execution loop works — state machine, stop hook,\ncompletion sentinel, lock, budgets, iteration cap. Read this skill any time\nyou are about to run \u002Fck:make, debug a stuck session, or write a new command\nthat needs the loop. Trigger phrases: \"how does the loop work\", \"stop hook\",\n\"autonomous\", \"completion sentinel\", \"why is the session looping\".","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\u002FJuliusBrussee\u002Fblueprint\u002Fskills\u002Fautonomous-loop\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"autonomous loop","loop","autonomous","stop","new","state machine","lock","you","hook","make","iteration","time","cap","run","write","read","command","work","why","how","sentinel","2026-11-10 10:12:30",false,"---\nname: autonomous-loop\ndescription: |\n  How Cavekit's autonomous execution loop works — state machine, stop hook,\n  completion sentinel, lock, budgets, iteration cap. Read this skill any time\n  you are about to run \u002Fck:make, debug a stuck session, or write a new command\n  that needs the loop. Trigger phrases: \"how does the loop work\", \"stop hook\",\n  \"autonomous\", \"completion sentinel\", \"why is the session looping\".\n---\n\n# Autonomous Loop\n\nThe loop lets a single `\u002Fck:make` invocation run dozens of agent iterations\nwithout user intervention, while still respecting per-task budgets, session\nbudgets, and explicit user-approval gates.\n\n## Architecture\n\n```\n┌─────────────────┐  Stop event   ┌────────────────────┐\n│  Claude Code    │──────────────▶│   stop-hook.sh     │\n│   session       │               │  (.cavekit\u002Floop    │\n└─────────────────┘               │   active?)         │\n        ▲                         └─────────┬──────────┘\n        │                                   │ route()\n        │ next prompt injected              ▼\n        │                         ┌────────────────────┐\n        │                         │ cavekit-tools.cjs  │\n        │                         │  routeDecision()   │\n        │                         │  + status-block    │\n        │                         │  + backprop-       │\n        │                         │    directive       │\n        │                         └─────────┬──────────┘\n        │                                   │\n        └───────── {decision:\"block\",       │\n                    reason:\u003Cnext prompt>} ◀─┘\n```\n\n## Files the loop touches\n\nAll under `\u003Cproject>\u002F.cavekit\u002F`:\n\n| File                            | Writer                | Purpose                                      |\n|---------------------------------|-----------------------|----------------------------------------------|\n| `.loop.json`                    | setup-loop            | Sentinel; stop-hook no-ops without it.       |\n| `.loop.lock`                    | stop-hook (heartbeat) | Single-writer lock. PID + hostname + ts.     |\n| `state.md`                      | cavekit-tools         | `phase`, `current_task`, `iteration`.        |\n| `token-ledger.json`             | token-monitor hook    | Session + per-task token tallies.            |\n| `task-status.json`              | commands              | Authoritative task registry.                 |\n| `.progress.json`                | progress-tracker      | Zero-context UI snapshot.                    |\n| `.auto-backprop-pending.json`   | auto-backprop hook    | Flag file from failed tests.                 |\n| `history\u002Fbackprop-log.md`       | backprop skill        | Append-only trace log.                       |\n| `capabilities.json`             | discover command      | MCP + CLI tool detection.                    |\n\n## Lifecycle\n\n1. **Setup** — `\u002Fck:make` calls:\n   ```\n   node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcavekit-tools.cjs\" setup-loop\n   ```\n   This writes `.loop.json` (activating the stop hook) and resets `state.md`.\n\n2. **Work** — the agent does one wave of task execution per iteration.\n\n3. **Stop fires** — Claude Code's Stop event triggers `stop-hook.sh`. The hook:\n   - reads stdin for `session_id` and `transcript_path`\n   - acquires \u002F refreshes the lock\n   - scans the last 20 transcript lines for `\u003Cpromise>CAVEKIT COMPLETE\u003C\u002Fpromise>`\n   - if sentinel found → teardown + exit silently\n   - else → asks `routeDecision()` for the next prompt\n   - prepends the backprop directive if the flag file exists\n   - returns `{\"decision\":\"block\",\"reason\":\u003Cnext prompt>}`\n\n4. **Repeat** — Claude Code treats `decision:block` + `reason:...` as a new\n   user message, so the session continues.\n\n5. **Teardown** — one of:\n   - completion sentinel detected\n   - max-iterations reached (`CAVEKIT_MAX_ITERATIONS`)\n   - session budget exhausted (`CAVEKIT_BUDGET_EXHAUSTED`)\n   - lock stolen by another session (`CAVEKIT_LOCK_CONFLICT`)\n   - user interrupt (hook returns no output; session stops normally)\n\n## Completion sentinel\n\nTo end the loop cleanly, emit exactly:\n\n```\n\u003Cpromise>CAVEKIT COMPLETE\u003C\u002Fpromise>\n```\n\nThe hook searches for this literal in the last 20 transcript lines. Put it on\nits own line at the very end of the final message. Do not wrap it in code\nfences or paraphrase it — the search is a literal substring match.\n\n## Terminal sentinels\n\nWhen `routeDecision()` cannot safely continue, it returns one of these\nstrings instead of a prompt:\n\n| Sentinel                     | Meaning                               |\n|------------------------------|---------------------------------------|\n| `CAVEKIT_LOOP_DONE`          | All tasks complete. Hook exits silent.|\n| `CAVEKIT_MAX_ITERATIONS`     | Iteration cap hit. Loop halted.       |\n| `CAVEKIT_BUDGET_EXHAUSTED`   | Session budget exhausted.             |\n| `CAVEKIT_LOCK_CONFLICT`      | Another session owns the lock.        |\n\nThe hook translates each into a short user-facing message before returning.\n\n## Lock protocol\n\nThe lock is a JSON file (`.loop.lock`) with `{owner, pid, host, heartbeat_at}`.\n\n- **Owner tag**: `session:\u003Csession_id>`.\n- **Heartbeat**: every Stop invocation refreshes `heartbeat_at`.\n- **Stale**: > 5 minutes since last heartbeat. A new session may steal a stale\n  lock.\n- **Conflict**: non-owner with fresh lock → returns `CAVEKIT_LOCK_CONFLICT`.\n\nNever delete `.loop.lock` while a session might be active. Use\n`cavekit-tools release-lock --owner \u003Ctag>` instead.\n\n## Debugging a stuck loop\n\n```bash\n# Inspect current state\nnode \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcavekit-tools.cjs\" status\n\n# Who holds the lock?\ncat .cavekit\u002F.loop.lock\n\n# What would the router do right now?\nnode \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcavekit-tools.cjs\" route\n\n# Drop the loop entirely (safe after a crash)\nnode \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcavekit-tools.cjs\" teardown-loop\n```\n\nTurn on debug logging by exporting `CAVEKIT_DEBUG=1`. The hook will write to\n`.cavekit\u002F.debug.log`.\n\n## What not to do\n\n- Do **not** hand-edit `state.md`'s `phase` field while a loop is active. The\n  hook assumes single-writer semantics and will overwrite you.\n- Do **not** set your own stop hook that also blocks. Multiple blocking hooks\n  race, and Claude Code picks one arbitrarily.\n- Do **not** emit the completion sentinel unless every task in the registry is\n  truly `complete`. The hook trusts the sentinel and tears down immediately.\n","# Autonomous Loop\n\nThe loop lets a single `\u002Fck:make` invocation run dozens of agent iterations\nwithout user intervention, while still respecting per-task budgets, session\nbudgets, and explicit user-approval gates.\n\n## Architecture\n\n```\n┌─────────────────┐  Stop event   ┌────────────────────┐\n│  Claude Code    │──────────────▶│   stop-hook.sh     │\n│   session       │               │  (.cavekit\u002Floop    │\n└─────────────────┘               │   active?)         │\n        ▲                         └─────────┬──────────┘\n        │                                   │ route()\n        │ next prompt injected              ▼\n        │                         ┌────────────────────┐\n        │                         │ cavekit-tools.cjs  │\n        │                         │  routeDecision()   │\n        │                         │  + status-block    │\n        │                         │  + backprop-       │\n        │                         │    directive       │\n        │                         └─────────┬──────────┘\n        │                                   │\n        └───────── {decision:\"block\",       │\n                    reason:\u003Cnext prompt>} ◀─┘\n```\n\n## Files the loop touches\n\nAll under `\u003Cproject>\u002F.cavekit\u002F`:\n\n| File                            | Writer                | Purpose                                      |\n|---------------------------------|-----------------------|----------------------------------------------|\n| `.loop.json`                    | setup-loop            | Sentinel; stop-hook no-ops without it.       |\n| `.loop.lock`                    | stop-hook (heartbeat) | Single-writer lock. PID + hostname + ts.     |\n| `state.md`                      | cavekit-tools         | `phase`, `current_task`, `iteration`.        |\n| `token-ledger.json`             | token-monitor hook    | Session + per-task token tallies.            |\n| `task-status.json`              | commands              | Authoritative task registry.                 |\n| `.progress.json`                | progress-tracker      | Zero-context UI snapshot.                    |\n| `.auto-backprop-pending.json`   | auto-backprop hook    | Flag file from failed tests.                 |\n| `history\u002Fbackprop-log.md`       | backprop skill        | Append-only trace log.                       |\n| `capabilities.json`             | discover command      | MCP + CLI tool detection.                    |\n\n## Lifecycle\n\n1. **Setup** — `\u002Fck:make` calls:\n   ```\n   node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcavekit-tools.cjs\" setup-loop\n   ```\n   This writes `.loop.json` (activating the stop hook) and resets `state.md`.\n\n2. **Work** — the agent does one wave of task execution per iteration.\n\n3. **Stop fires** — Claude Code's Stop event triggers `stop-hook.sh`. The hook:\n   - reads stdin for `session_id` and `transcript_path`\n   - acquires \u002F refreshes the lock\n   - scans the last 20 transcript lines for `\u003Cpromise>CAVEKIT COMPLETE\u003C\u002Fpromise>`\n   - if sentinel found → teardown + exit silently\n   - else → asks `routeDecision()` for the next prompt\n   - prepends the backprop directive if the flag file exists\n   - returns `{\"decision\":\"block\",\"reason\":\u003Cnext prompt>}`\n\n4. **Repeat** — Claude Code treats `decision:block` + `reason:...` as a new\n   user message, so the session continues.\n\n5. **Teardown** — one of:\n   - completion sentinel detected\n   - max-iterations reached (`CAVEKIT_MAX_ITERATIONS`)\n   - session budget exhausted (`CAVEKIT_BUDGET_EXHAUSTED`)\n   - lock stolen by another session (`CAVEKIT_LOCK_CONFLICT`)\n   - user interrupt (hook returns no output; session stops normally)\n\n## Completion sentinel\n\nTo end the loop cleanly, emit exactly:\n\n```\n\u003Cpromise>CAVEKIT COMPLETE\u003C\u002Fpromise>\n```\n\nThe hook searches for this literal in the last 20 transcript lines. Put it on\nits own line at the very end of the final message. Do not wrap it in code\nfences or paraphrase it — the search is a literal substring match.\n\n## Terminal sentinels\n\nWhen `routeDecision()` cannot safely continue, it returns one of these\nstrings instead of a prompt:\n\n| Sentinel                     | Meaning                               |\n|------------------------------|---------------------------------------|\n| `CAVEKIT_LOOP_DONE`          | All tasks complete. Hook exits silent.|\n| `CAVEKIT_MAX_ITERATIONS`     | Iteration cap hit. Loop halted.       |\n| `CAVEKIT_BUDGET_EXHAUSTED`   | Session budget exhausted.             |\n| `CAVEKIT_LOCK_CONFLICT`      | Another session owns the lock.        |\n\nThe hook translates each into a short user-facing message before returning.\n\n## Lock protocol\n\nThe lock is a JSON file (`.loop.lock`) with `{owner, pid, host, heartbeat_at}`.\n\n- **Owner tag**: `session:\u003Csession_id>`.\n- **Heartbeat**: every Stop invocation refreshes `heartbeat_at`.\n- **Stale**: > 5 minutes since last heartbeat. A new session may steal a stale\n  lock.\n- **Conflict**: non-owner with fresh lock → returns `CAVEKIT_LOCK_CONFLICT`.\n\nNever delete `.loop.lock` while a session might be active. Use\n`cavekit-tools release-lock --owner \u003Ctag>` instead.\n\n## Debugging a stuck loop\n\n```bash\n# Inspect current state\nnode \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcavekit-tools.cjs\" status\n\n# Who holds the lock?\ncat .cavekit\u002F.loop.lock\n\n# What would the router do right now?\nnode \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcavekit-tools.cjs\" route\n\n# Drop the loop entirely (safe after a crash)\nnode \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcavekit-tools.cjs\" teardown-loop\n```\n\nTurn on debug logging by exporting `CAVEKIT_DEBUG=1`. The hook will write to\n`.cavekit\u002F.debug.log`.\n\n## What not to do\n\n- Do **not** hand-edit `state.md`'s `phase` field while a loop is active. The\n  hook assumes single-writer semantics and will overwrite you.\n- Do **not** set your own stop hook that also blocks. Multiple blocking hooks\n  race, and Claude Code picks one arbitrarily.\n- Do **not** emit the completion sentinel unless every task in the registry is\n  truly `complete`. The hook trusts the sentinel and tears down immediately.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJuliusBrussee\u002Fblueprint\u002Fskills\u002Fautonomous-loop",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill autonomous-loop",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill autonomous-loop",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill autonomous-loop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJuliusBrussee\u002Fblueprint\u002Fskills\u002Fautonomous-loop\u002FSKILL.md",true,[],[70,80,88,96,104,112],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":79},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":79},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":79},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":79},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":79},"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",[],[]]