[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEMN9GSWY357XNBHAEW31S":3,"skill-same:01M6MEMN9GSWY357XNBHAEW31S":63},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6MEMN9GSWY357XNBHAEW31S","bindry-sync",null,"Compile a bound Bindry Binder into Codex skills for this project, so its Skills load on demand instead of sitting in every prompt. Use when the user asks to sync, install, or update Bindry Binder skills for this project.","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\u002Fbindryai\u002FPlugins\u002Fskills\u002Fbindry-sync\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"sync","bindry sync","codex","update","compile","prompt","user","install","use","project","binder","load","for","codex skills","when","2026-11-10 10:12:30",false,"---\nname: bindry-sync\ndescription: Compile a bound Bindry Binder into Codex skills for this project, so its Skills load on demand instead of sitting in every prompt. Use when the user asks to sync, install, or update Bindry Binder skills for this project.\n---\n\nCompile a Bindry Binder into Codex skills so its Skills load on demand instead of sitting in every prompt.\nInvoke explicitly with `$bindry-sync`, or let it trigger automatically when the user asks to sync\u002Fupdate Bindry\nskills.\n\n1. Determine the source from what the user actually said, in order:\n   - A Binder id (GUID) or a full export URL they gave you — sync live from the Bindry API.\n   - A file path they gave you — compile from that local export file.\n   - Neither given: check for `.\u002Fbindry.config.json` in the current project (written by a previous sync) and\n     reuse the Binder id it remembers.\n   - None of those apply — ask the user for a Binder id (from Bindry → Binder → Export → target \"codex\") or a\n     saved export file path, then stop.\n2. For a live sync, also need `--api-base \u003Curl>` (the Bindry API's base URL — ask the user if not obvious from\n   context) and, for a private Binder, `--token \u003Capi-key>` (generated from the workspace's team page in Bindry,\n   not Account settings). A published Library Binder (referenced by slug or GUID) needs no token at all — it\n   resolves through the public Library's anonymous export route. Only your own private Binders require one.\n3. Default is `--mode pinned` (a static snapshot). If the user wants this Binder to always stay current instead\n   — `--mode live` — first confirm the Bindry MCP server is connected (check the configured MCP servers for one\n   named `bindry`). If it isn't connected, tell the user to use the `bindry-connect` skill first and stop;\n   compiling live skills with no live connection would produce skills that always fail when used. `--mode live`\n   also only works from a live Binder id\u002FURL, not a local export file — its Skills need real GUID ids, which a\n   hand-written or example export file won't have.\n4. If the user wants a specific published version of a Library Binder rather than its latest — e.g. rules for\n   the framework release they are actually on — pass `--version \u003Cv>`. It is remembered in\n   `bindry.config.json`, so later syncs stay on that version until `--version latest` removes the pin. A\n   version pin only applies to a Library Binder (your own workspace Binder always compiles from its current\n   composition), and an unknown version fails with a message naming the versions that do exist rather than\n   quietly serving the latest.\n5. Locate this plugin's own installed root first (e.g. list installed Codex plugins and find the path for\n   `bindry@\u003Cmarketplace>`), then run:\n   `node \u003Cresolved-plugin-root>\u002Fscripts\u002Fcompile-binder.mjs [\u003Cbinder-id-or-file>] --out .agents\u002Fskills [--api-base \u003Curl>] [--token \u003Capi-key>] [--mode pinned|live] [--version \u003Cv>]`\n   If you can't locate `scripts\u002Fcompile-binder.mjs` under this plugin's installed root, stop and say so plainly\n   rather than guessing a path.\n6. Report exactly what the script printed: how many skills were written and where. If it failed with an\n   authentication error, tell the user plainly what it said — don't guess or retry silently. If it wrote a\n   `bindry.config.json`, mention that future syncs in this project can omit the Binder id (and remember the mode\n   too).\n7. Remind the user to re-run this whenever a **pinned** Binder changes in Bindry — each pinned skill is tagged\n   with a Skill version in an HTML comment, so the `bindry-check` skill can diff against it. A **live** skill\n   never goes stale — it calls the Bindry MCP server for current content every time it's used — so there's\n   nothing to re-sync for it, only re-run if the Binder's Skill *list* itself changed (added\u002Fremoved Skills).\n8. If any Skill carries a file attachment (e.g. an exact logo to place), the script downloads it into that\n   skill's `assets\u002F` folder alongside `SKILL.md` — in both pinned and live mode, since the live MCP tools don't\n   serve binary files. If the script printed a warning that it skipped an asset, mention that plainly too —\n   that skill still compiled, just without the file, and needs an `--api-base`\u002Fnetwork fix before it will\n   download.\n","Compile a Bindry Binder into Codex skills so its Skills load on demand instead of sitting in every prompt.\nInvoke explicitly with `$bindry-sync`, or let it trigger automatically when the user asks to sync\u002Fupdate Bindry\nskills.\n\n1. Determine the source from what the user actually said, in order:\n   - A Binder id (GUID) or a full export URL they gave you — sync live from the Bindry API.\n   - A file path they gave you — compile from that local export file.\n   - Neither given: check for `.\u002Fbindry.config.json` in the current project (written by a previous sync) and\n     reuse the Binder id it remembers.\n   - None of those apply — ask the user for a Binder id (from Bindry → Binder → Export → target \"codex\") or a\n     saved export file path, then stop.\n2. For a live sync, also need `--api-base \u003Curl>` (the Bindry API's base URL — ask the user if not obvious from\n   context) and, for a private Binder, `--token \u003Capi-key>` (generated from the workspace's team page in Bindry,\n   not Account settings). A published Library Binder (referenced by slug or GUID) needs no token at all — it\n   resolves through the public Library's anonymous export route. Only your own private Binders require one.\n3. Default is `--mode pinned` (a static snapshot). If the user wants this Binder to always stay current instead\n   — `--mode live` — first confirm the Bindry MCP server is connected (check the configured MCP servers for one\n   named `bindry`). If it isn't connected, tell the user to use the `bindry-connect` skill first and stop;\n   compiling live skills with no live connection would produce skills that always fail when used. `--mode live`\n   also only works from a live Binder id\u002FURL, not a local export file — its Skills need real GUID ids, which a\n   hand-written or example export file won't have.\n4. If the user wants a specific published version of a Library Binder rather than its latest — e.g. rules for\n   the framework release they are actually on — pass `--version \u003Cv>`. It is remembered in\n   `bindry.config.json`, so later syncs stay on that version until `--version latest` removes the pin. A\n   version pin only applies to a Library Binder (your own workspace Binder always compiles from its current\n   composition), and an unknown version fails with a message naming the versions that do exist rather than\n   quietly serving the latest.\n5. Locate this plugin's own installed root first (e.g. list installed Codex plugins and find the path for\n   `bindry@\u003Cmarketplace>`), then run:\n   `node \u003Cresolved-plugin-root>\u002Fscripts\u002Fcompile-binder.mjs [\u003Cbinder-id-or-file>] --out .agents\u002Fskills [--api-base \u003Curl>] [--token \u003Capi-key>] [--mode pinned|live] [--version \u003Cv>]`\n   If you can't locate `scripts\u002Fcompile-binder.mjs` under this plugin's installed root, stop and say so plainly\n   rather than guessing a path.\n6. Report exactly what the script printed: how many skills were written and where. If it failed with an\n   authentication error, tell the user plainly what it said — don't guess or retry silently. If it wrote a\n   `bindry.config.json`, mention that future syncs in this project can omit the Binder id (and remember the mode\n   too).\n7. Remind the user to re-run this whenever a **pinned** Binder changes in Bindry — each pinned skill is tagged\n   with a Skill version in an HTML comment, so the `bindry-check` skill can diff against it. A **live** skill\n   never goes stale — it calls the Bindry MCP server for current content every time it's used — so there's\n   nothing to re-sync for it, only re-run if the Binder's Skill *list* itself changed (added\u002Fremoved Skills).\n8. If any Skill carries a file attachment (e.g. an exact logo to place), the script downloads it into that\n   skill's `assets\u002F` folder alongside `SKILL.md` — in both pinned and live mode, since the live MCP tools don't\n   serve binary files. If the script printed a warning that it skipped an asset, mention that plainly too —\n   that skill still compiled, just without the file, and needs an `--api-base`\u002Fnetwork fix before it will\n   download.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fbindryai\u002FPlugins\u002Fskills\u002Fbindry-sync",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill bindry-sync",{"tool":55,"command":56},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill bindry-sync",{"tool":58,"command":59},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill bindry-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fbindryai\u002FPlugins\u002Fskills\u002Fbindry-sync\u002FSKILL.md",true,[],[64,74,82,90,98,106],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":73},"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":73},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":73},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":73},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":73},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":73},"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",[],[]]