[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MF46JHGQM8TY2TZDZJAEFN":3,"skill-same:01M6MF46JHGQM8TY2TZDZJAEFN":76},{"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},"01M6MF46JHGQM8TY2TZDZJAEFN","cometchat-android-v6-events",null,"React to what the CometChat Android v6 UI Kit is doing — the CometChatEvents SharedFlow bus (message, call, conversation, group, user and UI events), how to collect it in Compose vs XML Views with correct lifecycle scoping, and when to use UI-Kit events versus Chat SDK listeners. Triggers: 'listen for message sent android cometchat', 'cometchat events android', 'know when a call is accepted', 'react when a group is created', 'sdk listener vs uikit event'.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-android-v6-events\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","cometchat android v6 events","events","android","message","when","listeners","for","verified","kit","event","how to","jvm","conversation","compose","scoping","correct","how","lifecycle","collect","ui","chat sdk","react","2026-11-10 10:12:30",false,"---\nname: cometchat-android-v6-events\ndescription: \"React to what the CometChat Android v6 UI Kit is doing — the CometChatEvents SharedFlow bus (message, call, conversation, group, user and UI events), how to collect it in Compose vs XML Views with correct lifecycle scoping, and when to use UI-Kit events versus Chat SDK listeners. Triggers: 'listen for message sent android cometchat', 'cometchat events android', 'know when a call is accepted', 'react when a group is created', 'sdk listener vs uikit event'.\"\nlicense: \"MIT\"\ncompatibility: \"Android minSdk >=28; compileSdk >=36; Kotlin >=2.1; AGP >=8.9.1; JVM target 11; com.cometchat:chatuikit-kotlin-android ^6 OR com.cometchat:chatuikit-compose-android ^6 (6.0.x, verified 6.0.5); com.cometchat:chat-sdk-android ^5\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat android events v6 sharedflow lifecycle compose views\"\n---\n\n> **Ground truth:** catalog `android-v6.json` + the live pages `events` (the API reference) and `customization-events`. `CometChatEvents` lives in `chatuikit-core-android` (`com.cometchat.uikit.core.events.CometChatEvents`). Verify symbols against the catalog; fetch the exact sealed-class members from the docs page — the event lists below are a MAP, the page is the manual.\n\n## Companion skills (read first)\n- `cometchat-android-v6-core` — install, credentials, `initFromSettings → login → render`, the fetch map. Assumed here, never repeated.\n- `cometchat-android-v6-{kotlin,compose}-customization` — click\u002Fselection callbacks on a single component (usually the simpler answer than the global bus).\n\n## Use this skill when\n\"tell me when a message is sent\u002Fedited\u002Fdeleted\", \"run code when a call is accepted\", \"update my own badge when a conversation changes\", \"hook into group\u002Fmember changes\", \"what's the difference between an SDK listener and a UI Kit event?\".\n\n## Prerequisites & install\nSame kit + init as `core`. `CometChatEvents` ships in `chatuikit-core-android` (already a transitive dependency of both cohort artifacts) — nothing to add.\n\n## The event bus (BAKED map — fetch the page for each sealed class's members)\nAll events come from the **`CometChatEvents` singleton**; each domain exposes a **`SharedFlow`** of a sealed class:\n\n| Flow | Sealed class | What it covers |\n|---|---|---|\n| `CometChatEvents.messageEvents` | `CometChatMessageEvent` | sent · edited · deleted · read · live reaction · interactive\u002Fcard\u002Fform\u002Fscheduler received |\n| `CometChatEvents.callEvents` | `CometChatCallEvent` | call initiated · accepted · rejected · ended |\n| `CometChatEvents.conversationEvents` | `CometChatConversationEvent` | conversation deleted · updated |\n| `CometChatEvents.groupEvents` | `CometChatGroupEvent` | group created\u002Fdeleted · member changes |\n| `CometChatEvents.userEvents` | `CometChatUserEvent` | user blocked · unblocked |\n| `CometChatEvents.uiEvents` | `CometChatUIEvent` | panel visibility · active-chat changes |\n\nMember shapes are **prefixed too** and the message ones repeat the domain: `CometChatMessageEvent.MessageSent(message, status)` (status `IN_PROGRESS`\u002F`SUCCESS`\u002F`ERROR`) · `MessageEdited` · `MessageDeleted` · `MessageRead` · `TextMessageReceived` · `TypingStarted` · `ReactionAdded`. There is no `.Sent` — it is `.MessageSent`. Import the sealed class from `com.cometchat.uikit.core.events`. Full list: fetch `\u002Fui-kit\u002Fandroid\u002Fcustomization-events.md` (NOT `events.md`, which still teaches the old un-prefixed shape).\n\n## Subscribing per cohort (lifecycle is the whole point)\n**Kotlin XML Views** — collect in `lifecycleScope`; the coroutine is cancelled when the lifecycle owner is destroyed:\n```kotlin\nimport androidx.lifecycle.lifecycleScope       \u002F\u002F in an Activity\u002FFragment\nimport kotlinx.coroutines.launch\nimport com.cometchat.uikit.core.events.CometChatEvents\nimport com.cometchat.uikit.core.events.CometChatMessageEvent\n\nlifecycleScope.launch {\n    CometChatEvents.messageEvents.collect { event ->\n        when (event) {\n            is CometChatMessageEvent.MessageSent -> { \u002F* event.message, event.status *\u002F }\n            is CometChatMessageEvent.MessageDeleted -> { \u002F* event.message *\u002F }\n            else -> Unit\n        }\n    }\n}\n```\n**Jetpack Compose** — collect in `LaunchedEffect`; cancelled when the composable leaves composition:\n```kotlin\nLaunchedEffect(Unit) {\n    CometChatEvents.messageEvents.collect { event -> \u002F* when (event) { … } *\u002F }\n}\n```\n> **No manual removal needed.** Unlike the old static-listener pattern, `SharedFlow` collection is scoped — do NOT invent an `addListener`\u002F`removeListener` pair for `CometChatEvents`. Just don't collect outside a lifecycle-aware scope (a bare `GlobalScope.launch` IS a leak).\n\n## UI-Kit events vs Chat SDK listeners (pick the right bus)\n| | **UI-Kit events** (`CometChatEvents.*`) | **Chat SDK listeners** (`CometChat.add*Listener`) |\n|---|---|---|\n| Source | UI Kit components (what the UI just did) | the CometChat server (what arrived) |\n| Direction | component → component | server → client |\n| Registration | `.collect {}` in a lifecycle scope | `add*Listener(ID, …)` + **`remove*Listener(ID)` on teardown** |\n| Use for | \"the user sent\u002Fedited a message\", \"a call was accepted\", panel\u002Factive-chat changes | incoming messages, presence, typing, connection status, incoming calls |\n**Both are needed for a full app.** If you're reacting to something the server pushed while your UI didn't do it, that's an SDK listener (→ `core\u002Freferences\u002Fdocs-map.md` SDK section, or `cometchat-android-v5-sdk`) — and SDK listeners DO require explicit removal in `onDestroy`\u002F`onDispose`\u002F`onCleared`.\n\n## Common pitfalls\nCollecting on a non-lifecycle scope (leak) · inventing `CometChatEvents.addListener`\u002F`removeListener` (doesn't exist — it's a flow) · using a UI-Kit event to detect *incoming* messages (use an SDK message listener) · registering an SDK listener and never removing it · a `when` without an `else` branch breaking on a new sealed member · re-collecting the same flow in several places and double-handling · guessing a sealed-class case name instead of fetching the events page.\n\n## Verify it works\nCompile against the pinned kit (`.\u002Fgradlew :app:assembleDebug   # in YOUR app (npm run verify:fences:android-v6 is a pack-repo gate)`). On device: trigger the action (send\u002Fedit\u002Fdelete a message, accept a call) and confirm your handler runs exactly once; rotate the screen \u002F navigate away and back — no duplicate handling and no crash (proves the scope is right); for any SDK listener you added, confirm the matching remove runs on teardown.\n","> **Ground truth:** catalog `android-v6.json` + the live pages `events` (the API reference) and `customization-events`. `CometChatEvents` lives in `chatuikit-core-android` (`com.cometchat.uikit.core.events.CometChatEvents`). Verify symbols against the catalog; fetch the exact sealed-class members from the docs page — the event lists below are a MAP, the page is the manual.\n\n## Companion skills (read first)\n- `cometchat-android-v6-core` — install, credentials, `initFromSettings → login → render`, the fetch map. Assumed here, never repeated.\n- `cometchat-android-v6-{kotlin,compose}-customization` — click\u002Fselection callbacks on a single component (usually the simpler answer than the global bus).\n\n## Use this skill when\n\"tell me when a message is sent\u002Fedited\u002Fdeleted\", \"run code when a call is accepted\", \"update my own badge when a conversation changes\", \"hook into group\u002Fmember changes\", \"what's the difference between an SDK listener and a UI Kit event?\".\n\n## Prerequisites & install\nSame kit + init as `core`. `CometChatEvents` ships in `chatuikit-core-android` (already a transitive dependency of both cohort artifacts) — nothing to add.\n\n## The event bus (BAKED map — fetch the page for each sealed class's members)\nAll events come from the **`CometChatEvents` singleton**; each domain exposes a **`SharedFlow`** of a sealed class:\n\n| Flow | Sealed class | What it covers |\n|---|---|---|\n| `CometChatEvents.messageEvents` | `CometChatMessageEvent` | sent · edited · deleted · read · live reaction · interactive\u002Fcard\u002Fform\u002Fscheduler received |\n| `CometChatEvents.callEvents` | `CometChatCallEvent` | call initiated · accepted · rejected · ended |\n| `CometChatEvents.conversationEvents` | `CometChatConversationEvent` | conversation deleted · updated |\n| `CometChatEvents.groupEvents` | `CometChatGroupEvent` | group created\u002Fdeleted · member changes |\n| `CometChatEvents.userEvents` | `CometChatUserEvent` | user blocked · unblocked |\n| `CometChatEvents.uiEvents` | `CometChatUIEvent` | panel visibility · active-chat changes |\n\nMember shapes are **prefixed too** and the message ones repeat the domain: `CometChatMessageEvent.MessageSent(message, status)` (status `IN_PROGRESS`\u002F`SUCCESS`\u002F`ERROR`) · `MessageEdited` · `MessageDeleted` · `MessageRead` · `TextMessageReceived` · `TypingStarted` · `ReactionAdded`. There is no `.Sent` — it is `.MessageSent`. Import the sealed class from `com.cometchat.uikit.core.events`. Full list: fetch `\u002Fui-kit\u002Fandroid\u002Fcustomization-events.md` (NOT `events.md`, which still teaches the old un-prefixed shape).\n\n## Subscribing per cohort (lifecycle is the whole point)\n**Kotlin XML Views** — collect in `lifecycleScope`; the coroutine is cancelled when the lifecycle owner is destroyed:\n```kotlin\nimport androidx.lifecycle.lifecycleScope       \u002F\u002F in an Activity\u002FFragment\nimport kotlinx.coroutines.launch\nimport com.cometchat.uikit.core.events.CometChatEvents\nimport com.cometchat.uikit.core.events.CometChatMessageEvent\n\nlifecycleScope.launch {\n    CometChatEvents.messageEvents.collect { event ->\n        when (event) {\n            is CometChatMessageEvent.MessageSent -> { \u002F* event.message, event.status *\u002F }\n            is CometChatMessageEvent.MessageDeleted -> { \u002F* event.message *\u002F }\n            else -> Unit\n        }\n    }\n}\n```\n**Jetpack Compose** — collect in `LaunchedEffect`; cancelled when the composable leaves composition:\n```kotlin\nLaunchedEffect(Unit) {\n    CometChatEvents.messageEvents.collect { event -> \u002F* when (event) { … } *\u002F }\n}\n```\n> **No manual removal needed.** Unlike the old static-listener pattern, `SharedFlow` collection is scoped — do NOT invent an `addListener`\u002F`removeListener` pair for `CometChatEvents`. Just don't collect outside a lifecycle-aware scope (a bare `GlobalScope.launch` IS a leak).\n\n## UI-Kit events vs Chat SDK listeners (pick the right bus)\n| | **UI-Kit events** (`CometChatEvents.*`) | **Chat SDK listeners** (`CometChat.add*Listener`) |\n|---|---|---|\n| Source | UI Kit components (what the UI just did) | the CometChat server (what arrived) |\n| Direction | component → component | server → client |\n| Registration | `.collect {}` in a lifecycle scope | `add*Listener(ID, …)` + **`remove*Listener(ID)` on teardown** |\n| Use for | \"the user sent\u002Fedited a message\", \"a call was accepted\", panel\u002Factive-chat changes | incoming messages, presence, typing, connection status, incoming calls |\n**Both are needed for a full app.** If you're reacting to something the server pushed while your UI didn't do it, that's an SDK listener (→ `core\u002Freferences\u002Fdocs-map.md` SDK section, or `cometchat-android-v5-sdk`) — and SDK listeners DO require explicit removal in `onDestroy`\u002F`onDispose`\u002F`onCleared`.\n\n## Common pitfalls\nCollecting on a non-lifecycle scope (leak) · inventing `CometChatEvents.addListener`\u002F`removeListener` (doesn't exist — it's a flow) · using a UI-Kit event to detect *incoming* messages (use an SDK message listener) · registering an SDK listener and never removing it · a `when` without an `else` branch breaking on a new sealed member · re-collecting the same flow in several places and double-handling · guessing a sealed-class case name instead of fetching the events page.\n\n## Verify it works\nCompile against the pinned kit (`.\u002Fgradlew :app:assembleDebug   # in YOUR app (npm run verify:fences:android-v6 is a pack-repo gate)`). On device: trigger the action (send\u002Fedit\u002Fdelete a message, accept a call) and confirm your handler runs exactly once; rotate the screen \u002F navigate away and back — no duplicate handling and no crash (proves the scope is right); for any SDK listener you added, confirm the matching remove runs on teardown.\n",{"name":5,"license":15,"metadata":47,"description":7,"compatibility":51},{"tags":48,"author":49,"version":50},"cometchat android events v6 sharedflow lifecycle compose views","CometChat","1.0.0","Android minSdk >=28; compileSdk >=36; Kotlin >=2.1; AGP >=8.9.1; JVM target 11; com.cometchat:chatuikit-kotlin-android ^6 OR com.cometchat:chatuikit-compose-android ^6 (6.0.x, verified 6.0.5); com.cometchat:chat-sdk-android ^5","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-android-v6-events",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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-android-v6-events",{"tool":68,"command":69},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-android-v6-events",{"tool":71,"command":72},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-android-v6-events","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-android-v6-events\u002FSKILL.md",true,[],[77,86,93,100,126,151],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"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.","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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"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":81,"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":81,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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",[],[107,108,109,110,111,112,113,114,115,116,117,24,118,119,120,121,122,123,124,125],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"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",[],[133,134,135,121,136,137,138,139,140,141,142,143,144,145,112,146,147,148,149,150],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":168,"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",[157,162,165],{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":163,"categoryName":164,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":166,"categoryName":167,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000010","后端与接口",[153,169,170,171,172,173,174,147,175,113,176,177,178,179,24,180,181,182,183,184],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]