[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CW3H77PRVHF7M1QMHMKDPD":3,"skill-same:01M7CW3H77PRVHF7M1QMHMKDPD":56},{"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},"01M7CW3H77PRVHF7M1QMHMKDPD","linkedin-content-planner",null,"Generate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post pillar, format, hook type, CTA, posting time, daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week or month of content, not draft a single post (use linkedin-post-writer).","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-content-planner\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: linkedin-content-planner\ndescription: \"Generate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post pillar, format, hook type, CTA, posting time, daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week or month of content, not draft a single post (use linkedin-post-writer).\"\n---\n\n# LinkedIn Content Planner\n\nProduce a 7-day LinkedIn plan built around the 3-pillar discipline (Authority 40-50%, Personal Narrative 30-40%, Community 20-30%). Optionally adds a Product\u002FOffer pillar at 10-15%.\n\n## When to use\n\n- User asks \"plan my week\" or \"what should I post this week\"\n- User wants to escape ad-hoc shipping and establish rhythm\n- Before a launch week (user needs product-pillar alignment)\n\n## Input\n\n- **Theme** (optional): e.g., \"AI agents shipping in production\", \"first 6 months of Co.Actor\"\n- **Audience description:** e.g., \"B2B founders, AI ops leaders, marketing VPs\"\n- **Pillar mix** (optional): defaults to 40% Authority \u002F 30% Narrative \u002F 20% Community \u002F 10% Product\n- **Posting days** (optional): defaults to Tue\u002FWed\u002FThu\u002FFri (4 posts)\n- **Voice samples** (optional): paths to past posts for voice calibration\n\n## Output\n\nA markdown plan with:\n\n### 7-day calendar\n\n| Day | Time | Pillar | Format | Hook formula | 1-line angle | CTA type | Goal |\n|---|---|---|---|---|---|---|---|\n| Mon | — | (commenting day) | — | — | — | — | — |\n| Tue | 8:00 AM local | Authority | Text | F7 Odd-Precision Money | \"What 3 months of agent ops costs\" | Question close | Saves |\n| Wed | 9:30 AM local | Narrative | Text | F4 Time-Anchor Confession | \"Why I stopped publishing for 4 weeks\" | Mirror question | Comments |\n| Thu | 8:00 AM local | Community | Text | F14 Named Gratitude | \"The 3 people who shaped our launch\" | Tag + thanks | Reposts |\n| Fri | 9:00 AM local | Narrative | Text | F11 Emotional Cold-Open | \"The night our first deploy failed\" | Soft close | Likes |\n| Sat\u002FSun | — | (off) | — | — | — | — | — |\n\nThe Goal column spans saves \u002F comments \u002F reposts \u002F likes across the four posts, satisfying the Goal mix check below.\n\n### Daily comment targets\n\nFor each posting day:\n- **3-5 creators to engage** (names or archetypes: \"peer founders at 5-20k\", \"VCs with AI thesis\", \"BigCo CTOs\")\n- **Comment pattern** to apply (first-commenter, data-first, answer-their-question)\n- **Target count:** 10-20 substantive comments per day\n\n### Weekly inbound-readiness check\n\n- [ ] At least 1 vulnerability post (Narrative)\n- [ ] At least 1 receipt\u002Fdata post (Authority)\n- [ ] At least 1 soft offer or CTA-driving post\n- [ ] Comment strategy includes 70% peers, 20% aspirational, 10% prospects\n- [ ] No pillar >60% of the week's posts\n- [ ] No duplicate formula used twice in the same week\n- [ ] Goal mix spread: not every post chases the same reaction (see Goal mix below)\n\n## Rules\n\n- **3 pillars minimum, 5 maximum.** More than 5 dilutes signal.\n- **3-5 posts per week.** 6+\u002Fweek triggers cannibalization signal in 360Brew.\n- **10-20 comments\u002Fday** on other creators. Comments drive more inbound than posts.\n- **Tue\u002FWed\u002FThu** top for B2B. Avoid Fri after 2 PM, Sat\u002FSun (B2B 30-50% reach cut).\n- **One format per pillar per week.** Don't stack 3 text posts for Authority — vary.\n- **Product\u002FOffer pillar max 1 post\u002Fweek.** Overuse kills trust.\n\n## Formula → pillar mapping\n\n| Pillar | Preferred formulas |\n|---|---|\n| Authority | F7 Odd-Precision Money, F10 Contrarian Historical, F8 Paid-vs-Free, F5 Self-Proving Meta, F15 Explain-to-Kids |\n| Narrative | F4 Time-Anchor Confession, F3 Year-over-Year Pivot, F9 Curiosity-Gap, F11 Emotional Cold-Open, F16 Status-Strip |\n| Community | F6 Comment-Gate (use sparingly), F12 Permission Slip, F14 Named Gratitude, poll posts, spotlight mentions |\n| Product\u002FOffer | F2 R.I.P. Obituary (when pivoting category), F1 Anaphora (when framing product as fix), F13 Bait-and-Switch (upgrade announcements) |\n\n## Founders edition (alternative pillar set)\n\nWhen the whole plan is for a **founder** building trust with investors, hires, and design partners, swap the default pillar mix for the founder set from `..\u002F..\u002Freferences\u002Ffounder-topics.md`. It maps each pillar to founder **angles** (A1-A10) instead of generic topics, and leans on the structural formulas F17-F20.\n\n| Pillar | Share | Founder angles | Preferred formulas |\n|---|---|---|---|\n| **Conviction** (POV, category, product philosophy) | 30-40% | A1 Reprice, A7 Designed Serendipity, A8 Evasive-Sentence | F10, F18, F5 |\n| **Building in public** (the real, unglamorous work) | 30-40% | A5 Unglamorous Bet, A6 Limit of Delegation, A9 Delegation Line | F7, F4, F17 |\n| **The math** (how a founder actually decides) | 15-20% | A4 Scarce-Shots, A10 Learning Gate | F10, F18, F20 |\n| **Proof** (relationships and wins, told narrowly) | 10-15% | A2 Content-to-Pipeline, A3 Audience of One | F9, F11, F5 |\n\nSame guardrails apply: 3-5 posts\u002Fweek, no pillar above 60%, no formula repeated inside 7 days, spread the goal across the week. Ask the user \"founder plan or general plan?\" when the audience is a founder building a company, and default to this set if they say founder.\n\n## Goal mix (balance the week, not just the pillars)\n\nEvery formula earns a primary reaction: comments, reposts, likes, or saves (see `..\u002F..\u002Freferences\u002Fhook-formulas.md` \"Engagement-goal split\"). A week that is all comment-bait or all repost-bait reads as engineered and flattens reach. Spread the goals across the week:\n\n| Goal | Formulas | Weekly target |\n|---|---|---|\n| Comments | F4, F10, F12, F9 | at least 1 |\n| Reposts | F14, F2, F8 | at least 1 |\n| Likes | F11, F13, F16 | at least 1 |\n| Saves | F15, F7, F8 | at least 1 |\n\n## Steps\n\n1. Gather inputs. Ask user for theme, audience, pillar preferences if not provided.\n2. Validate pillar mix sums to 100%; warn if any pillar >60%.\n3. For each posting day, pick:\n   - Pillar (rotate to match mix)\n   - Formula from that pillar's bank (don't repeat within 7 days)\n   - Format (alternating text \u002F carousel \u002F poll per pillar rules)\n   - Specific angle (user provides or skill generates)\n   - Posting time (audience-timezone aware)\n4. For each posting day, add 3-5 comment targets with suggested pattern.\n5. Run inbound-readiness check; flag anything missing.\n6. Return as markdown + optional JSON for Notion\u002FAirtable import.\n\n## Example\n\nSee `references\u002Fexample-plan-week.md` for a filled-in 7-day plan.\n\n## Files\n\n- `SKILL.md` — this file\n- `references\u002Fexample-plan-week.md` — worked example\n- `references\u002Fpillars-framework.md` — the 3-pillar discipline explained\n- `..\u002F..\u002Freferences\u002Ffounder-topics.md` — founders-edition angle library (A1-A10) and founder pillar set\n\n## Related skills\n\n- `linkedin-post-writer` — generate each day's draft from the plan\n- `linkedin-comment-drafter` — execute the daily comment targets\n- `linkedin-thread-monitor` — track inbound from the comment strategy\n- `linkedin-engager-analytics` — segment audience on each post\n","# LinkedIn Content Planner\n\nProduce a 7-day LinkedIn plan built around the 3-pillar discipline (Authority 40-50%, Personal Narrative 30-40%, Community 20-30%). Optionally adds a Product\u002FOffer pillar at 10-15%.\n\n## When to use\n\n- User asks \"plan my week\" or \"what should I post this week\"\n- User wants to escape ad-hoc shipping and establish rhythm\n- Before a launch week (user needs product-pillar alignment)\n\n## Input\n\n- **Theme** (optional): e.g., \"AI agents shipping in production\", \"first 6 months of Co.Actor\"\n- **Audience description:** e.g., \"B2B founders, AI ops leaders, marketing VPs\"\n- **Pillar mix** (optional): defaults to 40% Authority \u002F 30% Narrative \u002F 20% Community \u002F 10% Product\n- **Posting days** (optional): defaults to Tue\u002FWed\u002FThu\u002FFri (4 posts)\n- **Voice samples** (optional): paths to past posts for voice calibration\n\n## Output\n\nA markdown plan with:\n\n### 7-day calendar\n\n| Day | Time | Pillar | Format | Hook formula | 1-line angle | CTA type | Goal |\n|---|---|---|---|---|---|---|---|\n| Mon | — | (commenting day) | — | — | — | — | — |\n| Tue | 8:00 AM local | Authority | Text | F7 Odd-Precision Money | \"What 3 months of agent ops costs\" | Question close | Saves |\n| Wed | 9:30 AM local | Narrative | Text | F4 Time-Anchor Confession | \"Why I stopped publishing for 4 weeks\" | Mirror question | Comments |\n| Thu | 8:00 AM local | Community | Text | F14 Named Gratitude | \"The 3 people who shaped our launch\" | Tag + thanks | Reposts |\n| Fri | 9:00 AM local | Narrative | Text | F11 Emotional Cold-Open | \"The night our first deploy failed\" | Soft close | Likes |\n| Sat\u002FSun | — | (off) | — | — | — | — | — |\n\nThe Goal column spans saves \u002F comments \u002F reposts \u002F likes across the four posts, satisfying the Goal mix check below.\n\n### Daily comment targets\n\nFor each posting day:\n- **3-5 creators to engage** (names or archetypes: \"peer founders at 5-20k\", \"VCs with AI thesis\", \"BigCo CTOs\")\n- **Comment pattern** to apply (first-commenter, data-first, answer-their-question)\n- **Target count:** 10-20 substantive comments per day\n\n### Weekly inbound-readiness check\n\n- [ ] At least 1 vulnerability post (Narrative)\n- [ ] At least 1 receipt\u002Fdata post (Authority)\n- [ ] At least 1 soft offer or CTA-driving post\n- [ ] Comment strategy includes 70% peers, 20% aspirational, 10% prospects\n- [ ] No pillar >60% of the week's posts\n- [ ] No duplicate formula used twice in the same week\n- [ ] Goal mix spread: not every post chases the same reaction (see Goal mix below)\n\n## Rules\n\n- **3 pillars minimum, 5 maximum.** More than 5 dilutes signal.\n- **3-5 posts per week.** 6+\u002Fweek triggers cannibalization signal in 360Brew.\n- **10-20 comments\u002Fday** on other creators. Comments drive more inbound than posts.\n- **Tue\u002FWed\u002FThu** top for B2B. Avoid Fri after 2 PM, Sat\u002FSun (B2B 30-50% reach cut).\n- **One format per pillar per week.** Don't stack 3 text posts for Authority — vary.\n- **Product\u002FOffer pillar max 1 post\u002Fweek.** Overuse kills trust.\n\n## Formula → pillar mapping\n\n| Pillar | Preferred formulas |\n|---|---|\n| Authority | F7 Odd-Precision Money, F10 Contrarian Historical, F8 Paid-vs-Free, F5 Self-Proving Meta, F15 Explain-to-Kids |\n| Narrative | F4 Time-Anchor Confession, F3 Year-over-Year Pivot, F9 Curiosity-Gap, F11 Emotional Cold-Open, F16 Status-Strip |\n| Community | F6 Comment-Gate (use sparingly), F12 Permission Slip, F14 Named Gratitude, poll posts, spotlight mentions |\n| Product\u002FOffer | F2 R.I.P. Obituary (when pivoting category), F1 Anaphora (when framing product as fix), F13 Bait-and-Switch (upgrade announcements) |\n\n## Founders edition (alternative pillar set)\n\nWhen the whole plan is for a **founder** building trust with investors, hires, and design partners, swap the default pillar mix for the founder set from `..\u002F..\u002Freferences\u002Ffounder-topics.md`. It maps each pillar to founder **angles** (A1-A10) instead of generic topics, and leans on the structural formulas F17-F20.\n\n| Pillar | Share | Founder angles | Preferred formulas |\n|---|---|---|---|\n| **Conviction** (POV, category, product philosophy) | 30-40% | A1 Reprice, A7 Designed Serendipity, A8 Evasive-Sentence | F10, F18, F5 |\n| **Building in public** (the real, unglamorous work) | 30-40% | A5 Unglamorous Bet, A6 Limit of Delegation, A9 Delegation Line | F7, F4, F17 |\n| **The math** (how a founder actually decides) | 15-20% | A4 Scarce-Shots, A10 Learning Gate | F10, F18, F20 |\n| **Proof** (relationships and wins, told narrowly) | 10-15% | A2 Content-to-Pipeline, A3 Audience of One | F9, F11, F5 |\n\nSame guardrails apply: 3-5 posts\u002Fweek, no pillar above 60%, no formula repeated inside 7 days, spread the goal across the week. Ask the user \"founder plan or general plan?\" when the audience is a founder building a company, and default to this set if they say founder.\n\n## Goal mix (balance the week, not just the pillars)\n\nEvery formula earns a primary reaction: comments, reposts, likes, or saves (see `..\u002F..\u002Freferences\u002Fhook-formulas.md` \"Engagement-goal split\"). A week that is all comment-bait or all repost-bait reads as engineered and flattens reach. Spread the goals across the week:\n\n| Goal | Formulas | Weekly target |\n|---|---|---|\n| Comments | F4, F10, F12, F9 | at least 1 |\n| Reposts | F14, F2, F8 | at least 1 |\n| Likes | F11, F13, F16 | at least 1 |\n| Saves | F15, F7, F8 | at least 1 |\n\n## Steps\n\n1. Gather inputs. Ask user for theme, audience, pillar preferences if not provided.\n2. Validate pillar mix sums to 100%; warn if any pillar >60%.\n3. For each posting day, pick:\n   - Pillar (rotate to match mix)\n   - Formula from that pillar's bank (don't repeat within 7 days)\n   - Format (alternating text \u002F carousel \u002F poll per pillar rules)\n   - Specific angle (user provides or skill generates)\n   - Posting time (audience-timezone aware)\n4. For each posting day, add 3-5 comment targets with suggested pattern.\n5. Run inbound-readiness check; flag anything missing.\n6. Return as markdown + optional JSON for Notion\u002FAirtable import.\n\n## Example\n\nSee `references\u002Fexample-plan-week.md` for a filled-in 7-day plan.\n\n## Files\n\n- `SKILL.md` — this file\n- `references\u002Fexample-plan-week.md` — worked example\n- `references\u002Fpillars-framework.md` — the 3-pillar discipline explained\n- `..\u002F..\u002Freferences\u002Ffounder-topics.md` — founders-edition angle library (A1-A10) and founder pillar set\n\n## Related skills\n\n- `linkedin-post-writer` — generate each day's draft from the plan\n- `linkedin-comment-drafter` — execute the daily comment targets\n- `linkedin-thread-monitor` — track inbound from the comment strategy\n- `linkedin-engager-analytics` — segment audience on each post\n",{"name":5,"description":7},"main","a73152352c0612252131e5cf84e91312a6cf17dc","marketing\u002Flinkedin-content-planner","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-content-planner",{"tool":38,"command":39},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill linkedin-content-planner",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill linkedin-content-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Flinkedin-content-planner\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fexample-plan-week.md","REFERENCE","参考文档",5166,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Flinkedin-content-planner\u002Freferences\u002Fexample-plan-week.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fpillars-framework.md",9676,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Flinkedin-content-planner\u002Freferences\u002Fpillars-framework.md",[57,64,71,79,86,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":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":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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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",[],[]]