[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFF0C3Y0V0J1ZZHPZNN4MP":3,"skill-same:01M6MFF0C3Y0V0J1ZZHPZNN4MP":91},{"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":34,"publishedAt":57,"linkOnly":58,"markdownContent":59,"markdownBody":60,"frontMatter":61,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":74,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M6MFF0C3Y0V0J1ZZHPZNN4MP","cometchat-moderation",null,"Trust & Safety for CometChat — auto-moderate text\u002Fimage\u002Fvideo\u002Ffile with dashboard rules + keyword lists, block or flag-for-review, let users report messages, and keep an audit trail. Cross-family: rules\u002Flists\u002Fqueues are dashboard+REST; report\u002Fblock UI is built into each family's UI Kit. Triggers: 'add moderation', 'profanity filter', 'image moderation', 'block bad words', 'report a message', 'flag inappropriate content', 'content safety', 'spam\u002Fscam detection', 'CSAM\u002Fminor safety', 'malware scan attachments', 'moderation queue'.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-moderation\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56],"cometchat","cometchat moderation","moderation","audit trail","image","kit","spam","scam","filter","content safety","message","auto","text","Video","api","Safety","malware","messages","ui","audit","dashboard","review","2026-11-10 10:12:30",false,"---\nname: cometchat-moderation\ndescription: \"Trust & Safety for CometChat — auto-moderate text\u002Fimage\u002Fvideo\u002Ffile with dashboard rules + keyword lists, block or flag-for-review, let users report messages, and keep an audit trail. Cross-family: rules\u002Flists\u002Fqueues are dashboard+REST; report\u002Fblock UI is built into each family's UI Kit. Triggers: 'add moderation', 'profanity filter', 'image moderation', 'block bad words', 'report a message', 'flag inappropriate content', 'content safety', 'spam\u002Fscam detection', 'CSAM\u002Fminor safety', 'malware scan attachments', 'moderation queue'.\"\nlicense: \"MIT\"\ncompatibility: \"CometChat Moderation (dashboard rules\u002Flists + Flagged\u002FBlocked\u002FReviewed queues) · Moderation REST API v3 · per-family UI Kit report\u002Fblock + Chat SDK flagging.\"\nmetadata:\n  author: \"CometChat\"\n  version: \"1.0.0\"\n  tags: \"cometchat moderation trust-safety profanity image-moderation spam csam malware report flag audit\"\n---\n\n> **Ground truth:** capabilities and rule names are FETCHED from the live docs — `{DOCS_BASE}\u002Fmoderation\u002Foverview`, `\u002Fmoderation\u002F{rules-management,lists-management,flagged-messages,blocked-messages,reviewed-messages}`, `{DOCS_BASE}\u002Frest-api\u002Fmoderation-apis\u002Foverview`, and the client hooks `{DOCS_BASE}\u002Fui-kit\u002F\u003Cfamily>\u002Fcore-features#moderation` (built-in report) + `{DOCS_BASE}\u002Fsdk\u002F\u003Cplatform>\u002Fai-moderation` (SDK flagging). `DOCS_BASE = https:\u002F\u002Fwww.cometchat.com\u002Fdocs`; append `.md`. Most of this is dashboard configuration; verify the exact rule\u002Flist options and any REST shapes against the docs before asserting them.\n\n## Use this skill when\nMaking a chat safe\u002Fcompliant: profanity\u002Ftoxicity filtering, image\u002Fvideo safety, spam\u002Fscam detection, malware scanning of attachments, letting users report content, a moderator review queue, or an audit trail for T&S. Trust & Safety is a procurement gate for social, gaming, marketplace, dating, education and healthcare apps.\n\n## How it works\nEvery message runs through the **rule engine** as it's sent; a rule either lets it through, **blocks** it (hidden immediately), or **flags** it for a moderator. Users can also **report** a message manually, which flags it. Blocked\u002Fflagged items land in dashboard queues; a moderator's decision (approve\u002Fblock\u002Fmark reviewed) moves it to the audit trail.\n\n```\nsend → rules → pass → delivered\n             → block → Blocked Messages\n             → flag  → Flagged Messages → moderator → Reviewed Messages (audit)\n```\n\n## 1. Configure rules + lists (dashboard \u002F REST)\n- **Rules Management** (`\u002Fmoderation\u002Frules-management`): turn on the built-in rules you need and set each to **block** or **flag**. Available categories (fetch the current list — it grows):\n  - **Text:** word-pattern match (profanity), contact\u002Femail removal, spam & scam, platform circumvention, toxicity, hate & harassment, self-harm, explicit content, privacy\u002Fsensitive-info, impersonation, violent\u002Fterroristic, non-consensual sexual content.\n  - **Image:** unsafe\u002Fprohibited, minor-safety\u002FCSAM, graphic violence, explicit\u002Fsexual, hate symbols, fraud (fake IDs), **malware scan**.\n  - **Video \u002F Audio \u002F File:** **malware & virus scan** of attachments.\n- **Lists Management** (`\u002Fmoderation\u002Flists-management`): your own keyword \u002F regex \u002F sentence lists, linked to rules — this is the \"banned words\" surface. Lists are reusable across rules.\n- **Programmatic setup:** the **Moderation REST API** (`\u002Frest-api\u002Fmoderation-apis\u002Foverview`) manages rules + keyword lists from your server (e.g. per-tenant config, CI-seeded rules). Fetch its shapes before writing calls.\n\n## 2. Wire the client (per family — built into the UI Kit)\n- **Report a message:** the UI Kits ship a built-in **Report Message** action on the message — enable it via that family's moderation feature (`{DOCS_BASE}\u002Fui-kit\u002F\u003Cfamily>\u002Fcore-features#moderation`; wire through `cometchat-\u003Cfamily>-features`). No hand-rolled report UI.\n- **Blocked content:** rule-blocked messages simply don't render for recipients; nothing extra to build.\n- **SDK path (custom UI \u002F headless):** flag messages directly with the Chat SDK (`{DOCS_BASE}\u002Fsdk\u002F\u003Cplatform>\u002Fai-moderation`) — the per-feature fallback when a family has no drop-in.\n\n## 3. Moderator review + audit\n- **Flagged Messages** \u002F **Blocked Messages** dashboards: moderators review, approve false positives, or confirm blocks — and use them to refine rules.\n- **Reviewed Messages** is the **audit trail** of every moderation decision (who did what, when) for compliance records — pair with `cometchat-compliance` for retention\u002FeDiscovery of these records.\n\n## Legacy extensions — migrate, don't double-run\nIf the app still uses the **legacy extensions** (Profanity Filter, Data Masking, Image Moderation), **disable them before enabling the new moderation rules.** Running both processes every message twice → performance issues and message delays. Treat this as a required migration step, not optional.\n\n## Enablement note\nModeration is a dashboard\u002Fplan capability — enable it on the app (and on the **production** app, not just dev). `npx @cometchat\u002Fskills-cli@3 features` can toggle app extensions\u002FAI after `auth login`; the rule\u002Flist configuration itself is done in the dashboard or via the Moderation REST API.\n\n## Common pitfalls\n1. **Legacy extensions left on** alongside new rules — double-processing, delays. Disable the old ones first.\n2. **Rules configured on dev only** — content ships unmoderated in production; enable on the production app.\n3. **Hand-rolling a report button** — the UI Kit already ships Report Message; wire the built-in.\n4. **Block vs flag confused** — block hides immediately (good for clear violations); flag routes to a human (good for borderline). Set each rule deliberately.\n5. **No one watching the queues** — flagged content needs a moderator workflow; wire notifications\u002Fownership.\n6. **Assuming a rule exists** — fetch the current rule catalog; don't promise a category the docs don't list.\n\n## Verify it works\nA message with a banned word\u002Fkeyword is blocked or flagged per the rule · an unsafe image is caught · an attachment is malware-scanned · a user's Report action flags a message into the queue · a moderator decision appears in Reviewed Messages · legacy extensions are off · rules are enabled on the production app.\n","> **Ground truth:** capabilities and rule names are FETCHED from the live docs — `{DOCS_BASE}\u002Fmoderation\u002Foverview`, `\u002Fmoderation\u002F{rules-management,lists-management,flagged-messages,blocked-messages,reviewed-messages}`, `{DOCS_BASE}\u002Frest-api\u002Fmoderation-apis\u002Foverview`, and the client hooks `{DOCS_BASE}\u002Fui-kit\u002F\u003Cfamily>\u002Fcore-features#moderation` (built-in report) + `{DOCS_BASE}\u002Fsdk\u002F\u003Cplatform>\u002Fai-moderation` (SDK flagging). `DOCS_BASE = https:\u002F\u002Fwww.cometchat.com\u002Fdocs`; append `.md`. Most of this is dashboard configuration; verify the exact rule\u002Flist options and any REST shapes against the docs before asserting them.\n\n## Use this skill when\nMaking a chat safe\u002Fcompliant: profanity\u002Ftoxicity filtering, image\u002Fvideo safety, spam\u002Fscam detection, malware scanning of attachments, letting users report content, a moderator review queue, or an audit trail for T&S. Trust & Safety is a procurement gate for social, gaming, marketplace, dating, education and healthcare apps.\n\n## How it works\nEvery message runs through the **rule engine** as it's sent; a rule either lets it through, **blocks** it (hidden immediately), or **flags** it for a moderator. Users can also **report** a message manually, which flags it. Blocked\u002Fflagged items land in dashboard queues; a moderator's decision (approve\u002Fblock\u002Fmark reviewed) moves it to the audit trail.\n\n```\nsend → rules → pass → delivered\n             → block → Blocked Messages\n             → flag  → Flagged Messages → moderator → Reviewed Messages (audit)\n```\n\n## 1. Configure rules + lists (dashboard \u002F REST)\n- **Rules Management** (`\u002Fmoderation\u002Frules-management`): turn on the built-in rules you need and set each to **block** or **flag**. Available categories (fetch the current list — it grows):\n  - **Text:** word-pattern match (profanity), contact\u002Femail removal, spam & scam, platform circumvention, toxicity, hate & harassment, self-harm, explicit content, privacy\u002Fsensitive-info, impersonation, violent\u002Fterroristic, non-consensual sexual content.\n  - **Image:** unsafe\u002Fprohibited, minor-safety\u002FCSAM, graphic violence, explicit\u002Fsexual, hate symbols, fraud (fake IDs), **malware scan**.\n  - **Video \u002F Audio \u002F File:** **malware & virus scan** of attachments.\n- **Lists Management** (`\u002Fmoderation\u002Flists-management`): your own keyword \u002F regex \u002F sentence lists, linked to rules — this is the \"banned words\" surface. Lists are reusable across rules.\n- **Programmatic setup:** the **Moderation REST API** (`\u002Frest-api\u002Fmoderation-apis\u002Foverview`) manages rules + keyword lists from your server (e.g. per-tenant config, CI-seeded rules). Fetch its shapes before writing calls.\n\n## 2. Wire the client (per family — built into the UI Kit)\n- **Report a message:** the UI Kits ship a built-in **Report Message** action on the message — enable it via that family's moderation feature (`{DOCS_BASE}\u002Fui-kit\u002F\u003Cfamily>\u002Fcore-features#moderation`; wire through `cometchat-\u003Cfamily>-features`). No hand-rolled report UI.\n- **Blocked content:** rule-blocked messages simply don't render for recipients; nothing extra to build.\n- **SDK path (custom UI \u002F headless):** flag messages directly with the Chat SDK (`{DOCS_BASE}\u002Fsdk\u002F\u003Cplatform>\u002Fai-moderation`) — the per-feature fallback when a family has no drop-in.\n\n## 3. Moderator review + audit\n- **Flagged Messages** \u002F **Blocked Messages** dashboards: moderators review, approve false positives, or confirm blocks — and use them to refine rules.\n- **Reviewed Messages** is the **audit trail** of every moderation decision (who did what, when) for compliance records — pair with `cometchat-compliance` for retention\u002FeDiscovery of these records.\n\n## Legacy extensions — migrate, don't double-run\nIf the app still uses the **legacy extensions** (Profanity Filter, Data Masking, Image Moderation), **disable them before enabling the new moderation rules.** Running both processes every message twice → performance issues and message delays. Treat this as a required migration step, not optional.\n\n## Enablement note\nModeration is a dashboard\u002Fplan capability — enable it on the app (and on the **production** app, not just dev). `npx @cometchat\u002Fskills-cli@3 features` can toggle app extensions\u002FAI after `auth login`; the rule\u002Flist configuration itself is done in the dashboard or via the Moderation REST API.\n\n## Common pitfalls\n1. **Legacy extensions left on** alongside new rules — double-processing, delays. Disable the old ones first.\n2. **Rules configured on dev only** — content ships unmoderated in production; enable on the production app.\n3. **Hand-rolling a report button** — the UI Kit already ships Report Message; wire the built-in.\n4. **Block vs flag confused** — block hides immediately (good for clear violations); flag routes to a human (good for borderline). Set each rule deliberately.\n5. **No one watching the queues** — flagged content needs a moderator workflow; wire notifications\u002Fownership.\n6. **Assuming a rule exists** — fetch the current rule catalog; don't promise a category the docs don't list.\n\n## Verify it works\nA message with a banned word\u002Fkeyword is blocked or flagged per the rule · an unsafe image is caught · an attachment is malware-scanned · a user's Report action flags a message into the queue · a moderator decision appears in Reviewed Messages · legacy extensions are off · rules are enabled on the production app.\n",{"name":5,"license":15,"metadata":62,"description":7,"compatibility":66},{"tags":63,"author":64,"version":65},"cometchat moderation trust-safety profanity image-moderation spam csam malware report flag audit","CometChat","1.0.0","CometChat Moderation (dashboard rules\u002Flists + Flagged\u002FBlocked\u002FReviewed queues) · Moderation REST API v3 · per-family UI Kit report\u002Fblock + Chat SDK flagging.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-moderation",474,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-11 14:40:14",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-moderation",{"tool":83,"command":84},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-moderation",{"tool":86,"command":87},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill cometchat-moderation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcometchat\u002Fcometchat-skills\u002Fskills\u002Fcometchat-moderation\u002FSKILL.md",true,[],[92,101,108,115,142,166],{"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":96,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":100},"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":100},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":100},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":57},"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",[],[122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":57},"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",[],[149,150,56,137,151,152,153,154,155,156,157,158,159,160,127,161,162,163,164,165],"deja reflect","reflect","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":179,"publishedAt":57},"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",[172,173,176],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":174,"categoryName":175,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":177,"categoryName":178,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[168,180,48,181,182,183,184,162,185,128,186,187,188,189,133,39,190,191,49,192],"URL","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","mcp server","schedule","publish"]