[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M781B2ASND57JEB394ZBGMPB":3,"skill-same:01M781B2ASND57JEB394ZBGMPB":92},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M781B2ASND57JEB394ZBGMPB","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.","TheAngryPit\u002FTheAngrySkills","TheAngryPit","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7040636?v=4","01M7803EENA9ATXJ46S9268QJX","Vitor Cepeda Lopes","01M7803EF9FMF4G4420XE4DV7Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-loops\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\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":25,"description":7},{"version":26},"1.8.4","main","f31e1d2df163b90a48e30d0a3df67285f6641418","skills\u002Fmirrors-marketing\u002Fmarketing-loops",1,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills","https:\u002F\u002Fgithub.com\u002FTheAngryPit","www.vitorcepedalopes.com","Creative Director | Executive Producer | Storyteller | Narrative Worlds & Creative Production Systems\r\nFounder @TheHive-Mind ","2026-11-14 21:48:38",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add TheAngryPit\u002FTheAngrySkills --skill marketing-loops",{"tool":42,"command":43},"bunx","bunx skills add TheAngryPit\u002FTheAngrySkills --skill marketing-loops",{"tool":45,"command":46},"pnpm","pnpm dlx skills add TheAngryPit\u002FTheAngrySkills --skill marketing-loops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-loops\u002FSKILL.md",true,[50,56,60,64,68,72,76,80,84,88],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"evals\u002Fevals.json","REFERENCE","参考文档",11928,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-loops\u002Fevals\u002Fevals.json",{"path":57,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":16},"LICENSE","许可证",1069,{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"MIRROR.md",584,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-loops\u002FMIRROR.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Floop-catalog.md",68529,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-loops\u002Freferences\u002Floop-catalog.md",{"path":69,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Floop-guardrails.md",4998,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-loops\u002Freferences\u002Floop-guardrails.md",{"path":73,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Floop-orchestration.md",5333,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-loops\u002Freferences\u002Floop-orchestration.md",{"path":77,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Floop-state.md",5868,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-loops\u002Freferences\u002Floop-state.md",{"path":81,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Floop-template.md",5122,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-loops\u002Freferences\u002Floop-template.md",{"path":85,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Foutbound-operator.md",5001,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-loops\u002Freferences\u002Foutbound-operator.md",{"path":89,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fseo-operator.md",8387,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-marketing\u002Fmarketing-loops\u002Freferences\u002Fseo-operator.md",[93,100,107,114,121,128],{"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":20},"01M782GJ4CTPNKZN0WXTASXXZ4","X MCP guide","ALWAYS read this before using any X tool (the X plugin, any X MCP, or Grok Bot's built-in public X reads) and again on any X error. X tools are included in Grok Bot at no cost: never estimate costs, check credits, or tell the user to buy credits. tools=0 \u002F user-X-* not found is a setup failure, not a paywall. Covers Spaces, communities, and Lists (reads and list writes), X Chat (XChat, inbox, DMs, unread, message requests, Chat PIN, juicebox, xchat_lite: clone xchat-grokbot-helper yourself and decrypt locally), scheduled X calls (schedule_call, list_scheduled_calls and the other call tools), and livestreams (stream sources, broadcasts, scheduled broadcasts, broadcast chat, moderators, mutes). Chat, call, livestream, Spaces, or Lists tools missing while other X tools work: reconnect the X plugin.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx\u002Fskills\u002Fx-api-mcp-guide\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M782GBW77901ESC9PD3XAM6V","X Money guide","Read this before the first X Money action in a session and again on any X Money error, refusal, or missing capability. Covers the approval rule for every action that moves money (always ask, every time, no exceptions), how the connection works (connection code plus passkey in the X app), how to guide the user through connect, reconnect, and revoke at x.com\u002Fi\u002Fmoney\u002Fsettings\u002Fconnections, and what each failure message means.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx-money\u002Fskills\u002Fx-money-guide\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M782G7CMYD2JSVT3RX81QRB8","google-slides","Build and edit Google Slides through the google-slides MCP tools - slides, grids of cards and columns, text boxes, shapes, images, tables, styling, layout inspection, and per-slide PNG rendering. Use when creating a deck, laying out slide elements, matching a template, or verifying how a slide looks.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-slides\u002Fskills\u002Fgoogle-slides\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M782G4DDAJ4SMGJEF13HTX69","google-sheets","Build and edit Google Sheets with the google-sheets tools - values, formatting, charts, conditional formatting, structure, validation, named and protected ranges. Use when creating a spreadsheet or dashboard, formatting cells, adding or fixing charts, or reorganizing tabs and rows.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-sheets\u002Fskills\u002Fgoogle-sheets\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M782G1F8QNMNKRSY6M3Y0QG6","google-drive","Work with Google Drive through its MCP tools - search, read, create, organize, share, comment, and export files. Use when creating files in specific folders, moving or renaming, converting Markdown\u002FCSV into Docs\u002FSheets, managing comments, or exporting a rendered PDF.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-drive\u002Fskills\u002Fgoogle-drive\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":20},"01M782FYVJ5XTP2R0B446RRYTX","google-docs","Author and edit Google Docs with the google-docs tools - structured writing, character and paragraph styling, lists, tables, images, headers\u002Ffooters. Use when creating a formatted document, editing document content, or applying styles.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-docs\u002Fskills\u002Fgoogle-docs\u002FSKILL.md",[],[]]