[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMR70GKHTJYDXEPSTZ4M0J":3,"skill-same:01M6MMR70GKHTJYDXEPSTZ4M0J":88},{"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":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6MMR70GKHTJYDXEPSTZ4M0J","linkedin-employee-advocacy",null,"Stand up and run a LinkedIn employee advocacy program for a marketing or sales team. Covers 14-day launch playbook, brand-guideline governance, per-post time budget, cadence benchmarks, and team ROI (reach, engagement, pipeline). Triggers on \"employee advocacy\", \"get the team posting\", \"scale LinkedIn across team\", \"advocacy ROI\". Not for planning one person's own calendar (use linkedin-content-planner).","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"linkedin employee advocacy","employee advocacy","linkedin","up","program","for","cadence","posting","get","across","time","calendar","roi","brand","marketing","team","Budget","playbook","pipeline","planning","run","2026-11-10 10:12:30",false,"---\nname: linkedin-employee-advocacy\ndescription: \"Stand up and run a LinkedIn employee advocacy program for a marketing or sales team. Covers 14-day launch playbook, brand-guideline governance, per-post time budget, cadence benchmarks, and team ROI (reach, engagement, pipeline). Triggers on \\\"employee advocacy\\\", \\\"get the team posting\\\", \\\"scale LinkedIn across team\\\", \\\"advocacy ROI\\\". Not for planning one person's own calendar (use linkedin-content-planner).\"\n---\n\n# LinkedIn Employee Advocacy\n\nStand up a marketing-team LinkedIn advocacy program that scales without killing authenticity. Employee posts get **8x more engagement** than brand-page posts — this skill operationalizes that advantage.\n\n## When to use\n\n- Marketing leader wants to get their team posting on LinkedIn\n- User is planning an advocacy program launch\n- Team is posting but output is inconsistent \u002F off-brand \u002F low-engagement\n- Need ROI measurement framework for an existing program\n- Requests: \"how do I get the team posting\", \"launch advocacy\", \"scale LinkedIn across 10 people\"\n\n## Input\n\n- Team size (5-50 typical)\n- Marketing goal (reach \u002F pipeline \u002F recruiting \u002F thought leadership)\n- Current state (everyone silent \u002F some active \u002F inconsistent)\n- Brand guideline constraints\n\n## Output\n\n- **14-day launch plan** (if cold-starting)\n- **Operating model** (voice capture, ideation, approval, posting, measurement)\n- **Cadence targets** per team member (realistic, not punishing)\n- **KPI dashboard spec** (team reach, engagement, pipeline attribution)\n- **Governance playbook** (brand safety without blocking velocity)\n\n## Four operating principles\n\n1. **Scale authentically.** Individuals compose in their own voice, not corporate language. Corporate-tone team posts underperform authentic voice 3x.\n2. **Maintain control.** Brand guidelines integrated into the workflow. Review step is **optional, not blocking** — high-trust roles bypass review entirely.\n3. **Remove friction.** Per-post time budget: **5 minutes**. Anything more and the program dies in week 3.\n4. **Prove ROI.** Track team reach, engagement, pipeline impact. Without attribution, the program gets cut at the first budget review.\n\n## Benchmarks\n\n- **Launch target:** team posting within **14 days**\n- **Active team size benchmark:** 8-11 members\n- **Output benchmark:** 70+ posts\u002Fweek (at 8 members) or 3-5 posts\u002Fmember\u002Fweek\n- **Per-post time budget:** 5 minutes\n- **Team touchpoint math:** 11 people × 3 posts\u002Fweek × 300 min impressions = **40,000 monthly touchpoints** baseline\n- **Employee vs. brand page:** 8x more engagement, 6-8x more reach on personal posts\n\n## 14-day launch playbook\n\n### Days 1-3: Voice capture\n- Short interview with each team member (5-10 min) to extract their actual voice\n- Identify their domain expertise and 2-3 content pillars\n- Set realistic individual cadence (some commit to 1\u002Fweek, some 3\u002Fweek — don't force uniformity)\n\n### Days 4-7: First posts\n- Everyone ships their first post, drafted in their voice\n- Marketing reviews only for brand safety (never for style)\n- Celebrate every first post internally — social proof unlocks the next team member\n\n### Days 8-10: Ideation pipeline\n- Set up a shared ideation source (newsletter digest, trending-topics feed, internal wins)\n- Each team member gets 5-10 topic suggestions per week\n- They pick, not assigned\n\n### Days 11-14: Rhythm lock\n- Establish cadence: each team member publishes on fixed days\u002Ftimes\n- Set up KPI dashboard (see below)\n- Run first weekly review\n\n## Governance: brand-safe without being blocked\n\n**What marketing reviews:**\n- Factual claims about the company \u002F products \u002F customers\n- Confidential info\n- Legal\u002Fcompliance issues (finance, health, regulated industries)\n\n**What marketing does NOT review:**\n- Personal voice, tone, style\n- Opinions the team member has about their own work\n- Formatting, hashtags, emoji choices\n- Topic selection (within pillars)\n\n**The review SLA:** \u003C4 business hours. Anything longer and the post is dead (posts go stale in the news cycle).\n\n## ROI measurement\n\n### Per-person metrics (content quality)\n- Impressions per post\n- Engagement rate (reactions + comments + shares \u002F impressions)\n- Comments (depth signal)\n- Profile views attributed to post\n\n### Team-level metrics (program health)\n- Total team reach\n- Total team engagement\n- Individual contribution rank (leaderboard)\n- Active members \u002F total members (participation rate)\n\n### Business metrics (pipeline impact)\n- Inbound DMs sourced from LinkedIn content\n- Meetings booked from LinkedIn\n- Closed-won deals with LinkedIn as first-touch channel\n- Employee referrals sourced from LinkedIn (if recruiting is a goal)\n\n## Anti-patterns\n\n- **Copy-paste corporate posts across team accounts** — LinkedIn detects this, suppresses all of them\n- **Ghostwriting that erases the writer's voice** — reads as fake\n- **Mandatory posting cadence without individual calibration** — program dies in 6 weeks\n- **Approval loops >24h** — makes the program feel like work\n- **Measuring only vanity metrics** — program gets cut without pipeline attribution\n- **All-same pillars across team** — redundancy kills team reach (360Brew penalizes clustering)\n\n## Resources\n\n- `references\u002Fadvocacy-principles.md` — the 4 operating principles with examples\n- `references\u002Fteam-cadence-matrix.md` — realistic cadence by role + seniority\n- `references\u002Fgovernance-playbook.md` — what to review, what not to, SLA\n\n## Related skills\n\n- `linkedin-post-writer` — each team member uses this for individual drafts\n- `linkedin-profile-optimizer` — team profiles should match before the program launches (otherwise profile clicks convert poorly)\n- `linkedin-content-planner` — each team member gets their own pillar mix\n- `linkedin-thread-monitor` — track which team members' comments drive author replies\n- `linkedin-engager-analytics` — see who's engaging with each team member's posts\n- `linkedin-comment-drafter` — its **reshare mode** is how team members amplify a brand or colleague post to their own feed with a short take (`lib.repost(post_url, commentary)` on approval); the cleanest advocacy action after an original post\n","# LinkedIn Employee Advocacy\n\nStand up a marketing-team LinkedIn advocacy program that scales without killing authenticity. Employee posts get **8x more engagement** than brand-page posts — this skill operationalizes that advantage.\n\n## When to use\n\n- Marketing leader wants to get their team posting on LinkedIn\n- User is planning an advocacy program launch\n- Team is posting but output is inconsistent \u002F off-brand \u002F low-engagement\n- Need ROI measurement framework for an existing program\n- Requests: \"how do I get the team posting\", \"launch advocacy\", \"scale LinkedIn across 10 people\"\n\n## Input\n\n- Team size (5-50 typical)\n- Marketing goal (reach \u002F pipeline \u002F recruiting \u002F thought leadership)\n- Current state (everyone silent \u002F some active \u002F inconsistent)\n- Brand guideline constraints\n\n## Output\n\n- **14-day launch plan** (if cold-starting)\n- **Operating model** (voice capture, ideation, approval, posting, measurement)\n- **Cadence targets** per team member (realistic, not punishing)\n- **KPI dashboard spec** (team reach, engagement, pipeline attribution)\n- **Governance playbook** (brand safety without blocking velocity)\n\n## Four operating principles\n\n1. **Scale authentically.** Individuals compose in their own voice, not corporate language. Corporate-tone team posts underperform authentic voice 3x.\n2. **Maintain control.** Brand guidelines integrated into the workflow. Review step is **optional, not blocking** — high-trust roles bypass review entirely.\n3. **Remove friction.** Per-post time budget: **5 minutes**. Anything more and the program dies in week 3.\n4. **Prove ROI.** Track team reach, engagement, pipeline impact. Without attribution, the program gets cut at the first budget review.\n\n## Benchmarks\n\n- **Launch target:** team posting within **14 days**\n- **Active team size benchmark:** 8-11 members\n- **Output benchmark:** 70+ posts\u002Fweek (at 8 members) or 3-5 posts\u002Fmember\u002Fweek\n- **Per-post time budget:** 5 minutes\n- **Team touchpoint math:** 11 people × 3 posts\u002Fweek × 300 min impressions = **40,000 monthly touchpoints** baseline\n- **Employee vs. brand page:** 8x more engagement, 6-8x more reach on personal posts\n\n## 14-day launch playbook\n\n### Days 1-3: Voice capture\n- Short interview with each team member (5-10 min) to extract their actual voice\n- Identify their domain expertise and 2-3 content pillars\n- Set realistic individual cadence (some commit to 1\u002Fweek, some 3\u002Fweek — don't force uniformity)\n\n### Days 4-7: First posts\n- Everyone ships their first post, drafted in their voice\n- Marketing reviews only for brand safety (never for style)\n- Celebrate every first post internally — social proof unlocks the next team member\n\n### Days 8-10: Ideation pipeline\n- Set up a shared ideation source (newsletter digest, trending-topics feed, internal wins)\n- Each team member gets 5-10 topic suggestions per week\n- They pick, not assigned\n\n### Days 11-14: Rhythm lock\n- Establish cadence: each team member publishes on fixed days\u002Ftimes\n- Set up KPI dashboard (see below)\n- Run first weekly review\n\n## Governance: brand-safe without being blocked\n\n**What marketing reviews:**\n- Factual claims about the company \u002F products \u002F customers\n- Confidential info\n- Legal\u002Fcompliance issues (finance, health, regulated industries)\n\n**What marketing does NOT review:**\n- Personal voice, tone, style\n- Opinions the team member has about their own work\n- Formatting, hashtags, emoji choices\n- Topic selection (within pillars)\n\n**The review SLA:** \u003C4 business hours. Anything longer and the post is dead (posts go stale in the news cycle).\n\n## ROI measurement\n\n### Per-person metrics (content quality)\n- Impressions per post\n- Engagement rate (reactions + comments + shares \u002F impressions)\n- Comments (depth signal)\n- Profile views attributed to post\n\n### Team-level metrics (program health)\n- Total team reach\n- Total team engagement\n- Individual contribution rank (leaderboard)\n- Active members \u002F total members (participation rate)\n\n### Business metrics (pipeline impact)\n- Inbound DMs sourced from LinkedIn content\n- Meetings booked from LinkedIn\n- Closed-won deals with LinkedIn as first-touch channel\n- Employee referrals sourced from LinkedIn (if recruiting is a goal)\n\n## Anti-patterns\n\n- **Copy-paste corporate posts across team accounts** — LinkedIn detects this, suppresses all of them\n- **Ghostwriting that erases the writer's voice** — reads as fake\n- **Mandatory posting cadence without individual calibration** — program dies in 6 weeks\n- **Approval loops >24h** — makes the program feel like work\n- **Measuring only vanity metrics** — program gets cut without pipeline attribution\n- **All-same pillars across team** — redundancy kills team reach (360Brew penalizes clustering)\n\n## Resources\n\n- `references\u002Fadvocacy-principles.md` — the 4 operating principles with examples\n- `references\u002Fteam-cadence-matrix.md` — realistic cadence by role + seniority\n- `references\u002Fgovernance-playbook.md` — what to review, what not to, SLA\n\n## Related skills\n\n- `linkedin-post-writer` — each team member uses this for individual drafts\n- `linkedin-profile-optimizer` — team profiles should match before the program launches (otherwise profile clicks convert poorly)\n- `linkedin-content-planner` — each team member gets their own pillar mix\n- `linkedin-thread-monitor` — track which team members' comments drive author replies\n- `linkedin-engager-analytics` — see who's engaging with each team member's posts\n- `linkedin-comment-drafter` — its **reshare mode** is how team members amplify a brand or colleague post to their own feed with a short take (`lib.repost(post_url, commentary)` on approval); the cleanest advocacy action after an original post\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-employee-advocacy",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-employee-advocacy",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-employee-advocacy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy\u002FSKILL.md",true,[74,80,84],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fadvocacy-principles.md","REFERENCE","参考文档",3462,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy\u002Freferences\u002Fadvocacy-principles.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fgovernance-playbook.md",5482,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy\u002Freferences\u002Fgovernance-playbook.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fteam-cadence-matrix.md",3788,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-employee-advocacy\u002Freferences\u002Fteam-cadence-matrix.md",[89,97,104,111,138,163],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":96},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":96},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":96},"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":45},"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",[],[118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":45},"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",[],[145,146,147,133,148,149,150,151,152,153,154,155,156,157,123,158,159,160,161,162],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":178,"publishedAt":45},"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",[169,172,175],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":176,"categoryName":177,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[165,179,180,181,182,183,184,159,185,124,186,187,188,189,129,190,191,192,193,194],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]