[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJ6WCKFJ5521VZPZ9G3KP7":3,"skill-same:01M6MJ6WCKFJ5521VZPZ9G3KP7":78},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":43,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6MJ6WCKFJ5521VZPZ9G3KP7","memory-clean",null,"Use when the user explicitly asks to clean, compact, prune, trim, deduplicate, optimize, or reduce Wingman memory, or asks to resolve stale or conflicting memory rules.","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\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-clean\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"memory","clean","memory clean","deduplicate","prune","Rules","user","use","stale","optimize","compact","reduce","trim","when","2026-11-10 10:12:30",false,"---\nname: memory-clean\ndescription: \"Use when the user explicitly asks to clean, compact, prune, trim, deduplicate, optimize, or reduce Wingman memory, or asks to resolve stale or conflicting memory rules.\"\n---\n\n# Wingman Memory Clean\n\nClean Wingman memory only when the user explicitly asks. Preserve the ownership model while reducing default-read noise and conflicts.\n\n## Ownership Model\n\n```text\nbrief.md \u002F domains\u002F = current projection, current binding truth bodies\nhistory\u002Fevents\u002F     = event log, historical event bodies\nhistory indexes     = projection indexes for historical lookup\ncontext.md          = hot cache, active work state and short pointers\n```\n\nCleanups should move memory toward one owning body per durable item:\n\n- current rule body lives in `brief.md` or `domains\u002F`;\n- historical event body lives in `history\u002Fevents\u002F`;\n- historical lookup entry lives in projection indexes;\n- hot state or short pointer lives in `context.md`.\n\n## Repository Gate\n\n1. Check `.wingman\u002Fmemory\u002F`.\n2. Check `.wingman\u002Fmemory\u002Fbrief.md` and `.wingman\u002Fmemory\u002Fcontext.md`.\n3. If core files are missing, stop and report repository memory state.\n4. Read `brief.md` and `context.md` first.\n5. Read domain or history files only when the requested cleanup scope points to them.\n\nNever scan all memory files by default.\n\n## Scope Selection\n\nUse the smallest scope that matches the request:\n\n| Scope | Read | Use When |\n| --- | --- | --- |\n| `context` | `context.md`, relevant current truth\u002Fhistory if linked | Context contains stale hot state, verbose old logs, or duplicate bodies. |\n| `current-truth` | `brief.md`, relevant domains | Current rules are duplicated, stale, conflicting, missing identity, or missing relations. |\n| `history-index` | relevant projections | History projections are bloated, missing useful routing, or copying event bodies. |\n| `history-event` | named event bodies only | User explicitly asks to inspect or edit specific history events. |\n| `migration` | target old context logs plus needed destinations | Old context logs need conversion into current truth, history, or pointers. |\n| `delete-proposal` | target files only | User asks to delete logs or remove noise. |\n\nIf unclear, choose `context` unless the user mentions current rules, domains, Project Decisions, or history.\n\n## Candidate Types\n\nClean only when at least one concrete candidate exists:\n\n- `COMPACT_TO_POINTER`: context has details already owned by current truth or history.\n- `PROMOTE_CURRENT_TRUTH`: context contains a durable rule future agents must obey.\n- `PROMOTE_HISTORY`: context contains a durable change narrative or reasoning event.\n- `PROMOTE_BOTH`: context contains both current rule and historical explanation.\n- `SUPERSEDE`: an old current rule was replaced and should become `superseded` or `deprecated`.\n- `REPAIR_RELATION`: same-subject entries need `updates`, `extends`, or conflict resolution.\n- `REPAIR_INDEX`: history projection should be link-only or needs a domain\u002Ftopic route.\n- `DELETE_CANDIDATE`: duplicate, obsolete, sensitive, or safely represented elsewhere.\n- `NO_ACTION`: cleanup cost or ambiguity exceeds benefit.\n\nFile size and line count are diagnostics only. They are not cleanup triggers by themselves.\n\n## Retention Review\n\nBefore changing a candidate, decide what would be lost:\n\n- Is it current truth, hot state, or history?\n- Is it still valid, replaced, or obsolete?\n- Is it the only evidence explaining a current rule?\n- Is a future task likely to need the rule, reason, failure mode, or pointer?\n- Can the same meaning be recovered from a current truth ID or history event link?\n\nIf uncertain, prefer `NO_ACTION` or a deletion proposal over irreversible cleanup.\n\n## Valid Actions\n\n### Compact Context\n\nReplace verbose context with a short pointer only after the durable meaning is preserved elsewhere.\n\nValid pointer shape:\n\n```md\n- \u003Cone-line state>; current truth: `\u003Cid\u002Fpath or None>`; event: `\u003Cpath or None>`; next: \u003Cimmediate action\u002Fblocker or None>.\n```\n\nPreserve pending tasks, active blockers, and unresolved current work.\n\n### Promote Current Truth\n\nWrite durable rules to `brief.md` or relevant `domains\u002F` when future agents must obey them. Include stable `ID`, `Subject`, `Status`, `Rule`, `Applies When`, `Evidence`, `Confidence`, `Relation`, `Since`, and `History`.\n\n### Promote History\n\nWrite historical events under `history\u002Fevents\u002FYYYY\u002FMM\u002F` when the old context contains durable rule evolution, old-to-new meaning, important correction, migration, incident, regression fix, or user-requested historical memory. Update only needed projections.\n\n### Repair Current Rules\n\nFor A -> B requirement changes, make B the only `current` rule for overlapping scope, mark A as `superseded` or `deprecated`, and link with `updates \u003Cold-id>`.\n\nIf both rules remain valid, link with `extends`. If they conflict and evidence does not settle the winner, stop and ask.\n\n### Repair History Projections\n\nProjection indexes should contain short summaries and links only. Remove copied event bodies from indexes only when the event body remains linked.\n\n### Delete\n\nNever delete without explicit user confirmation after showing a proposal with exact IDs, paths, reasons, preserved locations, and risks.\n\nDo not delete:\n\n- pending tasks;\n- current work;\n- unresolved bugs;\n- current Project Decisions;\n- current domain truths;\n- user-protected notes;\n- the only evidence explaining a current rule;\n- history event bodies, unless the user explicitly asked to delete those specific records.\n\n## Optional Resources\n\n- Run `scripts\u002Fmemory-stats.sh` when heading layout, file size, or candidate discovery is unclear. The script is read-only.\n- Read `examples\u002Flossless-compaction.md` when compaction safety is unclear.\n- Read `examples\u002Fdeletion-proposals.md` when preparing a deletion proposal.\n\nDo not read examples or run scripts by default.\n\n## Workflow\n\n1. Apply Repository Gate.\n2. Select the smallest cleanup scope.\n3. Identify concrete candidates.\n4. Run Retention Review.\n5. Classify candidates.\n6. Apply safe `COMPACT_TO_POINTER`, `PROMOTE_CURRENT_TRUTH`, `PROMOTE_HISTORY`, `PROMOTE_BOTH`, `SUPERSEDE`, `REPAIR_RELATION`, and `REPAIR_INDEX` changes.\n7. For `DELETE_CANDIDATE`, present a proposal and wait for explicit confirmation.\n8. Report files read, files changed, compactions, promotions, superseded rules, repaired indexes, and proposed or confirmed deletions.\n\nDo not say memory was cleaned if no file changed. If only a deletion proposal was produced, say cleanup is pending confirmation.\n","# Wingman Memory Clean\n\nClean Wingman memory only when the user explicitly asks. Preserve the ownership model while reducing default-read noise and conflicts.\n\n## Ownership Model\n\n```text\nbrief.md \u002F domains\u002F = current projection, current binding truth bodies\nhistory\u002Fevents\u002F     = event log, historical event bodies\nhistory indexes     = projection indexes for historical lookup\ncontext.md          = hot cache, active work state and short pointers\n```\n\nCleanups should move memory toward one owning body per durable item:\n\n- current rule body lives in `brief.md` or `domains\u002F`;\n- historical event body lives in `history\u002Fevents\u002F`;\n- historical lookup entry lives in projection indexes;\n- hot state or short pointer lives in `context.md`.\n\n## Repository Gate\n\n1. Check `.wingman\u002Fmemory\u002F`.\n2. Check `.wingman\u002Fmemory\u002Fbrief.md` and `.wingman\u002Fmemory\u002Fcontext.md`.\n3. If core files are missing, stop and report repository memory state.\n4. Read `brief.md` and `context.md` first.\n5. Read domain or history files only when the requested cleanup scope points to them.\n\nNever scan all memory files by default.\n\n## Scope Selection\n\nUse the smallest scope that matches the request:\n\n| Scope | Read | Use When |\n| --- | --- | --- |\n| `context` | `context.md`, relevant current truth\u002Fhistory if linked | Context contains stale hot state, verbose old logs, or duplicate bodies. |\n| `current-truth` | `brief.md`, relevant domains | Current rules are duplicated, stale, conflicting, missing identity, or missing relations. |\n| `history-index` | relevant projections | History projections are bloated, missing useful routing, or copying event bodies. |\n| `history-event` | named event bodies only | User explicitly asks to inspect or edit specific history events. |\n| `migration` | target old context logs plus needed destinations | Old context logs need conversion into current truth, history, or pointers. |\n| `delete-proposal` | target files only | User asks to delete logs or remove noise. |\n\nIf unclear, choose `context` unless the user mentions current rules, domains, Project Decisions, or history.\n\n## Candidate Types\n\nClean only when at least one concrete candidate exists:\n\n- `COMPACT_TO_POINTER`: context has details already owned by current truth or history.\n- `PROMOTE_CURRENT_TRUTH`: context contains a durable rule future agents must obey.\n- `PROMOTE_HISTORY`: context contains a durable change narrative or reasoning event.\n- `PROMOTE_BOTH`: context contains both current rule and historical explanation.\n- `SUPERSEDE`: an old current rule was replaced and should become `superseded` or `deprecated`.\n- `REPAIR_RELATION`: same-subject entries need `updates`, `extends`, or conflict resolution.\n- `REPAIR_INDEX`: history projection should be link-only or needs a domain\u002Ftopic route.\n- `DELETE_CANDIDATE`: duplicate, obsolete, sensitive, or safely represented elsewhere.\n- `NO_ACTION`: cleanup cost or ambiguity exceeds benefit.\n\nFile size and line count are diagnostics only. They are not cleanup triggers by themselves.\n\n## Retention Review\n\nBefore changing a candidate, decide what would be lost:\n\n- Is it current truth, hot state, or history?\n- Is it still valid, replaced, or obsolete?\n- Is it the only evidence explaining a current rule?\n- Is a future task likely to need the rule, reason, failure mode, or pointer?\n- Can the same meaning be recovered from a current truth ID or history event link?\n\nIf uncertain, prefer `NO_ACTION` or a deletion proposal over irreversible cleanup.\n\n## Valid Actions\n\n### Compact Context\n\nReplace verbose context with a short pointer only after the durable meaning is preserved elsewhere.\n\nValid pointer shape:\n\n```md\n- \u003Cone-line state>; current truth: `\u003Cid\u002Fpath or None>`; event: `\u003Cpath or None>`; next: \u003Cimmediate action\u002Fblocker or None>.\n```\n\nPreserve pending tasks, active blockers, and unresolved current work.\n\n### Promote Current Truth\n\nWrite durable rules to `brief.md` or relevant `domains\u002F` when future agents must obey them. Include stable `ID`, `Subject`, `Status`, `Rule`, `Applies When`, `Evidence`, `Confidence`, `Relation`, `Since`, and `History`.\n\n### Promote History\n\nWrite historical events under `history\u002Fevents\u002FYYYY\u002FMM\u002F` when the old context contains durable rule evolution, old-to-new meaning, important correction, migration, incident, regression fix, or user-requested historical memory. Update only needed projections.\n\n### Repair Current Rules\n\nFor A -> B requirement changes, make B the only `current` rule for overlapping scope, mark A as `superseded` or `deprecated`, and link with `updates \u003Cold-id>`.\n\nIf both rules remain valid, link with `extends`. If they conflict and evidence does not settle the winner, stop and ask.\n\n### Repair History Projections\n\nProjection indexes should contain short summaries and links only. Remove copied event bodies from indexes only when the event body remains linked.\n\n### Delete\n\nNever delete without explicit user confirmation after showing a proposal with exact IDs, paths, reasons, preserved locations, and risks.\n\nDo not delete:\n\n- pending tasks;\n- current work;\n- unresolved bugs;\n- current Project Decisions;\n- current domain truths;\n- user-protected notes;\n- the only evidence explaining a current rule;\n- history event bodies, unless the user explicitly asked to delete those specific records.\n\n## Optional Resources\n\n- Run `scripts\u002Fmemory-stats.sh` when heading layout, file size, or candidate discovery is unclear. The script is read-only.\n- Read `examples\u002Flossless-compaction.md` when compaction safety is unclear.\n- Read `examples\u002Fdeletion-proposals.md` when preparing a deletion proposal.\n\nDo not read examples or run scripts by default.\n\n## Workflow\n\n1. Apply Repository Gate.\n2. Select the smallest cleanup scope.\n3. Identify concrete candidates.\n4. Run Retention Review.\n5. Classify candidates.\n6. Apply safe `COMPACT_TO_POINTER`, `PROMOTE_CURRENT_TRUTH`, `PROMOTE_HISTORY`, `PROMOTE_BOTH`, `SUPERSEDE`, `REPAIR_RELATION`, and `REPAIR_INDEX` changes.\n7. For `DELETE_CANDIDATE`, present a proposal and wait for explicit confirmation.\n8. Report files read, files changed, compactions, promotions, superseded rules, repaired indexes, and proposed or confirmed deletions.\n\nDo not say memory was cleaned if no file changed. If only a deletion proposal was produced, say cleanup is pending confirmation.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-clean",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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill memory-clean",{"tool":54,"command":55},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill memory-clean",{"tool":57,"command":58},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill memory-clean","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-clean\u002FSKILL.md",true,[62,68,72],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"examples\u002Fdeletion-proposals.md","REFERENCE","参考文档",1566,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-clean\u002Fexamples\u002Fdeletion-proposals.md",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"examples\u002Flossless-compaction.md",3272,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-clean\u002Fexamples\u002Flossless-compaction.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fmemory-stats.sh","SCRIPT","脚本",2494,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-clean\u002Fscripts\u002Fmemory-stats.sh",[79,89,97,105,113,121],{"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":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":88},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":88},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":88},"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":88},"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":88},"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":88},"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",[],[]]