[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEJ7CEQ4PVGP7EPT99G6X5":3,"skill-same:01M7AEJ7CEQ4PVGP7EPT99G6X5":72},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M7AEJ7CEQ4PVGP7EPT99G6X5","launch-readiness-auditor",null,"Use when the user asks to \"audit our launch plan\", \"are we ready to launch\", or evaluate launch execution\u002Foutcomes; runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons. Not for recording launch state — use launch-registry; not for running launch day — use launch-day-conductor. 发布就绪审计\u002FRAMP分阶段评估\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\u002Flaunch\u002Fmobilize\u002Flaunch-readiness-auditor\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: launch-readiness-auditor\nslug: aaron-launch-readiness-auditor\ndisplayName: \"Launch Readiness Auditor · 发布就绪审计\"\nsummary: \"发布就绪审计\u002FRAMP分阶段评估\u002F发布前放行\"\ndescription: 'Use when the user asks to \"audit our launch plan\", \"are we ready to launch\", or evaluate launch execution\u002Foutcomes; runs one typed RAMP preflight, execution, or outcome profile without mixing time horizons. Not for recording launch state — use launch-registry; not for running launch day — use launch-day-conductor. 发布就绪审计\u002FRAMP分阶段评估\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 for launch-eve readiness, an observed launch-window execution audit, or a post-lag outcome review. Each run uses one lifecycle profile and never averages plans, execution, and outcomes.\"\nargument-hint: \"\u003Claunch slug\u002Fplan\u002Fevidence> [preflight|execution|outcome]\"\nallowed-tools: WebFetch\nclass: auditor\nmetadata: {\"author\": \"aaron-he-zhu\", \"version\": \"20.1.0\", \"discipline\": \"launch\", \"phase\": \"mobilize\", \"geo-relevance\": \"low\", \"hermes\": {\"tags\": [\"marketing\", \"launch\", \"mobilize\"], \"category\": \"launch\"}, \"openclaw\": {\"emoji\": \"🚀\", \"homepage\": \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills\"}}\n---\n\n# Launch Readiness Auditor\n\nAudit one launch at one lifecycle read. Preflight evaluates readiness\u002Fassets plus planned policy and instrumentation red lines; execution evaluates observed launch-window operation; outcome evaluates post-lag proof. There is no cross-time composite.\n\n## When This Must Trigger\n\n- Before a committed launch\u002Fannouncement when go\u002Fno-go evidence is needed.\n- During\u002Fafter the launch window when execution quality must be assessed.\n- After the declared lag when actual outcomes and learnings are reviewed.\n\n## Quick Start\n\n```text\nRun RAMP preflight for launch alpha against the registry stage, canon, claims, rules, and event QA.\nRun the outcome profile at day 30; keep it separate from the preflight result.\n```\n\n## Skill Contract\n\n**Reads:** one launch, one lifecycle read, registry\u002Fcanon\u002Fclaims state, and profile-specific evidence. **Writes:** only a permissioned v3 artifact. **Done when:** the selected profile is complete or its exact Unknowns are reported, with no launch execution or registry mutation.\n\n`launch-registry` owns stage\u002Fdate\u002Fembargo facts. `launch-day-conductor` executes the runbook. This auditor only judges the frozen evidence.\n\n## Data Sources\n\n| Need | Preferred evidence |\n|---|---|\n| Stage\u002Faccess | Projected launch record plus direct access\u002Feligibility check |\n| Narrative\u002Fclaims | Canon version, claims projection, rendered assets |\n| Operations\u002Frules | Launch plan, commitments, dated official platform rules |\n| Instrumentation | Verified events\u002FUTMs and destination truth checks |\n| Execution | Timestamped action\u002Fincident\u002Fresponse evidence |\n| Outcomes | Own analytics\u002FCRM\u002Fstore truth after declared lag |\n\n## Instructions\n\n### Runtime Reads\n\n- `..\u002F..\u002F..\u002Freferences\u002Fauditor-runbook.md`\n- `..\u002F..\u002F..\u002Freferences\u002Fscoring-semantics.md`\n- `..\u002F..\u002F..\u002Freferences\u002Framp-benchmark.md`\n- `..\u002F..\u002F..\u002Freferences\u002Fruntime-invocation.md`\n- `references\u002Fauditor-runtime.md`\n\n### Runtime and Setup\n\nRead `..\u002F..\u002F..\u002Freferences\u002Fauditor-runbook.md`, `scoring-semantics.md`, `ramp-benchmark.md`, and the RAMP catalog entry. Standalone installs use bundled immutable `references\u002Fauditor-runtime.md`; never fetch mutable `main`. Before deterministic calls, follow [`runtime-invocation.md`](..\u002F..\u002F..\u002Freferences\u002Fruntime-invocation.md), resolve `AARON_SKILLS_ROOT=\"${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull || true)}\"`, and require the scorer, validator, and typed catalogs. If unavailable, return `score_state: NOT_SCORED` \u002F `score_confidence: not_scored` with no gate verdict or persistent artifact.\n\nDeclare profile\u002Flifecycle read (`preflight|execution|outcome`), target launch, launch type, market, access model, observation date, and evidence window.\n\n### Profile Procedure\n\n- **Preflight:** score R1–R10, A1–A10, planned M1, and P1. A public pricing page is required only when the declared access model promises public paid availability.\n- **Execution:** score observed M1–M10; do not substitute planned runbook quality for actual execution.\n- **Outcome:** score P2–P10 after the declared lag; do not backfill forecast targets as actuals.\n\nEvery observed state needs source\u002Fdate\u002Ftype\u002Fconfidence. Missing applicable evidence is Unknown; catalog-authorized conditional items may be N\u002FA with reason. Run `python3 \"$AARON_SKILLS_ROOT\u002Fscripts\u002Frubric-score.py\" score \u003Crun.json>` on the selected typed profile.\n\nVerify profile-relevant vetoes: `RAMP-R1` stage\u002Faccess contradiction, `RAMP-A1` material claim\u002Fdisclosure failure, `RAMP-M1` planned or observed manipulation\u002Fembargo\u002Fplatform violation, and `RAMP-P1` demonstrably broken instrumentation on participating surfaces.\n\n## §2 RAMP Worked Examples\n\n- Complete preflight, raw 80, no veto\u002Ffail: `DONE\u002FSHIP`, final 80.\n- Complete preflight, raw 76, one verified A1 failure: `DONE_WITH_CONCERNS\u002FFIX`, final 59.\n- Complete preflight, verified R1 and M1 failures: `DONE\u002FBLOCK`, no final score.\n- Outcome read before conversion lag or without own-data actuals: `NEEDS_INPUT\u002FUNDECIDED`, no score.\n\n## §3 RAMP Guardrails\n\n- Stage truth follows promised access\u002Feligibility; a pricing page is not universal evidence of GA.\n- A genuine feedback request is not vote solicitation.\n- Privacy-limited modeled measurement may be Partial; broken required instrumentation is P1 Fail.\n- Launch stacking\u002Fcapacity is an M10 finding, not an automatic veto.\n- Never average preflight, execution, and outcome profiles or compare their scores as the same construct.\n\n## §5 RAMP Translation\n\nState lifecycle read with every result. On trace request, qualify `RAMP-R1\u002FA1\u002FM1\u002FP1`, especially against colliding ROAS IDs.\n\n## Report and Verdict\n\nBegin with the auditor-runbook's exact typed conversation header. Never replace `status`, `verdict`, or `score_state` with prose; list each explicitly missing qualified item as ``ID: `unknown``` before findings. Use the stable catalog ID verbatim (for example, `RAMP-R1`); never substitute an evidence-subcheck label or synthesize a suffixed ID such as `RAMP-R1d`.\n\nLead with lifecycle-specific verdict, target\u002Fcontext\u002Fdate, score or coverage\u002Finterval, confidence, profile detail, linked prior reads, critical evidence, Unknowns, and fix\u002Frerun owner. A preflight SHIP authorizes no external launch action by itself; explicit execution approval remains required.\n\n## Validation Checkpoints\n\n- One launch and one lifecycle profile are declared.\n- Plan, execution, and outcome evidence were not mixed.\n- Expected items only are scored; Unknown\u002FN\u002FA semantics are correct.\n- Stage\u002Faccess, policy, claims, and instrumentation vetoes are positively verified.\n- No launch, submission, registry, or campaign side effect occurred.\n\n## Persistence\n\nPersist only after explicit authorization to `memory\u002Faudits\u002Flaunch\u002FYYYY-MM-DD-\u003Ctopic>.md`. Preserve the scorer's orthogonal `status` and `verdict`; validate the complete v3 draft with `validate-audit-artifact.py` against the intended relative path, persist only through one full-content Write, and revalidate the target per the auditor runbook. Edit\u002Fshell\u002FMCP mutations of the reserved sink are unsupported. Create separate files for separate lifecycle reads and link them by launch ID rather than overwriting.\n\n## Reference Materials\n\n- [RAMP benchmark](..\u002F..\u002F..\u002Freferences\u002Framp-benchmark.md)\n- [Auditor runbook](..\u002F..\u002F..\u002Freferences\u002Fauditor-runbook.md)\n- [Scoring semantics](..\u002F..\u002F..\u002Freferences\u002Fscoring-semantics.md)\n- [Measurement protocol](..\u002F..\u002F..\u002Freferences\u002Fmeasurement-protocol.md)\n\n## Next Best Skill\n\n- **Stage\u002Fcommitment facts:** [launch-registry](..\u002F..\u002F..\u002Fprotocol\u002Flaunch-registry\u002FSKILL.md)\n- **Asset\u002Ftechnical fixes:** [launch-asset-packager](..\u002F..\u002Fassemble\u002Flaunch-asset-packager\u002FSKILL.md)\n- **Execute approved plan:** [launch-day-conductor](..\u002Flaunch-day-conductor\u002FSKILL.md)\n- **Outcome monitoring:** [launch-monitor](..\u002F..\u002Fprove\u002Flaunch-monitor\u002FSKILL.md)\n","# Launch Readiness Auditor\n\nAudit one launch at one lifecycle read. Preflight evaluates readiness\u002Fassets plus planned policy and instrumentation red lines; execution evaluates observed launch-window operation; outcome evaluates post-lag proof. There is no cross-time composite.\n\n## When This Must Trigger\n\n- Before a committed launch\u002Fannouncement when go\u002Fno-go evidence is needed.\n- During\u002Fafter the launch window when execution quality must be assessed.\n- After the declared lag when actual outcomes and learnings are reviewed.\n\n## Quick Start\n\n```text\nRun RAMP preflight for launch alpha against the registry stage, canon, claims, rules, and event QA.\nRun the outcome profile at day 30; keep it separate from the preflight result.\n```\n\n## Skill Contract\n\n**Reads:** one launch, one lifecycle read, registry\u002Fcanon\u002Fclaims state, and profile-specific evidence. **Writes:** only a permissioned v3 artifact. **Done when:** the selected profile is complete or its exact Unknowns are reported, with no launch execution or registry mutation.\n\n`launch-registry` owns stage\u002Fdate\u002Fembargo facts. `launch-day-conductor` executes the runbook. This auditor only judges the frozen evidence.\n\n## Data Sources\n\n| Need | Preferred evidence |\n|---|---|\n| Stage\u002Faccess | Projected launch record plus direct access\u002Feligibility check |\n| Narrative\u002Fclaims | Canon version, claims projection, rendered assets |\n| Operations\u002Frules | Launch plan, commitments, dated official platform rules |\n| Instrumentation | Verified events\u002FUTMs and destination truth checks |\n| Execution | Timestamped action\u002Fincident\u002Fresponse evidence |\n| Outcomes | Own analytics\u002FCRM\u002Fstore truth after declared lag |\n\n## Instructions\n\n### Runtime Reads\n\n- `..\u002F..\u002F..\u002Freferences\u002Fauditor-runbook.md`\n- `..\u002F..\u002F..\u002Freferences\u002Fscoring-semantics.md`\n- `..\u002F..\u002F..\u002Freferences\u002Framp-benchmark.md`\n- `..\u002F..\u002F..\u002Freferences\u002Fruntime-invocation.md`\n- `references\u002Fauditor-runtime.md`\n\n### Runtime and Setup\n\nRead `..\u002F..\u002F..\u002Freferences\u002Fauditor-runbook.md`, `scoring-semantics.md`, `ramp-benchmark.md`, and the RAMP catalog entry. Standalone installs use bundled immutable `references\u002Fauditor-runtime.md`; never fetch mutable `main`. Before deterministic calls, follow [`runtime-invocation.md`](..\u002F..\u002F..\u002Freferences\u002Fruntime-invocation.md), resolve `AARON_SKILLS_ROOT=\"${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull || true)}\"`, and require the scorer, validator, and typed catalogs. If unavailable, return `score_state: NOT_SCORED` \u002F `score_confidence: not_scored` with no gate verdict or persistent artifact.\n\nDeclare profile\u002Flifecycle read (`preflight|execution|outcome`), target launch, launch type, market, access model, observation date, and evidence window.\n\n### Profile Procedure\n\n- **Preflight:** score R1–R10, A1–A10, planned M1, and P1. A public pricing page is required only when the declared access model promises public paid availability.\n- **Execution:** score observed M1–M10; do not substitute planned runbook quality for actual execution.\n- **Outcome:** score P2–P10 after the declared lag; do not backfill forecast targets as actuals.\n\nEvery observed state needs source\u002Fdate\u002Ftype\u002Fconfidence. Missing applicable evidence is Unknown; catalog-authorized conditional items may be N\u002FA with reason. Run `python3 \"$AARON_SKILLS_ROOT\u002Fscripts\u002Frubric-score.py\" score \u003Crun.json>` on the selected typed profile.\n\nVerify profile-relevant vetoes: `RAMP-R1` stage\u002Faccess contradiction, `RAMP-A1` material claim\u002Fdisclosure failure, `RAMP-M1` planned or observed manipulation\u002Fembargo\u002Fplatform violation, and `RAMP-P1` demonstrably broken instrumentation on participating surfaces.\n\n## §2 RAMP Worked Examples\n\n- Complete preflight, raw 80, no veto\u002Ffail: `DONE\u002FSHIP`, final 80.\n- Complete preflight, raw 76, one verified A1 failure: `DONE_WITH_CONCERNS\u002FFIX`, final 59.\n- Complete preflight, verified R1 and M1 failures: `DONE\u002FBLOCK`, no final score.\n- Outcome read before conversion lag or without own-data actuals: `NEEDS_INPUT\u002FUNDECIDED`, no score.\n\n## §3 RAMP Guardrails\n\n- Stage truth follows promised access\u002Feligibility; a pricing page is not universal evidence of GA.\n- A genuine feedback request is not vote solicitation.\n- Privacy-limited modeled measurement may be Partial; broken required instrumentation is P1 Fail.\n- Launch stacking\u002Fcapacity is an M10 finding, not an automatic veto.\n- Never average preflight, execution, and outcome profiles or compare their scores as the same construct.\n\n## §5 RAMP Translation\n\nState lifecycle read with every result. On trace request, qualify `RAMP-R1\u002FA1\u002FM1\u002FP1`, especially against colliding ROAS IDs.\n\n## Report and Verdict\n\nBegin with the auditor-runbook's exact typed conversation header. Never replace `status`, `verdict`, or `score_state` with prose; list each explicitly missing qualified item as ``ID: `unknown``` before findings. Use the stable catalog ID verbatim (for example, `RAMP-R1`); never substitute an evidence-subcheck label or synthesize a suffixed ID such as `RAMP-R1d`.\n\nLead with lifecycle-specific verdict, target\u002Fcontext\u002Fdate, score or coverage\u002Finterval, confidence, profile detail, linked prior reads, critical evidence, Unknowns, and fix\u002Frerun owner. A preflight SHIP authorizes no external launch action by itself; explicit execution approval remains required.\n\n## Validation Checkpoints\n\n- One launch and one lifecycle profile are declared.\n- Plan, execution, and outcome evidence were not mixed.\n- Expected items only are scored; Unknown\u002FN\u002FA semantics are correct.\n- Stage\u002Faccess, policy, claims, and instrumentation vetoes are positively verified.\n- No launch, submission, registry, or campaign side effect occurred.\n\n## Persistence\n\nPersist only after explicit authorization to `memory\u002Faudits\u002Flaunch\u002FYYYY-MM-DD-\u003Ctopic>.md`. Preserve the scorer's orthogonal `status` and `verdict`; validate the complete v3 draft with `validate-audit-artifact.py` against the intended relative path, persist only through one full-content Write, and revalidate the target per the auditor runbook. Edit\u002Fshell\u002FMCP mutations of the reserved sink are unsupported. Create separate files for separate lifecycle reads and link them by launch ID rather than overwriting.\n\n## Reference Materials\n\n- [RAMP benchmark](..\u002F..\u002F..\u002Freferences\u002Framp-benchmark.md)\n- [Auditor runbook](..\u002F..\u002F..\u002Freferences\u002Fauditor-runbook.md)\n- [Scoring semantics](..\u002F..\u002F..\u002Freferences\u002Fscoring-semantics.md)\n- [Measurement protocol](..\u002F..\u002F..\u002Freferences\u002Fmeasurement-protocol.md)\n\n## Next Best Skill\n\n- **Stage\u002Fcommitment facts:** [launch-registry](..\u002F..\u002F..\u002Fprotocol\u002Flaunch-registry\u002FSKILL.md)\n- **Asset\u002Ftechnical fixes:** [launch-asset-packager](..\u002F..\u002Fassemble\u002Flaunch-asset-packager\u002FSKILL.md)\n- **Execute approved plan:** [launch-day-conductor](..\u002Flaunch-day-conductor\u002FSKILL.md)\n- **Outcome monitoring:** [launch-monitor](..\u002F..\u002Fprove\u002Flaunch-monitor\u002FSKILL.md)\n",{"name":5,"slug":24,"class":25,"license":15,"summary":26,"version":27,"homepage":28,"metadata":29,"description":7,"displayName":39,"when_to_use":40,"allowed-tools":41,"argument-hint":42,"compatibility":43},"aaron-launch-readiness-auditor","auditor","发布就绪审计\u002FRAMP分阶段评估\u002F发布前放行","20.1.0","https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Faaron-marketing-skills",{"phase":30,"author":31,"hermes":32,"version":27,"openclaw":36,"discipline":35,"geo-relevance":38},"mobilize","aaron-he-zhu",{"tags":33,"category":35},[34,35,30],"marketing","launch",{"emoji":37,"homepage":28},"🚀","low","Launch Readiness Auditor · 发布就绪审计","Use for launch-eve readiness, an observed launch-window execution audit, or a post-lag outcome review. Each run uses one lifecycle profile and never averages plans, execution, and outcomes.","WebFetch","\u003Claunch slug\u002Fplan\u002Fevidence> [preflight|execution|outcome]","Claude Code and compatible agent-skill hosts","main","ad108f7eb3f6764136d02fb875772ebb34f54078","upstreams\u002Fsource-a\u002Flaunch\u002Fmobilize\u002Flaunch-readiness-auditor",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill launch-readiness-auditor",{"tool":58,"command":59},"bunx","bunx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill launch-readiness-auditor",{"tool":61,"command":62},"pnpm","pnpm dlx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill launch-readiness-auditor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Flaunch\u002Fmobilize\u002Flaunch-readiness-auditor\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fauditor-runtime.md","REFERENCE","参考文档",16151,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-a\u002Flaunch\u002Fmobilize\u002Flaunch-readiness-auditor\u002Freferences\u002Fauditor-runtime.md",[73,80,87,94,101,108],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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",[],[]]