[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CW0P04BX548P48WXEFS104":3,"skill-same:01M7CW0P04BX548P48WXEFS104":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},"01M7CW0P04BX548P48WXEFS104","ig-repurposer",null,"Repurpose existing content into a native Instagram post. Take a LinkedIn, blog, YouTube script, or X tweet or thread and rebuild it for Instagram: a long piece becomes a carousel or a caption, re-hooked before the 125-char fold, off-platform artifacts stripped (X @-handles, link in bio), published via Publora on approval. Use to adapt content across platforms into Instagram. Not for writing from scratch (use ig-caption-writer or ig-carousel-planner), not for auditing a draft (ig-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\u002Finstagram-marketing\u002F.codex-marketplace\u002Finstagram-skills\u002Fskills\u002Fig-repurposer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ig-repurposer\ndescription: \"Repurpose existing content into a native Instagram post. Take a LinkedIn, blog, YouTube script, or X tweet or thread and rebuild it for Instagram: a long piece becomes a carousel or a caption, re-hooked before the 125-char fold, off-platform artifacts stripped (X @-handles, link in bio), published via Publora on approval. Use to adapt content across platforms into Instagram. Not for writing from scratch (use ig-caption-writer or ig-carousel-planner), not for auditing a draft (ig-humanizer --mode audit).\"\n---\n\n# Instagram Repurposer\n\nTurn something you already made into a post that reads like it was born on\nInstagram. Repurposing is not copy-paste. A post that killed on LinkedIn or a\nthread that flew on X will die on Instagram if you paste it: wrong hook, wrong\ncontainer, wrong rhythm, no media, and artifacts (\"link in bio\", @-handles,\nhashtag walls) that scream off-platform.\n\nThis skill transforms, it does not generate. It reads your source, keeps the\nidea, and rebuilds the delivery for Instagram.\n\n## When to use\n\n- \"Turn this LinkedIn post into an Instagram carousel \u002F caption\"\n- \"Repurpose my blog post \u002F newsletter \u002F YouTube script for Instagram\"\n- \"This thread worked on X, adapt it for Instagram\"\n- \"I have a rough idea in another format, make it native here\"\n\nNot for a blank-page draft (use `ig-caption-writer` for a single caption,\n`ig-carousel-planner` for a slide-by-slide carousel) and not for reviewing an\nalready-Instagram draft (use `ig-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 `ig-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules.\n\n**Never invent the specifics.** The rules below ask for a concrete number, a date and a named entity, because that is what separates a real post from a generated one. Take them from what the user actually said in this conversation. **Do not invent a figure, a date, a client name or a result, and do not soften a vague claim into a plausible-looking number.** If the user has nothing concrete for a beat, ask them once, and if they still have nothing, drop the claim rather than decorate it. A published invented number is a retraction; a missing one is only a weaker post.\n\n1. **Take the source.** Any format: a post, a paragraph, a script, a caption, a\n   transcript, a bullet list, a link to read. Ask for the source, the media the\n   user has (Instagram needs an image or video), and the goal (saves \u002F shares \u002F\n   comments \u002F follows) if not given.\n2. **Extract the spine.** Strip the source platform's shell and pull out the one\n   claim, the one story, or the one number worth keeping. Most repurposing fails\n   because it keeps the words instead of the point.\n3. **Choose the container.** One claim or number -> single caption. A teach, a\n   list, or a build -> carousel, one point per slide (hand structure to\n   `ig-carousel-planner`, hook slide to payoff slide). A long video -> a carousel\n   that delivers the payoff, not a summary.\n4. **Re-hook for the fold.** Instagram hides everything after ~125 characters\n   behind \"more\". Line one (or the hook slide) must land the whole punch on its\n   own. The source's hook almost never survives; write a new first line using a\n   2026 Instagram formula (see `..\u002F..\u002Freferences\u002Fhook-formulas.md`), picked by the\n   goal.\n5. **Refit the format.** Caption body skimmable, short lines, white space between\n   beats. Carousel: one idea per slide, no wall. Cut the source's connective\n   tissue; Instagram rewards the front-loaded payoff.\n6. **Strip off-platform artifacts.** Remove \"link in bio\" carried from another\n   platform, \"smash subscribe\", \"read more below\", X @-handles that only exist\n   there, and any \"as I wrote on LinkedIn\" throat-clearing. A repurposed post\n   should not admit it was repurposed.\n7. **Media reminder.** Instagram rejects text-only posts. Confirm the image,\n   video, or slide set the user will attach. A caption with no media is not\n   publishable.\n8. **Hashtags at the end.** Hand the topic to `ig-hashtag-strategist` or apply a\n   3-5 sized set yourself (see `..\u002F..\u002Freferences\u002Fhashtag-strategy.md`). Place them\n   as one block at the END of the caption or in the first comment, never as a\n   mid-text wall.\n9. **Humanizer pass.** Run `ig-humanizer` V3 on the result: 2026 AI vocab by\n   paragraph density, em dashes above the cap (about one per 100 words, never\n   swapped for a period), stacked rule-of-three triads, generic openers and\n   reveal bridges. Fix only a paragraph that reads machine-flat; never\n   manufacture variance. Keep the user's real numbers and named entities from\n   the source.\n10. **Approval card.** Show: source -> Instagram mapping (what became what), the\n    container (single caption or N-slide carousel), formula used, the hook (flag\n    if over 125 chars), hashtag set, the media the user must attach, primary goal.\n11. **On approval.** Publish via `lib.publish(kind=\"post\",\n    draft_text=\u003Capproved caption>, target_url=\"https:\u002F\u002Fwww.instagram.com\u002F\",\n    media=[\u003Clocal file paths>], platforms=[\u003CINSTAGRAM_PLATFORM_ID>],\n    scheduled_time=\u003Ciso_or_None>)`. For a Reel pass `kind=\"reel\"`. The wrapper\n    runs the Publora draft then upload then schedule flow. With no media or no\n    Publora key it returns a copy-paste block and a reminder to attach the media.\n\n## Native-fit rules (source -> Instagram)\n\n- **LinkedIn post -> Instagram:** a long post becomes a carousel (one point per\n  slide) or, if it is one sharp claim, a single caption. LinkedIn tolerates\n  warm-up; Instagram does not. The LinkedIn hook is usually too long; rewrite it\n  for the 125-char fold.\n- **Blog \u002F newsletter -> carousel:** turn the structure into slides, one point\n  per slide, hook slide first, payoff slide last. Do not paste the whole piece\n  into one caption.\n- **YouTube script -> carousel of the payoff:** lead with the video's payoff, not\n  its intro. Build the carousel around \"here's what I found\", not a scene-by-scene\n  recap.\n- **Tweet \u002F thread -> caption or carousel:** a single tweet becomes a caption; a\n  thread becomes a carousel, one tweet per slide with its own micro-point. Strip\n  X @-handles and thread numbering.\n\n## Hard rules\n\nGlobal voice rules: see root `SKILL.md` Voice rules. Additional skill-specific\nrules:\n\n- Keep the source's **claim and facts** intact. Repurposing changes the delivery,\n  never the meaning or the numbers.\n- The new first line (or hook slide) must stop the scroll on its own before the\n  125-char fold. If it needs the second line, rewrite it.\n- Never paste the source verbatim and trim. Rebuild the hook and rhythm from the\n  spine.\n- One specific number where the source offers one. Keep it.\n- 3-5 sized hashtags as one block at the end, never 30 and never mid-caption.\n- Media is required. Never present a repurposed caption as publishable without\n  reminding the user to attach the image, video, or slides.\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\", X\n  @-handles, thread numbering).\n- A hook that only makes sense after the 125-char fold.\n- A mid-caption hashtag wall instead of one block at the end.\n- Presenting a caption with no media as ready to post.\n- ALL CAPS first line for intensity. Carry it with word choice.\n- Em dashes above the cap (more than about one per 100 words), or an em dash swapped for a period.\n- \"The result?\" \u002F \"Here's the thing..\" reveal bridges and staccato stacks added during the rewrite.\n- Rule-of-three lists without specifics.\n- \"leverage\", \"fundamentally\", \"game-changer\", \"level up\", \"dive in\".\n- Meta throat-clearing (\"I originally posted this on...\").\n\n## Resources\n\n- `..\u002F..\u002Freferences\u002Fhook-formulas.md` - the 10 Instagram formula skeletons to re-hook with\n- `..\u002F..\u002Freferences\u002Falgorithm-heuristics.md` - 2026 Instagram ranking rules (fold, timing, signals)\n- `..\u002F..\u002Freferences\u002Fhashtag-strategy.md` - the 3-5 sized hashtag recipe\n- `..\u002F..\u002Freferences\u002Fmedia-workflow.md` - the draft, upload, schedule flow\n\n## Related skills\n\n- `ig-caption-writer` - write a fresh single caption from scratch\n- `ig-carousel-planner` - structure a slide-by-slide carousel (repurposer hands long builds here)\n- `ig-hashtag-strategist` - build the sized hashtag set\n- `ig-humanizer` - scrub AI tells, plus `--mode audit` to review the result\n","# Instagram Repurposer\n\nTurn something you already made into a post that reads like it was born on\nInstagram. Repurposing is not copy-paste. A post that killed on LinkedIn or a\nthread that flew on X will die on Instagram if you paste it: wrong hook, wrong\ncontainer, wrong rhythm, no media, and artifacts (\"link in bio\", @-handles,\nhashtag walls) that scream off-platform.\n\nThis skill transforms, it does not generate. It reads your source, keeps the\nidea, and rebuilds the delivery for Instagram.\n\n## When to use\n\n- \"Turn this LinkedIn post into an Instagram carousel \u002F caption\"\n- \"Repurpose my blog post \u002F newsletter \u002F YouTube script for Instagram\"\n- \"This thread worked on X, adapt it for Instagram\"\n- \"I have a rough idea in another format, make it native here\"\n\nNot for a blank-page draft (use `ig-caption-writer` for a single caption,\n`ig-carousel-planner` for a slide-by-slide carousel) and not for reviewing an\nalready-Instagram draft (use `ig-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 `ig-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules.\n\n**Never invent the specifics.** The rules below ask for a concrete number, a date and a named entity, because that is what separates a real post from a generated one. Take them from what the user actually said in this conversation. **Do not invent a figure, a date, a client name or a result, and do not soften a vague claim into a plausible-looking number.** If the user has nothing concrete for a beat, ask them once, and if they still have nothing, drop the claim rather than decorate it. A published invented number is a retraction; a missing one is only a weaker post.\n\n1. **Take the source.** Any format: a post, a paragraph, a script, a caption, a\n   transcript, a bullet list, a link to read. Ask for the source, the media the\n   user has (Instagram needs an image or video), and the goal (saves \u002F shares \u002F\n   comments \u002F follows) if not given.\n2. **Extract the spine.** Strip the source platform's shell and pull out the one\n   claim, the one story, or the one number worth keeping. Most repurposing fails\n   because it keeps the words instead of the point.\n3. **Choose the container.** One claim or number -> single caption. A teach, a\n   list, or a build -> carousel, one point per slide (hand structure to\n   `ig-carousel-planner`, hook slide to payoff slide). A long video -> a carousel\n   that delivers the payoff, not a summary.\n4. **Re-hook for the fold.** Instagram hides everything after ~125 characters\n   behind \"more\". Line one (or the hook slide) must land the whole punch on its\n   own. The source's hook almost never survives; write a new first line using a\n   2026 Instagram formula (see `..\u002F..\u002Freferences\u002Fhook-formulas.md`), picked by the\n   goal.\n5. **Refit the format.** Caption body skimmable, short lines, white space between\n   beats. Carousel: one idea per slide, no wall. Cut the source's connective\n   tissue; Instagram rewards the front-loaded payoff.\n6. **Strip off-platform artifacts.** Remove \"link in bio\" carried from another\n   platform, \"smash subscribe\", \"read more below\", X @-handles that only exist\n   there, and any \"as I wrote on LinkedIn\" throat-clearing. A repurposed post\n   should not admit it was repurposed.\n7. **Media reminder.** Instagram rejects text-only posts. Confirm the image,\n   video, or slide set the user will attach. A caption with no media is not\n   publishable.\n8. **Hashtags at the end.** Hand the topic to `ig-hashtag-strategist` or apply a\n   3-5 sized set yourself (see `..\u002F..\u002Freferences\u002Fhashtag-strategy.md`). Place them\n   as one block at the END of the caption or in the first comment, never as a\n   mid-text wall.\n9. **Humanizer pass.** Run `ig-humanizer` V3 on the result: 2026 AI vocab by\n   paragraph density, em dashes above the cap (about one per 100 words, never\n   swapped for a period), stacked rule-of-three triads, generic openers and\n   reveal bridges. Fix only a paragraph that reads machine-flat; never\n   manufacture variance. Keep the user's real numbers and named entities from\n   the source.\n10. **Approval card.** Show: source -> Instagram mapping (what became what), the\n    container (single caption or N-slide carousel), formula used, the hook (flag\n    if over 125 chars), hashtag set, the media the user must attach, primary goal.\n11. **On approval.** Publish via `lib.publish(kind=\"post\",\n    draft_text=\u003Capproved caption>, target_url=\"https:\u002F\u002Fwww.instagram.com\u002F\",\n    media=[\u003Clocal file paths>], platforms=[\u003CINSTAGRAM_PLATFORM_ID>],\n    scheduled_time=\u003Ciso_or_None>)`. For a Reel pass `kind=\"reel\"`. The wrapper\n    runs the Publora draft then upload then schedule flow. With no media or no\n    Publora key it returns a copy-paste block and a reminder to attach the media.\n\n## Native-fit rules (source -> Instagram)\n\n- **LinkedIn post -> Instagram:** a long post becomes a carousel (one point per\n  slide) or, if it is one sharp claim, a single caption. LinkedIn tolerates\n  warm-up; Instagram does not. The LinkedIn hook is usually too long; rewrite it\n  for the 125-char fold.\n- **Blog \u002F newsletter -> carousel:** turn the structure into slides, one point\n  per slide, hook slide first, payoff slide last. Do not paste the whole piece\n  into one caption.\n- **YouTube script -> carousel of the payoff:** lead with the video's payoff, not\n  its intro. Build the carousel around \"here's what I found\", not a scene-by-scene\n  recap.\n- **Tweet \u002F thread -> caption or carousel:** a single tweet becomes a caption; a\n  thread becomes a carousel, one tweet per slide with its own micro-point. Strip\n  X @-handles and thread numbering.\n\n## Hard rules\n\nGlobal voice rules: see root `SKILL.md` Voice rules. Additional skill-specific\nrules:\n\n- Keep the source's **claim and facts** intact. Repurposing changes the delivery,\n  never the meaning or the numbers.\n- The new first line (or hook slide) must stop the scroll on its own before the\n  125-char fold. If it needs the second line, rewrite it.\n- Never paste the source verbatim and trim. Rebuild the hook and rhythm from the\n  spine.\n- One specific number where the source offers one. Keep it.\n- 3-5 sized hashtags as one block at the end, never 30 and never mid-caption.\n- Media is required. Never present a repurposed caption as publishable without\n  reminding the user to attach the image, video, or slides.\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\", X\n  @-handles, thread numbering).\n- A hook that only makes sense after the 125-char fold.\n- A mid-caption hashtag wall instead of one block at the end.\n- Presenting a caption with no media as ready to post.\n- ALL CAPS first line for intensity. Carry it with word choice.\n- Em dashes above the cap (more than about one per 100 words), or an em dash swapped for a period.\n- \"The result?\" \u002F \"Here's the thing..\" reveal bridges and staccato stacks added during the rewrite.\n- Rule-of-three lists without specifics.\n- \"leverage\", \"fundamentally\", \"game-changer\", \"level up\", \"dive in\".\n- Meta throat-clearing (\"I originally posted this on...\").\n\n## Resources\n\n- `..\u002F..\u002Freferences\u002Fhook-formulas.md` - the 10 Instagram formula skeletons to re-hook with\n- `..\u002F..\u002Freferences\u002Falgorithm-heuristics.md` - 2026 Instagram ranking rules (fold, timing, signals)\n- `..\u002F..\u002Freferences\u002Fhashtag-strategy.md` - the 3-5 sized hashtag recipe\n- `..\u002F..\u002Freferences\u002Fmedia-workflow.md` - the draft, upload, schedule flow\n\n## Related skills\n\n- `ig-caption-writer` - write a fresh single caption from scratch\n- `ig-carousel-planner` - structure a slide-by-slide carousel (repurposer hands long builds here)\n- `ig-hashtag-strategist` - build the sized hashtag set\n- `ig-humanizer` - scrub AI tells, plus `--mode audit` to review the result\n",{"name":5,"description":7},"main","a73152352c0612252131e5cf84e91312a6cf17dc","marketing\u002Finstagram-marketing\u002F.codex-marketplace\u002Finstagram-skills\u002Fskills\u002Fig-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 ig-repurposer",{"tool":38,"command":39},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill ig-repurposer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill ig-repurposer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Finstagram-marketing\u002F.codex-marketplace\u002Finstagram-skills\u002Fskills\u002Fig-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",[],[]]