[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75Q34CS1PCTKX9W5JNF5CBP":3,"skill-same:01M75Q34CS1PCTKX9W5JNF5CBP":79},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M75Q34CS1PCTKX9W5JNF5CBP","senior-data-engineer",null,"Data engineering skill for building scalable data pipelines, ETL\u002FELT systems, and data infrastructure. Expertise in Python, SQL, Spark, Airflow, dbt, Kafka, and modern data stack. Includes data modeling, pipeline orchestration, data quality, and DataOps. Use when designing data architectures, building data pipelines, optimizing data workflows, implementing data governance, or troubleshooting data issues.","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-team\u002Fskills\u002Fsenior-data-engineer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"senior-data-engineer\"\ndescription: Data engineering skill for building scalable data pipelines, ETL\u002FELT systems, and data infrastructure. Expertise in Python, SQL, Spark, Airflow, dbt, Kafka, and modern data stack. Includes data modeling, pipeline orchestration, data quality, and DataOps. Use when designing data architectures, building data pipelines, optimizing data workflows, implementing data governance, or troubleshooting data issues.\n---\n\n# Senior Data Engineer\n\nProduction-grade data engineering skill for building scalable, reliable data systems.\n\n## Table of Contents\n\n1. [Trigger Phrases](#trigger-phrases)\n2. [Quick Start](#quick-start)\n3. [Workflows](#workflows)\n4. [Architecture Decision Framework](#architecture-decision-framework)\n5. [Tech Stack](#tech-stack)\n6. [Reference Documentation](#reference-documentation)\n7. [Troubleshooting](#troubleshooting)\n\n---\n\n## Trigger Phrases\n\nActivate this skill when you see:\n\n**Pipeline Design:**\n- \"Design a data pipeline for...\"\n- \"Build an ETL\u002FELT process...\"\n- \"How should I ingest data from...\"\n- \"Set up data extraction from...\"\n\n**Architecture:**\n- \"Should I use batch or streaming?\"\n- \"Lambda vs Kappa architecture\"\n- \"How to handle late-arriving data\"\n- \"Design a data lakehouse\"\n\n**Data Modeling:**\n- \"Create a dimensional model...\"\n- \"Star schema vs snowflake\"\n- \"Implement slowly changing dimensions\"\n- \"Design a data vault\"\n\n**Data Quality:**\n- \"Add data validation to...\"\n- \"Set up data quality checks\"\n- \"Monitor data freshness\"\n- \"Implement data contracts\"\n\n**Performance:**\n- \"Optimize this Spark job\"\n- \"Query is running slow\"\n- \"Reduce pipeline execution time\"\n- \"Tune Airflow DAG\"\n\n---\n\n## Quick Start\n\n### Core Tools\n\n```bash\n# Generate pipeline orchestration config\npython scripts\u002Fpipeline_orchestrator.py generate \\\n  --type airflow \\\n  --source postgres \\\n  --destination snowflake \\\n  --schedule \"0 5 * * *\"\n\n# Validate data quality\npython scripts\u002Fdata_quality_validator.py validate \\\n  --input data\u002Fsales.parquet \\\n  --schema schemas\u002Fsales.json \\\n  --checks freshness,completeness,uniqueness\n\n# Optimize ETL performance\npython scripts\u002Fetl_performance_optimizer.py analyze \\\n  --query queries\u002Fdaily_aggregation.sql \\\n  --engine spark \\\n  --recommend\n```\n\n---\n\n## Workflows\n→ See references\u002Fworkflows.md for details\n\n## Architecture Decision Framework\n\nUse this framework to choose the right approach for your data pipeline.\n\n### Batch vs Streaming\n\n| Criteria | Batch | Streaming |\n|----------|-------|-----------|\n| **Latency requirement** | Hours to days | Seconds to minutes |\n| **Data volume** | Large historical datasets | Continuous event streams |\n| **Processing complexity** | Complex transformations, ML | Simple aggregations, filtering |\n| **Cost sensitivity** | More cost-effective | Higher infrastructure cost |\n| **Error handling** | Easier to reprocess | Requires careful design |\n\n**Decision Tree:**\n```\nIs real-time insight required?\n├── Yes → Use streaming\n│   └── Is exactly-once semantics needed?\n│       ├── Yes → Kafka + Flink\u002FSpark Structured Streaming\n│       └── No → Kafka + consumer groups\n└── No → Use batch\n    └── Is data volume > 1TB daily?\n        ├── Yes → Spark\u002FDatabricks\n        └── No → dbt + warehouse compute\n```\n\n### Lambda vs Kappa Architecture\n\n| Aspect | Lambda | Kappa |\n|--------|--------|-------|\n| **Complexity** | Two codebases (batch + stream) | Single codebase |\n| **Maintenance** | Higher (sync batch\u002Fstream logic) | Lower |\n| **Reprocessing** | Native batch layer | Replay from source |\n| **Use case** | ML training + real-time serving | Pure event-driven |\n\n**When to choose Lambda:**\n- Need to train ML models on historical data\n- Complex batch transformations not feasible in streaming\n- Existing batch infrastructure\n\n**When to choose Kappa:**\n- Event-sourced architecture\n- All processing can be expressed as stream operations\n- Starting fresh without legacy systems\n\n### Data Warehouse vs Data Lakehouse\n\n| Feature | Warehouse (Snowflake\u002FBigQuery) | Lakehouse (Delta\u002FIceberg) |\n|---------|-------------------------------|---------------------------|\n| **Best for** | BI, SQL analytics | ML, unstructured data |\n| **Storage cost** | Higher (proprietary format) | Lower (open formats) |\n| **Flexibility** | Schema-on-write | Schema-on-read |\n| **Performance** | Excellent for SQL | Good, improving |\n| **Ecosystem** | Mature BI tools | Growing ML tooling |\n\n---\n\n## Tech Stack\n\n| Category | Technologies |\n|----------|--------------|\n| **Languages** | Python, SQL, Scala |\n| **Orchestration** | Airflow, Prefect, Dagster |\n| **Transformation** | dbt, Spark, Flink |\n| **Streaming** | Kafka, Kinesis, Pub\u002FSub |\n| **Storage** | S3, GCS, Delta Lake, Iceberg |\n| **Warehouses** | Snowflake, BigQuery, Redshift, Databricks |\n| **Quality** | Great Expectations, dbt tests, Monte Carlo |\n| **Monitoring** | Prometheus, Grafana, Datadog |\n\n---\n\n## Reference Documentation\n\n### 1. Data Pipeline Architecture\nSee `references\u002Fdata_pipeline_architecture.md` for:\n- Lambda vs Kappa architecture patterns\n- Batch processing with Spark and Airflow\n- Stream processing with Kafka and Flink\n- Exactly-once semantics implementation\n- Error handling and dead letter queues\n\n### 2. Data Modeling Patterns\nSee `references\u002Fdata_modeling_patterns.md` for:\n- Dimensional modeling (Star\u002FSnowflake)\n- Slowly Changing Dimensions (SCD Types 1-6)\n- Data Vault modeling\n- dbt best practices\n- Partitioning and clustering\n\n### 3. DataOps Best Practices\nSee `references\u002Fdataops_best_practices.md` for:\n- Data testing frameworks\n- Data contracts and schema validation\n- CI\u002FCD for data pipelines\n- Observability and lineage\n- Incident response\n\n---\n\n## Troubleshooting\n→ See references\u002Ftroubleshooting.md for details\n\n","# Senior Data Engineer\n\nProduction-grade data engineering skill for building scalable, reliable data systems.\n\n## Table of Contents\n\n1. [Trigger Phrases](#trigger-phrases)\n2. [Quick Start](#quick-start)\n3. [Workflows](#workflows)\n4. [Architecture Decision Framework](#architecture-decision-framework)\n5. [Tech Stack](#tech-stack)\n6. [Reference Documentation](#reference-documentation)\n7. [Troubleshooting](#troubleshooting)\n\n---\n\n## Trigger Phrases\n\nActivate this skill when you see:\n\n**Pipeline Design:**\n- \"Design a data pipeline for...\"\n- \"Build an ETL\u002FELT process...\"\n- \"How should I ingest data from...\"\n- \"Set up data extraction from...\"\n\n**Architecture:**\n- \"Should I use batch or streaming?\"\n- \"Lambda vs Kappa architecture\"\n- \"How to handle late-arriving data\"\n- \"Design a data lakehouse\"\n\n**Data Modeling:**\n- \"Create a dimensional model...\"\n- \"Star schema vs snowflake\"\n- \"Implement slowly changing dimensions\"\n- \"Design a data vault\"\n\n**Data Quality:**\n- \"Add data validation to...\"\n- \"Set up data quality checks\"\n- \"Monitor data freshness\"\n- \"Implement data contracts\"\n\n**Performance:**\n- \"Optimize this Spark job\"\n- \"Query is running slow\"\n- \"Reduce pipeline execution time\"\n- \"Tune Airflow DAG\"\n\n---\n\n## Quick Start\n\n### Core Tools\n\n```bash\n# Generate pipeline orchestration config\npython scripts\u002Fpipeline_orchestrator.py generate \\\n  --type airflow \\\n  --source postgres \\\n  --destination snowflake \\\n  --schedule \"0 5 * * *\"\n\n# Validate data quality\npython scripts\u002Fdata_quality_validator.py validate \\\n  --input data\u002Fsales.parquet \\\n  --schema schemas\u002Fsales.json \\\n  --checks freshness,completeness,uniqueness\n\n# Optimize ETL performance\npython scripts\u002Fetl_performance_optimizer.py analyze \\\n  --query queries\u002Fdaily_aggregation.sql \\\n  --engine spark \\\n  --recommend\n```\n\n---\n\n## Workflows\n→ See references\u002Fworkflows.md for details\n\n## Architecture Decision Framework\n\nUse this framework to choose the right approach for your data pipeline.\n\n### Batch vs Streaming\n\n| Criteria | Batch | Streaming |\n|----------|-------|-----------|\n| **Latency requirement** | Hours to days | Seconds to minutes |\n| **Data volume** | Large historical datasets | Continuous event streams |\n| **Processing complexity** | Complex transformations, ML | Simple aggregations, filtering |\n| **Cost sensitivity** | More cost-effective | Higher infrastructure cost |\n| **Error handling** | Easier to reprocess | Requires careful design |\n\n**Decision Tree:**\n```\nIs real-time insight required?\n├── Yes → Use streaming\n│   └── Is exactly-once semantics needed?\n│       ├── Yes → Kafka + Flink\u002FSpark Structured Streaming\n│       └── No → Kafka + consumer groups\n└── No → Use batch\n    └── Is data volume > 1TB daily?\n        ├── Yes → Spark\u002FDatabricks\n        └── No → dbt + warehouse compute\n```\n\n### Lambda vs Kappa Architecture\n\n| Aspect | Lambda | Kappa |\n|--------|--------|-------|\n| **Complexity** | Two codebases (batch + stream) | Single codebase |\n| **Maintenance** | Higher (sync batch\u002Fstream logic) | Lower |\n| **Reprocessing** | Native batch layer | Replay from source |\n| **Use case** | ML training + real-time serving | Pure event-driven |\n\n**When to choose Lambda:**\n- Need to train ML models on historical data\n- Complex batch transformations not feasible in streaming\n- Existing batch infrastructure\n\n**When to choose Kappa:**\n- Event-sourced architecture\n- All processing can be expressed as stream operations\n- Starting fresh without legacy systems\n\n### Data Warehouse vs Data Lakehouse\n\n| Feature | Warehouse (Snowflake\u002FBigQuery) | Lakehouse (Delta\u002FIceberg) |\n|---------|-------------------------------|---------------------------|\n| **Best for** | BI, SQL analytics | ML, unstructured data |\n| **Storage cost** | Higher (proprietary format) | Lower (open formats) |\n| **Flexibility** | Schema-on-write | Schema-on-read |\n| **Performance** | Excellent for SQL | Good, improving |\n| **Ecosystem** | Mature BI tools | Growing ML tooling |\n\n---\n\n## Tech Stack\n\n| Category | Technologies |\n|----------|--------------|\n| **Languages** | Python, SQL, Scala |\n| **Orchestration** | Airflow, Prefect, Dagster |\n| **Transformation** | dbt, Spark, Flink |\n| **Streaming** | Kafka, Kinesis, Pub\u002FSub |\n| **Storage** | S3, GCS, Delta Lake, Iceberg |\n| **Warehouses** | Snowflake, BigQuery, Redshift, Databricks |\n| **Quality** | Great Expectations, dbt tests, Monte Carlo |\n| **Monitoring** | Prometheus, Grafana, Datadog |\n\n---\n\n## Reference Documentation\n\n### 1. Data Pipeline Architecture\nSee `references\u002Fdata_pipeline_architecture.md` for:\n- Lambda vs Kappa architecture patterns\n- Batch processing with Spark and Airflow\n- Stream processing with Kafka and Flink\n- Exactly-once semantics implementation\n- Error handling and dead letter queues\n\n### 2. Data Modeling Patterns\nSee `references\u002Fdata_modeling_patterns.md` for:\n- Dimensional modeling (Star\u002FSnowflake)\n- Slowly Changing Dimensions (SCD Types 1-6)\n- Data Vault modeling\n- dbt best practices\n- Partitioning and clustering\n\n### 3. DataOps Best Practices\nSee `references\u002Fdataops_best_practices.md` for:\n- Data testing frameworks\n- Data contracts and schema validation\n- CI\u002FCD for data pipelines\n- Observability and lineage\n- Incident response\n\n---\n\n## Troubleshooting\n→ See references\u002Ftroubleshooting.md for details\n\n",{"name":5,"description":7},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fengineering-team\u002Fskills\u002Fsenior-data-engineer","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill senior-data-engineer",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill senior-data-engineer",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill senior-data-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-data-engineer\u002FSKILL.md",true,[43,49,53,57,61,65,71,75],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fdata_modeling_patterns.md","REFERENCE","参考文档",26737,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-data-engineer\u002Freferences\u002Fdata_modeling_patterns.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fdata_pipeline_architecture.md",34584,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-data-engineer\u002Freferences\u002Fdata_pipeline_architecture.md",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fdataops_best_practices.md",43421,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-data-engineer\u002Freferences\u002Fdataops_best_practices.md",{"path":58,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Ftroubleshooting.md",3317,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-data-engineer\u002Freferences\u002Ftroubleshooting.md",{"path":62,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fworkflows.md",15500,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-data-engineer\u002Freferences\u002Fworkflows.md",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Fdata_quality_validator.py","SCRIPT","脚本",60660,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-data-engineer\u002Fscripts\u002Fdata_quality_validator.py",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fetl_performance_optimizer.py",66066,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-data-engineer\u002Fscripts\u002Fetl_performance_optimizer.py",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fpipeline_orchestrator.py",28771,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-data-engineer\u002Fscripts\u002Fpipeline_orchestrator.py",[80,87,93,100,107,114],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"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":90,"categories":91,"keywords":92,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\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},"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":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},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"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",[],[]]