409건 · 관련도순
Analyzes Google Cloud BigQuery slot consumption, query costs, and execution bottlenecks using INFORMATION_SCHEMA. Use when diagnosing slow BigQuery queries, slot starvation, high on-demand query costs, unpartitioned table scans, or join performance issues. Don't use for generic BigQuery administration (use bigquery-basics), BigQuery ML (use bigquery-ai-ml), or DataFrame operations (use bigquery-bigframes).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reads, queries, and writes bigWig indexed binary signal tracks (coverage, fold-change, conservation, methylation-rate) with pyBigWig (Python) and the UCSC Kent tools (bedGraphToBigWig, bigWigToBedGraph, bigWigInfo, bigWigSummary, bigWigAverageOverBed) and deepTools (multiBigwigSummary, computeMatrix, bigwigCompare). Covers the central trap that a wide query returns a precomputed zoom-level summary (by default the mean, which annihilates narrow peaks) not per-base data, when exact=True/values() is mandatory, the NaN-not-zero gap-handling fork, choosing mean vs max vs sum vs coverage by biological question, and the sorted-bedGraph plus chrom.sizes build requirement. Use when extracting signal at regions, computing mean signal per gene/peak, building a browser track from bedGraph, comparing tracks, or building TSS/gene-body metaprofiles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reads, queries, and writes bigWig indexed binary signal tracks (coverage, fold-change, conservation, methylation-rate) with pyBigWig (Python) and the UCSC Kent tools (bedGraphToBigWig, bigWigToBedGraph, bigWigInfo, bigWigSummary, bigWigAverageOverBed) and deepTools (multiBigwigSummary, computeMatrix, bigwigCompare). Covers the central trap that a wide query returns a precomputed zoom-level summary (by default the mean, which annihilates narrow peaks) not per-base data, when exact=True/values() is mandatory, the NaN-not-zero gap-handling fork, choosing mean vs max vs sum vs coverage by biological question, and the sorted-bedGraph plus chrom.sizes build requirement. Use when extracting signal at regions, computing mean signal per gene/peak, building a browser track from bedGraph, comparing tracks, or building TSS/gene-body metaprofiles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write and improve SQL for major data warehouses, accounting for differences in their syntax. Use it to build analytical queries, translate existing SQL, investigate errors, and review slow queries for performance improvements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn everyday questions into SQL queries, the commands used to retrieve and summarize database records. Uses your database structure and platform to produce queries with explanations, performance notes, and optional validation scripts.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up monitoring for deployed agents to inspect execution paths, latency, and model interactions. It explains Cloud Trace, prompt and response logging, BigQuery analytics, and external monitoring integrations, with checks for missing data and unwanted content capture.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage files in Google Cloud's Cloud Storage buckets, the containers that hold stored data. Upload, download, and organize content, configure access and time-limited sharing links, and manage storage lifecycle, costs, and data protection.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Answers questions about GKE spending using BigQuery billing exports and live cluster metrics. It breaks down costs by project, namespace, or workload and compares requested computing resources with actual usage to investigate cost increases.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Retrieve BigQuery execution records and resource metrics using the right tool for each task. The skill guides monitoring tool selection and SQL queries for performance investigations, capacity analysis, and reviews of billable compute and storage usage.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review BigQuery capacity, table layouts, storage retention, and SQL to improve cost efficiency. Compare billing options, plan partitioned tables, and evaluate search indexes, stored aggregation results, and BI Engine for suitable workloads.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Implements automated PII discovery and classification using tools like Microsoft Purview, BigID, OneTrust DataDiscovery, and AWS Macie. Covers scanning schedules, accuracy tuning, false positive management, and integration patterns. Keywords: data discovery, PII scanning, Purview, BigID, Macie, OneTrust, automated classification, data cataloging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Summarizes Google Cloud Data Lineage graphs to help users debug data quality issues and understand data provenance for BQ/GCS. Use when summarizing upstream and downstream data flows, and presenting complex lineage data as an intuitive Markdown report. Don't use for generic BigQuery queries, editing lineage relationships, or downstream deprecation. Don't use for downstream blast-radius impact analysis (use datalineage-bigquery-asset-impact-analysis skill instead).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a BigQuery materialization to stream Estuary collections into BigQuery tables. Use when setting up BigQuery as a destination for captured data. Use when user says "send to BigQuery", "load into BigQuery", "materialize to BigQuery", or "BigQuery destination".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Process next-generation sequencing data with deepTools: convert alignment files into coverage tracks, normalize signals, compare samples, and check quality. Create heatmaps and profiles around genes or peak regions for ChIP-seq, RNA-seq, and ATAC-seq experiments.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write complex SQL, improve slow queries, and design database schemas for transaction processing and analytics. Uses schema details and query execution plans to guide indexing, validate results, and assess performance with realistic data volumes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a plain-language data request into SQL tailored to your database. Build queries that combine tables, filter records, and calculate summaries, with explanations of each step, performance considerations, and suggestions for adjusting dates or other conditions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Work with Apache Beam I/O connectors, components that read and write external data. Get guidance on connector usage, unit and integration tests, troubleshooting data connections, and the basic structure of new connectors.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use this skill for processing and analyzing large tabular datasets (billions of rows) that exceed available RAM. Vaex excels at out-of-core DataFrame operations, lazy evaluation, fast aggregations, efficient visualization of big data, and machine learning on large datasets. Apply when users need to work with large CSV/HDF5/Arrow/Parquet files, perform fast statistics on massive datasets, create visualizations of big data, or build ML pipelines that do not fit in memory.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix ClickHouse query errors in Rust when using clickhouse-rs crate. Use when: (1) "string is not valid utf8" errors - typically FixedString columns need CAST to String, (2) "tag for enum is not valid" errors - typically Option<T> fields receiving non-NULL values, (3) Sum/count aggregations returning Float64 but Rust expects u64, (4) LEFT JOIN results with empty strings where Rust expects Option::None, (5) "not enough data, probably a row type mismatches a database schema" - query SELECT returns fewer columns than the Rust Row struct expects (common when multiple query functions share the same struct but one function is missing columns added later), (6) Garbled/corrupted data when INSERTing to FixedString(N) columns using String Rust type - silently corrupts data (no error!) because String adds a length prefix but FixedString expects exactly N raw bytes. Fix: use [u8; N] with #[serde(with = "BigArray")] from serde-big-array, (7) "the trait bound `[u8; 64]: serde::Serialize` is not satisfied" when using [u8; N] arrays in Row structs - need #[serde(with = "BigArray")] annotation from serde-big-array crate.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when user asks to create/design a big screen (大屏), full-screen data visualization, or says "创建大屏", "生成大屏", "新建大屏", "设计大屏", "做一个大屏", "BI大屏", "数据大屏", "可视化大屏", "监控大屏", "create big screen", "design big screen", "BI visualization big screen". Also triggers when user describes big screen requirements like "做一个销售数据大屏" or mentions full-screen display like "展厅展示", "监控室大屏". Make sure to use this skill for big screens (大屏) — NOT dashboards (仪表盘/看板), which use a completely different layout and styling system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SEO/GEO Agent Operations SOP v2 — Rebuilt from real-world operations (analook.com 0→launch, GSC incident, DataForSEO monitoring, gingiris.tools post-migration recovery). What's new in v2: • Step-by-step onboarding (Q1→Q6), multiple choice wherever possible — no big forms • Mandatory daily SEO log — first item is always GSC token status check • Data cross-validation rule: any external metric must come from ≥2 sources before use • Backlink progress tracking (6-week wait → check → alert if not indexed) • New vs. established site strategy matrix (new site <6mo: KD≤20; mature: KD up to 35+) Real incidents baked in: GSC token expired silently for 2 weeks (analook.com), P0 keywords dropped out of Top 100 after domain migration (gingiris.tools), traffic data off by 17× from single-source DataForSEO. Triggers: "SEO agent" | "SEO daily report" | "GSC monitoring" | "DataForSEO" | "GEO agent" | "backlink tracking" | "IndexNow" | "competitor comparison page" | "SEO SOP" | "autonomous SEO" | "GEO triple combo" 🇨🇳 SEO/GEO Agent 运营 SOP v2 — 基于真实运营经验重写（analook.com 从零建站 + GSC 断档 2 周 + DataForSEO 监控 + gingiris.tools 迁移权重恢复）。 对话式开局、强制日报（GSC token 是第一项）、数据交叉验证铁律、外链进度追踪、新老站区分策略。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GTM prospecting, enrichment, outreach, and Deepline Play work/audits. Providers: adyntel,affinity,ai_ark,akta,allegrow,amplemarket,apify,attention,attio,aviato,bettercontact,bigquery,bluesky,bounceban,brave,browserbase,builtwith,cbinsights,clay,clickhouse,cloudflare,contactout,contextdev,crunchbase,crustdata-v3,customer_db,databricks,dataforseo,datagma,dealroom,deepline_ip_to_company,deepline_native,deeplineagent,discolike,dropleads,edges,emailbison,emailguard,enformion,enigma,exa,findymail,firecrawl,fireflies,firmable,forager,fullenrich,fundable,generic_http,getleads,gong,google_ads_audiences,google_workspace,govfiles,grain,hackernews,harvestapi,heyreach,hubspot,hunter,icypeas,instantly,intercom,ipqs,kaspr,kernel,leadmagic,lemlist,limadata,linkedin_ads_audiences,luma,lusha,meta_audiences,millionverifier,nooks,notion,openmart,opensosdata,openwebninja,outreach,parallel,peopledatalabs,pitchbook,podscan,polymarket,postgres,predictleads,prospeo,quickenrich,rapidapi,redshift,rocketreach,salesforce,salesforge,….
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run SQL against Google BigQuery and browse its catalog — submit queries (sync or async), poll job status, page through results, list datasets/tables, and read table schemas. Use this whenever the user wants to query a BigQuery table, ask "what's in this dataset", check a BigQuery job's status, or mentions bigquery.googleapis.com or a `project.dataset.table` path. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.