[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C1R46XMTG1TYRFT77RVN5N":3,"skill-same:01M6C1R46XMTG1TYRFT77RVN5N":137},{"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":25,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":13,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6C1R46XMTG1TYRFT77RVN5N","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.","mne20114-hash\u002Fgest35bi","mne20114-hash","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224168109?v=4","01M6C0JCR7334CZ39YWTZXX2NG","01M6C0JCWN0NBWMQTW1CPG2Z4G",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fskills\u002Fship-gate\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"ship gate","ship","audit","use","check","quality","stack","provisioning","Production","ci","frontend","observability","database","push","issues","code","run","deployment","code quality","launch","2026-11-10 10:12:30",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":51,"description":54},{"author":52,"version":53},"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","510dd2917e051cc953dc55f56fd6ef442aa01b38","claude-skills\u002Fengineering\u002Fskills\u002Fship-gate","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi","https:\u002F\u002Fgithub.com\u002Fmne20114-hash","2026-10-28 07:50:31",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add mne20114-hash\u002Fgest35bi --skill ship-gate",{"tool":67,"command":68},"bunx","bunx skills add mne20114-hash\u002Fgest35bi --skill ship-gate",{"tool":70,"command":71},"pnpm","pnpm dlx skills add mne20114-hash\u002Fgest35bi --skill ship-gate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fskills\u002Fship-gate\u002FSKILL.md",true,[75,81,85,91,95,101,105,109,113,117,121,125,129,133],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fchecks.md","REFERENCE","参考文档",19088,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fskills\u002Fship-gate\u002Freferences\u002Fchecks.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fpatterns.md",16780,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fskills\u002Fship-gate\u002Freferences\u002Fpatterns.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Fship_gate_scanner.py","SCRIPT","脚本",50439,"https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fengineering\u002Fskills\u002Fship-gate\u002Fscripts\u002Fship_gate_scanner.py",{"path":92,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":93,"sourceHtmlUrl":94},"sections\u002Fcanary.md",19804,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fland-and-deploy\u002Fsections\u002Fcanary.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"sections\u002Fcanary.md.tmpl","OTHER","其他",4242,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fland-and-deploy\u002Fsections\u002Fcanary.md.tmpl",{"path":102,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":103,"sourceHtmlUrl":104},"sections\u002Ffirst-run-validation.md",10400,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fland-and-deploy\u002Fsections\u002Ffirst-run-validation.md",{"path":106,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":107,"sourceHtmlUrl":108},"sections\u002Ffirst-run-validation.md.tmpl",8475,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fland-and-deploy\u002Fsections\u002Ffirst-run-validation.md.tmpl",{"path":110,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":111,"sourceHtmlUrl":112},"sections\u002Fmanifest.json",1502,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fland-and-deploy\u002Fsections\u002Fmanifest.json",{"path":114,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":115,"sourceHtmlUrl":116},"sections\u002Fmerge-and-deploy.md",16404,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fland-and-deploy\u002Fsections\u002Fmerge-and-deploy.md",{"path":118,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":119,"sourceHtmlUrl":120},"sections\u002Fmerge-and-deploy.md.tmpl",16281,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fland-and-deploy\u002Fsections\u002Fmerge-and-deploy.md.tmpl",{"path":122,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":123,"sourceHtmlUrl":124},"sections\u002Fpreamble.md",22396,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fland-and-deploy\u002Fsections\u002Fpreamble.md",{"path":126,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":127,"sourceHtmlUrl":128},"sections\u002Freadiness-gate.md",16526,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fland-and-deploy\u002Fsections\u002Freadiness-gate.md",{"path":130,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":131,"sourceHtmlUrl":132},"sections\u002Freadiness-gate.md.tmpl",16291,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fland-and-deploy\u002Fsections\u002Freadiness-gate.md.tmpl",{"path":134,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":135,"sourceHtmlUrl":136},"SKILL.md.tmpl",21300,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fland-and-deploy\u002FSKILL.md.tmpl",[138,173,195,218,242,262],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":155,"publishedAt":46},"01M6C27N3H0F9RGG2KASPASH04","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[144,147,150],{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":148,"categoryName":149,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":151,"categoryName":152,"taxonomyType":153,"taxonomyTypeDesc":154},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[140,156,157,158,159,160,28,161,162,163,164,165,166,167,168,169,170,171,29,172],"docx","pr","create","intake","search","integrity","checkpoint","learning","js","format","direct","Rules","find","consensus","list","extract","outcomes",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":183,"publishedAt":46},"01M6C27DMGZ4D6ERNHSVA8H8RJ","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[179,182],{"categoryNo":180,"categoryName":181,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":148,"categoryName":149,"taxonomyType":20,"taxonomyTypeDesc":21},[175,184,185,157,186,159,28,187,188,161,189,190,191,192,166,167,193,168,194,29],"research","web","sentiment analysis","sentiment","Citations","analysis","discovery","open","tool","twitter","user",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":206,"publishedAt":46},"01M6C279M59X635VPD6Y9R616J","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[201,202,203],{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":148,"categoryName":149,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":204,"categoryName":205,"taxonomyType":153,"taxonomyTypeDesc":154},"01JBSEEDCAT000000000000037","律师与法务",[197,156,157,207,208,209,159,160,28,189,210,211,212,167,213,214,215,216,29,217],"competitive landscape","routing","product","commits","Word","text","acquisition","decisions","strategy","coverage","advice",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":228,"publishedAt":46},"01M6C275RZWNRB3CCB14QQM7ES","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[224,227],{"categoryNo":225,"categoryName":226,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":148,"categoryName":149,"taxonomyType":20,"taxonomyTypeDesc":21},[220,229,230,184,231,232,233,234,235,236,237,238,191,212,166,30,239,240,241,29],"google","browser automation","automation","generate","browser","fast","SET","doc","Video","Audio","ask","environment","overview",{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":246,"categories":247,"keywords":252,"publishedAt":46},"01M6C2717B0QDJ3Y4PJP77BMW5","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[248,249,250,251],{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":180,"categoryName":181,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":148,"categoryName":149,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":151,"categoryName":152,"taxonomyType":153,"taxonomyTypeDesc":154},[244,156,253,254,255,157,159,160,256,257,258,162,259,211,260,167,169,261,216,29],"MCP","writing","review","lane","keyless","literature review","plan","researcher","question",{"skillNo":263,"name":264,"nameZh":6,"description":265,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":266,"categories":267,"keywords":272,"publishedAt":46},"01M6C26X5G3WDVWQ40Y16ZS19F","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fmne20114-hash\u002Fgest35bi\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[268,269,270,271],{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":180,"categoryName":181,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":148,"categoryName":149,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":151,"categoryName":152,"taxonomyType":153,"taxonomyTypeDesc":154},[264,156,184,157,273,159,160,28,274,275,161,189,211,167,168,169,215,240,29,276],"help","data","Budget","innovation"]