[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEXKXEWMPMAH9SS44Z5CTT":3,"skill-same:01M7AEXKXEWMPMAH9SS44Z5CTT":74},{"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":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M7AEXKXEWMPMAH9SS44Z5CTT","rank-tracker",null,"Use when the user asks to \"track rankings\" or \"查排名\"; measures keyword and SERP-position deltas over time from provided exports or connected tools, including AI-response checks. Not for multi-metric stakeholder reports or setting alerts — use performance-monitor (report or alert mode). 排名追踪\u002FSERP监控","iamwaqargulzar\u002FMarketing-Agent-OS","iamwaqargulzar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96654715?v=4","01M7ACMBN0TACNXY53QYG8KDF6","Waqar Gulzar","01M7ACMBNP5ZX60H8CD3JK0633",8,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Fseo-geo\u002Fevaluate\u002Frank-tracker\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rank-tracker\nslug: rank-tracker\ndisplayName: \"Rank Tracker · 排名追踪\"\nsummary: \"排名追踪\u002FSERP监控\"\ndescription: 'Use when the user asks to \"track rankings\" or \"查排名\"; measures keyword and SERP-position deltas over time from provided exports or connected tools, including AI-response checks. Not for multi-metric stakeholder reports or setting alerts — use performance-monitor (report or alert mode). 排名追踪\u002FSERP监控'\nversion: \"20.1.0\"\nlicense: Apache-2.0\ncompatibility: \"Claude Code and compatible agent-skill hosts\"\nhomepage: \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills\"\nwhen_to_use: \"Use when tracking keyword rankings, monitoring position changes, comparing ranking snapshots, or detecting ranking drops.\"\nargument-hint: \"\u003Cdomain> [keyword list]\"\nallowed-tools: WebFetch\nmetadata: {\"author\": \"aaron-he-zhu\", \"version\": \"20.1.0\", \"discipline\": \"seo-geo\", \"phase\": \"evaluate\", \"geo-relevance\": \"medium\", \"hermes\": {\"tags\": [\"marketing\", \"seo-geo\", \"evaluate\"], \"category\": \"seo-geo\"}, \"openclaw\": {\"emoji\": \"🔍\", \"homepage\": \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills\"}}\n---\n\n# Rank Tracker\n\nTracks keyword positions, SERP feature ownership, and AI visibility over time.\n\n## Quick Start\n\n```\nSet up rank tracking for [domain] targeting these keywords: [keyword list]\n```\n\n```\nAnalyze ranking changes for [domain] over the past [time period]\n```\n\n## Skill Contract\n\n**Expected output**: a ranking report or delta summary plus the standard handoff summary for `memory\u002Fmonitoring\u002F`.\n\n- **Reads**: current rankings, prior baselines, target keyword list, locale\u002Flanguage\u002Fdevice\u002Fengine, snapshot\u002Fsource refs, observation times\u002Fwindows, stable page\u002Fcontent bindings, and any user-provided or tool metrics.\n- **Writes**: a user-facing monitoring deliverable and reusable summary.\n- **Promotes**: significant changes, confirmed anomalies, follow-up actions, and pending decisions to `memory\u002Fopen-loops.md`.\n- **Done when**: every tracked keyword shows a current, context-matched position vs baseline with a labeled delta, or Unknown\u002FNEEDS_REFRESH with its reason; each observation cites its source ref, observed time, window, locale\u002Flanguage\u002Fdevice\u002Fengine, evidence label, and ranking page ref; conflicts remain visible; and biggest movers and likely causes are named.\n- **Primary next skill**: [performance-monitor](..\u002Fperformance-monitor\u002FSKILL.md) when recurring monitoring should become automated.\n\n### Handoff Summary\n\n> Emit the standard shape from [skill-contract.md §Handoff Summary Format](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md).\n\n## Data Sources\n\nAll integrations optional (see [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md)). With tools, pull rankings from ~~SEO tool, impressions from ~~search console, traffic from ~~analytics, and AI citations from ~~AI monitor. Without tools, ask for positions, volumes, competitor data, and SERP feature status.\n\n**Zero-dependency measurement loop** (no paid tool needed): never narrate a ranking movement you did not measure — record each check as a snapshot and let the ledger compute the delta. `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fconnectors\u002Fledger.py\" record \u003Cdomain> --source rank --data '{\"\u003Ckeyword>\": \u003Cposition>, ...}'`, then `ledger.py diff \u003Cdomain> --source rank` for the change since the last check and `ledger.py trend \u003Cdomain> --source rank --field \"\u003Ckeyword>\"` for the series. Record real Search Console positions when connected, or the positions the user provides at Tier 1. A ranking delta is a **week-scale, confounded outcome** — attribute it against a control (a holdout keyword\u002Fcompetitor), not against zero; see [references\u002Fmeasurement-protocol.md](..\u002F..\u002F..\u002Freferences\u002Fmeasurement-protocol.md). See [scripts\u002Fconnectors\u002FREADME.md](..\u002F..\u002F..\u002Fscripts\u002Fconnectors\u002FREADME.md).\n\n## Decision Gates\n\n**Stop and ask the user when:**\n- No target keywords are provided and none can be inferred from `CLAUDE.md` or prior monitoring records — offer: (1) supply a keyword list, (2) track the domain's top known terms, (3) cancel.\n\n**Continue silently (never stop for):**\n- No prior baseline exists — record the current run as the baseline, label all positions as the first snapshot, and proceed (do not invent a \"previous\" position).\n- Missing optional tool data (SERP features, AI citations) — mark N\u002FA and proceed.\n\n## Instructions\n\nWhen a user requests rank tracking or analysis:\n\n1. **Set Up Keyword Tracking** — configure domain, market\u002Flocale, device, language, engine, update frequency, priorities, competitor watchlist, and stable page refs. Apply the [SEO\u002FGEO Evidence and Cycle Control Profile](..\u002Fperformance-monitor\u002Freferences\u002Fevidence-and-cycle-control.md).\n2. **Record Current Rankings** — output a position table where every row cites its source (tool export \u002F user-provided \u002F estimated), with position ranges, ranking URLs, feature ownership, and movement vs baseline.\n3. **Analyze Ranking Changes** — highlight biggest wins, declines, stable terms, new rankings, lost rankings, likely causes, and recovery ideas; each delta labeled against its baseline.\n4. **Track SERP Features** — compare ownership of snippets, PAA, image\u002Fvideo packs, local packs, and related feature shifts.\n5. **Track GEO \u002F AI Visibility** — monitor AI Overview presence, citation rate, citation position, and trend; mark each value Measured (from an ~~AI monitor) or N\u002FA if unobserved.\n6. **Compare Against Competitors** — report share of voice, head-to-head comparisons, and threat levels.\n7. **Generate Ranking Report** — output overall trend, key wins, concerns, opportunities, SERP feature changes, GEO visibility, and recommendations, with each metric carrying its source tag.\n\nLabel every metric **Measured**, **User-provided**, **Calculated**, **Estimated**, **Proxy**, or **Unknown**; never present an estimate or proxy as measured. An applicable missing metric is Unknown with its reason. A stale or locale\u002Flanguage\u002Fdevice\u002Fengine-mismatched position is `NEEDS_REFRESH`, not a current ranking; N\u002FA is only for a genuinely non-applicable field.\n\n> **Reference**: See [Ranking Analysis Templates](references\u002Franking-analysis-templates.md) for the complete output templates for all seven steps.\n\n## Example\n\nA ranking report names the biggest winners, biggest drops, and next actions, with each position carrying its source tag and labeled delta against baseline.\n\n## Rank Change Quick Reference\n\n### Response Protocol\n\n| Change | Timeframe | Action |\n|--------|-----------|--------|\n| Drop 1-3 positions | Wait 1-2 weeks | Monitor — may be normal fluctuation |\n| Drop 3-5 positions | Investigate within 1 week | Check technical issues and competitor changes |\n| Drop 5-10 positions | Investigate immediately | Run a full diagnostic: technical, content, links |\n| Drop off page 1 | Emergency response | Comprehensive audit + recovery plan |\n| Position gained | Document and learn | Identify what worked and replicate |\n\n> **Reference**: See [Tracking Setup Guide](references\u002Ftracking-setup-guide.md) for tracking setup, root-cause taxonomy, CTR benchmarks, SERP feature impact, and algorithm-update assessment.\n\n### Save Results\n\nAsk \"Save these results?\" If yes, write to `memory\u002Fmonitoring\u002F` — see [Skill Contract](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md) §Save Results Template.\n\n## Reference Materials\n\n- [SEO\u002FGEO Evidence and Cycle Control Profile](..\u002Fperformance-monitor\u002Freferences\u002Fevidence-and-cycle-control.md) — exact search observations, freshness, page bindings, and cycle rules\n- [Tracking Setup Guide](references\u002Ftracking-setup-guide.md) — Setup rules, feature tracking, and interpretation guidance\n\n## Next Best Skill\n\nInitial setup (no baseline) → [performance-monitor](..\u002Fperformance-monitor\u002FSKILL.md). Subsequent runs (baseline exists) → Terminal. Visited-set rule applies per [skill-contract.md](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md).\n","# Rank Tracker\n\nTracks keyword positions, SERP feature ownership, and AI visibility over time.\n\n## Quick Start\n\n```\nSet up rank tracking for [domain] targeting these keywords: [keyword list]\n```\n\n```\nAnalyze ranking changes for [domain] over the past [time period]\n```\n\n## Skill Contract\n\n**Expected output**: a ranking report or delta summary plus the standard handoff summary for `memory\u002Fmonitoring\u002F`.\n\n- **Reads**: current rankings, prior baselines, target keyword list, locale\u002Flanguage\u002Fdevice\u002Fengine, snapshot\u002Fsource refs, observation times\u002Fwindows, stable page\u002Fcontent bindings, and any user-provided or tool metrics.\n- **Writes**: a user-facing monitoring deliverable and reusable summary.\n- **Promotes**: significant changes, confirmed anomalies, follow-up actions, and pending decisions to `memory\u002Fopen-loops.md`.\n- **Done when**: every tracked keyword shows a current, context-matched position vs baseline with a labeled delta, or Unknown\u002FNEEDS_REFRESH with its reason; each observation cites its source ref, observed time, window, locale\u002Flanguage\u002Fdevice\u002Fengine, evidence label, and ranking page ref; conflicts remain visible; and biggest movers and likely causes are named.\n- **Primary next skill**: [performance-monitor](..\u002Fperformance-monitor\u002FSKILL.md) when recurring monitoring should become automated.\n\n### Handoff Summary\n\n> Emit the standard shape from [skill-contract.md §Handoff Summary Format](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md).\n\n## Data Sources\n\nAll integrations optional (see [CONNECTORS.md](..\u002F..\u002F..\u002FCONNECTORS.md)). With tools, pull rankings from ~~SEO tool, impressions from ~~search console, traffic from ~~analytics, and AI citations from ~~AI monitor. Without tools, ask for positions, volumes, competitor data, and SERP feature status.\n\n**Zero-dependency measurement loop** (no paid tool needed): never narrate a ranking movement you did not measure — record each check as a snapshot and let the ledger compute the delta. `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fconnectors\u002Fledger.py\" record \u003Cdomain> --source rank --data '{\"\u003Ckeyword>\": \u003Cposition>, ...}'`, then `ledger.py diff \u003Cdomain> --source rank` for the change since the last check and `ledger.py trend \u003Cdomain> --source rank --field \"\u003Ckeyword>\"` for the series. Record real Search Console positions when connected, or the positions the user provides at Tier 1. A ranking delta is a **week-scale, confounded outcome** — attribute it against a control (a holdout keyword\u002Fcompetitor), not against zero; see [references\u002Fmeasurement-protocol.md](..\u002F..\u002F..\u002Freferences\u002Fmeasurement-protocol.md). See [scripts\u002Fconnectors\u002FREADME.md](..\u002F..\u002F..\u002Fscripts\u002Fconnectors\u002FREADME.md).\n\n## Decision Gates\n\n**Stop and ask the user when:**\n- No target keywords are provided and none can be inferred from `CLAUDE.md` or prior monitoring records — offer: (1) supply a keyword list, (2) track the domain's top known terms, (3) cancel.\n\n**Continue silently (never stop for):**\n- No prior baseline exists — record the current run as the baseline, label all positions as the first snapshot, and proceed (do not invent a \"previous\" position).\n- Missing optional tool data (SERP features, AI citations) — mark N\u002FA and proceed.\n\n## Instructions\n\nWhen a user requests rank tracking or analysis:\n\n1. **Set Up Keyword Tracking** — configure domain, market\u002Flocale, device, language, engine, update frequency, priorities, competitor watchlist, and stable page refs. Apply the [SEO\u002FGEO Evidence and Cycle Control Profile](..\u002Fperformance-monitor\u002Freferences\u002Fevidence-and-cycle-control.md).\n2. **Record Current Rankings** — output a position table where every row cites its source (tool export \u002F user-provided \u002F estimated), with position ranges, ranking URLs, feature ownership, and movement vs baseline.\n3. **Analyze Ranking Changes** — highlight biggest wins, declines, stable terms, new rankings, lost rankings, likely causes, and recovery ideas; each delta labeled against its baseline.\n4. **Track SERP Features** — compare ownership of snippets, PAA, image\u002Fvideo packs, local packs, and related feature shifts.\n5. **Track GEO \u002F AI Visibility** — monitor AI Overview presence, citation rate, citation position, and trend; mark each value Measured (from an ~~AI monitor) or N\u002FA if unobserved.\n6. **Compare Against Competitors** — report share of voice, head-to-head comparisons, and threat levels.\n7. **Generate Ranking Report** — output overall trend, key wins, concerns, opportunities, SERP feature changes, GEO visibility, and recommendations, with each metric carrying its source tag.\n\nLabel every metric **Measured**, **User-provided**, **Calculated**, **Estimated**, **Proxy**, or **Unknown**; never present an estimate or proxy as measured. An applicable missing metric is Unknown with its reason. A stale or locale\u002Flanguage\u002Fdevice\u002Fengine-mismatched position is `NEEDS_REFRESH`, not a current ranking; N\u002FA is only for a genuinely non-applicable field.\n\n> **Reference**: See [Ranking Analysis Templates](references\u002Franking-analysis-templates.md) for the complete output templates for all seven steps.\n\n## Example\n\nA ranking report names the biggest winners, biggest drops, and next actions, with each position carrying its source tag and labeled delta against baseline.\n\n## Rank Change Quick Reference\n\n### Response Protocol\n\n| Change | Timeframe | Action |\n|--------|-----------|--------|\n| Drop 1-3 positions | Wait 1-2 weeks | Monitor — may be normal fluctuation |\n| Drop 3-5 positions | Investigate within 1 week | Check technical issues and competitor changes |\n| Drop 5-10 positions | Investigate immediately | Run a full diagnostic: technical, content, links |\n| Drop off page 1 | Emergency response | Comprehensive audit + recovery plan |\n| Position gained | Document and learn | Identify what worked and replicate |\n\n> **Reference**: See [Tracking Setup Guide](references\u002Ftracking-setup-guide.md) for tracking setup, root-cause taxonomy, CTR benchmarks, SERP feature impact, and algorithm-update assessment.\n\n### Save Results\n\nAsk \"Save these results?\" If yes, write to `memory\u002Fmonitoring\u002F` — see [Skill Contract](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md) §Save Results Template.\n\n## Reference Materials\n\n- [SEO\u002FGEO Evidence and Cycle Control Profile](..\u002Fperformance-monitor\u002Freferences\u002Fevidence-and-cycle-control.md) — exact search observations, freshness, page bindings, and cycle rules\n- [Tracking Setup Guide](references\u002Ftracking-setup-guide.md) — Setup rules, feature tracking, and interpretation guidance\n\n## Next Best Skill\n\nInitial setup (no baseline) → [performance-monitor](..\u002Fperformance-monitor\u002FSKILL.md). Subsequent runs (baseline exists) → Terminal. Visited-set rule applies per [skill-contract.md](..\u002F..\u002F..\u002Freferences\u002Fskill-contract.md).\n",{"name":5,"slug":5,"license":15,"summary":24,"version":25,"homepage":26,"metadata":27,"description":7,"displayName":37,"when_to_use":38,"allowed-tools":39,"argument-hint":40,"compatibility":41},"排名追踪\u002FSERP监控","20.1.0","https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills",{"phase":28,"author":29,"hermes":30,"version":25,"openclaw":34,"discipline":33,"geo-relevance":36},"evaluate","aaron-he-zhu",{"tags":31,"category":33},[32,33,28],"marketing","seo-geo",{"emoji":35,"homepage":26},"🔍","medium","Rank Tracker · 排名追踪","Use when tracking keyword rankings, monitoring position changes, comparing ranking snapshots, or detecting ranking drops.","WebFetch","\u003Cdomain> [keyword list]","Claude Code and compatible agent-skill hosts","main","ad108f7eb3f6764136d02fb875772ebb34f54078","upstreams\u002Fsource-a\u002Fseo-geo\u002Fevaluate\u002Frank-tracker",2,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar","iamwaqargulzar.com","2026-11-03 21:14:34",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill rank-tracker",{"tool":56,"command":57},"bunx","bunx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill rank-tracker",{"tool":59,"command":60},"pnpm","pnpm dlx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill rank-tracker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Fseo-geo\u002Fevaluate\u002Frank-tracker\u002FSKILL.md",true,[64,70],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Franking-analysis-templates.md","REFERENCE","参考文档",4326,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Fseo-geo\u002Fevaluate\u002Frank-tracker\u002Freferences\u002Franking-analysis-templates.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Ftracking-setup-guide.md",5192,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Fseo-geo\u002Fevaluate\u002Frank-tracker\u002Freferences\u002Ftracking-setup-guide.md",[75,82,89,96,103,110],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AG5VYEX7J2R2AAD54A7YT7","video","When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'record a product demo,' 'feature demo video,' 'in-app demo,' 'video pipeline,' 'copy this edit,' 'match this video style,' 'reverse-engineer this video,' 'edit like this reference,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AG5FMXWA33FQDNS9PS1TE6","social","When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter\u002FX, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' 'create a reel,' 'social listening,' 'brand mentions,' 'competitor monitoring,' 'top posts to comment on,' 'find people asking for,' 'carousel,' 'slide-by-slide,' or 'document post.' Use this for social content, repurposing, scheduling, video scripts, and listening. Posts avoid AI tells like 'it's not X, it's Y' reveals and broetry. For broader content strategy, see content-strategy. For paid ads, see ad-creative. For earned media, see public-relations.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsocial\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7AG559W96W3DGE31KXYY78S","sms","When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional\u002Fauth SMS. Also use when the user mentions \"SMS marketing,\" \"text message campaigns,\" \"SMS sequence,\" \"SMS automation,\" \"abandoned cart text,\" \"post-purchase SMS,\" \"Klaviyo SMS,\" \"Postscript,\" \"Attentive,\" \"Twilio,\" \"A2P 10DLC,\" \"TCPA,\" \"SMS compliance,\" \"short code,\" \"toll-free SMS,\" \"MMS campaign,\" \"should I do SMS,\" \"SMS vs email,\" \"WhatsApp marketing,\" \"WhatsApp Business API,\" \"WhatsApp templates,\" or \"click-to-WhatsApp.\" For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsms\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7AG4WJ9EDSECNTQN0FEAYCQ","site-architecture","When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions \"sitemap,\" \"site map,\" \"visual sitemap,\" \"site structure,\" \"page hierarchy,\" \"information architecture,\" \"IA,\" \"navigation design,\" \"URL structure,\" \"breadcrumbs,\" \"internal linking strategy,\" \"website planning,\" \"what pages do I need,\" \"how should I organize my site,\" \"site navigation,\" \"which website builder should I use,\" \"migrate my website,\" or \"add a blog to my existing site.\" Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsite-architecture\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7AG4MH58GRMSHC0TADAWQ69","signup","When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup form optimization,\" \"free trial signup,\" \"reduce signup dropoff,\" \"account creation flow,\" \"people aren't signing up,\" \"signup abandonment,\" \"trial conversion rate,\" \"nobody completes registration,\" \"too many steps to sign up,\" or \"simplify our signup.\" Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsignup\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7AG4CGGH35KYDFHYSS1BQZ5","seo-audit","When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" \"SEO health check,\" \"my traffic dropped,\" \"lost rankings,\" \"not showing up in Google,\" \"site isn't ranking,\" \"Google update hit me,\" \"page speed,\" \"core web vitals,\" \"crawl errors,\" \"indexing issues,\" \"stuck on page 2,\" \"striking distance keywords,\" \"title tag rewrite,\" \"low CTR,\" \"local SEO,\" \"Google Business Profile,\" or \"map pack.\" Use this even if the user just says something vague like \"my SEO is bad\" or \"help with SEO\" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fseo-audit\u002FSKILL.md",[],[]]