「air quality」の検索結果

Expert-level air quality engineering covering pollutant sources, atmospheric dispersion, air quality standards, emission controls, and air quality modeling.

日本語の概要は準備中です。原文の説明を表示しています。

Turns Hi-C/Micro-C FASTQ into a deduplicated, filtered .pairs file with pairtools and decides whether the library worked. Covers the bwa mem -SP5M / bwa-mem2 / chromap --preset hic alignment idiom (mates mapped as independent single-end reads), pairtools parse vs parse2 and the walks-policy choice (5unique pairwise vs all for Pore-C/Micro-C concatemers), pair-type classification (keep UU and rescued UC), dedup (PCR vs optical/by-tile), select by pair_type/MAPQ/distance, restriction-fragment handling (restrict, Arima dual-enzyme, Micro-C/DNase fragment-free), and allele-specific phasing (pairtools phase to two coolers). The library-QC decision uses % long-range cis as the one-number quality metric, trans as the noise floor, orientation balance as fragment-map-free dangling-end/self-circle QC, and % duplicates as a complexity proxy. Use when processing Hi-C/Micro-C/Omni-C reads into pairs, judging library quality, handling multi-enzyme or restriction-agnostic protocols, or generating allele-specific contacts.

日本語の概要は準備中です。原文の説明を表示しています。

Turns Hi-C/Micro-C FASTQ into a deduplicated, filtered .pairs file with pairtools and decides whether the library worked. Covers the bwa mem -SP5M / bwa-mem2 / chromap --preset hic alignment idiom (mates mapped as independent single-end reads), pairtools parse vs parse2 and the walks-policy choice (5unique pairwise vs all for Pore-C/Micro-C concatemers), pair-type classification (keep UU and rescued UC), dedup (PCR vs optical/by-tile), select by pair_type/MAPQ/distance, restriction-fragment handling (restrict, Arima dual-enzyme, Micro-C/DNase fragment-free), and allele-specific phasing (pairtools phase to two coolers). The library-QC decision uses % long-range cis as the one-number quality metric, trans as the noise floor, orientation balance as fragment-map-free dangling-end/self-circle QC, and % duplicates as a complexity proxy. Use when processing Hi-C/Micro-C/Omni-C reads into pairs, judging library quality, handling multi-enzyme or restriction-agnostic protocols, or generating allele-specific contacts.

日本語の概要は準備中です。原文の説明を表示しています。

Turns Hi-C/Micro-C FASTQ into a deduplicated, filtered .pairs file with pairtools and decides whether the library worked. Covers the bwa mem -SP5M / bwa-mem2 / chromap --preset hic alignment idiom (mates mapped as independent single-end reads), pairtools parse vs parse2 and the walks-policy choice (5unique pairwise vs all for Pore-C/Micro-C concatemers), pair-type classification (keep UU and rescued UC), dedup (PCR vs optical/by-tile), select by pair_type/MAPQ/distance, restriction-fragment handling (restrict, Arima dual-enzyme, Micro-C/DNase fragment-free), and allele-specific phasing (pairtools phase to two coolers). The library-QC decision uses % long-range cis as the one-number quality metric, trans as the noise floor, orientation balance as fragment-map-free dangling-end/self-circle QC, and % duplicates as a complexity proxy. Use when processing Hi-C/Micro-C/Omni-C reads into pairs, judging library quality, handling multi-enzyme or restriction-agnostic protocols, or generating allele-specific contacts.

日本語の概要は準備中です。原文の説明を表示しています。

Check live air quality anywhere with zero API keys — Open-Meteo's air-quality API via curl, decoded from raw PM2.5 and AQI numbers into what they mean for going outside. Use when asked what's the air quality, is it safe to run outside, AQI in my city, or pollution levels right now. Produces the current AQI and pollutant levels, the plain-language health read with the standard bands, and the rerunnable command.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Air Quality Scientist. Use when a task calls for Air Quality Scientist judgment. Reasons from source emissions through transformation, transport, and dose using SMOKE/MOVES inventories, WRF-driven CTMs like CMAQ and CAMx, PMF/ME-2 apportionment, and concentration-response functions, while treating rotational PMF ambiguity, AOD-to-PM bias in humid regions, uncalibrated low-cost sensors, and untreated wildfire exceptional events as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Move quality earlier in the development lifecycle. Covers dev/QA pairing patterns, Three Amigos sessions, TDD facilitation (Red-Green-Refactor), PR review checklists for testability, and Definition of Done with quality gates. Includes shift-left maturity model for team assessment. Use when: "shift left," "TDD," "dev-QA pairing," "definition of done," "testability," "quality culture," "QA in sprint planning." Not for: writing the unit tests themselves — use unit-testing; automated PR test-quality review at scale — use ai-qa-review; multi-quarter QA direction or roadmap — use test-strategy. Related: unit-testing, ai-qa-review, test-strategy.

