[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMSMZTYH4BBANM09BNDBQ3":3,"skill-same:01M6MMSMZTYH4BBANM09BNDBQ3":78},{"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":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6MMSMZTYH4BBANM09BNDBQ3","linkedin-repurposer",null,"Repurpose existing content into a native LinkedIn post. Take a tweet, thread, YouTube video, blog, or newsletter and rebuild it for LinkedIn: re-hook before the fold, expand to the 900 to 1300 char sweet spot, add whitespace and a CTA, move links to the first comment, run the humanizer, publish via Publora on approval. Not for writing from scratch (use linkedin-post-writer), not for auditing a draft (use linkedin-humanizer --mode audit).","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-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],"linkedin repurposer","linkedin","rebuild","mode","re","hook","move","native","linkedin post","expand","writer","writing","newsletter","youtube","take","Video","publish","audit","run","humanizer","2026-11-10 10:12:30",false,"---\nname: linkedin-repurposer\ndescription: \"Repurpose existing content into a native LinkedIn post. Take a tweet, thread, YouTube video, blog, or newsletter and rebuild it for LinkedIn: re-hook before the fold, expand to the 900 to 1300 char sweet spot, add whitespace and a CTA, move links to the first comment, run the humanizer, publish via Publora on approval. Not for writing from scratch (use linkedin-post-writer), not for auditing a draft (use linkedin-humanizer --mode audit).\"\n---\n\n# LinkedIn Repurposer\n\nTurn something you already made into a post that reads like it was written for LinkedIn. Repurposing is not copy-paste. A tweet that flew on X will flop pasted into LinkedIn: too short, no whitespace, wrong rhythm, and a link in the body that tanks your reach.\n\nThis skill transforms, it does not generate. It reads your source, keeps the idea, and rebuilds the delivery for LinkedIn's 2026 algorithm.\n\n## When to use\n\n- \"Turn this tweet \u002F thread into a LinkedIn post\"\n- \"Repurpose my YouTube video \u002F blog \u002F newsletter for LinkedIn\"\n- \"This worked on Threads, adapt it for LinkedIn\"\n- \"I have a rough idea in another format, make it native here\"\n\nNot for a blank-page draft (use `linkedin-post-writer`) and not for reviewing a finished LinkedIn draft (use `linkedin-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 `linkedin-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules. If `..\u002F..\u002Freferences\u002Fstory-bank.md` has `filled: yes`, load it too and take concrete details (numbers, dates, named projects) from there instead of asking mid-draft. Never invent a figure that is not in it; if the bank has nothing that fits, ask the user or offer `linkedin-interviewer`.\n\n1. **Take the source.** Any format: a tweet or thread, a video or script, a blog paragraph, a caption, a transcript, a bullet list, a link to read. Ask for the source and the goal (comments \u002F reposts \u002F likes \u002F saves) if not given.\n2. **Extract the spine.** Strip the source platform's shell and pull out the one claim, story, or number worth keeping. Repurposing fails when it keeps the words instead of the point.\n3. **Re-hook for LinkedIn.** The hook must land in the first 210 characters, before the \"...see more\" fold. The source's hook rarely survives; write a new first line using one of the 20 formulas in `..\u002F..\u002Freferences\u002Fhook-formulas.md`, picked by the goal.\n4. **Expand to LinkedIn length.** X compresses; LinkedIn breathes. Grow the spine into the 900 to 1300 char sweet spot: short paragraphs, double line breaks between ideas, one concrete detail per beat. A dense tweet becomes 4 to 6 short paragraphs, not a wall.\n5. **Add the LinkedIn shape.** Whitespace between ideas, a moment of real stakes or vulnerability (pure-insight posts do not land in 2026), and one clear closing question or CTA.\n6. **Fix links and artifacts.** Move any external link to the first comment (in-body links suppress reach). Strip off-platform artifacts: hashtag walls, \"link in bio\", \"smash subscribe\", X @-handles, \"as I tweeted\" throat-clearing. 0 to 2 hashtags at the end.\n7. **Humanizer pass.** Run the scrub: 2026 AI vocab by density, em dashes above the cap (about one per 100 words), stacked rule-of-three triads, generic openers and reveal bridges. Keep the user's real numbers and named entities from the source.\n8. **Approval card.** Show: source -> LinkedIn mapping (what became what), formula used, char count, suggested posting window (Tue\u002FWed\u002FThu 7:30 to 9:00 AM local), the link-in-first-comment note.\n9. **On approval.** Publish via `lib.publish(kind=\"post\", draft_text=\u003Capproved>, target_url=\"https:\u002F\u002Fwww.linkedin.com\u002Fpost\u002Fnew\u002F\", platforms=[{\"platform\":\"linkedin\",\"platformId\":\u003Cid>}], scheduled_time=\u003Ciso_or_None>)`. The wrapper handles Publora \u002F manual \u002F diy routing. If the user reconsiders after approving, call `lib.unpublish(post_group_id=\u003CpostGroupId from the response>)` to cancel it before it goes out. On the publora tier the post is already queued, so the dashboard is otherwise the only way back.\n\n## Native-fit rules (source -> LinkedIn)\n\n- **Tweet -> LinkedIn:** expand, do not paste. One tweet is a hook; grow the argument underneath it with whitespace.\n- **X thread -> LinkedIn:** unroll into one flowing post, not a numbered list. Keep the best line as the hook.\n- **YouTube video \u002F script -> LinkedIn:** lead with the payoff, then the story of how you got there. Link the video in the first comment.\n- **Blog \u002F newsletter -> LinkedIn:** pick the single most quotable claim as the hook, then the one story that proves it. Do not summarize the whole piece.\n- **Instagram \u002F TikTok caption -> LinkedIn:** strip emoji density and hashtag blocks; add the professional stakes LinkedIn rewards.\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 hook must land in the first 210 characters, before the fold.\n- Never paste the source and trim. Rebuild the hook, length, and rhythm from the spine.\n- No external link in the post body. Offer to put it in the first comment.\n- Include at least one moment of real stakes or vulnerability. Keep the source's real numbers and named entities.\n- Do not name-drop the user's product as self-promo. 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- Shipping a tweet-length post with no whitespace or expansion.\n- All-caps first line (\"THIS CHANGED EVERYTHING\").\n- Em dashes above the cap (more than about one per 100 words), or an em dash swapped for a period.\n- Rule-of-three lists without receipts.\n- \"leverage\", \"fundamentally\", \"game-changer\", \"deep dive\".\n- External links in the body.\n- Meta throat-clearing (\"I originally posted this on...\").\n\n## Resources\n\n- `..\u002F..\u002Freferences\u002Fhook-formulas.md` - the 20 formula skeletons to re-hook with\n- `..\u002F..\u002Freferences\u002Falgorithm-heuristics.md` - 2026 posting rules (timing, format, length)\n\n## Related skills\n\n- `linkedin-post-writer` - write a fresh post from scratch\n- `linkedin-humanizer` - scrub AI tells, plus `--mode audit` to review the result\n- `linkedin-hook-extractor` - reverse-engineer a hook from a post you admire\n","# LinkedIn Repurposer\n\nTurn something you already made into a post that reads like it was written for LinkedIn. Repurposing is not copy-paste. A tweet that flew on X will flop pasted into LinkedIn: too short, no whitespace, wrong rhythm, and a link in the body that tanks your reach.\n\nThis skill transforms, it does not generate. It reads your source, keeps the idea, and rebuilds the delivery for LinkedIn's 2026 algorithm.\n\n## When to use\n\n- \"Turn this tweet \u002F thread into a LinkedIn post\"\n- \"Repurpose my YouTube video \u002F blog \u002F newsletter for LinkedIn\"\n- \"This worked on Threads, adapt it for LinkedIn\"\n- \"I have a rough idea in another format, make it native here\"\n\nNot for a blank-page draft (use `linkedin-post-writer`) and not for reviewing a finished LinkedIn draft (use `linkedin-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 `linkedin-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules. If `..\u002F..\u002Freferences\u002Fstory-bank.md` has `filled: yes`, load it too and take concrete details (numbers, dates, named projects) from there instead of asking mid-draft. Never invent a figure that is not in it; if the bank has nothing that fits, ask the user or offer `linkedin-interviewer`.\n\n1. **Take the source.** Any format: a tweet or thread, a video or script, a blog paragraph, a caption, a transcript, a bullet list, a link to read. Ask for the source and the goal (comments \u002F reposts \u002F likes \u002F saves) if not given.\n2. **Extract the spine.** Strip the source platform's shell and pull out the one claim, story, or number worth keeping. Repurposing fails when it keeps the words instead of the point.\n3. **Re-hook for LinkedIn.** The hook must land in the first 210 characters, before the \"...see more\" fold. The source's hook rarely survives; write a new first line using one of the 20 formulas in `..\u002F..\u002Freferences\u002Fhook-formulas.md`, picked by the goal.\n4. **Expand to LinkedIn length.** X compresses; LinkedIn breathes. Grow the spine into the 900 to 1300 char sweet spot: short paragraphs, double line breaks between ideas, one concrete detail per beat. A dense tweet becomes 4 to 6 short paragraphs, not a wall.\n5. **Add the LinkedIn shape.** Whitespace between ideas, a moment of real stakes or vulnerability (pure-insight posts do not land in 2026), and one clear closing question or CTA.\n6. **Fix links and artifacts.** Move any external link to the first comment (in-body links suppress reach). Strip off-platform artifacts: hashtag walls, \"link in bio\", \"smash subscribe\", X @-handles, \"as I tweeted\" throat-clearing. 0 to 2 hashtags at the end.\n7. **Humanizer pass.** Run the scrub: 2026 AI vocab by density, em dashes above the cap (about one per 100 words), stacked rule-of-three triads, generic openers and reveal bridges. Keep the user's real numbers and named entities from the source.\n8. **Approval card.** Show: source -> LinkedIn mapping (what became what), formula used, char count, suggested posting window (Tue\u002FWed\u002FThu 7:30 to 9:00 AM local), the link-in-first-comment note.\n9. **On approval.** Publish via `lib.publish(kind=\"post\", draft_text=\u003Capproved>, target_url=\"https:\u002F\u002Fwww.linkedin.com\u002Fpost\u002Fnew\u002F\", platforms=[{\"platform\":\"linkedin\",\"platformId\":\u003Cid>}], scheduled_time=\u003Ciso_or_None>)`. The wrapper handles Publora \u002F manual \u002F diy routing. If the user reconsiders after approving, call `lib.unpublish(post_group_id=\u003CpostGroupId from the response>)` to cancel it before it goes out. On the publora tier the post is already queued, so the dashboard is otherwise the only way back.\n\n## Native-fit rules (source -> LinkedIn)\n\n- **Tweet -> LinkedIn:** expand, do not paste. One tweet is a hook; grow the argument underneath it with whitespace.\n- **X thread -> LinkedIn:** unroll into one flowing post, not a numbered list. Keep the best line as the hook.\n- **YouTube video \u002F script -> LinkedIn:** lead with the payoff, then the story of how you got there. Link the video in the first comment.\n- **Blog \u002F newsletter -> LinkedIn:** pick the single most quotable claim as the hook, then the one story that proves it. Do not summarize the whole piece.\n- **Instagram \u002F TikTok caption -> LinkedIn:** strip emoji density and hashtag blocks; add the professional stakes LinkedIn rewards.\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 hook must land in the first 210 characters, before the fold.\n- Never paste the source and trim. Rebuild the hook, length, and rhythm from the spine.\n- No external link in the post body. Offer to put it in the first comment.\n- Include at least one moment of real stakes or vulnerability. Keep the source's real numbers and named entities.\n- Do not name-drop the user's product as self-promo. 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- Shipping a tweet-length post with no whitespace or expansion.\n- All-caps first line (\"THIS CHANGED EVERYTHING\").\n- Em dashes above the cap (more than about one per 100 words), or an em dash swapped for a period.\n- Rule-of-three lists without receipts.\n- \"leverage\", \"fundamentally\", \"game-changer\", \"deep dive\".\n- External links in the body.\n- Meta throat-clearing (\"I originally posted this on...\").\n\n## Resources\n\n- `..\u002F..\u002Freferences\u002Fhook-formulas.md` - the 20 formula skeletons to re-hook with\n- `..\u002F..\u002Freferences\u002Falgorithm-heuristics.md` - 2026 posting rules (timing, format, length)\n\n## Related skills\n\n- `linkedin-post-writer` - write a fresh post from scratch\n- `linkedin-humanizer` - scrub AI tells, plus `--mode audit` to review the result\n- `linkedin-hook-extractor` - reverse-engineer a hook from a post you admire\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-repurposer",490,"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-14 02:12:02",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-repurposer",{"tool":70,"command":71},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-repurposer",{"tool":73,"command":74},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-repurposer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-repurposer\u002FSKILL.md",true,[],[79,87,94,101,127,152],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":86},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":86},"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":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":49},"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",[],[108,109,110,111,112,113,33,114,115,116,117,118,119,120,121,122,123,124,125,126],"search","deja search","never","error","ready","memory","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":49},"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",[],[134,135,136,122,137,138,139,140,141,142,143,144,145,146,113,147,148,149,150,151],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":167,"publishedAt":49},"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",[158,161,164],{"categoryNo":159,"categoryName":160,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":165,"categoryName":166,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[154,168,44,169,170,171,172,148,173,33,174,175,176,177,118,178,179,180,181,45],"URL","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api"]