[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMVCDQ1QY3NVC7Y96FRRTK":3,"skill-same:01M6MMVCDQ1QY3NVC7Y96FRRTK":79},{"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":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6MMVCDQ1QY3NVC7Y96FRRTK","x-repurposer",null,"Repurpose existing content into a native X (Twitter) post or thread. Take a LinkedIn post, blog, YouTube script, or newsletter and rewrite it for X: re-hook for the no-fold first line, refit to 280 chars or a thread, strip off-platform artifacts, run the humanizer, publish via Publora on approval. Not for writing from scratch (use x-post-writer or x-thread-builder), not for auditing a draft (use x-humanizer --mode audit).","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Fx-skills\u002Fskills\u002Fx-repurposer\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"x repurposer","writer","first line","for","mode","re","hook","native","linkedin post","line","platform","writing","newsletter","youtube","Fold","builder","take","publish","audit","run","humanizer","2026-11-10 10:12:30",false,"---\nname: x-repurposer\ndescription: \"Repurpose existing content into a native X (Twitter) post or thread. Take a LinkedIn post, blog, YouTube script, or newsletter and rewrite it for X: re-hook for the no-fold first line, refit to 280 chars or a thread, strip off-platform artifacts, run the humanizer, publish via Publora on approval. Not for writing from scratch (use x-post-writer or x-thread-builder), not for auditing a draft (use x-humanizer --mode audit).\"\n---\n\n# X Repurposer\n\nTurn something you already made into a tweet or thread that reads like it was born on X. Repurposing is not copy-paste. A post that killed on LinkedIn will die on X if you paste it: wrong hook, wrong length, wrong rhythm, and artifacts (\"link in bio\", hashtag walls) that scream off-platform.\n\nThis skill transforms, it does not generate. It reads your source, keeps the idea, and rebuilds the delivery for X.\n\n## When to use\n\n- \"Turn this LinkedIn post into a tweet \u002F thread\"\n- \"Repurpose my blog post \u002F newsletter \u002F YouTube script for X\"\n- \"This worked on Threads, adapt it for X\"\n- \"I have a rough idea in another format, make it native here\"\n\nNot for a blank-page draft (use `x-post-writer` for a tweet, `x-thread-builder` for a thread) and not for reviewing an already-X draft (use `x-humanizer --mode audit`).\n\n## How it works\n\n**Voice profile first (all drafts).** If `..\u002F..\u002Freferences\u002Fvoice-profile.md` has `filled: yes`, load it and match the user's voice fingerprint, hard rules, and CTA\u002Flink style throughout. If it is not filled, mention once that `x-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules.\n\n**Story bank next.** If `..\u002F..\u002Freferences\u002Fstory-bank.md` has `filled: yes`, load it and take every concrete detail (numbers, dates, named projects, positions) from there instead of asking mid-draft. **Never invent a figure, a date or a client name that is not in the bank or supplied by the user in this conversation.** If the bank has nothing that fits, ask the user, or say once that `x-humanizer --mode interview` fills it in 20 to 40 minutes. A draft with a plausible invented number is worse than a draft with none: one is vague, the other is a retraction.\n\n1. **Take the source.** Any format: a post, a paragraph, a script, a caption, a transcript, a bullet list, a link to read. Ask for the source and the goal (replies \u002F reposts \u002F likes \u002F bookmarks) if not given.\n2. **Extract the spine.** Strip the source platform's shell and pull out the one claim, the one story, or the one number worth keeping. Most repurposing fails because it keeps the words instead of the point.\n3. **Choose the container.** One claim or number -> single tweet. A teach or a build -> thread (hand structure to `x-thread-builder`'s shapes). A LinkedIn carousel or a listicle -> a thread, one slide per tweet, hook rebuilt. A long video -> a thread that delivers the payoff, not a summary.\n4. **Re-hook for X.** X has no \"see more\" fold: line one must land the whole punch. The source's hook almost never survives; write a new first line using a 2026 X formula (see `..\u002F..\u002Freferences\u002Fhook-formulas.md`), picked by the goal.\n5. **Refit the format.** 280 chars on a standard account (emoji count as 2). One idea per tweet, line breaks as beats. Cut the source's connective tissue; X rewards compression.\n6. **Strip off-platform artifacts.** Remove \"link in bio\", \"smash subscribe\", \"read more below\", hashtag walls, @-handles that only exist elsewhere, and any \"as I wrote on LinkedIn\" throat-clearing. A repurposed post should not admit it was repurposed.\n7. **Humanizer pass.** Run the scrub: 2026 AI vocab by density, em dashes above the cap (at most one per tweet, never swapped for a period), stacked rule-of-three triads, generic openers and reveal bridges. Leave a single tweet's rhythm alone; on a thread never insert a punch tweet for variance. Keep the user's real numbers and named entities from the source. Canonical rules: `x-humanizer` V3.\n8. **Approval card.** Show: source -> X mapping (what became what), the container (tweet or N-tweet thread), formula used, char counts, primary goal.\n9. **On approval.** Publish via `lib.publish(kind=\"post\", draft_text=\u003Capproved>, target_url=\"https:\u002F\u002Fx.com\u002Fcompose\u002Ftweet\", platforms=[\u003CX_PLATFORM_ID>], scheduled_time=\u003Ciso_or_None>)`. Publora auto-splits an over-length draft into a numbered thread.\n\n## Native-fit rules (source -> X)\n\n- **LinkedIn post -> X:** cut ~40%. LinkedIn tolerates warm-up; X does not. The LinkedIn hook is usually too long; rewrite it.\n- **Blog \u002F newsletter -> X:** pick the single most quotable claim as the hook, then thread the supporting beats. Do not summarize the whole piece.\n- **YouTube script -> X:** lead with the video's payoff, not its intro. \"Here's what I found\" beats \"In this video\".\n- **Carousel \u002F listicle -> thread:** one item per tweet, each with its own micro-hook, not a wall.\n- **Instagram \u002F TikTok caption -> X:** strip emoji density and hashtag blocks; X reads them as noise.\n\n## Hard rules\n\nGlobal voice rules: see root `SKILL.md` Voice rules. Additional skill-specific rules:\n\n- Keep the source's **claim and facts** intact. Repurposing changes the delivery, never the meaning or the numbers.\n- The new first line must stop the scroll on its own. If it needs line two, rewrite it.\n- Never paste the source verbatim and trim. Rebuild the hook and rhythm from the spine.\n- One specific number where the source offers one. Keep it.\n- Do not hard-sell the user's product. One natural mention max.\n\n## Anti-patterns (skill will refuse)\n\n- Copy-pasting the source with light edits (that is not repurposing).\n- Keeping the source platform's artifacts (\"link in bio\", \"smash subscribe\", hashtag walls).\n- ALL CAPS first line for intensity. Carry it with word choice.\n- Em dashes above the cap (more than one in a tweet), or an em dash swapped for a period.\n- \"The result?\" \u002F \"Here's what\" reveal bridges and staccato stacks added during the rewrite.\n- Rule-of-three lists without specifics.\n- \"leverage\", \"fundamentally\", \"game-changer\", \"deep dive\".\n- An external link in the tweet body (offer a reply).\n- Meta throat-clearing (\"I originally posted this on...\").\n\n## Resources\n\n- `..\u002F..\u002Freferences\u002Fhook-formulas.md` - the 11 X formula skeletons to re-hook with\n- `..\u002F..\u002Freferences\u002Falgorithm-heuristics.md` - 2026 X ranking rules (length, timing, signals)\n\n## Related skills\n\n- `x-post-writer` - write a fresh tweet from scratch\n- `x-thread-builder` - structure a multi-tweet thread (repurposer hands long builds here)\n- `x-humanizer` - scrub AI tells, plus `--mode audit` to review the result\n","# X Repurposer\n\nTurn something you already made into a tweet or thread that reads like it was born on X. Repurposing is not copy-paste. A post that killed on LinkedIn will die on X if you paste it: wrong hook, wrong length, wrong rhythm, and artifacts (\"link in bio\", hashtag walls) that scream off-platform.\n\nThis skill transforms, it does not generate. It reads your source, keeps the idea, and rebuilds the delivery for X.\n\n## When to use\n\n- \"Turn this LinkedIn post into a tweet \u002F thread\"\n- \"Repurpose my blog post \u002F newsletter \u002F YouTube script for X\"\n- \"This worked on Threads, adapt it for X\"\n- \"I have a rough idea in another format, make it native here\"\n\nNot for a blank-page draft (use `x-post-writer` for a tweet, `x-thread-builder` for a thread) and not for reviewing an already-X draft (use `x-humanizer --mode audit`).\n\n## How it works\n\n**Voice profile first (all drafts).** If `..\u002F..\u002Freferences\u002Fvoice-profile.md` has `filled: yes`, load it and match the user's voice fingerprint, hard rules, and CTA\u002Flink style throughout. If it is not filled, mention once that `x-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules.\n\n**Story bank next.** If `..\u002F..\u002Freferences\u002Fstory-bank.md` has `filled: yes`, load it and take every concrete detail (numbers, dates, named projects, positions) from there instead of asking mid-draft. **Never invent a figure, a date or a client name that is not in the bank or supplied by the user in this conversation.** If the bank has nothing that fits, ask the user, or say once that `x-humanizer --mode interview` fills it in 20 to 40 minutes. A draft with a plausible invented number is worse than a draft with none: one is vague, the other is a retraction.\n\n1. **Take the source.** Any format: a post, a paragraph, a script, a caption, a transcript, a bullet list, a link to read. Ask for the source and the goal (replies \u002F reposts \u002F likes \u002F bookmarks) if not given.\n2. **Extract the spine.** Strip the source platform's shell and pull out the one claim, the one story, or the one number worth keeping. Most repurposing fails because it keeps the words instead of the point.\n3. **Choose the container.** One claim or number -> single tweet. A teach or a build -> thread (hand structure to `x-thread-builder`'s shapes). A LinkedIn carousel or a listicle -> a thread, one slide per tweet, hook rebuilt. A long video -> a thread that delivers the payoff, not a summary.\n4. **Re-hook for X.** X has no \"see more\" fold: line one must land the whole punch. The source's hook almost never survives; write a new first line using a 2026 X formula (see `..\u002F..\u002Freferences\u002Fhook-formulas.md`), picked by the goal.\n5. **Refit the format.** 280 chars on a standard account (emoji count as 2). One idea per tweet, line breaks as beats. Cut the source's connective tissue; X rewards compression.\n6. **Strip off-platform artifacts.** Remove \"link in bio\", \"smash subscribe\", \"read more below\", hashtag walls, @-handles that only exist elsewhere, and any \"as I wrote on LinkedIn\" throat-clearing. A repurposed post should not admit it was repurposed.\n7. **Humanizer pass.** Run the scrub: 2026 AI vocab by density, em dashes above the cap (at most one per tweet, never swapped for a period), stacked rule-of-three triads, generic openers and reveal bridges. Leave a single tweet's rhythm alone; on a thread never insert a punch tweet for variance. Keep the user's real numbers and named entities from the source. Canonical rules: `x-humanizer` V3.\n8. **Approval card.** Show: source -> X mapping (what became what), the container (tweet or N-tweet thread), formula used, char counts, primary goal.\n9. **On approval.** Publish via `lib.publish(kind=\"post\", draft_text=\u003Capproved>, target_url=\"https:\u002F\u002Fx.com\u002Fcompose\u002Ftweet\", platforms=[\u003CX_PLATFORM_ID>], scheduled_time=\u003Ciso_or_None>)`. Publora auto-splits an over-length draft into a numbered thread.\n\n## Native-fit rules (source -> X)\n\n- **LinkedIn post -> X:** cut ~40%. LinkedIn tolerates warm-up; X does not. The LinkedIn hook is usually too long; rewrite it.\n- **Blog \u002F newsletter -> X:** pick the single most quotable claim as the hook, then thread the supporting beats. Do not summarize the whole piece.\n- **YouTube script -> X:** lead with the video's payoff, not its intro. \"Here's what I found\" beats \"In this video\".\n- **Carousel \u002F listicle -> thread:** one item per tweet, each with its own micro-hook, not a wall.\n- **Instagram \u002F TikTok caption -> X:** strip emoji density and hashtag blocks; X reads them as noise.\n\n## Hard rules\n\nGlobal voice rules: see root `SKILL.md` Voice rules. Additional skill-specific rules:\n\n- Keep the source's **claim and facts** intact. Repurposing changes the delivery, never the meaning or the numbers.\n- The new first line must stop the scroll on its own. If it needs line two, rewrite it.\n- Never paste the source verbatim and trim. Rebuild the hook and rhythm from the spine.\n- One specific number where the source offers one. Keep it.\n- Do not hard-sell the user's product. One natural mention max.\n\n## Anti-patterns (skill will refuse)\n\n- Copy-pasting the source with light edits (that is not repurposing).\n- Keeping the source platform's artifacts (\"link in bio\", \"smash subscribe\", hashtag walls).\n- ALL CAPS first line for intensity. Carry it with word choice.\n- Em dashes above the cap (more than one in a tweet), or an em dash swapped for a period.\n- \"The result?\" \u002F \"Here's what\" reveal bridges and staccato stacks added during the rewrite.\n- Rule-of-three lists without specifics.\n- \"leverage\", \"fundamentally\", \"game-changer\", \"deep dive\".\n- An external link in the tweet body (offer a reply).\n- Meta throat-clearing (\"I originally posted this on...\").\n\n## Resources\n\n- `..\u002F..\u002Freferences\u002Fhook-formulas.md` - the 11 X formula skeletons to re-hook with\n- `..\u002F..\u002Freferences\u002Falgorithm-heuristics.md` - 2026 X ranking rules (length, timing, signals)\n\n## Related skills\n\n- `x-post-writer` - write a fresh tweet from scratch\n- `x-thread-builder` - structure a multi-tweet thread (repurposer hands long builds here)\n- `x-humanizer` - scrub AI tells, plus `--mode audit` to review the result\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fsergebulaev\u002Fx-skills\u002Fskills\u002Fx-repurposer",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill x-repurposer",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill x-repurposer",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill x-repurposer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Fx-skills\u002Fskills\u002Fx-repurposer\u002FSKILL.md",true,[],[80,88,95,102,128,153],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":87},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":87},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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",[],[109,110,111,112,113,114,34,115,116,117,118,119,120,121,122,123,124,125,126,127],"search","deja search","never","error","ready","memory","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"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",[],[135,136,137,123,138,139,140,141,142,143,144,145,146,147,114,148,149,150,151,152],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":168,"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",[159,162,165],{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":163,"categoryName":164,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[155,169,170,171,172,173,174,149,175,34,176,177,178,179,119,180,181,182,183,46],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api"]