[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEYP46B6K9WV664KDWZEDH":3,"skill-same:01M6MEYP46B6K9WV664KDWZEDH":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},"01M6MEYP46B6K9WV664KDWZEDH","install-memory",null,"Use when the owner asks to add vidbyte-memory to a repo, or to repair a partial install. Runs the installer, which copies the memory protocol into the repo without overwriting anything and wires the Stop hook for each coding agent it finds, then fills the Task section with the owner and runs the tests.","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\u002Fcerredz\u002Fvidbyte-memory\u002Fskills\u002Finstall-memory\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"memory","install memory","install","when","coding agent","section","for","which","hook","with","it","add","tests","repair","task","stop","installer","use","repo","coding","protocol","2026-11-10 10:12:30",false,"---\nname: install-memory\ndescription: Use when the owner asks to add vidbyte-memory to a repo, or to repair a partial install. Runs the installer, which copies the memory protocol into the repo without overwriting anything and wires the Stop hook for each coding agent it finds, then fills the Task section with the owner and runs the tests.\n---\n\n# Install memory\n\n## Goal\n\nA repo the owner already works in gains the whole memory protocol in one step, with nothing of theirs overwritten. From the next request on, the agent starts by reading memory, every correction becomes a fact and a test, and the guard enforces the guarantees in every coding agent the owner uses on that repo. The install is visible and reversible: every file it touched is listed, and every file it changed has a backup.\n\n## Objective\n\nRun the installer on the target repo, show the owner the plan before writing, apply it, and leave the repo with a filled Task section, a passing test suite and a commit that records the install. Report what was written, which agents were wired, which existing files were kept, and any step the owner must take by hand.\n\n## Tasks\n\n1. Find the installer. When this skill was loaded from the vidbyte-memory plugin or a clone, it is `scripts\u002Finstall.py` two folders above this file. Otherwise clone the release this skill shipped with into a temporary folder outside the repo, `git clone --depth 1 --branch v0.3.0 https:\u002F\u002Fgithub.com\u002Fcerredz\u002Fvidbyte-memory \u003Ctmp>`, and use `\u003Ctmp>\u002Fscripts\u002Finstall.py`, so the owner can read the script before it runs and the install is the reviewed release, not whatever `main` holds today. Run it as `python \u003Cinstaller> --target \u003Crepo>` from then on.\n2. Run it with `--dry-run --target \u003Crepo>` and show the owner the plan: the files it would create, the agents it detected and why, and any existing files it would keep.\n3. If the plan lists a conflict on a file the memory needs (its tests helpers, its integrity test, the guard or the footprint script), stop and ask the owner how to resolve it before going on.\n4. Run it again without `--dry-run`.\n5. Ask the owner for the recurring task this repo serves, then replace the paragraph in the `## Task` section of `AGENTS.md` with it: what is produced, for whom, from what inputs, and where it goes. If the installer moved the old instructions to `AGENTS.previous.md`, keep that file and the pointer to it.\n6. Run `python -m pytest -q tests`. Fix what the install caused; report anything that was already failing in the owner's own tests.\n7. Commit with `python scripts\u002Ffootprint.py --commit --title \"install vidbyte-memory\"`.\n\n## Instructions\n\n- **Never overwrite the owner's files.** The installer keeps every existing file and lists the ones that differ from the template; leave them as they are unless the owner says otherwise. A backup named `\u003Cfile>.vidbyte-memory-backup` sits next to every file it edited, such as `.claude\u002Fsettings.json` or `CLAUDE.md`.\n- **Wire only the agents the owner uses.** Detection looks at the repo, the home folder and PATH. When the owner names their agents, pass them with `--agents`, so the repo does not collect hook files for tools nobody runs.\n- **Tell the owner about steps an agent cannot take.** Codex skips project hooks until the owner trusts them with `\u002Fhooks`; Grok Build needs `\u002Fhooks-trust`; Hermes loads project skills after `hermes skills trust`. The installer prints these as notes; repeat them in the report.\n- **The guard is the enforcement.** After the install, `scripts\u002Fguard.py` blocks the end of a turn while tests fail, feedback is pending or memory is uncommitted, in every agent whose hook was wired. In other agents the checklist in `AGENTS.md` is the same contract, kept by hand.\n\n## Checklist\n\n- [ ] **The owner saw the dry-run plan before anything was written.** The report quotes the number of files and the agents wired.\n- [ ] **No existing file was overwritten.** Every kept file is listed, and every edited file has a backup.\n- [ ] **The `## Task` section of `AGENTS.md` describes the owner's recurring task.** The template's placeholder paragraph is gone.\n- [ ] **`python -m pytest -q tests` passes, or the report names each failure and whether the install caused it.**\n- [ ] **The install is committed**, and `.vidbyte-memory\u002Finstall.json` lists what was written.\n\n## Output\n\nA short report: the repo, the files written (count and the notable ones), the agents wired and why each was detected, the files kept because they already existed, the hand steps left for the owner (hook trust, conflicts), the test result, and the commit.\n\n## Runtime behavior\n\n- Loaded only when the owner asks to add memory to a repo or to repair an install; it is not part of the per-request protocol.\n- The installer is idempotent: running it again creates only what is missing, so it also repairs a partial install.\n- When the owner asks to remove the memory, run `python scripts\u002Finstall.py uninstall --dry-run`, show the plan, then run it without `--dry-run`. It deletes what the install created, restores edited files from their backups, takes the guard hook out of agent settings the owner edited since, and keeps memory the agent wrote unless the owner asks for `--force`.\n- Uses `scripts\u002Finstall.py`, which needs Python 3.9 or later and nothing outside the standard library.\n","# Install memory\n\n## Goal\n\nA repo the owner already works in gains the whole memory protocol in one step, with nothing of theirs overwritten. From the next request on, the agent starts by reading memory, every correction becomes a fact and a test, and the guard enforces the guarantees in every coding agent the owner uses on that repo. The install is visible and reversible: every file it touched is listed, and every file it changed has a backup.\n\n## Objective\n\nRun the installer on the target repo, show the owner the plan before writing, apply it, and leave the repo with a filled Task section, a passing test suite and a commit that records the install. Report what was written, which agents were wired, which existing files were kept, and any step the owner must take by hand.\n\n## Tasks\n\n1. Find the installer. When this skill was loaded from the vidbyte-memory plugin or a clone, it is `scripts\u002Finstall.py` two folders above this file. Otherwise clone the release this skill shipped with into a temporary folder outside the repo, `git clone --depth 1 --branch v0.3.0 https:\u002F\u002Fgithub.com\u002Fcerredz\u002Fvidbyte-memory \u003Ctmp>`, and use `\u003Ctmp>\u002Fscripts\u002Finstall.py`, so the owner can read the script before it runs and the install is the reviewed release, not whatever `main` holds today. Run it as `python \u003Cinstaller> --target \u003Crepo>` from then on.\n2. Run it with `--dry-run --target \u003Crepo>` and show the owner the plan: the files it would create, the agents it detected and why, and any existing files it would keep.\n3. If the plan lists a conflict on a file the memory needs (its tests helpers, its integrity test, the guard or the footprint script), stop and ask the owner how to resolve it before going on.\n4. Run it again without `--dry-run`.\n5. Ask the owner for the recurring task this repo serves, then replace the paragraph in the `## Task` section of `AGENTS.md` with it: what is produced, for whom, from what inputs, and where it goes. If the installer moved the old instructions to `AGENTS.previous.md`, keep that file and the pointer to it.\n6. Run `python -m pytest -q tests`. Fix what the install caused; report anything that was already failing in the owner's own tests.\n7. Commit with `python scripts\u002Ffootprint.py --commit --title \"install vidbyte-memory\"`.\n\n## Instructions\n\n- **Never overwrite the owner's files.** The installer keeps every existing file and lists the ones that differ from the template; leave them as they are unless the owner says otherwise. A backup named `\u003Cfile>.vidbyte-memory-backup` sits next to every file it edited, such as `.claude\u002Fsettings.json` or `CLAUDE.md`.\n- **Wire only the agents the owner uses.** Detection looks at the repo, the home folder and PATH. When the owner names their agents, pass them with `--agents`, so the repo does not collect hook files for tools nobody runs.\n- **Tell the owner about steps an agent cannot take.** Codex skips project hooks until the owner trusts them with `\u002Fhooks`; Grok Build needs `\u002Fhooks-trust`; Hermes loads project skills after `hermes skills trust`. The installer prints these as notes; repeat them in the report.\n- **The guard is the enforcement.** After the install, `scripts\u002Fguard.py` blocks the end of a turn while tests fail, feedback is pending or memory is uncommitted, in every agent whose hook was wired. In other agents the checklist in `AGENTS.md` is the same contract, kept by hand.\n\n## Checklist\n\n- [ ] **The owner saw the dry-run plan before anything was written.** The report quotes the number of files and the agents wired.\n- [ ] **No existing file was overwritten.** Every kept file is listed, and every edited file has a backup.\n- [ ] **The `## Task` section of `AGENTS.md` describes the owner's recurring task.** The template's placeholder paragraph is gone.\n- [ ] **`python -m pytest -q tests` passes, or the report names each failure and whether the install caused it.**\n- [ ] **The install is committed**, and `.vidbyte-memory\u002Finstall.json` lists what was written.\n\n## Output\n\nA short report: the repo, the files written (count and the notable ones), the agents wired and why each was detected, the files kept because they already existed, the hand steps left for the owner (hook trust, conflicts), the test result, and the commit.\n\n## Runtime behavior\n\n- Loaded only when the owner asks to add memory to a repo or to repair an install; it is not part of the per-request protocol.\n- The installer is idempotent: running it again creates only what is missing, so it also repairs a partial install.\n- When the owner asks to remove the memory, run `python scripts\u002Finstall.py uninstall --dry-run`, show the plan, then run it without `--dry-run`. It deletes what the install created, restores edited files from their backups, takes the guard hook out of agent settings the owner edited since, and keeps memory the agent wrote unless the owner asks for `--force`.\n- Uses `scripts\u002Finstall.py`, which needs Python 3.9 or later and nothing outside the standard library.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fcerredz\u002Fvidbyte-memory\u002Fskills\u002Finstall-memory",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 install-memory",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill install-memory",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill install-memory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcerredz\u002Fvidbyte-memory\u002Fskills\u002Finstall-memory\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",[],[]]