[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJ703T25CQYF4CBM05VC2R":3,"skill-same:01M6MJ703T25CQYF4CBM05VC2R":67},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6MJ703T25CQYF4CBM05VC2R","memory-load",null,"Use when Wingman memory is already known enabled in the current repository and starting non-trivial coding, debugging, planning, review, API integration, or business-logic work, or when the user explicitly asks to load or read Wingman memory.","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-load\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"memory","memory load","load","when","review","logic","api integration","use","business","user","read","work","coding","business-logic","api","repository","integration","planning","debugging","2026-11-10 10:12:30",false,"---\nname: memory-load\ndescription: Use when Wingman memory is already known enabled in the current repository and starting non-trivial coding, debugging, planning, review, API integration, or business-logic work, or when the user explicitly asks to load or read Wingman memory.\n---\n\n# Wingman Memory Load\n\n`memory-load` is read-only. It loads current truth by default and history only when the task needs explanation or past-change context.\n\n## Memory State\n\nUse `.wingman\u002Fmemory\u002F` as the repository-local memory root.\n\nRepository memory is enabled only when both core entry files exist:\n\n```text\n.wingman\u002Fmemory\u002Fbrief.md\n.wingman\u002Fmemory\u002Fcontext.md\n```\n\nIf `.wingman\u002Fmemory\u002F` is missing, continue without memory unless the user explicitly asked about memory. If the directory exists but a core entry file is missing, report partial memory only when the user asked about memory or the task depends on memory consistency.\n\n## Authority\n\nUse this authority order when memory files disagree:\n\n```text\nbrief.md current Project Decisions\n> domains\u002F current truths\n> context.md hot working state\n> history\u002F past events and evidence\n```\n\nHistory explains why something changed. It is not current truth unless a current entry in `brief.md` or `domains\u002F` links to it as evidence.\n\nOnly `Status: current` current-truth entries are binding. `candidate`, `deprecated`, and `superseded` entries are background only.\n\nRelations:\n\n- `updates \u003Cid>` replaces the referenced entry for overlapping scope.\n- `extends \u003Cid>` keeps both entries valid when compatible.\n- `derived_from \u003Cid-or-path>` records evidence lineage, not authority.\n\nIf two current entries with the same `Subject` conflict and no relation resolves them, stop and ask which rule is valid.\n\n## When To Load\n\nSkip memory for trivial isolated work: typo-only edits, formatting, isolated style tweaks, throwaway experiments, or local changes with no business, state, data, contract, reuse, or existing-behavior impact.\n\nLoad memory before non-trivial coding, debugging, planning, review, refactor, API integration, reusable implementation work, or changes touching business logic, state flow, permissions, quotas, billing, field mappings, contracts, or existing behavior.\n\nAlso load memory when the user mentions previous work, consistency, \"之前\", \"上次\", \"沿用\", \"保持一致\", \"不要破坏\", or asks to use memory.\n\n## Load Protocol\n\n1. Check memory state.\n2. If memory is disabled or not needed, continue without reading memory files.\n3. Read `.wingman\u002Fmemory\u002Fbrief.md`.\n4. Use the Domain Registry to choose relevant current domain truth.\n5. Read relevant `domains\u002F` files.\n6. Read `.wingman\u002Fmemory\u002Fcontext.md` only for hot task state and direct pointers.\n7. Read history projections only when Historical-Risk Signals are present.\n8. Read at most 0-3 selected history event bodies by default.\n\nFor folder domains, read the folder `index.md` first, then only the relevant subfiles named by that index. Do not read every domain subfile by default.\n\n## Domain Registry\n\nThe Domain Registry in `brief.md` is a routing table:\n\n```md\n| Domain | Read When | Current File | History Domain Index | History Topics | Aliases | Related Domains | Status |\n```\n\n- `Current File` points to current truth.\n- `History Domain Index` and `History Topics` point to historical lookup indexes.\n- `Related Domains` are hints, not automatic expansion.\n- Deprecated or superseded registry rows are not authoritative unless the replacement points there.\n\nRead a current domain when the task matches `Domain`, `Read When`, or `Aliases`. Read related domains only when the task also touches that related area or the current domain file points to a specific related rule.\n\n## Context\n\n`context.md` is a hot cache. Read it for:\n\n- active unfinished work;\n- pending follow-up;\n- blocker or debugging state needed soon;\n- direct pointer to current truth or history for the active task.\n\nTreat context pointers as routing hints. If a pointer names a current truth, read that truth. If it names a history event, read the event only when Historical-Risk Signals are present or the pointer is directly needed for the task.\n\n## Historical-Risk Signals\n\nRead history projections only when at least one signal is present:\n\n- the user asks about previous work, \"before\", \"last time\", \"why\", \"what changed\", \"之前\", or \"上次\";\n- the task changes or depends on rule semantics, field meanings, state flows, API contracts, business meaning, or agent behavior;\n- current truth links to a history event and the reason matters for the task;\n- a context pointer directly names a relevant history event;\n- history is needed to avoid repeated debugging or repeated wrong interpretation.\n\nWhen history is needed, prefer sources in this order:\n\n1. Direct event links from current truth or context pointers.\n2. `history\u002Ftopics\u002F\u003Ctopic>.md`.\n3. `history\u002Fdomains\u002F\u003Cdomain>.md`.\n4. `history\u002Fmonths\u002FYYYY-MM.md` for date questions.\n5. `history\u002Findex.md` when projection routing is unclear or the user asks broadly.\n\nChoose only the strongest 0-3 event bodies for the current task unless the user asks for deeper history.\n\nDo not scan `history\u002Fevents\u002F` directly by default.\n\n## Internal Checklist\n\nBefore editing code, internally confirm:\n\n- active task and relevant files;\n- memory files read;\n- relevant current truth IDs and subjects;\n- any candidate, deprecated, or superseded entries;\n- any relation targets needed to understand the current rule;\n- history projections or event bodies read, if any;\n- exact fields, symbols, contracts, or rules that are binding;\n- whether the requested change conflicts with memory.\n\nDo not show the checklist by default. Surface it only when there is a conflict, missing context, or the user asks.\n\n## Memory Pressure Signals\n\n`memory-load` may notice memory pressure but must not clean, compact, summarize, promote, or delete memory.\n\nMention cleanup only when a concrete candidate affects the task:\n\n- `context.md` contains durable rule bodies instead of pointers;\n- context repeats bodies already owned by `brief.md`, `domains\u002F`, or `history\u002Fevents\u002F`;\n- two current truths conflict;\n- a replaced rule is still marked current;\n- history projections copy event bodies instead of linking them;\n- relevant history exists but no topic or domain projection helps lookup.\n\nSuggest explicit `memory-clean` later. If a conflict blocks correct work, ask the user which rule is valid.\n\n## Binding Rules\n\n- Never substitute one business field for a semantically different field for convenience.\n- If memory specifies a canonical field or contract, follow it unless the user changes the rule.\n- Treat existing `\u002F\u002F @invariant:` comments as local binding context when present.\n- `memory-load` is read-only; new comments or memory updates belong to the relevant coding task or `memory-sync`.\n- Existing capability and reuse lookup belongs to `project-map-find`; do not read project-map files during `memory-load` unless the user explicitly asks for project-map context.\n","# Wingman Memory Load\n\n`memory-load` is read-only. It loads current truth by default and history only when the task needs explanation or past-change context.\n\n## Memory State\n\nUse `.wingman\u002Fmemory\u002F` as the repository-local memory root.\n\nRepository memory is enabled only when both core entry files exist:\n\n```text\n.wingman\u002Fmemory\u002Fbrief.md\n.wingman\u002Fmemory\u002Fcontext.md\n```\n\nIf `.wingman\u002Fmemory\u002F` is missing, continue without memory unless the user explicitly asked about memory. If the directory exists but a core entry file is missing, report partial memory only when the user asked about memory or the task depends on memory consistency.\n\n## Authority\n\nUse this authority order when memory files disagree:\n\n```text\nbrief.md current Project Decisions\n> domains\u002F current truths\n> context.md hot working state\n> history\u002F past events and evidence\n```\n\nHistory explains why something changed. It is not current truth unless a current entry in `brief.md` or `domains\u002F` links to it as evidence.\n\nOnly `Status: current` current-truth entries are binding. `candidate`, `deprecated`, and `superseded` entries are background only.\n\nRelations:\n\n- `updates \u003Cid>` replaces the referenced entry for overlapping scope.\n- `extends \u003Cid>` keeps both entries valid when compatible.\n- `derived_from \u003Cid-or-path>` records evidence lineage, not authority.\n\nIf two current entries with the same `Subject` conflict and no relation resolves them, stop and ask which rule is valid.\n\n## When To Load\n\nSkip memory for trivial isolated work: typo-only edits, formatting, isolated style tweaks, throwaway experiments, or local changes with no business, state, data, contract, reuse, or existing-behavior impact.\n\nLoad memory before non-trivial coding, debugging, planning, review, refactor, API integration, reusable implementation work, or changes touching business logic, state flow, permissions, quotas, billing, field mappings, contracts, or existing behavior.\n\nAlso load memory when the user mentions previous work, consistency, \"之前\", \"上次\", \"沿用\", \"保持一致\", \"不要破坏\", or asks to use memory.\n\n## Load Protocol\n\n1. Check memory state.\n2. If memory is disabled or not needed, continue without reading memory files.\n3. Read `.wingman\u002Fmemory\u002Fbrief.md`.\n4. Use the Domain Registry to choose relevant current domain truth.\n5. Read relevant `domains\u002F` files.\n6. Read `.wingman\u002Fmemory\u002Fcontext.md` only for hot task state and direct pointers.\n7. Read history projections only when Historical-Risk Signals are present.\n8. Read at most 0-3 selected history event bodies by default.\n\nFor folder domains, read the folder `index.md` first, then only the relevant subfiles named by that index. Do not read every domain subfile by default.\n\n## Domain Registry\n\nThe Domain Registry in `brief.md` is a routing table:\n\n```md\n| Domain | Read When | Current File | History Domain Index | History Topics | Aliases | Related Domains | Status |\n```\n\n- `Current File` points to current truth.\n- `History Domain Index` and `History Topics` point to historical lookup indexes.\n- `Related Domains` are hints, not automatic expansion.\n- Deprecated or superseded registry rows are not authoritative unless the replacement points there.\n\nRead a current domain when the task matches `Domain`, `Read When`, or `Aliases`. Read related domains only when the task also touches that related area or the current domain file points to a specific related rule.\n\n## Context\n\n`context.md` is a hot cache. Read it for:\n\n- active unfinished work;\n- pending follow-up;\n- blocker or debugging state needed soon;\n- direct pointer to current truth or history for the active task.\n\nTreat context pointers as routing hints. If a pointer names a current truth, read that truth. If it names a history event, read the event only when Historical-Risk Signals are present or the pointer is directly needed for the task.\n\n## Historical-Risk Signals\n\nRead history projections only when at least one signal is present:\n\n- the user asks about previous work, \"before\", \"last time\", \"why\", \"what changed\", \"之前\", or \"上次\";\n- the task changes or depends on rule semantics, field meanings, state flows, API contracts, business meaning, or agent behavior;\n- current truth links to a history event and the reason matters for the task;\n- a context pointer directly names a relevant history event;\n- history is needed to avoid repeated debugging or repeated wrong interpretation.\n\nWhen history is needed, prefer sources in this order:\n\n1. Direct event links from current truth or context pointers.\n2. `history\u002Ftopics\u002F\u003Ctopic>.md`.\n3. `history\u002Fdomains\u002F\u003Cdomain>.md`.\n4. `history\u002Fmonths\u002FYYYY-MM.md` for date questions.\n5. `history\u002Findex.md` when projection routing is unclear or the user asks broadly.\n\nChoose only the strongest 0-3 event bodies for the current task unless the user asks for deeper history.\n\nDo not scan `history\u002Fevents\u002F` directly by default.\n\n## Internal Checklist\n\nBefore editing code, internally confirm:\n\n- active task and relevant files;\n- memory files read;\n- relevant current truth IDs and subjects;\n- any candidate, deprecated, or superseded entries;\n- any relation targets needed to understand the current rule;\n- history projections or event bodies read, if any;\n- exact fields, symbols, contracts, or rules that are binding;\n- whether the requested change conflicts with memory.\n\nDo not show the checklist by default. Surface it only when there is a conflict, missing context, or the user asks.\n\n## Memory Pressure Signals\n\n`memory-load` may notice memory pressure but must not clean, compact, summarize, promote, or delete memory.\n\nMention cleanup only when a concrete candidate affects the task:\n\n- `context.md` contains durable rule bodies instead of pointers;\n- context repeats bodies already owned by `brief.md`, `domains\u002F`, or `history\u002Fevents\u002F`;\n- two current truths conflict;\n- a replaced rule is still marked current;\n- history projections copy event bodies instead of linking them;\n- relevant history exists but no topic or domain projection helps lookup.\n\nSuggest explicit `memory-clean` later. If a conflict blocks correct work, ask the user which rule is valid.\n\n## Binding Rules\n\n- Never substitute one business field for a semantically different field for convenience.\n- If memory specifies a canonical field or contract, follow it unless the user changes the rule.\n- Treat existing `\u002F\u002F @invariant:` comments as local binding context when present.\n- `memory-load` is read-only; new comments or memory updates belong to the relevant coding task or `memory-sync`.\n- Existing capability and reuse lookup belongs to `project-map-find`; do not read project-map files during `memory-load` unless the user explicitly asks for project-map context.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-load",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill memory-load",{"tool":59,"command":60},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill memory-load",{"tool":62,"command":63},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill memory-load","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-load\u002FSKILL.md",true,[],[68,78,86,94,102,110],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":77},"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":77},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":77},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":77},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":77},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":77},"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",[],[]]