[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78NRZWK56E18VTPCFM6DF5V":3,"skill-same:01M78NRZWK56E18VTPCFM6DF5V":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},"01M78NRZWK56E18VTPCFM6DF5V","loom-mentor",null,"Use when a loom hint (a tool result's `hint`, an `X-Loom-Hint` header or a \"Loom mentor\" line) names a plane or op you do not know how to use, or when the user asks \"what can loom do\", \"how should I be using loom\", \"am I using loom well\", \"loom mentor\". A hint that already names the op to call needs no skill: call it or carry on with the task. Maps a situation to the loom plane and op that fits — code index, tracker record, documents, records, working memory, offload, the entity graph, runs, decisions, procedures, duplicates, conflicts, bisect — and says what to do about each hint code. NOT for deciding the shape of one write (loom-memory), NOT for grep-vs-code.* in an indexed repo (loom-code), NOT for reworking a namespace that already holds the wrong shape (loom-optimize).","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-mentor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: loom-mentor\ndescription: >\n  Use when a loom hint (a tool result's `hint`, an `X-Loom-Hint` header or\n  a \"Loom mentor\" line) names a plane or op you do not know how to use, or\n  when the user asks \"what can loom do\", \"how should I be using loom\", \"am I\n  using loom well\", \"loom mentor\". A hint that already names the op to call\n  needs no skill: call it or carry on with the task. Maps a situation to the\n  loom plane and op that fits — code index, tracker record, documents,\n  records, working memory, offload, the entity graph, runs, decisions,\n  procedures, duplicates, conflicts, bisect — and says what to do about each\n  hint code. NOT for deciding the shape of one write (loom-memory), NOT for\n  grep-vs-code.* in an indexed repo (loom-code), NOT for reworking a\n  namespace that already holds the wrong shape (loom-optimize).\ndisable-model-invocation: true\n---\n\n# loom-mentor — the store's advice, and where each plane lives\n\nLoom has a few hundred operations; your tool list shows the ones a coding\nsession uses most. The mentor reads what your agent called this week and\nnames the plane it is not using: a `hint` on a tool result, a `Loom mentor`\nline in the session primer. Read a hint once, act on it once; the same code\nis not shown again this session.\n\nThis skill routes. The destination skill owns the detail: the shape of a\nwrite is `loom-memory`, code questions are `loom-code`, reworking stored\nrows is `loom-optimize`.\n\n## Calling an op your tool list does not show\n\nA listed op is the tool `loom_\u003Cop with dots as underscores>`\n(`tracker.similar` → `loom_tracker_similar`). An op that is not in your\ntool list runs through `loom_op {op: \"tracker.similar\", arguments: {…}}`;\n`loom_op {op: \"help\", query: \"\u003Cwords>\"}` lists matching ops and their\narguments. Your host can only call tools it was shown, so never call an\nunlisted `loom_*` name directly. The tracker tools are listed when the MCP\nentry mounts `\u002Fmcp?toolset=coding+tracker` (the plugin's `toolset` option),\nor a second entry mounts `\u002Fmcp?toolset=tracker`.\n\n## The planes a hint points at\n\n| Situation | Op |\n|---|---|\n| \"has this crash \u002F test failure \u002F report been seen before\" | `loom_tracker_duplicate_check` (listed: draft title + body → `duplicate_of` \u002F `related` \u002F `none`); `loom_tracker_similar`, `tracker.flaky`, `tracker.test_signal` (listed on `coding+tracker`, else through `loom_op`) |\n| which PR broke a behaviour between two versions | `loom_code_bisect_candidates` (symbols or paths, `good_version`, `bad_version`) |\n| about to open a PR | `loom_code_pr_check` (title, body, paths, symbols, issues) |\n| is it safe to change X | `loom_code_impact` |\n| a document, runbook or report over ~2 KB | `knowledge.upsert` + one pointer row (`loom-memory`) |\n| a table of facts with identity (PRs, alerts, services) | `memory_schema.register` once, then `memory.record.write` |\n| your plan, a lease, \"where was I\" | `loom_working_memory_set` |\n| a 3,000-line log or diff to park | `context.offload`, then `context.fetch` |\n\nTracker ops take the tracker namespace, or the repository's code namespace\nwhen it is bound to one (`tracker.binding` says which).\n\n## The hints you will see most\n\n| code | do |\n|---|---|\n| `tracker_unused` | run the tracker check above before filing or grepping |\n| `code_index_unused` | `loom_code_symbol` \u002F `loom_code_search` for identifier questions |\n| `bisect_available` | `loom_code_bisect_candidates` first, blame second |\n| `get_miss` | `loom_search` by meaning; `memory.list prefix=`; `follow: true` |\n| `set_duplicate` \u002F `duplicates_written` | revise the named row, never a third copy |\n| `documents_as_memories` \u002F `set_large_value` | a knowledge document plus a pointer row |\n\nEvery other code, the full situation table and `mentor.brief` (the counts\nbehind a hint) are in `reference.md` beside this file. A code that is in\nneither table is newer than this skill: follow the hint's own sentence and\nthe ops it names, or ask `mentor.brief` for its evidence.\n","# loom-mentor — the store's advice, and where each plane lives\n\nLoom has a few hundred operations; your tool list shows the ones a coding\nsession uses most. The mentor reads what your agent called this week and\nnames the plane it is not using: a `hint` on a tool result, a `Loom mentor`\nline in the session primer. Read a hint once, act on it once; the same code\nis not shown again this session.\n\nThis skill routes. The destination skill owns the detail: the shape of a\nwrite is `loom-memory`, code questions are `loom-code`, reworking stored\nrows is `loom-optimize`.\n\n## Calling an op your tool list does not show\n\nA listed op is the tool `loom_\u003Cop with dots as underscores>`\n(`tracker.similar` → `loom_tracker_similar`). An op that is not in your\ntool list runs through `loom_op {op: \"tracker.similar\", arguments: {…}}`;\n`loom_op {op: \"help\", query: \"\u003Cwords>\"}` lists matching ops and their\narguments. Your host can only call tools it was shown, so never call an\nunlisted `loom_*` name directly. The tracker tools are listed when the MCP\nentry mounts `\u002Fmcp?toolset=coding+tracker` (the plugin's `toolset` option),\nor a second entry mounts `\u002Fmcp?toolset=tracker`.\n\n## The planes a hint points at\n\n| Situation | Op |\n|---|---|\n| \"has this crash \u002F test failure \u002F report been seen before\" | `loom_tracker_duplicate_check` (listed: draft title + body → `duplicate_of` \u002F `related` \u002F `none`); `loom_tracker_similar`, `tracker.flaky`, `tracker.test_signal` (listed on `coding+tracker`, else through `loom_op`) |\n| which PR broke a behaviour between two versions | `loom_code_bisect_candidates` (symbols or paths, `good_version`, `bad_version`) |\n| about to open a PR | `loom_code_pr_check` (title, body, paths, symbols, issues) |\n| is it safe to change X | `loom_code_impact` |\n| a document, runbook or report over ~2 KB | `knowledge.upsert` + one pointer row (`loom-memory`) |\n| a table of facts with identity (PRs, alerts, services) | `memory_schema.register` once, then `memory.record.write` |\n| your plan, a lease, \"where was I\" | `loom_working_memory_set` |\n| a 3,000-line log or diff to park | `context.offload`, then `context.fetch` |\n\nTracker ops take the tracker namespace, or the repository's code namespace\nwhen it is bound to one (`tracker.binding` says which).\n\n## The hints you will see most\n\n| code | do |\n|---|---|\n| `tracker_unused` | run the tracker check above before filing or grepping |\n| `code_index_unused` | `loom_code_symbol` \u002F `loom_code_search` for identifier questions |\n| `bisect_available` | `loom_code_bisect_candidates` first, blame second |\n| `get_miss` | `loom_search` by meaning; `memory.list prefix=`; `follow: true` |\n| `set_duplicate` \u002F `duplicates_written` | revise the named row, never a third copy |\n| `documents_as_memories` \u002F `set_large_value` | a knowledge document plus a pointer row |\n\nEvery other code, the full situation table and `mentor.brief` (the counts\nbehind a hint) are in `reference.md` beside this file. A code that is in\nneither table is newer than this skill: follow the hint's own sentence and\nthe ops it names, or ask `mentor.brief` for its evidence.\n",{"name":5,"description":24,"disable-model-invocation":25},"Use when a loom hint (a tool result's `hint`, an `X-Loom-Hint` header or a \"Loom mentor\" line) names a plane or op you do not know how to use, or when the user asks \"what can loom do\", \"how should I be using loom\", \"am I using loom well\", \"loom mentor\". A hint that already names the op to call needs no skill: call it or carry on with the task. Maps a situation to the loom plane and op that fits — code index, tracker record, documents, records, working memory, offload, the entity graph, runs, decisions, procedures, duplicates, conflicts, bisect — and says what to do about each hint code. NOT for deciding the shape of one write (loom-memory), NOT for grep-vs-code.* in an indexed repo (loom-code), NOT for reworking a namespace that already holds the wrong shape (loom-optimize).\n",true,"main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002FClickHouse\u002Floom\u002Fskills\u002Floom-mentor",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-mentor",{"tool":42,"command":43},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill loom-mentor",{"tool":45,"command":46},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill loom-mentor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FClickHouse\u002Floom\u002Fskills\u002Floom-mentor\u002FSKILL.md",[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"reference.md","REFERENCE","参考文档",12436,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FClickHouse\u002Floom\u002Fskills\u002Floom-mentor\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",[],[]]