[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MF7CG7PJSXYBHK0KBRFJ9C":3,"skill-same:01M6MF7CG7PJSXYBHK0KBRFJ9C":82},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6MF7CG7PJSXYBHK0KBRFJ9C","cometchat-angular-v5-migration",null,"Upgrade an Angular app from CometChat UI Kit v4 → v5 (`@cometchat\u002Fchat-uikit-angular` ^4 → ^5). Reads the repo's CometChat usage, applies the breaking-change map (deps, composite components removed, bare→Component renames, CometChatThemeService → CSS variables, event inputs → Outputs, DataSource → composition, localization renames), fetches the exhaustive guide, and verifies the build. Triggers: 'upgrade my v4 uikit to v5', 'migrate cometchat angular v4 to v5', 'upgrade @cometchat\u002Fchat-uikit-angular to v5', 'cometchat angular v4 to v5', 'bump cometchat angular uikit'.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-migration\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"cometchat angular v5 migration","migration","angular","cometchat","new","bare","component","change","components","migrate","Variables","upgrade","map","kit","bump","css variables","css","official","resources","Composition","deps","app","shared","2026-11-10 10:12:30",false,"---\nname: cometchat-angular-v5-migration\ndescription: \"Upgrade an Angular app from CometChat UI Kit v4 → v5 (`@cometchat\u002Fchat-uikit-angular` ^4 → ^5). Reads the repo's CometChat usage, applies the breaking-change map (deps, composite components removed, bare→Component renames, CometChatThemeService → CSS variables, event inputs → Outputs, DataSource → composition, localization renames), fetches the exhaustive guide, and verifies the build. Triggers: 'upgrade my v4 uikit to v5', 'migrate cometchat angular v4 to v5', 'upgrade @cometchat\u002Fchat-uikit-angular to v5', 'cometchat angular v4 to v5', 'bump cometchat angular uikit'.\"\nlicense: \"MIT\"\ncompatibility: \"Angular 17-21; FROM @cometchat\u002Fchat-uikit-angular ^4 (4.3.36) → ^5 (5.1.0–5.2.2 verified); @cometchat\u002Fchat-sdk-javascript ^4.1.13 (peer; 5.2.x needs ^4.2.0); @cometchat\u002Fcards-angular ^1.0.0 (new peer, undocumented in the official guide); @cometchat\u002Fuikit-elements\u002F-resources\u002F-shared removed\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat angular migration upgrade v4 v5 uikit\"\n---\n\n> **Ground truth:** migrates an Angular app **FROM `@cometchat\u002Fchat-uikit-angular@4` TO `@5`**. v5 target symbols are catalog-verified vs installed 5.1.0; the v4→v5 breaking-change map is BAKED in `references\u002Fmigration-guide.md` (distilled from the official \"Upgrading From V4\" guide + a real v4.3.36→v5.1.0 export diff — 146 genuine removals, 33 bare→`Component` renames, kept separate). The exhaustive per-component prop table is FETCHED from `cometchat-angular-v5-components\u002Freferences\u002Fcatalog.md` + the docs `.md` twins. **APPEND\u002Ftransform the user's code — never wipe it; work on a branch and confirm before bulk edits** (`RULES.md`).\n\n## Companion skills (read first)\n- `cometchat-angular-v5-core` — the v5 init\u002Flogin\u002Frender the migrated app lands on. This skill ASSUMES it.\n- `cometchat-angular-v5-components` — the v5 component catalog (the target names + real inputs\u002Foutputs).\n- `cometchat-angular-v5-placement` — how to rebuild a v4 composite from v5 modules (§2 of the migration guide points here per composite).\n\n## Use this skill when\n\"upgrade my v4 UI Kit to v5\", \"migrate CometChat Angular v4→v5\", \"bump `@cometchat\u002Fchat-uikit-angular` to v5\". Precondition: the project currently has `@cometchat\u002Fchat-uikit-angular@4`.\n\n## Migration workflow (BAKED)\n1. **Detect the starting point.** Confirm `package.json` has `@cometchat\u002Fchat-uikit-angular@4` (already `@5` → STOP, nothing to migrate). Note whether the app uses composite components (`...WithMessages`\u002F`...WithDetails`), `CometChatThemeService`, `*Style` inputs, `DataSource`\u002F`ChatConfigurator`, or custom localization keys — each drives a later step. **Work on a branch; transform in place, never delete the user's code.**\n2. **Update dependencies.** `npm install @cometchat\u002Fchat-uikit-angular@5 @cometchat\u002Fchat-sdk-javascript@^4.1.13 @cometchat\u002Fcards-angular@^1.0.0` then `npm uninstall @cometchat\u002Fuikit-elements @cometchat\u002Fuikit-resources @cometchat\u002Fuikit-shared`. `@cometchat\u002Fcards-angular` is a genuine new 5.1.0 peer the official guide never mentions — install it or the build fails on a missing peer, not a CometChat error.\n3. **Scan the repo for v4 usage.** Grep for every symbol in `references\u002Fmigration-guide.md` §2 (composites, no-equivalent standalones, `DataSource`\u002Fdecorators, the ~35 `*Style` objects) and §2b (the 33 bare-name renames) — produce the concrete change list before editing anything. A bare name is not automatically \"removed\"; check §2b first.\n4. **Apply the breaking-change map** (`references\u002Fmigration-guide.md`): §2\u002F§2b symbol removals + renames, §3 theming (`CometChatThemeService` + `*Style` → CSS variables + the real `ThemeService`, **not** the official guide's own hand-rolled `matchMedia` example — see the warning in §3), §4 event-input → Output rename, §5 `DataSource`\u002F`ChatConfigurator` → `MessageBubbleConfigService` or \"nothing, it's auto-rendered,\" §6 drop `CUSTOM_ELEMENTS_SCHEMA` + convert to standalone, §7 optional `ChatStateService` adoption, §8 localization method renames.\n   **The baked map is a closed list, not a prop reference — FETCH the rest** (`RULES.md` § Fetch discipline; **never** `node_modules\u002F**\u002F*.d.ts`), routed from `cometchat-angular-v5-core\u002Freferences\u002Fdocs-map.md`: the **official guide** `{DOCS_BASE}\u002Fui-kit\u002Fangular\u002Fcustomization\u002Fmigration-guide.md` for anything the map omits; a **component's** exact inputs\u002Foutputs\u002Fslots from its own `.md` twin (Angular has no `migration-property-changes` page — there is no single prop-diff table); an **SDK method** for a capability with no v5 component (`{SDK_DOCS_BASE}\u002Fsdk\u002Fjavascript\u002Fgroups-overview.md` et al.) — that is where the host-composed group surfaces in step 5 come from.\n5. **Rebuild every composite from modules.** v5 has no composite components at all — `CometChatConversationsWithMessages` etc. must become a hand-stitched surface. Use `cometchat-angular-v5-placement\u002Freferences\u002Fcore-surface.md` (1:1) or `combined-app.md` (tabbed) as the target shape, not a literal prop-for-prop port — the composite's *configuration options* (which v4 had many of) don't exist in v5; its *behavior* is what you're reproducing.\n6. **Verify.** Build\u002Ftypecheck passes; NO v4 symbols remain (grep `references\u002Fmigration-guide.md` §2's full list); every kit component is in its consumer's `imports: []`; the app renders after init→login resolves (`cometchat-angular-v5-core\u002Freferences\u002Flifecycle.md`). Reuse `cometchat-angular-v5-core` \"Verify it works\".\n\n## Common pitfalls (BAKED)\n- **Porting the official guide's own theming example.** It shows a hand-rolled `matchMedia` listener for OS-follow — that predates the real v5 mechanism. `ThemeService.initFromPreference()` already does this; don't reintroduce v4-era manual theme-tracking code (§3).\n- **Treating a bare v4 name as removed when it's only renamed.** Check §2b (33 bare→`Component` renames) before concluding a component is gone — most \"missing\" names are one word away from their v5 form.\n- **Missing `@cometchat\u002Fcards-angular`.** Genuinely undocumented in the official migration guide; the install fails on a peer-dependency error that looks unrelated to the migration.\n- **Forgetting `imports: []` after dropping `CUSTOM_ELEMENTS_SCHEMA`.** v4's schema tolerated unregistered elements; v5's standalone components render **nothing, silently** if omitted from `imports: []` — the single most common v5 failure mode, and migrated code is exactly where it's missed (`cometchat-angular-v5-core\u002FSKILL.md`).\n- **Rebuilding a composite as a literal prop-for-prop port.** v4 composites had large configuration surfaces (`*Style` objects, callback inputs) with no v5 equivalent — port the *behavior*, not the *configuration*, using `cometchat-angular-v5-placement`'s real recipes as the target.\n- **Assuming every `DataSourceDecorator` needs `MessageBubbleConfigService`.** Some were registering a *built-in extension* (polls, stickers, translation) — v5 auto-renders most of those once enabled in the dashboard, with nothing to register (`cometchat-angular-v5-features\u002FSKILL.md`; verify against `needs_stitching` in `features.angular-v5.json`, never assume).\n\n## Verify it works\nBuild\u002Ftypecheck is green; a repo-wide grep finds NO §2 v4 symbols (composites, `CometChatThemeService`, `DataSource`\u002F`ChatConfigurator`, any `*Style` object, any bare §2b name unqualified); every kit component is in `imports: []`; the app renders once init→login resolves; migrated theming follows the OS via `ThemeService`, not a leftover `matchMedia` listener. Full per-component prop reference: `cometchat-angular-v5-components\u002Freferences\u002Fcatalog.md` + the docs `.md` twins.\n","> **Ground truth:** migrates an Angular app **FROM `@cometchat\u002Fchat-uikit-angular@4` TO `@5`**. v5 target symbols are catalog-verified vs installed 5.1.0; the v4→v5 breaking-change map is BAKED in `references\u002Fmigration-guide.md` (distilled from the official \"Upgrading From V4\" guide + a real v4.3.36→v5.1.0 export diff — 146 genuine removals, 33 bare→`Component` renames, kept separate). The exhaustive per-component prop table is FETCHED from `cometchat-angular-v5-components\u002Freferences\u002Fcatalog.md` + the docs `.md` twins. **APPEND\u002Ftransform the user's code — never wipe it; work on a branch and confirm before bulk edits** (`RULES.md`).\n\n## Companion skills (read first)\n- `cometchat-angular-v5-core` — the v5 init\u002Flogin\u002Frender the migrated app lands on. This skill ASSUMES it.\n- `cometchat-angular-v5-components` — the v5 component catalog (the target names + real inputs\u002Foutputs).\n- `cometchat-angular-v5-placement` — how to rebuild a v4 composite from v5 modules (§2 of the migration guide points here per composite).\n\n## Use this skill when\n\"upgrade my v4 UI Kit to v5\", \"migrate CometChat Angular v4→v5\", \"bump `@cometchat\u002Fchat-uikit-angular` to v5\". Precondition: the project currently has `@cometchat\u002Fchat-uikit-angular@4`.\n\n## Migration workflow (BAKED)\n1. **Detect the starting point.** Confirm `package.json` has `@cometchat\u002Fchat-uikit-angular@4` (already `@5` → STOP, nothing to migrate). Note whether the app uses composite components (`...WithMessages`\u002F`...WithDetails`), `CometChatThemeService`, `*Style` inputs, `DataSource`\u002F`ChatConfigurator`, or custom localization keys — each drives a later step. **Work on a branch; transform in place, never delete the user's code.**\n2. **Update dependencies.** `npm install @cometchat\u002Fchat-uikit-angular@5 @cometchat\u002Fchat-sdk-javascript@^4.1.13 @cometchat\u002Fcards-angular@^1.0.0` then `npm uninstall @cometchat\u002Fuikit-elements @cometchat\u002Fuikit-resources @cometchat\u002Fuikit-shared`. `@cometchat\u002Fcards-angular` is a genuine new 5.1.0 peer the official guide never mentions — install it or the build fails on a missing peer, not a CometChat error.\n3. **Scan the repo for v4 usage.** Grep for every symbol in `references\u002Fmigration-guide.md` §2 (composites, no-equivalent standalones, `DataSource`\u002Fdecorators, the ~35 `*Style` objects) and §2b (the 33 bare-name renames) — produce the concrete change list before editing anything. A bare name is not automatically \"removed\"; check §2b first.\n4. **Apply the breaking-change map** (`references\u002Fmigration-guide.md`): §2\u002F§2b symbol removals + renames, §3 theming (`CometChatThemeService` + `*Style` → CSS variables + the real `ThemeService`, **not** the official guide's own hand-rolled `matchMedia` example — see the warning in §3), §4 event-input → Output rename, §5 `DataSource`\u002F`ChatConfigurator` → `MessageBubbleConfigService` or \"nothing, it's auto-rendered,\" §6 drop `CUSTOM_ELEMENTS_SCHEMA` + convert to standalone, §7 optional `ChatStateService` adoption, §8 localization method renames.\n   **The baked map is a closed list, not a prop reference — FETCH the rest** (`RULES.md` § Fetch discipline; **never** `node_modules\u002F**\u002F*.d.ts`), routed from `cometchat-angular-v5-core\u002Freferences\u002Fdocs-map.md`: the **official guide** `{DOCS_BASE}\u002Fui-kit\u002Fangular\u002Fcustomization\u002Fmigration-guide.md` for anything the map omits; a **component's** exact inputs\u002Foutputs\u002Fslots from its own `.md` twin (Angular has no `migration-property-changes` page — there is no single prop-diff table); an **SDK method** for a capability with no v5 component (`{SDK_DOCS_BASE}\u002Fsdk\u002Fjavascript\u002Fgroups-overview.md` et al.) — that is where the host-composed group surfaces in step 5 come from.\n5. **Rebuild every composite from modules.** v5 has no composite components at all — `CometChatConversationsWithMessages` etc. must become a hand-stitched surface. Use `cometchat-angular-v5-placement\u002Freferences\u002Fcore-surface.md` (1:1) or `combined-app.md` (tabbed) as the target shape, not a literal prop-for-prop port — the composite's *configuration options* (which v4 had many of) don't exist in v5; its *behavior* is what you're reproducing.\n6. **Verify.** Build\u002Ftypecheck passes; NO v4 symbols remain (grep `references\u002Fmigration-guide.md` §2's full list); every kit component is in its consumer's `imports: []`; the app renders after init→login resolves (`cometchat-angular-v5-core\u002Freferences\u002Flifecycle.md`). Reuse `cometchat-angular-v5-core` \"Verify it works\".\n\n## Common pitfalls (BAKED)\n- **Porting the official guide's own theming example.** It shows a hand-rolled `matchMedia` listener for OS-follow — that predates the real v5 mechanism. `ThemeService.initFromPreference()` already does this; don't reintroduce v4-era manual theme-tracking code (§3).\n- **Treating a bare v4 name as removed when it's only renamed.** Check §2b (33 bare→`Component` renames) before concluding a component is gone — most \"missing\" names are one word away from their v5 form.\n- **Missing `@cometchat\u002Fcards-angular`.** Genuinely undocumented in the official migration guide; the install fails on a peer-dependency error that looks unrelated to the migration.\n- **Forgetting `imports: []` after dropping `CUSTOM_ELEMENTS_SCHEMA`.** v4's schema tolerated unregistered elements; v5's standalone components render **nothing, silently** if omitted from `imports: []` — the single most common v5 failure mode, and migrated code is exactly where it's missed (`cometchat-angular-v5-core\u002FSKILL.md`).\n- **Rebuilding a composite as a literal prop-for-prop port.** v4 composites had large configuration surfaces (`*Style` objects, callback inputs) with no v5 equivalent — port the *behavior*, not the *configuration*, using `cometchat-angular-v5-placement`'s real recipes as the target.\n- **Assuming every `DataSourceDecorator` needs `MessageBubbleConfigService`.** Some were registering a *built-in extension* (polls, stickers, translation) — v5 auto-renders most of those once enabled in the dashboard, with nothing to register (`cometchat-angular-v5-features\u002FSKILL.md`; verify against `needs_stitching` in `features.angular-v5.json`, never assume).\n\n## Verify it works\nBuild\u002Ftypecheck is green; a repo-wide grep finds NO §2 v4 symbols (composites, `CometChatThemeService`, `DataSource`\u002F`ChatConfigurator`, any `*Style` object, any bare §2b name unqualified); every kit component is in `imports: []`; the app renders once init→login resolves; migrated theming follows the OS via `ThemeService`, not a leftover `matchMedia` listener. Full per-component prop reference: `cometchat-angular-v5-components\u002Freferences\u002Fcatalog.md` + the docs `.md` twins.\n",{"name":5,"license":15,"metadata":47,"description":7,"compatibility":51},{"tags":48,"author":49,"version":50},"cometchat angular migration upgrade v4 v5 uikit","CometChat","1.0.0","Angular 17-21; FROM @cometchat\u002Fchat-uikit-angular ^4 (4.3.36) → ^5 (5.1.0–5.2.2 verified); @cometchat\u002Fchat-sdk-javascript ^4.1.13 (peer; 5.2.x needs ^4.2.0); @cometchat\u002Fcards-angular ^1.0.0 (new peer, undocumented in the official guide); @cometchat\u002Fuikit-elements\u002F-resources\u002F-shared removed","main","cebc3dce495d7eb80d3b1d5841f877a4a92e162d","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-migration",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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-migration",{"tool":68,"command":69},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-migration",{"tool":71,"command":72},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-angular-v5-migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-migration\u002FSKILL.md",true,[76],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fmigration-guide.md","REFERENCE","参考文档",19890,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-angular-v5-migration\u002Freferences\u002Fmigration-guide.md",[83,92,99,106,132,157],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"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.","Apache-2.0","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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":91},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":91},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":42},"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",[],[113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,26,129,130,131],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","cli","merge","past",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":42},"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",[],[139,140,141,128,142,143,144,145,146,147,148,149,150,151,118,152,153,154,155,156],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":174,"publishedAt":42},"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",[163,168,171],{"categoryNo":164,"categoryName":165,"taxonomyType":166,"taxonomyTypeDesc":167},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":169,"categoryName":170,"taxonomyType":166,"taxonomyTypeDesc":167},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":172,"categoryName":173,"taxonomyType":166,"taxonomyTypeDesc":167},"01JBSEEDCAT000000000000010","后端与接口",[159,175,176,177,178,179,180,153,181,119,182,183,184,185,124,186,187,188,189,190],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]