[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDBFFDHPA1VB3TQAC0Q1QN":3,"skill-same:01M6MDBFFDHPA1VB3TQAC0Q1QN":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6MDBFFDHPA1VB3TQAC0Q1QN","skill-duplication-audit",null,"Audit overlapping skills across A Team and builder packs; identify redundant or conflicting guidance.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fskill-duplication-audit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32],"audit","duplication","skill duplication audit","team","v0","builder","guidance","across","2026","2026-11-10 10:12:30",false,"---\nname: skill-duplication-audit\ndescription: \"Audit overlapping skills across A Team and builder packs; identify redundant or conflicting guidance.\"\nversion: v0.1\nstate: Approved\nowner: Miguel\ntarget: a-team\ncreated: 2026-06-14\nupdated: 2026-06-14\nscore: 88\ncompliance-risk: Low\n---\n\n# skill-duplication-audit\n\n## Problem\n\nSkills across the 5 ecosystem repositories overlap in scope without documented distinctions. This creates confusion about which skill to invoke, silent redundancy in packs, and conflicting guidance when two skills are active in the same session. Without a structured way to detect and classify overlaps, the ecosystem grows noisier over time.\n\n## Objective\n\nGiven 2 or more skills with their triggers and objectives, identify pairs that have overlapping scope and classify each pair. Produce a duplication report with a classification and a specific recommendation for each pair.\n\n## When to Use\n\n- When adding a new skill and checking whether an existing skill already covers the same use case\n- When auditing a pack for internal redundancy\n- When comparing skills across packs after an ecosystem audit\n- When a user reports confusion about which of two skills to invoke\n\n## When NOT to Use\n\n- For a single skill — needs at least 2 skills to compare\n- For agents — agents have tool scope and state, not just trigger scope; use a separate analysis\n- When the boundary is already documented in an existing boundary doc — verify first\n- When the skills are from completely different domains with no plausible trigger overlap\n\n## Inputs\n\n| Input | Required | Description |\n| --- | --- | --- |\n| skill-list | required | 2+ skills, each with: name, trigger (when to use), objective (one sentence), and optionally the repo |\n| scope | optional | `pack` (compare within one repo) or `ecosystem` (compare across repos). Default: `ecosystem` |\n\n## Outputs\n\n| Output | Description |\n| --- | --- |\n| duplication-report | List of pairs with classification and recommendation |\n| boundary-docs-needed | List of pairs requiring a documented distinction (partial-overlap pairs only) |\n\n## Steps\n\n1. Read all inputs. For each skill, extract: name, trigger (what situation invokes it?), objective (what does it produce?).\n2. Group skills by domain. Only compare skills where triggers could plausibly describe the same situation.\n3. For each pair within the same domain, compare triggers and outputs:\n   - **Triggers:** do they describe the same situation or context?\n   - **Outputs:** do they produce the same type of result?\n4. Classify each pair using exactly one label:\n   - **True duplicate:** same trigger AND same output type → recommend merge\n   - **Partial overlap:** triggers overlap but differ, OR outputs overlap but differ → recommend document boundary\n   - **Complementary:** same domain, different workflow stage, no trigger overlap → keep both, note relationship\n   - **False positive:** similar name but different trigger and output → no action required\n5. For each partial-overlap pair, draft a one-sentence boundary statement: \"Use [A] when [condition A]; use [B] when [condition B].\"\n6. List pairs that need a boundary doc (partial-overlap only).\n7. Fill the Completion Statement.\n\n## Completion Statement Format\n\n```text\nskill-duplication-audit complete.\nSkills analysed: [count]\nPairs evaluated: [count]\nTrue duplicates: [count] — [names or NONE]\nPartial overlaps: [count] — [names or NONE]\nComplementary pairs: [count] — [names or NONE]\nFalse positives: [count] — [names or NONE]\nBoundary docs needed: [count] — [skill pairs or NONE]\nRecommendation: [summary action]\n```\n\n## Red Flags\n\n- \"These two skills have similar names so they must be duplicates\" — name similarity is not scope overlap; compare triggers and outputs, not names\n- \"I'll merge them to reduce complexity\" — merging loses scope distinctions; only recommend a merge if triggers AND outputs are genuinely identical\n- \"The boundary is obvious so it doesn't need documentation\" — undocumented boundaries get violated; if there is overlap, document it\n- \"They're in different repos so they can't conflict\" — cross-repo skills are the most common source of undocumented overlap in the ecosystem\n- \"I'll classify as partial overlap to be safe\" — over-classifying creates unnecessary boundary docs; only classify as partial overlap if trigger overlap is real and observable\n\n## Examples\n\n### Example 1 — True duplicate\n\n**Input:**\n- api-doc-writer: trigger \"when writing documentation for a REST API\", objective \"produce API reference docs\"\n- api-reference-generator: trigger \"when documenting a REST API\", objective \"generate API reference documentation\"\n\n**Expected output:** True duplicate. Triggers and outputs are semantically identical. Recommend merge. Keep the skill with stronger test coverage.\n\n### Example 2 — Complementary\n\n**Input:**\n- prd-quality-gate (builder-product): trigger \"when a PRD is drafted and ready for engineering review\", objective \"gate PRD quality before handoff\"\n- copy-quality-gate (builder-growth): trigger \"when landing page copy is written\", objective \"gate copy quality before publishing\"\n\n**Expected output:** Complementary. Same quality gate pattern, different domains (product vs. growth), no trigger overlap. No action needed.\n\n## Counter-Examples\n\n### Counter-Example 1 — False positive mistakenly treated as duplicate\n\n**Input:**\n- design-token-audit (builder-design): trigger \"when reviewing design token consistency across components\"\n- positioning-audit (builder-growth): trigger \"when evaluating brand positioning and messaging clarity\"\n\n**What should happen:** False positive. \"Audit\" in the name is irrelevant — triggers are in completely different domains. No action.\n\n**What the skill must NOT do:** Recommend a merge or boundary doc based on shared vocabulary alone.\n\n### Counter-Example 2 — Complementary pair forced into partial-overlap\n\n**Input:**\n- eval-before-ship (builder-ai): trigger \"before deploying an LLM model or prompt to production\"\n- prd-quality-gate (builder-product): trigger \"when a PRD is drafted and ready for engineering review\"\n\n**What should happen:** Complementary — different stages of the product lifecycle, no trigger overlap.\n\n**What the skill must NOT do:** Classify these as partial-overlap because both are \"gates\" in an AI product workflow.\n\n## Test Cases\n\n| ID | File | Description | Pass |\n| --- | --- | --- | --- |\n| TC-001 | test-cases\u002Fcase-001-true-duplicate.md | True duplicate: identical trigger and output type | ✅ |\n| TC-002 | test-cases\u002Fcase-002-complementary-quality-gates.md | Complementary: prd-quality-gate vs copy-quality-gate | ✅ |\n| TC-003 | test-cases\u002Fcase-003-partial-overlap-ai-reviewers.md | Partial overlap: ai-reviewer vs ai-safety-reviewer | ✅ |\n| TC-004 | test-cases\u002Fcase-004-false-positive-audit-name.md | False positive: same word in name, different domain | ✅ |\n| TC-005 | test-cases\u002Fcase-005-ecosystem-experiment-ab-test.md | Ecosystem: experiment-design vs ab-test-design | ✅ |\n| TC-006 | test-cases\u002Fcase-006-ecosystem-ai-feature-safety.md | Ecosystem: ai-feature-validation vs ai-safety-review | ✅ |\n| TC-007 | test-cases\u002Fcase-007-ecosystem-messaging-safety.md | Ecosystem: ai-messaging-review vs ai-safety-review | ✅ |\n| TC-008 | test-cases\u002Fcase-008-no-duplicates.md | No duplicates: 3 skills in different domains | ✅ |\n| TC-009 | test-cases\u002Fcase-009-large-list.md | Large list: 5 skills, 1 true duplicate, 1 partial overlap | ✅ |\n| TC-010 | test-cases\u002Fcase-010-low-context.md | Low context: skill names only, no triggers provided | ✅ |\n\n## Evaluation History\n\n| Version | Date | Score | Recommendation | Report |\n| --- | --- | --- | --- | --- |\n| v0.1 | 2026-06-14 | 88 | Approved — promotion proposal pending | evaluations\u002Fskills\u002Fskill-duplication-audit\u002Feval-001.md |\n","# skill-duplication-audit\n\n## Problem\n\nSkills across the 5 ecosystem repositories overlap in scope without documented distinctions. This creates confusion about which skill to invoke, silent redundancy in packs, and conflicting guidance when two skills are active in the same session. Without a structured way to detect and classify overlaps, the ecosystem grows noisier over time.\n\n## Objective\n\nGiven 2 or more skills with their triggers and objectives, identify pairs that have overlapping scope and classify each pair. Produce a duplication report with a classification and a specific recommendation for each pair.\n\n## When to Use\n\n- When adding a new skill and checking whether an existing skill already covers the same use case\n- When auditing a pack for internal redundancy\n- When comparing skills across packs after an ecosystem audit\n- When a user reports confusion about which of two skills to invoke\n\n## When NOT to Use\n\n- For a single skill — needs at least 2 skills to compare\n- For agents — agents have tool scope and state, not just trigger scope; use a separate analysis\n- When the boundary is already documented in an existing boundary doc — verify first\n- When the skills are from completely different domains with no plausible trigger overlap\n\n## Inputs\n\n| Input | Required | Description |\n| --- | --- | --- |\n| skill-list | required | 2+ skills, each with: name, trigger (when to use), objective (one sentence), and optionally the repo |\n| scope | optional | `pack` (compare within one repo) or `ecosystem` (compare across repos). Default: `ecosystem` |\n\n## Outputs\n\n| Output | Description |\n| --- | --- |\n| duplication-report | List of pairs with classification and recommendation |\n| boundary-docs-needed | List of pairs requiring a documented distinction (partial-overlap pairs only) |\n\n## Steps\n\n1. Read all inputs. For each skill, extract: name, trigger (what situation invokes it?), objective (what does it produce?).\n2. Group skills by domain. Only compare skills where triggers could plausibly describe the same situation.\n3. For each pair within the same domain, compare triggers and outputs:\n   - **Triggers:** do they describe the same situation or context?\n   - **Outputs:** do they produce the same type of result?\n4. Classify each pair using exactly one label:\n   - **True duplicate:** same trigger AND same output type → recommend merge\n   - **Partial overlap:** triggers overlap but differ, OR outputs overlap but differ → recommend document boundary\n   - **Complementary:** same domain, different workflow stage, no trigger overlap → keep both, note relationship\n   - **False positive:** similar name but different trigger and output → no action required\n5. For each partial-overlap pair, draft a one-sentence boundary statement: \"Use [A] when [condition A]; use [B] when [condition B].\"\n6. List pairs that need a boundary doc (partial-overlap only).\n7. Fill the Completion Statement.\n\n## Completion Statement Format\n\n```text\nskill-duplication-audit complete.\nSkills analysed: [count]\nPairs evaluated: [count]\nTrue duplicates: [count] — [names or NONE]\nPartial overlaps: [count] — [names or NONE]\nComplementary pairs: [count] — [names or NONE]\nFalse positives: [count] — [names or NONE]\nBoundary docs needed: [count] — [skill pairs or NONE]\nRecommendation: [summary action]\n```\n\n## Red Flags\n\n- \"These two skills have similar names so they must be duplicates\" — name similarity is not scope overlap; compare triggers and outputs, not names\n- \"I'll merge them to reduce complexity\" — merging loses scope distinctions; only recommend a merge if triggers AND outputs are genuinely identical\n- \"The boundary is obvious so it doesn't need documentation\" — undocumented boundaries get violated; if there is overlap, document it\n- \"They're in different repos so they can't conflict\" — cross-repo skills are the most common source of undocumented overlap in the ecosystem\n- \"I'll classify as partial overlap to be safe\" — over-classifying creates unnecessary boundary docs; only classify as partial overlap if trigger overlap is real and observable\n\n## Examples\n\n### Example 1 — True duplicate\n\n**Input:**\n- api-doc-writer: trigger \"when writing documentation for a REST API\", objective \"produce API reference docs\"\n- api-reference-generator: trigger \"when documenting a REST API\", objective \"generate API reference documentation\"\n\n**Expected output:** True duplicate. Triggers and outputs are semantically identical. Recommend merge. Keep the skill with stronger test coverage.\n\n### Example 2 — Complementary\n\n**Input:**\n- prd-quality-gate (builder-product): trigger \"when a PRD is drafted and ready for engineering review\", objective \"gate PRD quality before handoff\"\n- copy-quality-gate (builder-growth): trigger \"when landing page copy is written\", objective \"gate copy quality before publishing\"\n\n**Expected output:** Complementary. Same quality gate pattern, different domains (product vs. growth), no trigger overlap. No action needed.\n\n## Counter-Examples\n\n### Counter-Example 1 — False positive mistakenly treated as duplicate\n\n**Input:**\n- design-token-audit (builder-design): trigger \"when reviewing design token consistency across components\"\n- positioning-audit (builder-growth): trigger \"when evaluating brand positioning and messaging clarity\"\n\n**What should happen:** False positive. \"Audit\" in the name is irrelevant — triggers are in completely different domains. No action.\n\n**What the skill must NOT do:** Recommend a merge or boundary doc based on shared vocabulary alone.\n\n### Counter-Example 2 — Complementary pair forced into partial-overlap\n\n**Input:**\n- eval-before-ship (builder-ai): trigger \"before deploying an LLM model or prompt to production\"\n- prd-quality-gate (builder-product): trigger \"when a PRD is drafted and ready for engineering review\"\n\n**What should happen:** Complementary — different stages of the product lifecycle, no trigger overlap.\n\n**What the skill must NOT do:** Classify these as partial-overlap because both are \"gates\" in an AI product workflow.\n\n## Test Cases\n\n| ID | File | Description | Pass |\n| --- | --- | --- | --- |\n| TC-001 | test-cases\u002Fcase-001-true-duplicate.md | True duplicate: identical trigger and output type | ✅ |\n| TC-002 | test-cases\u002Fcase-002-complementary-quality-gates.md | Complementary: prd-quality-gate vs copy-quality-gate | ✅ |\n| TC-003 | test-cases\u002Fcase-003-partial-overlap-ai-reviewers.md | Partial overlap: ai-reviewer vs ai-safety-reviewer | ✅ |\n| TC-004 | test-cases\u002Fcase-004-false-positive-audit-name.md | False positive: same word in name, different domain | ✅ |\n| TC-005 | test-cases\u002Fcase-005-ecosystem-experiment-ab-test.md | Ecosystem: experiment-design vs ab-test-design | ✅ |\n| TC-006 | test-cases\u002Fcase-006-ecosystem-ai-feature-safety.md | Ecosystem: ai-feature-validation vs ai-safety-review | ✅ |\n| TC-007 | test-cases\u002Fcase-007-ecosystem-messaging-safety.md | Ecosystem: ai-messaging-review vs ai-safety-review | ✅ |\n| TC-008 | test-cases\u002Fcase-008-no-duplicates.md | No duplicates: 3 skills in different domains | ✅ |\n| TC-009 | test-cases\u002Fcase-009-large-list.md | Large list: 5 skills, 1 true duplicate, 1 partial overlap | ✅ |\n| TC-010 | test-cases\u002Fcase-010-low-context.md | Low context: skill names only, no triggers provided | ✅ |\n\n## Evaluation History\n\n| Version | Date | Score | Recommendation | Report |\n| --- | --- | --- | --- | --- |\n| v0.1 | 2026-06-14 | 88 | Approved — promotion proposal pending | evaluations\u002Fskills\u002Fskill-duplication-audit\u002Feval-001.md |\n",{"name":5,"owner":38,"score":39,"state":40,"target":41,"created":42,"updated":42,"version":43,"description":7,"compliance-risk":44},"Miguel",88,"Approved","a-team",1781395200000,"v0.1","Low","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fskill-duplication-audit",483,"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-13 02:16:32",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-duplication-audit",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-duplication-audit",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-duplication-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FRBraga01\u002Fa-team\u002Fskills\u002Fskill-duplication-audit\u002FSKILL.md",true,[],[70,78,85,92,119,144],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":77},"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":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":77},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":77},"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":33},"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",[],[99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":33},"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",[],[126,127,128,114,129,130,131,132,133,134,135,136,137,138,104,139,140,141,142,143],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":157,"publishedAt":33},"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",[150,153,154],{"categoryNo":151,"categoryName":152,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[146,158,159,160,161,162,163,140,164,105,165,166,167,168,110,169,170,171,172,173],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]