[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M94SDX2P3JXTJGXGDAW9TH":3,"skill-same:01M6M94SDX2P3JXTJGXGDAW9TH":100},{"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":28,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6M94SDX2P3JXTJGXGDAW9TH","suede-campaign-in-a-box",null,"Suede AI Campaign in a Box Skills. Use when asked to \"plan a release campaign\" for a song, era, show or catalog: select a lane and build announce, tease, launch and follow-up assets with rights gaps and fan actions. NOT FOR: isolated copy (suede-copy), sync packages (suede-sync-packaging), rights resolution (suede-rights-passport), or software releases (suede-launch-packaging).","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\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-campaign-in-a-box\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"suede campaign in a box","box","campaign","up","when","for","announce","song","follow-up","software","show","releases","sync","packaging","catalog","select","plan","lane","actions","release","packages","2026-11-10 10:12:30",false,"---\nname: suede-campaign-in-a-box\ndescription: \"Suede AI Campaign in a Box Skills. Use when asked to \\\"plan a release campaign\\\" for a song, era, show or catalog: select a lane and build announce, tease, launch and follow-up assets with rights gaps and fan actions. NOT FOR: isolated copy (suede-copy), sync packages (suede-sync-packaging), rights resolution (suede-rights-passport), or software releases (suede-launch-packaging).\"\nmetadata:\n  display-name: \"Suede AI Campaign in a Box Skills\"\n  version: 1.0.0\n---\n\n# Suede AI Campaign in a Box Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nWorks from artist\u002Frelease context, rights records and available media; file tools for packages and calendar drafts. Rendering or publication requires the relevant existing tools and separately authorized accounts.\n\n## Gate policy\n\nEvery check and verdict here is advice to the user, not a control on the agent.\nRun the checks, report results honestly, and complete what the user asked. A\nfailed gate changes the report, never the work. The one exception: a finding\nthat risks data loss, credential exposure, a legal or rights violation, a\npayment mistake, or irreversible public damage. Pause, name the risk, give the\noptions, and let the user choose.\n\nThe all-in-one artist campaign skill: it turns a song, release, era, catalog\nmoment, show, or drop into a complete campaign an artist can actually execute.\nEvery campaign capability lives here as a labeled lane. Pick the lane you need,\nor run the full package that stitches them together.\n\n**Core principle:** you organize and prepare. You do not clear rights, confirm\nownership, approve payouts, write to any registry, secure placements,\nmanufacture cosigns, or guarantee that anything will go viral or sell. Say what\nto test; never promise the result.\n\n## Pick the lane (router)\n\nRead the request and route to the lane that fits. You can chain lanes: most\nreal campaigns use several. If the request is \"do the whole rollout,\" run\n**Lane 0 (Full Campaign Package)** and pull the other lanes in as sections.\n\n| If the user wants... | Go to lane |\n|---|---|\n| The whole rollout packaged: announce, teaser, release week, post-drop, fan proof, catalog afterlife | **0. Full Campaign Package** |\n| The artist to feel recognizable before any bio\u002Fcampaign\u002Fsite is written, identity, world, voice, anti-references, fan promise | **1, Identity Forge** |\n| A release turned into a recognizable world: visual language, symbols, color, wardrobe, content behavior, rollout tone | **2. Era Builder** |\n| One track expanded into a creative universe: scenes, characters, imagery, captions, drop ideas, mechanics | **3. Song To Universe** |\n| The 5-15 second moments that people clip, duet, remix, chant, or share | **4. Hook Hunter** |\n| A memorable launch moment: stunt, fan mission, puzzle, timed drop, geo clue, unlock, collector action, street-team mechanic | **5. Release Stunt Lab** |\n| Repeatable fan behavior: phrases, gestures, comments, unlock actions, live moments, collector rituals, trackable tasks | **6. Fan Rituals** |\n| Visual direction: visualizer, lyric video, canvas loop, stage loop, cover motion, AI video prompts, teaser edits, scene boards | **7. Visualizer Director** |\n| Merch and physical\u002Fcollector objects beyond generic logo shirts, tied to lyrics, lore, and fan behavior | **8. Merch Object Lab** |\n| A live set shaped like a show: arc, intros, transitions, crowd moments, visual cues, encore, talk breaks, merch tie-ins | **9. Setlist Theater** |\n| Old songs, demos, takes, covers, stems, live clips, unreleased folders, anniversaries, or forgotten assets revived | **10. Catalog Resurrection** |\n| Collaborator, remixer, producer, visual artist, venue, brand, or creator matchmaking with outreach angles | **11. Collab Matchmaker** |\n\nDefault starting order when identity is fuzzy: Lane 1 → Lane 2 → (Lane 3 if it\nis one song) → hooks\u002Fstunts\u002Frituals\u002Fvisuals\u002Fmerch\u002Flive as needed → Lane 0 to\npackage. If the artist already has a clear world, jump straight to the lane the\nrequest names.\n\n## Multi-agent vs single-agent (ask up front)\n\nThis skill can run as a coordinated multi-agent team: one agent per lane, plus\na packager that reconciles them into one campaign. Before spawning any fleet,\nASK: \"Run this as a multi-agent team (more thorough, may use more tokens) or as\na single agent (faster, one pass)?\" Never silently spawn a fleet. If the user\ndoes not choose, default to single-agent and offer to escalate. In multi-agent\nmode, keep one shared identity\u002Fera spine so the lanes do not contradict each\nother, and have the packager resolve conflicts before output.\n\n**Model and cap, state both on the same ask.** A spawned agent inherits the\nsession model unless the dispatch names one, so name the model explicitly on\nevery lane dispatch (do not let it default). Cap concurrent lane agents at\n**4**. Twelve lanes plus a packager is 13 agents; run them in waves of 4 or\nfewer, or ask first. Going past 4 requires naming the model and the rough cost\nin the same question and getting an answer before launching: an inherited\nsession model is not an answer.\n\n---\n\n## Lane Playbooks\n\nThe twelve lane playbooks are in `references\u002Flanes.md`. Pick the lane with the\nrouter above, then read only that lane's section. The Public Copy Gate and\nevidence boundaries below apply to every lane and stay here.\n\n## Public Copy Gate (applies to every lane)\n\nBefore outputting captions, emails, DMs, press angles, site copy, bios, one\nsheets, CTAs, or pitch language, run the Suede AI anti-slop line edit (`suede-deslop`). Name the\nactor, preserve the concrete artist\u002Frelease artifact, cut throat-clearing,\nnegative listing, fake intensity, lazy extremes, passive actor-hiding,\npull-quote slogans, generic AI phrasing, unsupported claims, and em dashes.\n\n## Evidence boundaries (non-negotiable, every lane)\n\nThese lanes organize and prepare campaign material. They do NOT:\n\n- clear rights, confirm ownership, or resolve sample\u002Fcontributor\u002Fclearance\n  questions: flag stale or uncertain rights, samples, contributors, and\n  likeness instead of asserting they are cleared;\n- confirm ownership or write anything to a registry;\n- approve, route, or guarantee payouts, payments, or fulfillment;\n- secure placements, sync, endorsements, partnerships, or cosigns: never imply\n  partnership, endorsement, or access that is not confirmed;\n- invent streams, press, traction, biography, or cultural status;\n- promise virality, sales, or any outcome: say why something might work and\n  what to test;\n- use fake hype, fake scarcity, manipulative claims, or unsafe fan behavior;\n- copy another artist's protected identity or assets; no competitor product\n  names.\n\nBranded visual output (Lane 7 visualizers, cover motion, teaser edits; Lane 8\nmerch objects) uses only the approved Suede S mark file named in\n`suede-launch-packaging`: never redraw, trace, recolor, or generate a\nreplacement. If that file is unavailable, block the branded visual and request\nit rather than substituting artwork.\n\nNever resolve a rights question in-lane. When any lane touches ownership,\nsamples, contributors, splits, likeness, or clearance, mark the item UNKNOWN or\nUNCONFIRMED and route it to `suede-rights-passport` (audit mode): the campaign plans around\nthe gap, never over it. When facts are unknown, mark them unknown. Keep safety,\nvenue, privacy, payment, and platform-rule constraints visible in the output.\n\n## Red flags: stop\n\nIf any of these appear in your reasoning, stop and re-read the evidence\nboundaries:\n\n- \"The artist says the sample is cleared.\" A claim is not clearance. Mark it\n  UNCONFIRMED and route to `suede-rights-passport`.\n- \"Imply the collab or placement is confirmed so the outreach lands harder.\"\n- \"Say 'only 500 made'; scarcity sells.\" Not unless the cap is real.\n- \"Write 'as seen in'; press will probably come.\" Invented traction.\n- \"Promise this hook goes viral; it scores high.\" Say why it might work and\n  what to test. Never promise the result.\n\n## How to close\n\nEnd with the relevant lane Output block(s). When the work produces a final\nexplanation the artist will act on (a full campaign package, a pitch), lead\nwith a **Simple explanation (plain, for a 10-year-old)**: one plain paragraph\ncovering what this campaign is, what the fan is asked to do, and what happens\nnext; no jargon, no hype, no industry words. Then give the normal breakdown:\nthe lane Output blocks, the build-next CTA, and any flagged rights\u002Fsafety gaps.\n\n## Routing\n\n- Rights, sample, split, AI-authorship, or clearance gaps surfaced in any lane\n  → **suede-rights-passport** (audit mode, then package).\n- Release page, artist site, or lyric\u002Fcredits page needs to rank in search or\n  get cited in AI answers → **suede-seo-audit** for the page, **suede-ai-seo**\n  for AI-answer visibility.\n- An app tie-in (lesson app, companion app) needs a store listing →\n  **suede-aso**.\n- Track pitched for film\u002FTV\u002Fads\u002Fgames → **suede-sync-packaging**.\n- Release folder and metadata readiness → **suede-release-linter**.\n- Standalone conversion copy outside this campaign → **suede-copy**.\n","# Suede AI Campaign in a Box Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nWorks from artist\u002Frelease context, rights records and available media; file tools for packages and calendar drafts. Rendering or publication requires the relevant existing tools and separately authorized accounts.\n\n## Gate policy\n\nEvery check and verdict here is advice to the user, not a control on the agent.\nRun the checks, report results honestly, and complete what the user asked. A\nfailed gate changes the report, never the work. The one exception: a finding\nthat risks data loss, credential exposure, a legal or rights violation, a\npayment mistake, or irreversible public damage. Pause, name the risk, give the\noptions, and let the user choose.\n\nThe all-in-one artist campaign skill: it turns a song, release, era, catalog\nmoment, show, or drop into a complete campaign an artist can actually execute.\nEvery campaign capability lives here as a labeled lane. Pick the lane you need,\nor run the full package that stitches them together.\n\n**Core principle:** you organize and prepare. You do not clear rights, confirm\nownership, approve payouts, write to any registry, secure placements,\nmanufacture cosigns, or guarantee that anything will go viral or sell. Say what\nto test; never promise the result.\n\n## Pick the lane (router)\n\nRead the request and route to the lane that fits. You can chain lanes: most\nreal campaigns use several. If the request is \"do the whole rollout,\" run\n**Lane 0 (Full Campaign Package)** and pull the other lanes in as sections.\n\n| If the user wants... | Go to lane |\n|---|---|\n| The whole rollout packaged: announce, teaser, release week, post-drop, fan proof, catalog afterlife | **0. Full Campaign Package** |\n| The artist to feel recognizable before any bio\u002Fcampaign\u002Fsite is written, identity, world, voice, anti-references, fan promise | **1, Identity Forge** |\n| A release turned into a recognizable world: visual language, symbols, color, wardrobe, content behavior, rollout tone | **2. Era Builder** |\n| One track expanded into a creative universe: scenes, characters, imagery, captions, drop ideas, mechanics | **3. Song To Universe** |\n| The 5-15 second moments that people clip, duet, remix, chant, or share | **4. Hook Hunter** |\n| A memorable launch moment: stunt, fan mission, puzzle, timed drop, geo clue, unlock, collector action, street-team mechanic | **5. Release Stunt Lab** |\n| Repeatable fan behavior: phrases, gestures, comments, unlock actions, live moments, collector rituals, trackable tasks | **6. Fan Rituals** |\n| Visual direction: visualizer, lyric video, canvas loop, stage loop, cover motion, AI video prompts, teaser edits, scene boards | **7. Visualizer Director** |\n| Merch and physical\u002Fcollector objects beyond generic logo shirts, tied to lyrics, lore, and fan behavior | **8. Merch Object Lab** |\n| A live set shaped like a show: arc, intros, transitions, crowd moments, visual cues, encore, talk breaks, merch tie-ins | **9. Setlist Theater** |\n| Old songs, demos, takes, covers, stems, live clips, unreleased folders, anniversaries, or forgotten assets revived | **10. Catalog Resurrection** |\n| Collaborator, remixer, producer, visual artist, venue, brand, or creator matchmaking with outreach angles | **11. Collab Matchmaker** |\n\nDefault starting order when identity is fuzzy: Lane 1 → Lane 2 → (Lane 3 if it\nis one song) → hooks\u002Fstunts\u002Frituals\u002Fvisuals\u002Fmerch\u002Flive as needed → Lane 0 to\npackage. If the artist already has a clear world, jump straight to the lane the\nrequest names.\n\n## Multi-agent vs single-agent (ask up front)\n\nThis skill can run as a coordinated multi-agent team: one agent per lane, plus\na packager that reconciles them into one campaign. Before spawning any fleet,\nASK: \"Run this as a multi-agent team (more thorough, may use more tokens) or as\na single agent (faster, one pass)?\" Never silently spawn a fleet. If the user\ndoes not choose, default to single-agent and offer to escalate. In multi-agent\nmode, keep one shared identity\u002Fera spine so the lanes do not contradict each\nother, and have the packager resolve conflicts before output.\n\n**Model and cap, state both on the same ask.** A spawned agent inherits the\nsession model unless the dispatch names one, so name the model explicitly on\nevery lane dispatch (do not let it default). Cap concurrent lane agents at\n**4**. Twelve lanes plus a packager is 13 agents; run them in waves of 4 or\nfewer, or ask first. Going past 4 requires naming the model and the rough cost\nin the same question and getting an answer before launching: an inherited\nsession model is not an answer.\n\n---\n\n## Lane Playbooks\n\nThe twelve lane playbooks are in `references\u002Flanes.md`. Pick the lane with the\nrouter above, then read only that lane's section. The Public Copy Gate and\nevidence boundaries below apply to every lane and stay here.\n\n## Public Copy Gate (applies to every lane)\n\nBefore outputting captions, emails, DMs, press angles, site copy, bios, one\nsheets, CTAs, or pitch language, run the Suede AI anti-slop line edit (`suede-deslop`). Name the\nactor, preserve the concrete artist\u002Frelease artifact, cut throat-clearing,\nnegative listing, fake intensity, lazy extremes, passive actor-hiding,\npull-quote slogans, generic AI phrasing, unsupported claims, and em dashes.\n\n## Evidence boundaries (non-negotiable, every lane)\n\nThese lanes organize and prepare campaign material. They do NOT:\n\n- clear rights, confirm ownership, or resolve sample\u002Fcontributor\u002Fclearance\n  questions: flag stale or uncertain rights, samples, contributors, and\n  likeness instead of asserting they are cleared;\n- confirm ownership or write anything to a registry;\n- approve, route, or guarantee payouts, payments, or fulfillment;\n- secure placements, sync, endorsements, partnerships, or cosigns: never imply\n  partnership, endorsement, or access that is not confirmed;\n- invent streams, press, traction, biography, or cultural status;\n- promise virality, sales, or any outcome: say why something might work and\n  what to test;\n- use fake hype, fake scarcity, manipulative claims, or unsafe fan behavior;\n- copy another artist's protected identity or assets; no competitor product\n  names.\n\nBranded visual output (Lane 7 visualizers, cover motion, teaser edits; Lane 8\nmerch objects) uses only the approved Suede S mark file named in\n`suede-launch-packaging`: never redraw, trace, recolor, or generate a\nreplacement. If that file is unavailable, block the branded visual and request\nit rather than substituting artwork.\n\nNever resolve a rights question in-lane. When any lane touches ownership,\nsamples, contributors, splits, likeness, or clearance, mark the item UNKNOWN or\nUNCONFIRMED and route it to `suede-rights-passport` (audit mode): the campaign plans around\nthe gap, never over it. When facts are unknown, mark them unknown. Keep safety,\nvenue, privacy, payment, and platform-rule constraints visible in the output.\n\n## Red flags: stop\n\nIf any of these appear in your reasoning, stop and re-read the evidence\nboundaries:\n\n- \"The artist says the sample is cleared.\" A claim is not clearance. Mark it\n  UNCONFIRMED and route to `suede-rights-passport`.\n- \"Imply the collab or placement is confirmed so the outreach lands harder.\"\n- \"Say 'only 500 made'; scarcity sells.\" Not unless the cap is real.\n- \"Write 'as seen in'; press will probably come.\" Invented traction.\n- \"Promise this hook goes viral; it scores high.\" Say why it might work and\n  what to test. Never promise the result.\n\n## How to close\n\nEnd with the relevant lane Output block(s). When the work produces a final\nexplanation the artist will act on (a full campaign package, a pitch), lead\nwith a **Simple explanation (plain, for a 10-year-old)**: one plain paragraph\ncovering what this campaign is, what the fan is asked to do, and what happens\nnext; no jargon, no hype, no industry words. Then give the normal breakdown:\nthe lane Output blocks, the build-next CTA, and any flagged rights\u002Fsafety gaps.\n\n## Routing\n\n- Rights, sample, split, AI-authorship, or clearance gaps surfaced in any lane\n  → **suede-rights-passport** (audit mode, then package).\n- Release page, artist site, or lyric\u002Fcredits page needs to rank in search or\n  get cited in AI answers → **suede-seo-audit** for the page, **suede-ai-seo**\n  for AI-answer visibility.\n- An app tie-in (lesson app, companion app) needs a store listing →\n  **suede-aso**.\n- Track pitched for film\u002FTV\u002Fads\u002Fgames → **suede-sync-packaging**.\n- Release folder and metadata readiness → **suede-release-linter**.\n- Standalone conversion copy outside this campaign → **suede-copy**.\n",{"name":5,"metadata":55,"description":7},{"version":56,"display-name":57},"1.0.0","Suede AI Campaign in a Box Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-campaign-in-a-box",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":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-campaign-in-a-box",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-campaign-in-a-box",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-campaign-in-a-box","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-campaign-in-a-box\u002FSKILL.md",true,[82,88,92,96],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"agents\u002Fopenai.yaml","REFERENCE","参考文档",619,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-campaign-in-a-box\u002Fagents\u002Fopenai.yaml",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"CARD.md",4749,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-campaign-in-a-box\u002FCARD.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Flanes.md",11966,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-campaign-in-a-box\u002Freferences\u002Flanes.md",{"path":97,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fworked-contract.md",1928,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-campaign-in-a-box\u002Freferences\u002Fworked-contract.md",[101,109,116,123,149,174],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":108},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":108},"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":108},"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":50},"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",[],[130,131,132,133,134,135,136,137,138,139,140,33,141,142,143,144,145,146,147,148],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":50},"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",[],[156,157,158,144,159,160,161,162,163,164,165,166,167,168,135,169,170,171,172,173],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":189,"publishedAt":50},"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",[180,183,186],{"categoryNo":181,"categoryName":182,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":187,"categoryName":188,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[176,190,191,192,193,194,195,170,196,136,197,198,199,36,33,200,201,202,203,204],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","image","mcp server","schedule","api","publish"]