[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CWCAXM3TDRRX3J6PR4BK6P":3,"skill-same:01M7CWCAXM3TDRRX3J6PR4BK6P":82},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CWCAXM3TDRRX3J6PR4BK6P","marketing-loops",null,"When the user wants a recurring marketing job an AI agent runs on a cadence or trigger, or asks what a weekly or daily automated check should do, remember, and when it should stop: SEO and ads checks, churn watches, outbound triage. For one-off ideas, see marketing-ideas. For the test loop, see ab-testing.","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\u002Fmarketing-loops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: marketing-loops\ndescription: \"When the user wants a recurring marketing job an AI agent runs on a cadence or trigger, or asks what a weekly or daily automated check should do, remember, and when it should stop: SEO and ads checks, churn watches, outbound triage. For one-off ideas, see marketing-ideas. For the test loop, see ab-testing.\"\nmetadata:\n  version: 1.8.4\n---\n\n# Marketing Loops\n\nYou help set up **marketing loops** — repeatable marketing workflows an AI agent runs on a cadence, each with a defined trigger, a bounded set of steps, a self-check, and an explicit stopping condition. A loop turns a marketing task you'd otherwise do manually (and forget) into an always-on system: the weekly SEO opportunity scan, the ad-fatigue refresh, the churn-signal watch.\n\nThis is the operational cousin of `marketing-ideas`. Ideas tell you *what to try once*. Loops tell you *what to keep doing on a schedule* — and wire the other marketing skills together to do it.\n\n## How to Use This Skill\n\n**Check for product marketing context first:** if `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md`), read it before asking questions. Use that context and only ask for what's missing.\n\nThen:\n1. **Clarify the job.** What outcome should this loop protect or grow? (rankings, ad efficiency, activation, retention, revenue, referrals)\n2. **Pick a loop** from the catalog in `references\u002Floop-catalog.md` — or adapt the closest one.\n3. **Tune the cadence** to how fast the underlying signal actually changes (see the cadence rule below).\n4. **Confirm the human checkpoint.** Decide what the loop does autonomously vs. what it stages for human approval before publishing or spending — see `references\u002Floop-guardrails.md`.\n5. **Schedule it** (see \"Scheduling a loop\" below).\n\nBuilding more than one loop, or a whole marketing operating system? See `references\u002Floop-orchestration.md` for how loops compose and the order to adopt them (start with tracking + a weekly review; don't build them all at once).\n\n## Anatomy of a Marketing Loop\n\nEvery loop in the catalog has these nine parts. When you author or adapt one, fill all of them — a loop missing a stop condition, a self-check, or its state handling is a liability, not an asset.\n\n| Part | What it defines |\n|------|-----------------|\n| **Check cadence** | How often the loop *looks* (weekly \u002F daily \u002F on-trigger). Match it to signal speed. |\n| **Acts when** | The action condition — what must be true to actually *do* something, vs. just check and skip. Most runs of a good loop are \"checked, nothing to do.\" |\n| **Purpose** | The one outcome this loop exists to move. |\n| **Skills used** | Which marketing skills the loop orchestrates each iteration. |\n| **Loop body** | The ordered steps run each iteration. |\n| **Self-check** | The verification done *before* acting — so the loop doesn't act on noise, seasonality, or a tracking bug. |\n| **State \u002F idempotency** | What the loop remembers between runs: last-run marker, dedupe key, cooldown window, \"already handled\" set. Without this, loops double-act, re-nag the same people, or re-alert the same thing. Non-negotiable for anything scheduled — see `references\u002Floop-state.md` for where state lives and the idempotency patterns. |\n| **Stop \u002F bail-out** | When the loop skips, halts, escalates to a human, or disables itself — plus what it does on error. Every loop needs one, including heartbeat loops (their stop is \"manual disable + error-halt,\" never \"n\u002Fa\"). |\n| **Output** | Where results go: a file, a PR, a staged draft, a notification, a report. |\n\nThe **Check cadence \u002F Acts when** split matters: a churn-signal loop might *check* daily but only *act* when an account crosses a risk threshold it hasn't been contacted about inside the cooldown window. Conflating the two produces loops that either miss the window or spam.\n\n## The cadence rule\n\nMatch cadence to how fast the signal actually changes — not to how often you'd *like* an update.\n\n| Signal | Realistic cadence | Why |\n|--------|-------------------|-----|\n| Rankings, backlinks, domain authority | Weekly | Move slowly; daily checks are noise |\n| Ad creative fatigue, CPA drift | Every 2–3 days | Meta\u002FGoogle feedback loops are days, not hours |\n| Activation \u002F onboarding funnel | Weekly | Needs enough signups to be significant |\n| Churn signals | Daily or on-trigger | Early intervention window is short |\n| Content \u002F copy decay | Monthly | Traffic erosion is gradual |\n| Competitor changes | Weekly | Pricing\u002Fpositioning shifts are infrequent but matter |\n| Social listening \u002F mentions | Daily | Engagement windows close fast |\n\nOver-frequent loops are the most common failure mode: they generate busywork, burn budget, and train you to ignore the output.\n\n## When NOT to loop\n\nNot everything should be automated on a cadence. Skip a loop — or add a mandatory human checkpoint — when:\n\n- **Strategy or creative direction is the real work.** Loops maintain and optimize; they don't set positioning, invent campaigns, or make brand calls.\n- **The action publishes or spends without review.** Auto-*drafting* an ad, email, or post is fine. Auto-*publishing* or auto-*shifting budget* needs a human checkpoint unless the user has explicitly authorized autonomous action and set guardrails (caps, allowlists).\n- **The signal is too sparse to be significant.** A weekly conversion-rate loop on 40 visitors\u002Fweek is measuring noise.\n- **It's a vanity loop.** If nobody acts on the output, delete the loop. A loop that emails a dashboard nobody reads is worse than nothing.\n\nFor any loop that sends, spends, publishes, or touches personal data, apply `references\u002Floop-guardrails.md` — the two-tier action model (autonomous-safe vs. gated), spend\u002Fsend caps, CAN-SPAM\u002FGDPR\u002FFTC\u002FToS rules, the always-escalate list, and a required kill switch.\n\n## Scheduling a loop\n\nThese loops are agent-agnostic — the *body* works in any agent. The *scheduling* depends on your environment:\n\n- **Claude Code** — native options: `\u002Floop` (self-paced, until a condition), `ScheduleWakeup` (dynamic pacing that reacts to state), and `CronCreate` (fixed cron schedule). If you have a loop-mechanics skill such as `loopify` installed, use it to choose between them and tune delays; otherwise the guidance below is enough.\n- **Any agent + cron** — wrap the loop body as a scheduled prompt\u002Fscript (`0 9 * * 1` for Mondays 9am, etc.).\n- **Manual cadence** — for high-judgment loops, \"run this skill every Monday\" is a perfectly good loop. The value is the repeatable *body*, not the automation.\n\nDefault to time-of-day cron for review-style loops (weekly review, ranking watch) and dynamic pacing for monitor-until-threshold loops (churn watch, launch-day tracking).\n\n## The Catalog\n\n`references\u002Floop-catalog.md` holds the full library — 60 marketing loops with thorough funnel coverage: SEO & Content, Paid, Earned\u002FSocial\u002FPartnerships, Outbound, Activation, Retention, Revenue, Referral & Advocacy, and Ongoing Ops. Each is a complete, adaptable spec. Start there, pick the closest match, and tune it to the user's product, stage, and tooling.\n\n## Running a whole channel: the SEO operator\n\nWhen the user wants an agent to own SEO for a site rather than run one loop, use `references\u002Fseo-operator.md`. It bundles the SEO loops (site health, claim drift, striking-distance push, AI-answer check, keyword gap, content decay, competitor watch, and more) into one schedule with shared memory in `.agents\u002Fseo\u002F`, a first-run checklist, operating rules, a writing gate, and a one-screen weekly report.\n\n## Running outbound: the outbound operator\n\nFor an agent running day-to-day outbound (signal sweeps, staged outreach, reply triage, sending-domain health, weekly sequence retros), use `references\u002Foutbound-operator.md`. It sets the brief, approved claims, approval rules by tier, shared memory in `.agents\u002Foutbound\u002F`, and a weekly report.\n\n## Authoring a new loop\n\nWhen nothing in the catalog fits, author a new loop from `references\u002Floop-template.md` — a copy-paste template with fill-in prompts, a worked before\u002Fafter example, and a ship checklist. Fill all nine anatomy parts; if you can't answer the self-check, state\u002Fidempotency, and stop\u002Fbail-out concretely, the loop isn't ready to run.\n\n## Anti-patterns\n\n- Looping without a stop condition → runaway spend or infinite churn.\n- Same cadence for every loop → most run too often and get ignored.\n- No self-check → the loop acts on noise, seasonality, or a tracking bug.\n- No human checkpoint on spend\u002Fpublish actions.\n- Building 10 loops at once → start with one, prove it earns its keep, then add the next.\n\n## Banned vocabulary\n\nAvoid: \"set it and forget it,\" \"fully autonomous marketing,\" \"AI does everything,\" \"10x on autopilot,\" \"growth hacking machine.\" Loops are disciplined systems with checkpoints, not magic. Describe them honestly.\n\n## Related Skills\n\n- **marketing-ideas** — one-off tactics and inspiration (what to try). Loops operationalize the ones worth repeating.\n- **ab-testing** — the experimentation loop specifically (hypothesis → test → promote winner → repeat).\n- **analytics** — most loops read from analytics to decide whether to act.\n- **reverse-engineer-marketing** — the growth-move watch loop keeps a competitor teardown current, and teardown plays name the loop that sustains each one.\n- Individual channel skills (`ads`, `seo-audit`, `emails`, `social`, `churn-prevention`, `pricing`, `referrals`) — the loop bodies orchestrate these.\n","# Marketing Loops\n\nYou help set up **marketing loops** — repeatable marketing workflows an AI agent runs on a cadence, each with a defined trigger, a bounded set of steps, a self-check, and an explicit stopping condition. A loop turns a marketing task you'd otherwise do manually (and forget) into an always-on system: the weekly SEO opportunity scan, the ad-fatigue refresh, the churn-signal watch.\n\nThis is the operational cousin of `marketing-ideas`. Ideas tell you *what to try once*. Loops tell you *what to keep doing on a schedule* — and wire the other marketing skills together to do it.\n\n## How to Use This Skill\n\n**Check for product marketing context first:** if `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md`), read it before asking questions. Use that context and only ask for what's missing.\n\nThen:\n1. **Clarify the job.** What outcome should this loop protect or grow? (rankings, ad efficiency, activation, retention, revenue, referrals)\n2. **Pick a loop** from the catalog in `references\u002Floop-catalog.md` — or adapt the closest one.\n3. **Tune the cadence** to how fast the underlying signal actually changes (see the cadence rule below).\n4. **Confirm the human checkpoint.** Decide what the loop does autonomously vs. what it stages for human approval before publishing or spending — see `references\u002Floop-guardrails.md`.\n5. **Schedule it** (see \"Scheduling a loop\" below).\n\nBuilding more than one loop, or a whole marketing operating system? See `references\u002Floop-orchestration.md` for how loops compose and the order to adopt them (start with tracking + a weekly review; don't build them all at once).\n\n## Anatomy of a Marketing Loop\n\nEvery loop in the catalog has these nine parts. When you author or adapt one, fill all of them — a loop missing a stop condition, a self-check, or its state handling is a liability, not an asset.\n\n| Part | What it defines |\n|------|-----------------|\n| **Check cadence** | How often the loop *looks* (weekly \u002F daily \u002F on-trigger). Match it to signal speed. |\n| **Acts when** | The action condition — what must be true to actually *do* something, vs. just check and skip. Most runs of a good loop are \"checked, nothing to do.\" |\n| **Purpose** | The one outcome this loop exists to move. |\n| **Skills used** | Which marketing skills the loop orchestrates each iteration. |\n| **Loop body** | The ordered steps run each iteration. |\n| **Self-check** | The verification done *before* acting — so the loop doesn't act on noise, seasonality, or a tracking bug. |\n| **State \u002F idempotency** | What the loop remembers between runs: last-run marker, dedupe key, cooldown window, \"already handled\" set. Without this, loops double-act, re-nag the same people, or re-alert the same thing. Non-negotiable for anything scheduled — see `references\u002Floop-state.md` for where state lives and the idempotency patterns. |\n| **Stop \u002F bail-out** | When the loop skips, halts, escalates to a human, or disables itself — plus what it does on error. Every loop needs one, including heartbeat loops (their stop is \"manual disable + error-halt,\" never \"n\u002Fa\"). |\n| **Output** | Where results go: a file, a PR, a staged draft, a notification, a report. |\n\nThe **Check cadence \u002F Acts when** split matters: a churn-signal loop might *check* daily but only *act* when an account crosses a risk threshold it hasn't been contacted about inside the cooldown window. Conflating the two produces loops that either miss the window or spam.\n\n## The cadence rule\n\nMatch cadence to how fast the signal actually changes — not to how often you'd *like* an update.\n\n| Signal | Realistic cadence | Why |\n|--------|-------------------|-----|\n| Rankings, backlinks, domain authority | Weekly | Move slowly; daily checks are noise |\n| Ad creative fatigue, CPA drift | Every 2–3 days | Meta\u002FGoogle feedback loops are days, not hours |\n| Activation \u002F onboarding funnel | Weekly | Needs enough signups to be significant |\n| Churn signals | Daily or on-trigger | Early intervention window is short |\n| Content \u002F copy decay | Monthly | Traffic erosion is gradual |\n| Competitor changes | Weekly | Pricing\u002Fpositioning shifts are infrequent but matter |\n| Social listening \u002F mentions | Daily | Engagement windows close fast |\n\nOver-frequent loops are the most common failure mode: they generate busywork, burn budget, and train you to ignore the output.\n\n## When NOT to loop\n\nNot everything should be automated on a cadence. Skip a loop — or add a mandatory human checkpoint — when:\n\n- **Strategy or creative direction is the real work.** Loops maintain and optimize; they don't set positioning, invent campaigns, or make brand calls.\n- **The action publishes or spends without review.** Auto-*drafting* an ad, email, or post is fine. Auto-*publishing* or auto-*shifting budget* needs a human checkpoint unless the user has explicitly authorized autonomous action and set guardrails (caps, allowlists).\n- **The signal is too sparse to be significant.** A weekly conversion-rate loop on 40 visitors\u002Fweek is measuring noise.\n- **It's a vanity loop.** If nobody acts on the output, delete the loop. A loop that emails a dashboard nobody reads is worse than nothing.\n\nFor any loop that sends, spends, publishes, or touches personal data, apply `references\u002Floop-guardrails.md` — the two-tier action model (autonomous-safe vs. gated), spend\u002Fsend caps, CAN-SPAM\u002FGDPR\u002FFTC\u002FToS rules, the always-escalate list, and a required kill switch.\n\n## Scheduling a loop\n\nThese loops are agent-agnostic — the *body* works in any agent. The *scheduling* depends on your environment:\n\n- **Claude Code** — native options: `\u002Floop` (self-paced, until a condition), `ScheduleWakeup` (dynamic pacing that reacts to state), and `CronCreate` (fixed cron schedule). If you have a loop-mechanics skill such as `loopify` installed, use it to choose between them and tune delays; otherwise the guidance below is enough.\n- **Any agent + cron** — wrap the loop body as a scheduled prompt\u002Fscript (`0 9 * * 1` for Mondays 9am, etc.).\n- **Manual cadence** — for high-judgment loops, \"run this skill every Monday\" is a perfectly good loop. The value is the repeatable *body*, not the automation.\n\nDefault to time-of-day cron for review-style loops (weekly review, ranking watch) and dynamic pacing for monitor-until-threshold loops (churn watch, launch-day tracking).\n\n## The Catalog\n\n`references\u002Floop-catalog.md` holds the full library — 60 marketing loops with thorough funnel coverage: SEO & Content, Paid, Earned\u002FSocial\u002FPartnerships, Outbound, Activation, Retention, Revenue, Referral & Advocacy, and Ongoing Ops. Each is a complete, adaptable spec. Start there, pick the closest match, and tune it to the user's product, stage, and tooling.\n\n## Running a whole channel: the SEO operator\n\nWhen the user wants an agent to own SEO for a site rather than run one loop, use `references\u002Fseo-operator.md`. It bundles the SEO loops (site health, claim drift, striking-distance push, AI-answer check, keyword gap, content decay, competitor watch, and more) into one schedule with shared memory in `.agents\u002Fseo\u002F`, a first-run checklist, operating rules, a writing gate, and a one-screen weekly report.\n\n## Running outbound: the outbound operator\n\nFor an agent running day-to-day outbound (signal sweeps, staged outreach, reply triage, sending-domain health, weekly sequence retros), use `references\u002Foutbound-operator.md`. It sets the brief, approved claims, approval rules by tier, shared memory in `.agents\u002Foutbound\u002F`, and a weekly report.\n\n## Authoring a new loop\n\nWhen nothing in the catalog fits, author a new loop from `references\u002Floop-template.md` — a copy-paste template with fill-in prompts, a worked before\u002Fafter example, and a ship checklist. Fill all nine anatomy parts; if you can't answer the self-check, state\u002Fidempotency, and stop\u002Fbail-out concretely, the loop isn't ready to run.\n\n## Anti-patterns\n\n- Looping without a stop condition → runaway spend or infinite churn.\n- Same cadence for every loop → most run too often and get ignored.\n- No self-check → the loop acts on noise, seasonality, or a tracking bug.\n- No human checkpoint on spend\u002Fpublish actions.\n- Building 10 loops at once → start with one, prove it earns its keep, then add the next.\n\n## Banned vocabulary\n\nAvoid: \"set it and forget it,\" \"fully autonomous marketing,\" \"AI does everything,\" \"10x on autopilot,\" \"growth hacking machine.\" Loops are disciplined systems with checkpoints, not magic. Describe them honestly.\n\n## Related Skills\n\n- **marketing-ideas** — one-off tactics and inspiration (what to try). Loops operationalize the ones worth repeating.\n- **ab-testing** — the experimentation loop specifically (hypothesis → test → promote winner → repeat).\n- **analytics** — most loops read from analytics to decide whether to act.\n- **reverse-engineer-marketing** — the growth-move watch loop keeps a competitor teardown current, and teardown plays name the loop that sustains each one.\n- Individual channel skills (`ads`, `seo-audit`, `emails`, `social`, `churn-prevention`, `pricing`, `referrals`) — the loop bodies orchestrate these.\n",{"name":5,"metadata":24,"description":7},{"version":25},"1.8.4","main","a73152352c0612252131e5cf84e91312a6cf17dc","marketing\u002Fmarketing-loops","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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill marketing-loops",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill marketing-loops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill marketing-loops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-loops\u002FSKILL.md",true,[48,54,58,62,66,70,74,78],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"evals\u002Fevals.json","REFERENCE","参考文档",11928,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-loops\u002Fevals\u002Fevals.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Floop-catalog.md",68519,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-loops\u002Freferences\u002Floop-catalog.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Floop-guardrails.md",4998,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-loops\u002Freferences\u002Floop-guardrails.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Floop-orchestration.md",5333,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-loops\u002Freferences\u002Floop-orchestration.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Floop-state.md",5868,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-loops\u002Freferences\u002Floop-state.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Floop-template.md",5122,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-loops\u002Freferences\u002Floop-template.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Foutbound-operator.md",5001,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-loops\u002Freferences\u002Foutbound-operator.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fseo-operator.md",8377,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fmarketing\u002Fmarketing-loops\u002Freferences\u002Fseo-operator.md",[83,90,97,105,112,119],{"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},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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",[],[]]