日本語の概要は準備中です。原文の説明を表示しています。

数据工程 — 数据平台从业者的认知操作系统, 覆盖把数据从源系统搬运成可靠 / 可查询 / 可信赖形态供分析 / ML / 数据产品消费的全生命周期 (生成 → 摄取 → 存储 → 转换 → 服务 + 安全/数据管理/DataOps/数据架构/编排/软件工程 六条暗流, Reis & Housley 框架): 摄取与集成 (批 + CDC 变更数据捕获 Debezium + EL 工具 Fivetran/Airbyte/Meltano/dlt + Kafka Connect + schema drift) / 存储与文件表格式 (对象存储数据湖 + 列存 Parquet/ORC/Arrow/Avro + 开放表格式 Apache Iceberg/Delta Lake/Apache Hudi + lakehouse + 分区/compaction) / 转换与建模 (ELT dbt/SQLMesh + Spark + 维度建模 Kimball + Inmon + Data Vault + 大宽表 OBT + 渐变维 SCD + 增量模型 + 语义/指标层) / 编排与工作流 (Apache Airflow/Dagster/Prefect/Mage/Kestra/Apache DolphinScheduler + DAG + 幂等 + 回填 backfill + 数据资产调度) / 批流与实时 (Apache Kafka/Apache Flink/Spark Structured Streaming/Kinesis/Pulsar/Redpanda + Lambda vs Kappa + watermark/窗口/exactly-once + 流式 SQL Materialize/RisingWave + 实时 OLAP ClickHouse/Apache Druid/Apache Pinot/StarRocks/Apache Doris) / 数仓与查询引擎 (Snowflake/BigQuery/Redshift/Databricks SQL/Trino/Presto/DuckDB/Polars + 存算分离 + MPP) / 数据质量测试与可观测性 (dbt tests/Great Expectations/Soda + 数据契约 + Monte Carlo data downtime + 新鲜度/量/schema 异常检测) / 数据治理编目与血缘 (DataHub/Amundsen/OpenMetadata/Unity Catalog + 列级血缘 + PII 分类 + 访问控制 + GDPR) / DataOps 与可靠性 (数据 CI/CD + 转换版本控制 + 环境隔离 + 幂等重处理 + 数据 SLA/SLO + 计算存储 FinOps) / 数据架构范式 (现代数据栈 + lakehouse + data mesh + data fabric + 去中心化 vs 中心化所有权) / 分析工程角色 (dbt 时代连接数据工程与分析的桥) — 不含 数据科学/ML 建模本身 (是下游消费者) / BI 仪表盘制作 (serving 下游) / 数据分析报表为终点 / 'data engineer = 跑 Hadoop 的' 过时窄化 / 通用后端应用开发 (平行学科) (Data Engineering — the cognitive operating system of practitioners who design, build, and operate the data platform: moving data from source systems into reliable, queryable, trustworthy form for analytics / ML / products, covering (a) the data engineering lifecycle (generation → ingestion → storage → transformation → serving, with the undercurrents security / data management / DataOps / data architecture / orchestration / software engineering — Reis & Housley framing), (b) ingestion & integration (batch + CDC change-data-capture with Debezium, EL tools Fivetran / Airbyte / Meltano / dlt, Kafka Connect, API + file + database sources, schema drift handling), (c) storage & file/table formats (object storage data lakes, columnar formats Parquet / ORC / Arrow / Avro, open table formats Apache Iceberg / Delta Lake / Apache Hudi, lakehouse architecture, partitioning / compaction / Z-ordering), (d) transformation & modeling (ELT with dbt / SQLMesh, Spark, dimensional modeling Kimball, Inmon CIF, Data Vault, One Big Table / wide tables, normalization vs denormalization, slowly changing dimensions, incremental models, the semantic / metrics layer), (e) orchestration & workflow (Apache Airflow, Dagster, Prefect, Mage, Kestra, Apache DolphinScheduler, DAGs, idempotency, backfills, data-aware / asset-based scheduling), (f) batch vs streaming & real-time (Apache Kafka, Apache Flink, Spark Structured Streaming, Kinesis / Pulsar / Redpanda, the Lambda vs Kappa debate, watermarks / windowing / exactly-once, streaming SQL Materialize / RisingWave, real-time OLAP ClickHouse / Apache Druid / Apache Pinot / StarRocks / Apache Doris), (g) warehouses & query engines (Snowflake, BigQuery, Redshift, Databricks SQL, Trino / Presto, DuckDB, Polars, decoupled storage & compute, MPP), (h) data quality, testing & observability (dbt tests, Great Expectations, Soda, data contracts, Monte Carlo / data downtime, freshness / volume / schema anomaly detection, unit / integration testing of pipelines), (i) data governance, catalog & lineage (DataHub, Amundsen, OpenMetadata, Unity Catalog, column-level lineage, PII / data classification, access control, GDPR / data privacy), (j) DataOps & reliability (CI/CD for data, version control of transformations, environments, idempotent reprocessing, SLAs / SLOs for data, cost / FinOps for compute & storage), (k) data architecture paradigms (modern data stack, data lakehouse, data mesh, data fabric, decentralized vs centralized ownership), (l) the analytics engineering role (the dbt-era bridge between data engineering and analysis); N

日本語の概要は準備中です。原文の説明を表示しています。

Qualify the exact final diff for a LoopX-managed goal. Use when goal policy enables change_quality_qualification, before a non-trivial delivery or merge, and when producing or repairing an exact-scope quality receipt. The workflow is language-neutral, permits at most one policy-authorized safe-fix pass, and never grants merge or repository authority.

日本語の概要は準備中です。原文の説明を表示しています。

Qualify the exact final diff for a LoopX-managed goal. Use when goal policy enables change_quality_qualification, before a non-trivial delivery or merge, and when producing or repairing an exact-scope quality receipt. The workflow is language-neutral, permits at most one policy-authorized safe-fix pass, and never grants merge or repository authority.

日本語の概要は準備中です。原文の説明を表示しています。

Score and diagnose Google Ads landing pages. Use when asked to audit a landing page, check landing page quality, diagnose high-CTR but low-conversion-rate ad groups, improve Quality Score's Landing Page Experience component, or compare an ad group's messaging against its landing page. Trigger on "landing page audit", "landing page score", "landing page quality", "why is my conversion rate low", "LPX", "landing page experience", "ad to page match", or when `/google-ads-audit` surfaces a high-CTR / low-CVR ad group.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "evaluate LLM output quality", "set up LLM-as-judge", "build an eval rubric", "compare model outputs pairwise", or "measure agent quality".

日本語の概要は準備中です。原文の説明を表示しています。

Data pipeline specialist for ETL design, data quality, CDC patterns, and batch/stream processingUse when "data pipeline, etl, cdc, data quality, batch processing, stream processing, data transformation, data warehouse, data lake, data validation, data-engineering, etl, cdc, batch, streaming, data-quality, dbt, airflow, dagster, data-pipeline, ml-memory" mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

投行并购 (投行并购 / 交易撮合 (Investment Banking M&A / Dealmaking) — 面向并购顾问、企业融资、卖方/买方交易执行的职业认知操作系统，从业者(分析师 Analyst / 经理 Associate / 副总裁 VP / 董事 Director / 董事总经理 MD / 内部公司发展 Corp Dev / PE 投资人)、想入行者、以及服务这行(法律/会计/估值/咨询)的视角。覆盖: (a) 第一性张力 — 投行 M&A 的核心世界观分歧: **价格 vs 价值 (price 是市场愿意付的, value 是内在的, deal 在两者缝隙里成交) ⇄ 确定性 vs 最高价 (certainty of close 对卖方常胜过纸面最高报价) ⇄ 顾问/中介 vs 委托代理 (banker 是 agent, 客户利益 vs 成交费的激励冲突真实存在, 「banker 总想成交」是行业原罪批判)**; 更深层 — 「过程/竞价纪律 (controlled auction 制造竞争张力、信息不对称管理) ⇄ 关系/信任 (relationship banking、长期 coverage、reputational capital)」, 「叙事/包装 (the story, equity story, positioning) ⇄ 数字/尽调 (the numbers, diligence, quality of earnings)」, 「估值的科学外衣 (DCF/comps 的伪精确) ⇄ 谈判的真实定价 (价格由 leverage、竞争、时机决定)」; (b) 估值与分析正典 (最标准化、最易蒸出高质量+CLI 化) — DCF (折现现金流: FCF 预测/WACC 折现率/terminal value 终值/Gordon growth vs exit multiple), Comparable Companies (可比公司/trading comps: EV/EBITDA, EV/Revenue, P/E), Precedent Transactions (先例交易/deal comps: control premium 控制权溢价), LBO (杠杆收购模型: IRR/MOIC/debt schedule/sources & uses), Accretion/Dilution (增厚/摊薄分析: EPS 影响、pro forma), Sum-of-the-Parts (分部估值/SOTP), Football Field (估值区间图), Merger Model (合并模型: synergies 协同/purchase accounting/goodwill), Sensitivity/scenario; (c) 交易流程与产出物 — 卖方流程 (sell-side: teaser 简介 → NDA → CIM/IM 信息备忘录 → management presentation → IOI 意向函 → data room 数据室 → LOI/term sheet → confirmatory diligence → SPA 买卖协议 → signing → closing), 买方流程 (buy-side: thesis/sourcing → outreach → valuation → bid → exclusivity → diligence → financing → close), auction 类型 (broad/targeted/negotiated/preemptive bid); 产出物: pitchbook 推介材料、CIM、fairness opinion 公平意见、board presentation、fee letter、engagement letter; (d) 交易结构与条款 — consideration (cash/stock/mix/earnout 对赌)、deal protections (breakup fee 分手费/go-shop/no-shop/MAC 重大不利变化条款)、representations & warranties 陈述与保证、escrow 托管、working capital adjustment 营运资金调整、reverse termination fee、collar 价格区间、tender offer vs merger、hostile vs friendly、defensive tactics (poison pill 毒丸/white knight 白衣骑士/staggered board); (e) 行业结构与角色 — bulge bracket (高盛/摩根士丹利/JPM/BofA/花旗) vs elite boutique (Centerview/Evercore/Moelis/Lazard/PJT/Perella) vs middle market (Houlihan Lokey/William Blair/Harris Williams) vs regional/independent; analyst→associate→VP→director→MD 晋升金字塔; coverage (行业组) vs product (M&A/ECM/DCM/leveraged finance/restructuring); sponsors group (服务 PE); 买方包括 PE/strategic acquirer/corp dev; (f) 量化指标与节奏 — deal fee (success fee 业内通常约 1-2% 视规模递减/retainer/Lehman formula)、league table 排行榜、pitch→mandate 转化、deal velocity、hours culture (analyst 80-100h/week 文化批判)、bonus/comp 结构、deal sheet (简历上的成交清单); (g) 争议/批判 — fairness opinion 是否橡皮图章 (利益冲突: 出意见的 banker 也收成交费)、estimate 的伪精确 (DCF garbage in garbage out、假设驱动结论)、banker 永远建议成交 (deal 偏见、empire building 助推 CEO 自利并购)、协同效应系统性高估 (大量并购毁灭价值、winner's curse 赢家诅咒)、analyst 血汗工厂文化 (2021 高盛 13 人 deck 事件、过劳死争议)、advisory 价值 vs 中介寻租之争、bulge vs boutique 的利益独立性叙事 (boutique 标榜「无承销利益冲突」)、SPAC 泡沫与 de-SPAC 教训; (h) 流派/思想谱系 — 估值学派 (Aswath Damodaran 估值教父/纽大、Tim Koller McKinsey《Valuation》、McKinsey valuation 体系) vs 公司金融教科书派 (Rosenbaum & Pearl《Investment Banking》行业圣经、Brealey Myers Allen、CFI/WSP/BIWS 培训体系) vs 交易实战派 (Bruce Wasserstein《Big Deal》、Joseph Perella/Felix Rohatyn 老派 dealmaker、现代 boutique 创始人) vs 行为/批判派 (并购毁灭价值的学术证据、Damodaran 对协同/控制权溢价的批判、Matt Levine《Money Stuff》解构华尔街逻辑) vs PE/buy-side 视角 (LBO 数学、value creation 杠杆/运营/multiple expansion)。不含: 二级市场股票交易/卖方研究 (equity research)、零售财富管理/private banking、纯 ECM/IPO 承销执行 (虽相关但聚焦 M&A advisory)、纯 PE 投后运营、量化交易/对冲基金策略、纯公司财务报表会计。) Master OS — automated mastery of 投行并购 / 交易撮合 (Investment Banking M&A / Dealmaking) — 面向并购顾问、企业融资、卖方/买方交易执行的职业认知操作系统，从业者(分析师 Analyst / 经理 Associate / 副总裁 VP / 董事 Director / 董事总经理 MD / 内部公司发展 Corp Dev / PE 投资人)、想入行者、以及服务这行(法律/会计/估值/咨询)的视角。覆盖: (a) 第一性张力 — 投行 M&A 的核心世界观分歧: **价格 vs 价值 (price 是市场愿意付的, value 是内在的, deal 在两者缝隙里成交) ⇄ 确定性 vs 最高价 (certainty of close 对卖方常胜过纸面最高报价) ⇄ 顾问/中介 vs 委托代理 (banker 是 agent, 客户利益 vs 成交费的激励冲突真实存在, 「banker 总想成交」是行业原罪批判)**; 更深层 — 「过程/竞价纪律 (controlled auction 制造竞争张力、信息不对称管理) ⇄ 关系/信任 (rela

日本語の概要は準備中です。原文の説明を表示しています。

Perform a rigorous Carmack Council code review. Use when explicitly asked to review code, do a "council review", "carmack review", or invoke /council-review. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo Collina (Node.js), Brandur Leach (Postgres), Vercel Performance, Simon Willison (LLM pipelines), Karri Saarinen (UI quality), Vitaly Friedman (UX quality), Kent Beck (test quality). Uses parallel subagents for deep, independent review. Produces prioritised P1/P2/P3 findings. Stack: Next.js App Router / React / TypeScript / tRPC / Prisma / Neon / Clerk.

日本語の概要は準備中です。原文の説明を表示しています。

Expert-level environmental engineering covering water treatment, wastewater treatment, air quality, solid waste, site remediation, and environmental regulations.

日本語の概要は準備中です。原文の説明を表示しています。

Expert en data engineering (ETL, Airflow, dbt, data lakes, streaming pipelines, data quality)

日本語の概要は準備中です。原文の説明を表示しています。

Evaluate LLM outputs using frontier models as judges. Use for pairwise model comparison, quality scoring with custom rubrics, and automated evaluation pipelines. Covers position bias mitigation, statistical significance, and generating preference data for DPO/RLHF.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to optimize aerospace and defense supply chains, manage long lead-time components, handle MRO operations, or ensure AS9100 compliance. Also use when the user mentions "aerospace supply chain," "aviation manufacturing," "MRO supply chain," "AS9100," "aircraft parts," "defense procurement," "AOG support," "airworthiness," "ITAR compliance," "aerospace certification," or "aviation aftermarket." For general manufacturing, see production-scheduling. For quality, see quality-management.

日本語の概要は準備中です。原文の説明を表示しています。

AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with truth-score verification.

日本語の概要は準備中です。原文の説明を表示しています。

AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with truth-score verification.

日本語の概要は準備中です。原文の説明を表示しています。

Content quality and E-E-A-T assessment for AI citability — evaluate experience, expertise, authoritativeness, trustworthiness, and content structure

日本語の概要は準備中です。原文の説明を表示しています。

AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with truth-score verification.

日本語の概要は準備中です。原文の説明を表示しています。

Single-page SEO audit: content quality under Google's E-E-A-T framework and Helpful Content guidelines, on-page factors, search intent, technical signals and readability. Pulls GSC data for the page, crawls the live HTML, checks metadata, schema, internal linking and depth, and produces a scored report with fixes. Use whenever the user wants to analyze a specific page or URL, not the whole site. Trigger on: "analyze this page", "audit this URL", "how is this page doing", "evaluate my blog post", "check this landing page", "page SEO", "content quality check", "is this page good enough", "review this page's SEO", "what's wrong with this page", "how can I improve this page", "page analysis", "single page audit", "content audit for [URL]", or any request naming a specific URL/page for SEO evaluation. If the user provides a specific URL (not just a domain), this is likely the right skill; use /seo-analysis for full-site audits instead.

日本語の概要は準備中です。原文の説明を表示しています。