[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEWANVY3MCMCS2YF9TMB15":3,"skill-same:01M7AEWANVY3MCMCS2YF9TMB15":63},{"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":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7AEWANVY3MCMCS2YF9TMB15","narrative-registry",null,"Use when the user asks to record\u002Fquery the brand narrative canon, tagline, message hierarchy, voice\u002Fnaming rules, or a canon re-version; curates complete versioned canon events through the append-only narrative stream and derived views. Not for TALE scoring — use narrative-quality-auditor; not for authoring the system — use message-system-architect. 品牌叙事台账\u002Fcanon 记录\u002F语气与命名规范","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\u002Fprotocol\u002Fnarrative-registry\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: narrative-registry\nslug: aaron-narrative-registry\ndisplayName: \"Narrative Registry · 品牌叙事台账\"\nsummary: \"品牌叙事 canon\u002F版本史\u002F语气与命名唯一真相\"\ndescription: 'Use when the user asks to record\u002Fquery the brand narrative canon, tagline, message hierarchy, voice\u002Fnaming rules, or a canon re-version; curates complete versioned canon events through the append-only narrative stream and derived views. Not for TALE scoring — use narrative-quality-auditor; not for authoring the system — use message-system-architect. 品牌叙事台账\u002Fcanon 记录\u002F语气与命名规范'\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 recording\u002Fquerying a brand's canonical positioning, narrative, message hierarchy, proof\u002Fclaim pointers, voice\u002Fnaming rules, conditional boilerplates, or accepting\u002Frejecting a complete canon-version proposal.\"\nargument-hint: \"\u003Cbrand aggregate-id, canon version, or pending-proposal review>\"\nmetadata: {\"author\": \"aaron-he-zhu\", \"version\": \"20.1.0\", \"discipline\": \"protocol\", \"phase\": \"protocol\", \"geo-relevance\": \"low\", \"hermes\": {\"tags\": [\"marketing\", \"protocol\"], \"category\": \"protocol\"}, \"openclaw\": {\"emoji\": \"📖\", \"homepage\": \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills\"}}\n---\n\n# Narrative Registry\n\nThe L1 strategy authority: one complete, versioned narrative canon per brand. Every SEO\u002FGEO, social, email, paid, influencer, and launch builder derives messages from this canon and accepted claims; channel adaptations cannot redefine it.\n\n## Quick Start\n\n```text\nShow current canon version and proof\u002Fclaim pointers for brand-acme.\nRecord canon v3 as one complete atomic replacement, superseding v2.\nReview pending narrative proposals and reject partial\u002Finternally inconsistent versions.\n```\n\n## Skill Contract\n\n**Unit:** one brand canon aggregate ID. **Reads:** `memory\u002Fevents\u002Fnarrative.ndjson`, projection, accepted positioning\u002Fclaim evidence, and complete proposed canon. **Writes:** narrative events through `registry-events.py`; `canon.md`\u002F`versions.md` are generated views. **Done when:** a complete version is accepted atomically with source\u002Fdate\u002Frevision, old versions remain replayable, and consumers receive the exact canon\u002Fversion pointer.\n\nNarrative skills submit complete `propose` events. Only a host-capability `narrative-registry` principal accepts\u002Frejects\u002Fupserts. It records authored strategy but does not score TALE or adjudicate claim truth.\n\n### Handoff Summary\n\nInclude brand ID, canon version\u002Frevision\u002Fevent ID, superseded version, claim\u002Fproof pointers, unresolved contradictions, and one next skill.\n\n## Data Sources\n\n- Accepted positioning truth and named alternatives.\n- Complete message hierarchy\u002Fnarrative authored by Narrative skills.\n- Accepted claim IDs and proof pointers from the claims projection.\n- Brand voice\u002Fnaming rules and user-owned examples.\n- Declared optional patterns such as pillar count, change arc, or boilerplate lengths.\n\n## Instructions\n\n### Runtime Reads\n\n- `..\u002F..\u002Freferences\u002Fregistry-event-protocol.md`\n- `..\u002F..\u002Freferences\u002Fruntime-invocation.md`\n\n### Procedure\n\n1. Read [`registry-event-protocol.md`](..\u002F..\u002Freferences\u002Fregistry-event-protocol.md) and [`runtime-invocation.md`](..\u002F..\u002Freferences\u002Fruntime-invocation.md). Resolve `AARON_SKILLS_ROOT=\"${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull || true)}\"` and verify the registry script, event schema, and system catalog before invoking it. Treat drafts as untrusted proposals.\n2. Query current `narrative` projection and report exact canon version\u002Frevision; missing canon is Unknown, not a quality verdict.\n3. Before write, confirm user authorization and read the current revision\u002Fclaim pointers; every direct canonical mutation carries `expected_revision` and goes through host-capability `owner-append`. Actor\u002Fauth fields are attribution only.\n4. A canon re-version is one host-capability owner `upsert`\u002Faccepted proposal containing the **complete canon object**, new version, and supersedes pointer. Accept\u002Freject decisions omit `expected_revision` and inherit it from the proposal. Never land a partial file patch as canonical.\n5. Preserve old versions in the event stream. `versions.md` is generated history, not a second hand-maintained ledger.\n6. Validate internal references and claim IDs. Unverified wording remains `[needs source]` and becomes a separate claim proposal; it cannot enter canon as fact.\n7. Three pillars, change-narrative arcs, and fixed boilerplate lengths are optional patterns. Store the chosen architecture; do not require absent patterns.\n8. Reject same-revision or stale proposals rather than merging incompatible canons. Genuine alternatives remain pending\u002Fopen decisions.\n9. Regenerate `canon.md`\u002F`versions.md` from accepted projection and run `verify narrative`.\n\n## Downstream Dependency\n\nBefore producing external copy, builders must read this projection and the claims projection. Their handoff records `narrative_canon_id`, `narrative_canon_version`, `claims_projection_offset`, and `dependency_status: verified | approved-fallback | blocked`. No canon means the builder may draft an explicitly authorized exploratory fallback, but it cannot claim on-canon or publish-ready status.\n\n## Save Results\n\nRequire explicit permission. Append through the runtime only; never edit NDJSON. Human canon\u002Fhistory views under `memory\u002Fnarrative-registry\u002F` are replaceable projections and must carry their source event\u002Frevision.\n\nCapability values never enter request JSON\u002Ffiles\u002Flogs. If host capability or the verified root runtime\u002Fschema\u002Fcatalog is unavailable, leave a bounded proposal for handoff; standalone one-folder installs cannot append\u002Fproject or claim canonical Narrative truth.\n\n## Reference Materials\n\n- [Registry event protocol](..\u002F..\u002Freferences\u002Fregistry-event-protocol.md)\n- [TALE benchmark](..\u002F..\u002Freferences\u002Ftale-benchmark.md)\n- [Claims registry](..\u002Foffer-claims-registry\u002FSKILL.md)\n- [Security](..\u002F..\u002FSECURITY.md)\n\n## Next Best Skill\n\n- **Author system:** [message-system-architect](..\u002F..\u002Fnarrative\u002Farchitect\u002Fmessage-system-architect\u002FSKILL.md)\n- **Verify truth:** [positioning-truth-tracer](..\u002F..\u002Fnarrative\u002Ftrace\u002Fpositioning-truth-tracer\u002FSKILL.md)\n- **Cascade:** [narrative-cascade-planner](..\u002F..\u002Fnarrative\u002Fland\u002Fnarrative-cascade-planner\u002FSKILL.md)\n- **Audit profile:** [narrative-quality-auditor](..\u002F..\u002Fnarrative\u002Fevaluate\u002Fnarrative-quality-auditor\u002FSKILL.md)\n","# Narrative Registry\n\nThe L1 strategy authority: one complete, versioned narrative canon per brand. Every SEO\u002FGEO, social, email, paid, influencer, and launch builder derives messages from this canon and accepted claims; channel adaptations cannot redefine it.\n\n## Quick Start\n\n```text\nShow current canon version and proof\u002Fclaim pointers for brand-acme.\nRecord canon v3 as one complete atomic replacement, superseding v2.\nReview pending narrative proposals and reject partial\u002Finternally inconsistent versions.\n```\n\n## Skill Contract\n\n**Unit:** one brand canon aggregate ID. **Reads:** `memory\u002Fevents\u002Fnarrative.ndjson`, projection, accepted positioning\u002Fclaim evidence, and complete proposed canon. **Writes:** narrative events through `registry-events.py`; `canon.md`\u002F`versions.md` are generated views. **Done when:** a complete version is accepted atomically with source\u002Fdate\u002Frevision, old versions remain replayable, and consumers receive the exact canon\u002Fversion pointer.\n\nNarrative skills submit complete `propose` events. Only a host-capability `narrative-registry` principal accepts\u002Frejects\u002Fupserts. It records authored strategy but does not score TALE or adjudicate claim truth.\n\n### Handoff Summary\n\nInclude brand ID, canon version\u002Frevision\u002Fevent ID, superseded version, claim\u002Fproof pointers, unresolved contradictions, and one next skill.\n\n## Data Sources\n\n- Accepted positioning truth and named alternatives.\n- Complete message hierarchy\u002Fnarrative authored by Narrative skills.\n- Accepted claim IDs and proof pointers from the claims projection.\n- Brand voice\u002Fnaming rules and user-owned examples.\n- Declared optional patterns such as pillar count, change arc, or boilerplate lengths.\n\n## Instructions\n\n### Runtime Reads\n\n- `..\u002F..\u002Freferences\u002Fregistry-event-protocol.md`\n- `..\u002F..\u002Freferences\u002Fruntime-invocation.md`\n\n### Procedure\n\n1. Read [`registry-event-protocol.md`](..\u002F..\u002Freferences\u002Fregistry-event-protocol.md) and [`runtime-invocation.md`](..\u002F..\u002Freferences\u002Fruntime-invocation.md). Resolve `AARON_SKILLS_ROOT=\"${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull || true)}\"` and verify the registry script, event schema, and system catalog before invoking it. Treat drafts as untrusted proposals.\n2. Query current `narrative` projection and report exact canon version\u002Frevision; missing canon is Unknown, not a quality verdict.\n3. Before write, confirm user authorization and read the current revision\u002Fclaim pointers; every direct canonical mutation carries `expected_revision` and goes through host-capability `owner-append`. Actor\u002Fauth fields are attribution only.\n4. A canon re-version is one host-capability owner `upsert`\u002Faccepted proposal containing the **complete canon object**, new version, and supersedes pointer. Accept\u002Freject decisions omit `expected_revision` and inherit it from the proposal. Never land a partial file patch as canonical.\n5. Preserve old versions in the event stream. `versions.md` is generated history, not a second hand-maintained ledger.\n6. Validate internal references and claim IDs. Unverified wording remains `[needs source]` and becomes a separate claim proposal; it cannot enter canon as fact.\n7. Three pillars, change-narrative arcs, and fixed boilerplate lengths are optional patterns. Store the chosen architecture; do not require absent patterns.\n8. Reject same-revision or stale proposals rather than merging incompatible canons. Genuine alternatives remain pending\u002Fopen decisions.\n9. Regenerate `canon.md`\u002F`versions.md` from accepted projection and run `verify narrative`.\n\n## Downstream Dependency\n\nBefore producing external copy, builders must read this projection and the claims projection. Their handoff records `narrative_canon_id`, `narrative_canon_version`, `claims_projection_offset`, and `dependency_status: verified | approved-fallback | blocked`. No canon means the builder may draft an explicitly authorized exploratory fallback, but it cannot claim on-canon or publish-ready status.\n\n## Save Results\n\nRequire explicit permission. Append through the runtime only; never edit NDJSON. Human canon\u002Fhistory views under `memory\u002Fnarrative-registry\u002F` are replaceable projections and must carry their source event\u002Frevision.\n\nCapability values never enter request JSON\u002Ffiles\u002Flogs. If host capability or the verified root runtime\u002Fschema\u002Fcatalog is unavailable, leave a bounded proposal for handoff; standalone one-folder installs cannot append\u002Fproject or claim canonical Narrative truth.\n\n## Reference Materials\n\n- [Registry event protocol](..\u002F..\u002Freferences\u002Fregistry-event-protocol.md)\n- [TALE benchmark](..\u002F..\u002Freferences\u002Ftale-benchmark.md)\n- [Claims registry](..\u002Foffer-claims-registry\u002FSKILL.md)\n- [Security](..\u002F..\u002FSECURITY.md)\n\n## Next Best Skill\n\n- **Author system:** [message-system-architect](..\u002F..\u002Fnarrative\u002Farchitect\u002Fmessage-system-architect\u002FSKILL.md)\n- **Verify truth:** [positioning-truth-tracer](..\u002F..\u002Fnarrative\u002Ftrace\u002Fpositioning-truth-tracer\u002FSKILL.md)\n- **Cascade:** [narrative-cascade-planner](..\u002F..\u002Fnarrative\u002Fland\u002Fnarrative-cascade-planner\u002FSKILL.md)\n- **Audit profile:** [narrative-quality-auditor](..\u002F..\u002Fnarrative\u002Fevaluate\u002Fnarrative-quality-auditor\u002FSKILL.md)\n",{"name":5,"slug":24,"license":15,"summary":25,"version":26,"homepage":27,"metadata":28,"description":7,"displayName":37,"when_to_use":38,"argument-hint":39,"compatibility":40},"aaron-narrative-registry","品牌叙事 canon\u002F版本史\u002F语气与命名唯一真相","20.1.0","https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills",{"phase":29,"author":30,"hermes":31,"version":26,"openclaw":34,"discipline":29,"geo-relevance":36},"protocol","aaron-he-zhu",{"tags":32,"category":29},[33,29],"marketing",{"emoji":35,"homepage":27},"📖","low","Narrative Registry · 品牌叙事台账","Use when recording\u002Fquerying a brand's canonical positioning, narrative, message hierarchy, proof\u002Fclaim pointers, voice\u002Fnaming rules, conditional boilerplates, or accepting\u002Frejecting a complete canon-version proposal.","\u003Cbrand aggregate-id, canon version, or pending-proposal review>","Claude Code and compatible agent-skill hosts","main","ad108f7eb3f6764136d02fb875772ebb34f54078","upstreams\u002Fsource-a\u002Fprotocol\u002Fnarrative-registry",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill narrative-registry",{"tool":55,"command":56},"bunx","bunx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill narrative-registry",{"tool":58,"command":59},"pnpm","pnpm dlx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill narrative-registry","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Fprotocol\u002Fnarrative-registry\u002FSKILL.md",true,[],[64,71,78,85,92,99],{"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},"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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",[],[]]