[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75QJQY6TDFZRAF9AVN4RTCD":3,"skill-same:01M75QJQY6TDFZRAF9AVN4RTCD":63},{"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":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75QJQY6TDFZRAF9AVN4RTCD","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.","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\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","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fengineering\u002Fskills\u002Fship-gate","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill ship-gate",{"tool":39,"command":40},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill ship-gate",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill ship-gate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fship-gate\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fchecks.md","REFERENCE","参考文档",19088,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fship-gate\u002Freferences\u002Fchecks.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fpatterns.md",16780,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fship-gate\u002Freferences\u002Fpatterns.md",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Fship_gate_scanner.py","SCRIPT","脚本",50439,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering\u002Fskills\u002Fship-gate\u002Fscripts\u002Fship_gate_scanner.py",[64,71,77,84,91,98],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M76XP63XDM4PFPX8MMVYN9JX","preamble-gate","Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent\u002Fsubagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI\u002Ftriggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log\u002Fdiff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpreamble-gate\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75RAQN9Q450RD57J2S6FSR4","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\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75RAG1XMCJMF30HFV5S79AK","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M75RA8RK2JVWB8MYGRB65V75","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\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M75RA08RXYRFSTNC6EEEX4ZD","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\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[]]