[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78NRG9FD5CAYP9HAZV26VR5":3,"skill-same:01M78NRG9FD5CAYP9HAZV26VR5":55},{"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},"01M78NRG9FD5CAYP9HAZV26VR5","loom-code",null,"Use the moment you are about to grep, glob, or open files to answer a question about a loom-indexed codebase — \"where is X\", \"how does X work\", \"who calls Y\", \"is it safe to change Z\", \"what does this stack trace touch\". The tell is linguistic: if you just thought \"let me search the codebase\", \"let me grep for that\", or \"let me read a few files\", that sentence is the trigger — code.grep covers exact literals too. NOT for repos loom hasn't indexed (a code.search that abstains on everything is the tell), and NOT for your own uncommitted files (grep those; pass your diff to code.impact for blast radius).","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-code\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: loom-code\ndescription: >\n  Use the moment you are about to grep, glob, or open files to answer a\n  question about a loom-indexed codebase — \"where is X\", \"how does X work\",\n  \"who calls Y\", \"is it safe to change Z\", \"what does this stack trace\n  touch\". The tell is linguistic: if you just thought \"let me search the\n  codebase\", \"let me grep for that\", or \"let me read a few files\", that\n  sentence is the trigger — code.grep covers exact literals too. NOT for\n  repos loom hasn't indexed (a code.search that abstains on everything is\n  the tell), and NOT for your own uncommitted files (grep those; pass your\n  diff to code.impact for blast radius).\ndisable-model-invocation: true\n---\n\n# loom-code — the indexed answer before the grep reflex\n\nLoom holds a compiler-grade index of this codebase (symbols, call graph,\ntests, PR history), served as MCP tools. One call replaces a grep plus\nseveral whole-file reads and returns what grep cannot see: resolved callers,\nblast radius, the tests that reach a function. The `loom-code-shunt` hook\nenforces the substitutions mechanically (a symbol grep or a bulk read in an\nindexed repo is denied with the answer or the tool to call).\n\n## The tools (MCP names)\n\n| Question | Call |\n|---|---|\n| where is X defined \u002F its signature and doc | `loom_code_symbol` (`name`) |\n| who calls X | `loom_code_callers`, or `loom_code_symbol` with `uses_brief: true` |\n| a concept with no greppable keyword (\"where do we retry s3 uploads\") | `loom_code_search` |\n| an exact literal or error string | `loom_code_grep` (each hit with its enclosing symbol) |\n| what is in a file | `loom_code_outline` (`path`) — then read one span |\n| the function around a `path:line` | `loom_code_symbol` with `name=\"src\u002FF.cpp:123\"`, or `loom_code_enclosing` |\n| how does X work, in prose, with citations | `loom_code_ask` |\n| a bundle for a task (symbols, callers, tests, history) | `loom_code_context_pack` |\n\nPass `namespace` when the session primer names it. The MCP code tools infer\n`org` from the token. For your own UNCOMMITTED files, grep. In a repository\nthe index does not cover, grep —\nthe abstentions will tell you.\n\n## Reading a result\n\n- `abstain: true` is an answer (\"nothing relevant\"); do not retry with\n  synonyms more than once — grep instead.\n- `as_of` names the indexed commit. Line numbers are that commit's; when the\n  session primer says your checkout is behind, report them as the index's.\n- Caller and impact counts are floors: dynamic dispatch is invisible to any\n  static tier. A structural claim (\"nothing calls X\") needs `loom_code_callers`\n  evidence, not a hunch.\n\n## Stop rules\n\n- One clear hit plus one focused read of the returned span is enough; do not\n  chain callers + impact + history as a ritual.\n- If two loom calls in a row did not move you forward, grep.\n\nThe full substitution table (impact, test_gate, pr_check, trace, verify,\noutline, grep neighbours) and the verification gate are in `reference.md`\nbeside this file; open it only when one of those rows is what you need.\n","# loom-code — the indexed answer before the grep reflex\n\nLoom holds a compiler-grade index of this codebase (symbols, call graph,\ntests, PR history), served as MCP tools. One call replaces a grep plus\nseveral whole-file reads and returns what grep cannot see: resolved callers,\nblast radius, the tests that reach a function. The `loom-code-shunt` hook\nenforces the substitutions mechanically (a symbol grep or a bulk read in an\nindexed repo is denied with the answer or the tool to call).\n\n## The tools (MCP names)\n\n| Question | Call |\n|---|---|\n| where is X defined \u002F its signature and doc | `loom_code_symbol` (`name`) |\n| who calls X | `loom_code_callers`, or `loom_code_symbol` with `uses_brief: true` |\n| a concept with no greppable keyword (\"where do we retry s3 uploads\") | `loom_code_search` |\n| an exact literal or error string | `loom_code_grep` (each hit with its enclosing symbol) |\n| what is in a file | `loom_code_outline` (`path`) — then read one span |\n| the function around a `path:line` | `loom_code_symbol` with `name=\"src\u002FF.cpp:123\"`, or `loom_code_enclosing` |\n| how does X work, in prose, with citations | `loom_code_ask` |\n| a bundle for a task (symbols, callers, tests, history) | `loom_code_context_pack` |\n\nPass `namespace` when the session primer names it. The MCP code tools infer\n`org` from the token. For your own UNCOMMITTED files, grep. In a repository\nthe index does not cover, grep —\nthe abstentions will tell you.\n\n## Reading a result\n\n- `abstain: true` is an answer (\"nothing relevant\"); do not retry with\n  synonyms more than once — grep instead.\n- `as_of` names the indexed commit. Line numbers are that commit's; when the\n  session primer says your checkout is behind, report them as the index's.\n- Caller and impact counts are floors: dynamic dispatch is invisible to any\n  static tier. A structural claim (\"nothing calls X\") needs `loom_code_callers`\n  evidence, not a hunch.\n\n## Stop rules\n\n- One clear hit plus one focused read of the returned span is enough; do not\n  chain callers + impact + history as a ritual.\n- If two loom calls in a row did not move you forward, grep.\n\nThe full substitution table (impact, test_gate, pr_check, trace, verify,\noutline, grep neighbours) and the verification gate are in `reference.md`\nbeside this file; open it only when one of those rows is what you need.\n",{"name":5,"description":24,"disable-model-invocation":25},"Use the moment you are about to grep, glob, or open files to answer a question about a loom-indexed codebase — \"where is X\", \"how does X work\", \"who calls Y\", \"is it safe to change Z\", \"what does this stack trace touch\". The tell is linguistic: if you just thought \"let me search the codebase\", \"let me grep for that\", or \"let me read a few files\", that sentence is the trigger — code.grep covers exact literals too. NOT for repos loom hasn't indexed (a code.search that abstains on everything is the tell), and NOT for your own uncommitted files (grep those; pass your diff to code.impact for blast radius).\n",true,"main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002FClickHouse\u002Floom\u002Fskills\u002Floom-code",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-code",{"tool":42,"command":43},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill loom-code",{"tool":45,"command":46},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill loom-code","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FClickHouse\u002Floom\u002Fskills\u002Floom-code\u002FSKILL.md",[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"reference.md","REFERENCE","参考文档",7188,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FClickHouse\u002Floom\u002Fskills\u002Floom-code\u002Freference.md",[56,65,73,81,89,97],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":61,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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",[],[]]