131건 · 관련도순
Use sales history and current stock to estimate stockout dates, reorder timing, quantities, and costs. Identify cash tied up in slow-moving inventory, and prepare purchase order and supplier email drafts for approval.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review data strategy plans through six focused questions covering training data permissions, infrastructure choices, data asset value, and hiring. Produce a structured verdict with unresolved issues and three concrete next steps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Helps startup leaders make strategic data decisions: assess permission to train AI on customer data, choose data architecture, evaluate customer data as a business asset, and sequence hiring around the decisions the business needs to make.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design a shared data platform across Google Cloud, AWS, and Azure for analytics and AI. The skill turns requirements into architecture diagrams, infrastructure code, deployment instructions, and validation checks using Apache Iceberg and BigQuery data agents.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design hybrid search on AlloyDB by combining meaning-based search, keywords, and SQL filters. Turn requirements into architecture diagrams, database setup scripts, deployment guidance, and validation plans for search applications on Google Cloud.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze product usage in PostHog and manage experiments, dashboards, surveys, and feature flags, which control feature availability. Use connected tools to investigate user behavior and errors, run queries, and summarize findings with numbers and links.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Answer business questions about counts, trends, comparisons, or rankings using SQL, a language for querying tables. Validate the results, then present a concise answer, a small table, the executed query, and supporting checks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resolve data lake and lakehouse asset references across Glue Data Catalog, S3, S3 Tables, and Redshift. Triggers on: find the table, where is our data, which table has, locate dataset, find data for, search catalog, what tables match, Redshift table, lakehouse table, data lake table, warehouse table, reverse lookup S3 path. Do NOT use for: full catalog audits (use exploring-data-catalog), running queries (use querying-data-lake), creating tables (use creating-data-lake-table).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides an end-to-end data-warehouse migration to Amazon Redshift — discovery, schema/SQL/stored-procedure/macro/script conversion, data migration, validation, performance comparison, and reporting. Source-routed via `references/<source>/`; Teradata (Vantage) is the supported source; additional sources are added as their own `references/<source>/` sets. Text-only knowledge (no executable code) — the AI generates all execution at runtime. Applies when a user wants to migrate Teradata to Amazon Redshift, convert Teradata DDL/SQL/stored procedures/macros/BTEQ to Redshift/RSQL, or assess Teradata-to-Redshift migration complexity. Applies only to migrations targeting Amazon Redshift; migrations to other platforms (Snowflake, BigQuery, Databricks, etc.) are out of scope regardless of source. Does not cover general Redshift administration, performance tuning, or troubleshooting of existing Redshift clusters (no migration involved), or sources not listed under references/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Owns data as an asset — governance, quality, the warehouse and semantic layer, analytics capability, and the governance of models built on top. Use this for a decision about how data is collected, stored, defined, or shared; when numbers disagree between teams; when deciding what to build in-house versus buy; when standing up a data function; or when an AI or model decision needs governance rather than engineering.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when asked 5S 检查表, 6S 管理, 现场管理检查, 5S 评分标准, 车间 6S 稽核, 做一份 5S 推行计划, or design a 5S or 6S audit for a workshop, warehouse or office in a Chinese factory. Produces an audit checklist for the area with scored criteria for 整理, 整顿, 清扫, 清洁, 素养 (and 安全 for 6S), a scoring guide with photo evidence rules, a results summary and red-tag list, a corrective-action tracker with owners and dates, and an audit rota, in Chinese.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manages a Fabric SQL database item, the OLTP SQL Server engine, including running T-SQL through sqlcmd, temporal and vector similarity search, schema and sys.tables inspection, dacpac deployment, and Query Store, blocked sessions and regressed-plan investigation. Use for any query or change against a SQL database item. Warehouse, lakehouse SQL endpoint and mirrored items belong to sqldw-cli.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manages Fabric Dataflow Gen2 items, including creation, M editing, connections, output destinations, getDefinition and updateDefinition inspection, executeQuery, refresh history, and Gen1-to-Gen2 save-as upgrades via saveAsNativeArtifact. Use for Dataflow items or Power Query M definitions. For pipeline JSON use pipeline-migration; for Spark or Warehouse transformations use their own skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query Fabric lakehouse and warehouse data using DuckDB, either locally or inside a Fabric notebook. Automatically invoke when the user mentions "DuckDB", "query Delta tables locally", or asks to "attach DuckDB to a lakehouse", "query OneLake data", "explore lakehouse data", "data freshness check", "validate data quality", "use DuckDB in Fabric".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How to actually instrument product analytics correctly. Event taxonomy, property design, naming conventions, schema versioning, identity stitching, funnel design, retention cohorts, North Star metric selection, dashboard hygiene, instrumentation debt, and the failure modes that produce data nobody trusts. Triggers on product analytics setup, event taxonomy, tracking plan, instrumentation, schema versioning, North Star metric, retention cohorts, funnel design, naming conventions, instrument new feature, audit existing analytics, dashboard reconciliation, instrumentation debt, Mixpanel setup, Amplitude setup, PostHog setup, warehouse-native analytics. Also triggers when the team has data but cannot trust it, or when designing instrumentation for a new feature, or when auditing an existing setup that has drifted.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
A platform decision framework for experimentation. When to use Statsig vs PostHog vs GrowthBook vs Optimizely vs Amplitude vs Eppo vs Kameleoon. How to migrate between them. How to coordinate when multi-platform is genuinely warranted. The decisions that compound for years and the ones you can defer. Triggers on which experimentation platform, choose Statsig vs PostHog, evaluate experimentation tools, switch experimentation platform, migrate from Optimizely, consolidate experimentation tools, multi-platform experimentation, experimentation platform decision, ab test platform selection, feature flag platform vs experiment platform, warehouse-native experiments, vendor lock-in experimentation. Also triggers when a team is asking about cost, governance, or migration cost across experimentation tools, or when an evaluation is starting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analytics engineering across data modeling, dbt, transformation, and semantic layers. Use when building dbt models, designing star schemas, writing staging or mart SQL, configuring data tests, or optimizing warehouse queries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit data quality across pipelines, warehouses, and stores. Use when designing a DQ program, defining DQ dimensions, building rule-based checks, detecting schema drift, monitoring freshness SLAs, or responding to a DQ incident.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Export marketing data to a warehouse or Sheets, PII-redacted, approval-gated. "export contacts to a sheet"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.