[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CW9BNR3AWA9FTP02VXQDDP":3,"skill-same:01M7CW9BNR3AWA9FTP02VXQDDP":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CW9BNR3AWA9FTP02VXQDDP","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).","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Flinkedin-repurposer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","a73152352c0612252131e5cf84e91312a6cf17dc","marketing\u002Flinkedin-repurposer","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill linkedin-repurposer",{"tool":38,"command":39},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill linkedin-repurposer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill linkedin-repurposer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Flinkedin-repurposer\u002FSKILL.md",true,[],[47,54,61,69,76,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]