[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74QX0KJS6P7DF8XCCWY2FHM":3,"skill-same:01M74QX0KJS6P7DF8XCCWY2FHM":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":13,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M74QX0KJS6P7DF8XCCWY2FHM","ship-gate",null,"Pre-production audit that scans a codebase for security, database, deployment, code quality, AI\u002FLLM, dependency, frontend, and observability issues. Intercepts deploy commands and blocks until critical items pass. Stack-agnostic. Use for \"run ship gate\", \"am I ready to ship\", \"pre-launch audit\", \"can I deploy\", \"push to production\", \"go live checklist\", \"preflight check\". Not for CI\u002FCD setup or infra provisioning.","ziyabicilecommerce-hub\u002Fai-cash-machine","ziyabicilecommerce-hub","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F285820068?v=4","01M74H526DGBPF10MA7T706NT1","01M74H5273WRZRFEWH3TPDJK4T",0,"MIT","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship-gate\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ship-gate\ndescription: >\n  Pre-production audit that scans a codebase for security, database,\n  deployment, code quality, AI\u002FLLM, dependency, frontend, and observability\n  issues. Intercepts deploy commands and blocks until critical items pass.\n  Stack-agnostic. Use for \"run ship gate\", \"am I ready to ship\",\n  \"pre-launch audit\", \"can I deploy\", \"push to production\", \"go live\n  checklist\", \"preflight check\". Not for CI\u002FCD setup or infra provisioning.\nlicense: MIT\nmetadata:\n  author: Rajaraman Arumugam\n  version: 1.0.0\n---\n\n# Ship Gate\n\nPre-production audit that scans a codebase and reports pass\u002Ffail\u002Fmanual\nacross 8 categories before anything ships.\n\n## Intercept Behavior\n\nWhen the user says \"push to production\", \"deploy\", \"ship it\", \"go live\",\nor similar deploy-intent phrases, do NOT proceed with deployment. Instead:\n\n1. Ask: \"Have you run the ship gate? Want me to scan now?\"\n2. If yes, run the full audit below.\n3. If the user says they already ran it, ask when. If more than 24 hours\n   ago or if code changed since, recommend re-running.\n\n## How It Works\n\n### Step 1: Detect Stack\n\nRun these checks in order to identify the project stack:\n\n```\nFramework detection:\n  package.json exists        -> Node.js project\n    \"next\" in dependencies   -> Next.js\n    \"react\" in dependencies  -> React (if not Next.js)\n    \"vue\" in dependencies    -> Vue\n    \"svelte\" in dependencies -> Svelte\n    \"astro\" in dependencies  -> Astro\n    \"express\" in dependencies -> Express\n    \"fastify\" in dependencies -> Fastify\n    \"hono\" in dependencies   -> Hono\n  requirements.txt or pyproject.toml -> Python project\n    \"django\" present         -> Django\n    \"flask\" present          -> Flask\n    \"fastapi\" present        -> FastAPI\n  go.mod exists              -> Go project\n  Cargo.toml exists          -> Rust project\n\nDatabase detection:\n  \"@supabase\u002Fsupabase-js\" in package.json -> Supabase\n  supabase\u002F directory exists              -> Supabase\n  \"prisma\" in dependencies                -> Prisma (check schema for DB type)\n  \"mongoose\" in dependencies              -> MongoDB\n  \"pg\" or \"postgres\" in dependencies      -> PostgreSQL\n  firebase.json or .firebaserc exists     -> Firebase\n\nDeploy target detection:\n  vercel.json or .vercel\u002F exists          -> Vercel\n  netlify.toml exists                     -> Netlify\n  Dockerfile exists                       -> Docker\u002FVPS\n  fly.toml exists                         -> Fly.io\n  railway.json exists                     -> Railway\n  .platform\u002Fapplications.yaml            -> Platform.sh\n\nAuth detection:\n  \"@clerk\" in dependencies                -> Clerk\n  \"next-auth\" in dependencies             -> NextAuth\n  \"@supabase\u002Fauth-helpers\" in deps        -> Supabase Auth\n  \"firebase\u002Fauth\" in imports              -> Firebase Auth\n\nAI\u002FLLM detection:\n  \"openai\" in dependencies                -> OpenAI\n  \"@anthropic-ai\u002Fsdk\" in dependencies     -> Claude API\n  \"@google\u002Fgenerative-ai\" in deps         -> Gemini\n```\n\nReport detected stack before proceeding. This determines which checks\nare relevant. Checks tagged with a specific stack in `references\u002Fchecks.md`\nare skipped if that stack is not detected.\n\n### Step 2: Run Automated Checks\n\nRun categories in this order: SEC, DB, CODE, DEP, AI, DEPLOY, FE, OBS.\nSecurity and database first because they produce the most critical findings.\n\nFor each category, run every auto-scannable check from\n`references\u002Fchecks.md` using the patterns in `references\u002Fpatterns.md`.\n\nReport progress after each category completes:\n```\n[1\u002F8] Security: 3 FAIL, 12 PASS, 3 SKIP\n[2\u002F8] Database: 1 FAIL, 5 PASS, 6 SKIP\n...\n```\n\nReport results as:\n- PASS: check passed\n- FAIL: issue found (with file path and line number)\n- SKIP: not applicable to this stack\n\n### Step 3: Manual Confirmation\n\nFor checks that cannot be automated (backup restore tested, rollback plan\nexists, staging test passed), present them as a checklist and ask the user\nto confirm each one.\n\n### Step 4: Verdict\n\nClassify results into three severities:\n- CRITICAL: must fix before shipping (secrets exposed, no auth on routes,\n  no HTTPS, SQL injection vectors, no RLS on Supabase tables)\n- HIGH: should fix before shipping (no error boundaries, no rate limiting,\n  console.logs in production, no pagination)\n- ADVISORY: recommended but not blocking (no OG tags, no custom 404,\n  no analytics, no SBOM)\n\nFinal output:\n\n```\nSHIP GATE REPORT\n================\nStack: Next.js + Supabase + Vercel\nScan time: 12s\n\nCRITICAL (3 items, must fix)\n  FAIL  [SEC-01] API key found in src\u002Flib\u002Fapi.ts:14\n  FAIL  [DB-07] RLS not enabled on \"profiles\" table\n  FAIL  [SEC-05] No CSRF protection on \u002Fapi\u002Fcheckout\n\nHIGH (5 items, should fix)\n  FAIL  [CODE-01] 12 console.log statements in production code\n  FAIL  [CODE-03] Empty catch block in src\u002Futils\u002Fauth.ts:45\n  FAIL  [DEP-04] 3 critical npm audit vulnerabilities\n  FAIL  [DEPLOY-05] No rollback plan documented\n  MANUAL [DEPLOY-06] Staging test not confirmed\n\nADVISORY (4 items, recommended)\n  FAIL  [FE-01] Missing OG meta tags\n  FAIL  [FE-03] No custom 404 page\n  PASS  [OBS-01] Error monitoring configured\n  SKIP  [AI-01] No AI\u002FLLM usage detected\n\nVERDICT: DO NOT SHIP (3 critical issues)\nFix critical items and re-run.\n```\n\nIf zero critical items remain, verdict is: CLEAR TO SHIP.\nIf only high items remain, verdict is: SHIP WITH CAUTION (acknowledge risks).\n\n## Categories\n\nEight categories, each with a code prefix. Full check details in\n`references\u002Fchecks.md`.\n\n| Prefix | Category | Auto | Manual | Tool |\n|--------|----------|------|--------|------|\n| SEC | Security | 15 | 3 | 0 |\n| DB | Database | 7 | 5 | 0 |\n| DEPLOY | Deployment | 3 | 8 | 0 |\n| CODE | Code Quality | 11 | 0 | 1 |\n| AI | AI\u002FLLM Security | 5 | 3 | 0 |\n| DEP | Dependencies | 5 | 0 | 1 |\n| FE | Frontend Quality | 7 | 3 | 0 |\n| OBS | Observability | 2 | 5 | 0 |\n\n## Scope\n\nThis skill audits. It does not fix. When it finds issues, it reports\nthem with file locations and remediation guidance. The user or another\nskill (systematic-debugging, backend-patterns, shadcn-stack) handles\nthe fix.\n\nThis skill does not:\n- Set up CI\u002FCD pipelines\n- Provision infrastructure\n- Configure monitoring tools\n- Run after deployment (it is pre-deploy only)\n\n## Integration Points\n\n- **karpathy-coder**: run ship-gate after karpathy-check passes — simplicity first, then production readiness\n- **adversarial-reviewer**: deep security review for items ship-gate flags as critical\n- **security-pen-testing**: penetration testing methodology for SEC-category findings\n- **code-reviewer**: general code quality review complements ship-gate's automated checks\n","# Ship Gate\n\nPre-production audit that scans a codebase and reports pass\u002Ffail\u002Fmanual\nacross 8 categories before anything ships.\n\n## Intercept Behavior\n\nWhen the user says \"push to production\", \"deploy\", \"ship it\", \"go live\",\nor similar deploy-intent phrases, do NOT proceed with deployment. Instead:\n\n1. Ask: \"Have you run the ship gate? Want me to scan now?\"\n2. If yes, run the full audit below.\n3. If the user says they already ran it, ask when. If more than 24 hours\n   ago or if code changed since, recommend re-running.\n\n## How It Works\n\n### Step 1: Detect Stack\n\nRun these checks in order to identify the project stack:\n\n```\nFramework detection:\n  package.json exists        -> Node.js project\n    \"next\" in dependencies   -> Next.js\n    \"react\" in dependencies  -> React (if not Next.js)\n    \"vue\" in dependencies    -> Vue\n    \"svelte\" in dependencies -> Svelte\n    \"astro\" in dependencies  -> Astro\n    \"express\" in dependencies -> Express\n    \"fastify\" in dependencies -> Fastify\n    \"hono\" in dependencies   -> Hono\n  requirements.txt or pyproject.toml -> Python project\n    \"django\" present         -> Django\n    \"flask\" present          -> Flask\n    \"fastapi\" present        -> FastAPI\n  go.mod exists              -> Go project\n  Cargo.toml exists          -> Rust project\n\nDatabase detection:\n  \"@supabase\u002Fsupabase-js\" in package.json -> Supabase\n  supabase\u002F directory exists              -> Supabase\n  \"prisma\" in dependencies                -> Prisma (check schema for DB type)\n  \"mongoose\" in dependencies              -> MongoDB\n  \"pg\" or \"postgres\" in dependencies      -> PostgreSQL\n  firebase.json or .firebaserc exists     -> Firebase\n\nDeploy target detection:\n  vercel.json or .vercel\u002F exists          -> Vercel\n  netlify.toml exists                     -> Netlify\n  Dockerfile exists                       -> Docker\u002FVPS\n  fly.toml exists                         -> Fly.io\n  railway.json exists                     -> Railway\n  .platform\u002Fapplications.yaml            -> Platform.sh\n\nAuth detection:\n  \"@clerk\" in dependencies                -> Clerk\n  \"next-auth\" in dependencies             -> NextAuth\n  \"@supabase\u002Fauth-helpers\" in deps        -> Supabase Auth\n  \"firebase\u002Fauth\" in imports              -> Firebase Auth\n\nAI\u002FLLM detection:\n  \"openai\" in dependencies                -> OpenAI\n  \"@anthropic-ai\u002Fsdk\" in dependencies     -> Claude API\n  \"@google\u002Fgenerative-ai\" in deps         -> Gemini\n```\n\nReport detected stack before proceeding. This determines which checks\nare relevant. Checks tagged with a specific stack in `references\u002Fchecks.md`\nare skipped if that stack is not detected.\n\n### Step 2: Run Automated Checks\n\nRun categories in this order: SEC, DB, CODE, DEP, AI, DEPLOY, FE, OBS.\nSecurity and database first because they produce the most critical findings.\n\nFor each category, run every auto-scannable check from\n`references\u002Fchecks.md` using the patterns in `references\u002Fpatterns.md`.\n\nReport progress after each category completes:\n```\n[1\u002F8] Security: 3 FAIL, 12 PASS, 3 SKIP\n[2\u002F8] Database: 1 FAIL, 5 PASS, 6 SKIP\n...\n```\n\nReport results as:\n- PASS: check passed\n- FAIL: issue found (with file path and line number)\n- SKIP: not applicable to this stack\n\n### Step 3: Manual Confirmation\n\nFor checks that cannot be automated (backup restore tested, rollback plan\nexists, staging test passed), present them as a checklist and ask the user\nto confirm each one.\n\n### Step 4: Verdict\n\nClassify results into three severities:\n- CRITICAL: must fix before shipping (secrets exposed, no auth on routes,\n  no HTTPS, SQL injection vectors, no RLS on Supabase tables)\n- HIGH: should fix before shipping (no error boundaries, no rate limiting,\n  console.logs in production, no pagination)\n- ADVISORY: recommended but not blocking (no OG tags, no custom 404,\n  no analytics, no SBOM)\n\nFinal output:\n\n```\nSHIP GATE REPORT\n================\nStack: Next.js + Supabase + Vercel\nScan time: 12s\n\nCRITICAL (3 items, must fix)\n  FAIL  [SEC-01] API key found in src\u002Flib\u002Fapi.ts:14\n  FAIL  [DB-07] RLS not enabled on \"profiles\" table\n  FAIL  [SEC-05] No CSRF protection on \u002Fapi\u002Fcheckout\n\nHIGH (5 items, should fix)\n  FAIL  [CODE-01] 12 console.log statements in production code\n  FAIL  [CODE-03] Empty catch block in src\u002Futils\u002Fauth.ts:45\n  FAIL  [DEP-04] 3 critical npm audit vulnerabilities\n  FAIL  [DEPLOY-05] No rollback plan documented\n  MANUAL [DEPLOY-06] Staging test not confirmed\n\nADVISORY (4 items, recommended)\n  FAIL  [FE-01] Missing OG meta tags\n  FAIL  [FE-03] No custom 404 page\n  PASS  [OBS-01] Error monitoring configured\n  SKIP  [AI-01] No AI\u002FLLM usage detected\n\nVERDICT: DO NOT SHIP (3 critical issues)\nFix critical items and re-run.\n```\n\nIf zero critical items remain, verdict is: CLEAR TO SHIP.\nIf only high items remain, verdict is: SHIP WITH CAUTION (acknowledge risks).\n\n## Categories\n\nEight categories, each with a code prefix. Full check details in\n`references\u002Fchecks.md`.\n\n| Prefix | Category | Auto | Manual | Tool |\n|--------|----------|------|--------|------|\n| SEC | Security | 15 | 3 | 0 |\n| DB | Database | 7 | 5 | 0 |\n| DEPLOY | Deployment | 3 | 8 | 0 |\n| CODE | Code Quality | 11 | 0 | 1 |\n| AI | AI\u002FLLM Security | 5 | 3 | 0 |\n| DEP | Dependencies | 5 | 0 | 1 |\n| FE | Frontend Quality | 7 | 3 | 0 |\n| OBS | Observability | 2 | 5 | 0 |\n\n## Scope\n\nThis skill audits. It does not fix. When it finds issues, it reports\nthem with file locations and remediation guidance. The user or another\nskill (systematic-debugging, backend-patterns, shadcn-stack) handles\nthe fix.\n\nThis skill does not:\n- Set up CI\u002FCD pipelines\n- Provision infrastructure\n- Configure monitoring tools\n- Run after deployment (it is pre-deploy only)\n\n## Integration Points\n\n- **karpathy-coder**: run ship-gate after karpathy-check passes — simplicity first, then production readiness\n- **adversarial-reviewer**: deep security review for items ship-gate flags as critical\n- **security-pen-testing**: penetration testing methodology for SEC-category findings\n- **code-reviewer**: general code quality review complements ship-gate's automated checks\n",{"name":5,"license":14,"metadata":23,"description":26},{"author":24,"version":25},"Rajaraman Arumugam","1.0.0","Pre-production audit that scans a codebase for security, database, deployment, code quality, AI\u002FLLM, dependency, frontend, and observability issues. Intercepts deploy commands and blocks until critical items pass. Stack-agnostic. Use for \"run ship gate\", \"am I ready to ship\", \"pre-launch audit\", \"can I deploy\", \"push to production\", \"go live checklist\", \"preflight check\". Not for CI\u002FCD setup or infra provisioning.\n","main","ba099ce4bf0c0c705380fc823059cefc2f70facc",".agents\u002Fskills\u002Fship-gate","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine","https:\u002F\u002Fai-cash-machine.vercel.app","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub","2026-11-15 04:53:17",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add ziyabicilecommerce-hub\u002Fai-cash-machine --skill ship-gate",{"tool":40,"command":41},"bunx","bunx skills add ziyabicilecommerce-hub\u002Fai-cash-machine --skill ship-gate",{"tool":43,"command":44},"pnpm","pnpm dlx skills add ziyabicilecommerce-hub\u002Fai-cash-machine --skill ship-gate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship-gate\u002FSKILL.md",true,[48,54,58],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fchecks.md","REFERENCE","参考文档",19088,"https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship-gate\u002Freferences\u002Fchecks.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fpatterns.md",16780,"https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship-gate\u002Freferences\u002Fpatterns.md",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"scripts\u002Fship_gate_scanner.py","SCRIPT","脚本",50439,"https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fship-gate\u002Fscripts\u002Fship_gate_scanner.py",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M74WRQ932DK7689ZN1Z2N6M5","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M74WRJG0WC6345TK70T5RGGK","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M74WRFPSRFD04HM7QH930775","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M74WRC2HG0YAYTNWVWEBQHR9","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M74WR6MJEHCAAFBSYG1N3YSX","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":18},"01M74WR0JXWJQTVJ8JQQ2M8H8M","webinar-marketing","When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebinar-marketing\u002FSKILL.md",[],[]]