[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJ7CXYCH1HR9GD179814CP":3,"skill-same:01M6MJ7CXYCH1HR9GD179814CP":77},{"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},"01M6MJ7CXYCH1HR9GD179814CP","memory-sync",null,"Use when Wingman memory is already known enabled in the current repository and progress, decisions, business logic, API contracts, state flow, field mappings, or durable project knowledge should be recorded, or when the user explicitly asks to sync Wingman memory.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-sync\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"sync","memory","memory sync","when","api contracts","progress","logic","project","project knowledge","contracts","use","business","user","decisions","knowledge","api","flow","repository","state","2026-11-10 10:12:30",false,"---\nname: memory-sync\ndescription: Use when Wingman memory is already known enabled in the current repository and progress, decisions, business logic, API contracts, state flow, field mappings, or durable project knowledge should be recorded, or when the user explicitly asks to sync Wingman memory.\n---\n\n# Wingman Memory Sync\n\n`memory-sync` writes the smallest useful memory update after meaningful work. It chooses the owning body for each memory item before writing.\n\n## Storage Roles\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\nAuthority order:\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\nCurrent truth says what future agents must obey now. History explains what changed and why. Context carries only active work state and short pointers.\n\n## Gate\n\nApply these gates before reading or writing memory:\n\n1. If the user opts out of memory for this work, stop without reading or writing memory.\n2. If `.wingman\u002Fmemory\u002F` is missing, ordinary completion does not use `memory-sync`. If sync was explicitly requested, report that repository memory is disabled and `memory-setup` is the explicit enable path.\n3. If `.wingman\u002Fmemory\u002F` exists but `.wingman\u002Fmemory\u002Fbrief.md` or `.wingman\u002Fmemory\u002Fcontext.md` is missing, stop before writing, report the missing core entry files, and suggest `memory-setup`. Do not repair from `memory-sync`.\n4. Continue only when both `brief.md` and `context.md` exist.\n\nBefore reporting meaningful coding, documentation, configuration, product, or operational work as complete in a repository where memory is enabled, run the routing checks below. If a write route qualifies, sync memory before saying the work is done unless the user opted out.\n\n## Ownership Routing\n\nClassify each memory item into one of these routes:\n\n| Route | Owner | Qualifies When |\n| --- | --- | --- |\n| `IGNORE` | none | The change has no reusable future value. |\n| `CURRENT_TRUTH` | `brief.md` or `domains\u002F` | Future agents must obey the rule, contract, field meaning, state flow, policy, invariant, or recurring debugging conclusion. |\n| `HISTORY_EVENT` | `history\u002Fevents\u002F` | The change explains durable rule evolution, old-to-new meaning, important correction, migration, incident, important regression fix, or user-requested historical memory. |\n| `CONTEXT_POINTER` | `context.md` | Active unfinished work, pending follow-up, blocker, debugging state, or an immediate continuation pointer is needed. |\n\nUse `IGNORE` for typo-only edits, formatting-only edits, rename-only cleanup, isolated visual tweaks, obvious local implementation details, and failed attempts with no reusable lesson.\n\nA task may write more than one route, but each route needs its own reason. When current truth and history are both written, current truth owns the binding rule and history owns the change narrative.\n\n## Single Owner Body\n\nEach durable memory item has one owning body:\n\n- current binding rule body: `brief.md` or `domains\u002F`;\n- historical event body: `history\u002Fevents\u002F`;\n- historical lookup entry: `history\u002Findex.md`, `history\u002Fdomains\u002F`, `history\u002Ftopics\u002F`, or `history\u002Fmonths\u002F`;\n- hot working state or pointer: `context.md`.\n\nShort summaries and pointers are valid. Full duplicated rule bodies, event narratives, evidence, reasoning, or debugging paths are not valid.\n\n## Write Flow\n\n1. Apply the Gate.\n2. Route each memory item with Ownership Routing.\n3. If every item is `IGNORE`, write nothing and report the threshold that blocked writing.\n4. Write `CURRENT_TRUTH` before `HISTORY_EVENT` when both are needed.\n5. Write `HISTORY_EVENT` only when the event has durable trace value beyond the current rule.\n6. Write `CONTEXT_POINTER` only for hot state or immediate continuation.\n7. Update history projections only for new or changed history events.\n8. Report changed memory files or the route that blocked writing.\n\n## Current Truth\n\nWrite current truth when future agents must obey the result or would otherwise need old logs to avoid a semantic mistake.\n\nUse `brief.md` for project-wide decisions: global conventions, cross-domain rules, architecture choices, repository policies, memory policy, and project-wide agent behavior.\n\nUse `domains\u002F` for one-domain rules: business rules, API contracts, canonical fields, field meanings, state flow, enum mapping, permissions, routing, money, quotas, lifecycle, product invariants, operational procedures, or recurring debugging conclusions.\n\nBefore writing current truth:\n\n1. Read `brief.md`.\n2. Use the Domain Registry to choose `brief.md` or a domain file.\n3. Inspect same-subject current entries when practical.\n4. Verify evidence from user direction, existing memory, docs, schema, tests, accepted specs, or intentional implementation behavior.\n5. If two current entries conflict and no `updates` or `extends` relation resolves them, stop and ask which rule is valid.\n\nUse stable identity:\n\n- `ID`: `mem:\u003Cdomain>:\u003Csubject-slug>`.\n- `Subject`: stable dotted subject such as `order.status.meaning`.\n- `Status`: `current | superseded | deprecated | candidate`.\n- `Relation`: `updates \u003Cid> | extends \u003Cid> | derived_from \u003Cid-or-path> | None`.\n- `Confidence`: `confirmed | implementation-backed | inferred`.\n\nOnly `Status: current` entries are binding. Inferred entries start as `candidate` unless confirmed by user, spec, schema, test, or intentional implementation contract.\n\nWhen replacing a rule, mark the old entry `superseded` or `deprecated` and point to the replacement. When extending a compatible rule, keep both current and link with `extends`.\n\nRead `references\u002Ftemplates.md` before using the default current truth template.\n\n## History Event\n\nWrite history when a completed change has durable trace value beyond hot context, especially when:\n\n- a current truth was added, changed, deprecated, or superseded and the reason matters;\n- a rule, field meaning, workflow interpretation, data contract, or agent behavior changed;\n- the event explains why a current rule exists;\n- a recurring confusion, debugging path, or wrong interpretation was resolved;\n- a migration, incident, important regression fix, or user-requested historical record needs later lookup.\n\nHistory is not mandatory for every current truth. Skip history when the reason is obvious from the current rule or the change is trivial.\n\nWhen writing history:\n\n1. Read `references\u002Fhistory-events.md`.\n2. Write one event body under `.wingman\u002Fmemory\u002Fhistory\u002Fevents\u002FYYYY\u002FMM\u002FYYYY-MM-DD-\u003Cevent-slug>.md`.\n3. Update only the needed projections: `history\u002Findex.md`, `history\u002Fdomains\u002F\u003Cdomain>.md`, `history\u002Ftopics\u002F\u003Ctopic>.md`, and `history\u002Fmonths\u002FYYYY-MM.md`.\n4. Link `Promoted Truths` to current truth IDs or use `None`.\n5. Keep projection indexes short and link-only.\n\nUse generic topic names such as `order-status`, `checkout-flow`, `payment-selection`, `upload-retry`, or `quota-display`.\n\n## Context Pointer\n\nWrite `context.md` only for active working state:\n\n- unfinished work;\n- pending follow-up;\n- blocker or debugging state needed in the next few sessions;\n- immediate continuation pointer to a current truth or history event.\n\nIf current truth or history owns the durable detail, context receives only a short pointer. If no hot follow-up exists, write no context entry.\n\nUse the `## Short Pointers` section when present. If an older memory file lacks that section, add it near current work rather than creating a new log section.\n\nRead `references\u002Ftemplates.md` before using the default context pointer shape.\n\n## Domain Registry\n\nUpdate the Domain Registry only when creating, renaming, deprecating, or superseding a domain route.\n\nRegistry rows use:\n\n```md\n| Domain | Read When | Current File | History Domain Index | History Topics | Aliases | Related Domains | Status |\n```\n\n`History Domain Index` and `History Topics` are routing hints for historical lookup. They do not make history current truth.\n\n## Language And Completion\n\nMemory language follows `brief.md` Memory Settings when set; otherwise follow existing memory language, then the user's language, then English. Keep code symbols, paths, API names, config names, and field names unchanged.\n\nFinish by reporting changed memory files. If nothing was written, name the blocking gate or route.\n","# Wingman Memory Sync\n\n`memory-sync` writes the smallest useful memory update after meaningful work. It chooses the owning body for each memory item before writing.\n\n## Storage Roles\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\nAuthority order:\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\nCurrent truth says what future agents must obey now. History explains what changed and why. Context carries only active work state and short pointers.\n\n## Gate\n\nApply these gates before reading or writing memory:\n\n1. If the user opts out of memory for this work, stop without reading or writing memory.\n2. If `.wingman\u002Fmemory\u002F` is missing, ordinary completion does not use `memory-sync`. If sync was explicitly requested, report that repository memory is disabled and `memory-setup` is the explicit enable path.\n3. If `.wingman\u002Fmemory\u002F` exists but `.wingman\u002Fmemory\u002Fbrief.md` or `.wingman\u002Fmemory\u002Fcontext.md` is missing, stop before writing, report the missing core entry files, and suggest `memory-setup`. Do not repair from `memory-sync`.\n4. Continue only when both `brief.md` and `context.md` exist.\n\nBefore reporting meaningful coding, documentation, configuration, product, or operational work as complete in a repository where memory is enabled, run the routing checks below. If a write route qualifies, sync memory before saying the work is done unless the user opted out.\n\n## Ownership Routing\n\nClassify each memory item into one of these routes:\n\n| Route | Owner | Qualifies When |\n| --- | --- | --- |\n| `IGNORE` | none | The change has no reusable future value. |\n| `CURRENT_TRUTH` | `brief.md` or `domains\u002F` | Future agents must obey the rule, contract, field meaning, state flow, policy, invariant, or recurring debugging conclusion. |\n| `HISTORY_EVENT` | `history\u002Fevents\u002F` | The change explains durable rule evolution, old-to-new meaning, important correction, migration, incident, important regression fix, or user-requested historical memory. |\n| `CONTEXT_POINTER` | `context.md` | Active unfinished work, pending follow-up, blocker, debugging state, or an immediate continuation pointer is needed. |\n\nUse `IGNORE` for typo-only edits, formatting-only edits, rename-only cleanup, isolated visual tweaks, obvious local implementation details, and failed attempts with no reusable lesson.\n\nA task may write more than one route, but each route needs its own reason. When current truth and history are both written, current truth owns the binding rule and history owns the change narrative.\n\n## Single Owner Body\n\nEach durable memory item has one owning body:\n\n- current binding rule body: `brief.md` or `domains\u002F`;\n- historical event body: `history\u002Fevents\u002F`;\n- historical lookup entry: `history\u002Findex.md`, `history\u002Fdomains\u002F`, `history\u002Ftopics\u002F`, or `history\u002Fmonths\u002F`;\n- hot working state or pointer: `context.md`.\n\nShort summaries and pointers are valid. Full duplicated rule bodies, event narratives, evidence, reasoning, or debugging paths are not valid.\n\n## Write Flow\n\n1. Apply the Gate.\n2. Route each memory item with Ownership Routing.\n3. If every item is `IGNORE`, write nothing and report the threshold that blocked writing.\n4. Write `CURRENT_TRUTH` before `HISTORY_EVENT` when both are needed.\n5. Write `HISTORY_EVENT` only when the event has durable trace value beyond the current rule.\n6. Write `CONTEXT_POINTER` only for hot state or immediate continuation.\n7. Update history projections only for new or changed history events.\n8. Report changed memory files or the route that blocked writing.\n\n## Current Truth\n\nWrite current truth when future agents must obey the result or would otherwise need old logs to avoid a semantic mistake.\n\nUse `brief.md` for project-wide decisions: global conventions, cross-domain rules, architecture choices, repository policies, memory policy, and project-wide agent behavior.\n\nUse `domains\u002F` for one-domain rules: business rules, API contracts, canonical fields, field meanings, state flow, enum mapping, permissions, routing, money, quotas, lifecycle, product invariants, operational procedures, or recurring debugging conclusions.\n\nBefore writing current truth:\n\n1. Read `brief.md`.\n2. Use the Domain Registry to choose `brief.md` or a domain file.\n3. Inspect same-subject current entries when practical.\n4. Verify evidence from user direction, existing memory, docs, schema, tests, accepted specs, or intentional implementation behavior.\n5. If two current entries conflict and no `updates` or `extends` relation resolves them, stop and ask which rule is valid.\n\nUse stable identity:\n\n- `ID`: `mem:\u003Cdomain>:\u003Csubject-slug>`.\n- `Subject`: stable dotted subject such as `order.status.meaning`.\n- `Status`: `current | superseded | deprecated | candidate`.\n- `Relation`: `updates \u003Cid> | extends \u003Cid> | derived_from \u003Cid-or-path> | None`.\n- `Confidence`: `confirmed | implementation-backed | inferred`.\n\nOnly `Status: current` entries are binding. Inferred entries start as `candidate` unless confirmed by user, spec, schema, test, or intentional implementation contract.\n\nWhen replacing a rule, mark the old entry `superseded` or `deprecated` and point to the replacement. When extending a compatible rule, keep both current and link with `extends`.\n\nRead `references\u002Ftemplates.md` before using the default current truth template.\n\n## History Event\n\nWrite history when a completed change has durable trace value beyond hot context, especially when:\n\n- a current truth was added, changed, deprecated, or superseded and the reason matters;\n- a rule, field meaning, workflow interpretation, data contract, or agent behavior changed;\n- the event explains why a current rule exists;\n- a recurring confusion, debugging path, or wrong interpretation was resolved;\n- a migration, incident, important regression fix, or user-requested historical record needs later lookup.\n\nHistory is not mandatory for every current truth. Skip history when the reason is obvious from the current rule or the change is trivial.\n\nWhen writing history:\n\n1. Read `references\u002Fhistory-events.md`.\n2. Write one event body under `.wingman\u002Fmemory\u002Fhistory\u002Fevents\u002FYYYY\u002FMM\u002FYYYY-MM-DD-\u003Cevent-slug>.md`.\n3. Update only the needed projections: `history\u002Findex.md`, `history\u002Fdomains\u002F\u003Cdomain>.md`, `history\u002Ftopics\u002F\u003Ctopic>.md`, and `history\u002Fmonths\u002FYYYY-MM.md`.\n4. Link `Promoted Truths` to current truth IDs or use `None`.\n5. Keep projection indexes short and link-only.\n\nUse generic topic names such as `order-status`, `checkout-flow`, `payment-selection`, `upload-retry`, or `quota-display`.\n\n## Context Pointer\n\nWrite `context.md` only for active working state:\n\n- unfinished work;\n- pending follow-up;\n- blocker or debugging state needed in the next few sessions;\n- immediate continuation pointer to a current truth or history event.\n\nIf current truth or history owns the durable detail, context receives only a short pointer. If no hot follow-up exists, write no context entry.\n\nUse the `## Short Pointers` section when present. If an older memory file lacks that section, add it near current work rather than creating a new log section.\n\nRead `references\u002Ftemplates.md` before using the default context pointer shape.\n\n## Domain Registry\n\nUpdate the Domain Registry only when creating, renaming, deprecating, or superseding a domain route.\n\nRegistry rows use:\n\n```md\n| Domain | Read When | Current File | History Domain Index | History Topics | Aliases | Related Domains | Status |\n```\n\n`History Domain Index` and `History Topics` are routing hints for historical lookup. They do not make history current truth.\n\n## Language And Completion\n\nMemory language follows `brief.md` Memory Settings when set; otherwise follow existing memory language, then the user's language, then English. Keep code symbols, paths, API names, config names, and field names unchanged.\n\nFinish by reporting changed memory files. If nothing was written, name the blocking gate or route.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-sync",474,"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-11 14:40:14",{"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-sync",{"tool":59,"command":60},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill memory-sync",{"tool":62,"command":63},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill memory-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-sync\u002FSKILL.md",true,[67,73],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fhistory-events.md","REFERENCE","参考文档",2508,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-sync\u002Freferences\u002Fhistory-events.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Ftemplates.md",2792,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flsshym\u002Fwingman.ai\u002Fskills\u002Fmemory-sync\u002Freferences\u002Ftemplates.md",[78,86,93,100,125,148],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":85},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":85},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":38},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[107,108,109,110,111,20,112,113,114,115,116,22,117,118,119,120,121,122,123,124],"search","deja search","never","error","ready","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":38},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[132,133,134,120,135,136,137,138,139,140,141,32,142,143,20,144,26,145,146,147],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","brew","remember","project rules","session","end","reflection",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":165,"publishedAt":38},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[154,159,162],{"categoryNo":155,"categoryName":156,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":160,"categoryName":161,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":163,"categoryName":164,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000010","后端与接口",[150,166,167,168,169,170,171,26,172,112,173,174,175,176,22,177,178,179,34,180],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","publish"]