[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78NSP2DK2EQM08256PS9651":3,"skill-same:01M78NSP2DK2EQM08256PS9651":61},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":48},"01M78NSP2DK2EQM08256PS9651","loom-status",null,"Use when Loom seems quiet or wrong: a loom tool answers \"unauthenticated\", \"not available\" or an empty result for something the user says was saved; the session-start primer did not appear; the user asks \"is loom working\", \"why didn't it remember\", \"is my token ok\", or a Loom hook says `Executable not found in $PATH: \"node\"` or `node: not found`, or prints a `loom:` line about Node.js 18+. Checks the Node hook runtime, then runs the plugin's client check and reads its lines, so the answer names the cause (missing runtime, unreachable server, rejected or expired token, no writer grant on the write namespace, plugin or MCP entry missing, stranded captures) and the one fix. NOT for server-side operations (that is `loom doctor` on the server) and NOT for deciding what to remember (loom-memory).","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\u002FClickHouse\u002Floom\u002Fskills\u002Floom-status\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: loom-status\ndescription: >\n  Use when Loom seems quiet or wrong: a loom tool answers \"unauthenticated\",\n  \"not available\" or an empty result for something the user says was saved;\n  the session-start primer did not appear; the user asks \"is loom working\",\n  \"why didn't it remember\", \"is my token ok\", or a Loom hook says\n  `Executable not found in $PATH: \"node\"` or `node: not found`, or prints a\n  `loom:` line about Node.js 18+.\n  Checks the Node hook runtime, then runs the plugin's client check and reads\n  its lines, so the answer names the cause (missing runtime, unreachable\n  server, rejected or expired token, no writer grant on the write namespace,\n  plugin or MCP entry missing, stranded captures) and the one fix. NOT for\n  server-side operations (that is `loom doctor` on the server) and NOT for\n  deciding what to remember (loom-memory).\ndisable-model-invocation: true\n---\n\n# loom-status — why is Loom quiet?\n\nEvery client-side failure is silent by design: the hooks fail open, a 401\nreads as \"no memories\", a viewer token makes every capture a 403 nobody\nsees. This skill diagnoses. It writes nothing to Loom and changes nothing\non the machine unless the user agrees to the one fix it names.\n\n`\u003Croot>` below is the installed plugin: `$CLAUDE_PLUGIN_ROOT` in Claude\nCode; in Codex, the newest `~\u002F.codex\u002Fplugins\u002Fcache\u002Floom\u002Floom\u002F*\u002F` directory.\n\n## Check in this order; the first failure is the cause\n\n1. **Local runtime.** `sh \"\u003Croot>\u002Fskills\u002Floom-status\u002Fscripts\u002Fensure-node.sh\" --check`\n   prints the Node 18+ the hooks run under (Claude Code: the `node` on PATH;\n   Codex: the launcher's pick), or one line saying none was found or the one\n   found is too old. A second line names a launch that finds none, with its\n   fix: relay it. On a failure, tell the user the hooks cannot run and offer\n   the fix: for Claude Code, set `PATH` in the `env` block of its settings to\n   the whole search path with Node 18+'s directory first (that `PATH`\n   replaces every session's); under Codex `LOOM_NODE=\u002Fpath\u002Fto\u002Fnode` reaches\n   the hooks, and the MCP header helper needs that Node on PATH. Else the same\n   script without `--check` installs Node (root or passwordless sudo, then\n   apt\u002Fdnf\u002Fyum, apk or Homebrew). Run it only when the user says yes; if it\n   exits 2, report its blocker line, do not retry. After an install the user\n   restarts the session: SessionStart hooks cannot rerun in this one.\n   An MCP-only client has no hooks and skips this step.\n2. **Server, token, auth, grant.** `sh \"\u003Croot>\u002Fbin\u002Floom-node\" \"\u003Croot>\u002Fbin\u002Floom-client-status.mjs\"`\n   prints JSON whose `checks` come in this order: `server`, `server version`\n   (only when the server is older), `token`, `source`, `auth`, `namespace`,\n   `flush` (`ok` is false when `server`, `token`, `auth` or `namespace` fails).\n   `source` names the lookup that supplied the token.\n   In Claude Code the server checked is the one the MCP entry calls: the\n   plugin's install URL when a session saved it, else `LOOM_BASE_URL`, else\n   localhost. In Codex, whose entry lives in its own config, it is the\n   hooks' server and `source` only names the lookup.\n   It ships with the plugin: do not look for a Loom checkout or install the\n   Python CLI. It sends no test write; a listed grant is evidence of\n   permission, not proof a write landed. If `loom` is already\n   on PATH, `loom doctor --client --json` adds deeper checks.\n3. **Plugin registration.** `claude plugin list` (or `codex plugin list`)\n   shows the `loom` plugin enabled; `\u002Fmcp` in the session (or `codex mcp list`)\n   shows the `loom` server connected. A missing entry is the cause even when\n   every check above passed.\n4. **Stranded captures.** The client check's `flush` line (WARN only).\n\n## Report\n\nOne cause — the first failing step — and one next action from\n[reference.md](reference.md). Do not guess at causes no check reported. If\neverything passes, ask what the user expected to find: the memory may never\nhave been written.\n","# loom-status — why is Loom quiet?\n\nEvery client-side failure is silent by design: the hooks fail open, a 401\nreads as \"no memories\", a viewer token makes every capture a 403 nobody\nsees. This skill diagnoses. It writes nothing to Loom and changes nothing\non the machine unless the user agrees to the one fix it names.\n\n`\u003Croot>` below is the installed plugin: `$CLAUDE_PLUGIN_ROOT` in Claude\nCode; in Codex, the newest `~\u002F.codex\u002Fplugins\u002Fcache\u002Floom\u002Floom\u002F*\u002F` directory.\n\n## Check in this order; the first failure is the cause\n\n1. **Local runtime.** `sh \"\u003Croot>\u002Fskills\u002Floom-status\u002Fscripts\u002Fensure-node.sh\" --check`\n   prints the Node 18+ the hooks run under (Claude Code: the `node` on PATH;\n   Codex: the launcher's pick), or one line saying none was found or the one\n   found is too old. A second line names a launch that finds none, with its\n   fix: relay it. On a failure, tell the user the hooks cannot run and offer\n   the fix: for Claude Code, set `PATH` in the `env` block of its settings to\n   the whole search path with Node 18+'s directory first (that `PATH`\n   replaces every session's); under Codex `LOOM_NODE=\u002Fpath\u002Fto\u002Fnode` reaches\n   the hooks, and the MCP header helper needs that Node on PATH. Else the same\n   script without `--check` installs Node (root or passwordless sudo, then\n   apt\u002Fdnf\u002Fyum, apk or Homebrew). Run it only when the user says yes; if it\n   exits 2, report its blocker line, do not retry. After an install the user\n   restarts the session: SessionStart hooks cannot rerun in this one.\n   An MCP-only client has no hooks and skips this step.\n2. **Server, token, auth, grant.** `sh \"\u003Croot>\u002Fbin\u002Floom-node\" \"\u003Croot>\u002Fbin\u002Floom-client-status.mjs\"`\n   prints JSON whose `checks` come in this order: `server`, `server version`\n   (only when the server is older), `token`, `source`, `auth`, `namespace`,\n   `flush` (`ok` is false when `server`, `token`, `auth` or `namespace` fails).\n   `source` names the lookup that supplied the token.\n   In Claude Code the server checked is the one the MCP entry calls: the\n   plugin's install URL when a session saved it, else `LOOM_BASE_URL`, else\n   localhost. In Codex, whose entry lives in its own config, it is the\n   hooks' server and `source` only names the lookup.\n   It ships with the plugin: do not look for a Loom checkout or install the\n   Python CLI. It sends no test write; a listed grant is evidence of\n   permission, not proof a write landed. If `loom` is already\n   on PATH, `loom doctor --client --json` adds deeper checks.\n3. **Plugin registration.** `claude plugin list` (or `codex plugin list`)\n   shows the `loom` plugin enabled; `\u002Fmcp` in the session (or `codex mcp list`)\n   shows the `loom` server connected. A missing entry is the cause even when\n   every check above passed.\n4. **Stranded captures.** The client check's `flush` line (WARN only).\n\n## Report\n\nOne cause — the first failing step — and one next action from\n[reference.md](reference.md). Do not guess at causes no check reported. If\neverything passes, ask what the user expected to find: the memory may never\nhave been written.\n",{"name":5,"description":24,"disable-model-invocation":25},"Use when Loom seems quiet or wrong: a loom tool answers \"unauthenticated\", \"not available\" or an empty result for something the user says was saved; the session-start primer did not appear; the user asks \"is loom working\", \"why didn't it remember\", \"is my token ok\", or a Loom hook says `Executable not found in $PATH: \"node\"` or `node: not found`, or prints a `loom:` line about Node.js 18+. Checks the Node hook runtime, then runs the plugin's client check and reads its lines, so the answer names the cause (missing runtime, unreachable server, rejected or expired token, no writer grant on the write namespace, plugin or MCP entry missing, stranded captures) and the one fix. NOT for server-side operations (that is `loom doctor` on the server) and NOT for deciding what to remember (loom-memory).\n",true,"main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002FClickHouse\u002Floom\u002Fskills\u002Floom-status",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":37,"prompt":47,"zipAvailable":25},[38,41,44],{"tool":39,"command":40},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill loom-status",{"tool":42,"command":43},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill loom-status",{"tool":45,"command":46},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill loom-status","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FClickHouse\u002Floom\u002Fskills\u002Floom-status\u002FSKILL.md",[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"reference.md","REFERENCE","参考文档",3965,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FClickHouse\u002Floom\u002Fskills\u002Floom-status\u002Freference.md",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"scripts\u002Fensure-node.sh","SCRIPT","脚本",7202,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FClickHouse\u002Floom\u002Fskills\u002Floom-status\u002Fscripts\u002Fensure-node.sh",[62,71,79,87,95,103],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"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",[],[],{"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":66,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"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",[],[]]