「compare」の検索結果

同業種の複数企業（3〜5社程度）を横並びで比較し、業界内のポジショニングを整理する時に使う。「〇〇と△△を比較して」「この業界の主要企業を並べて」のような、複数社の比較指示で発火する。

Standard operating procedure for an auditable, headless MIKE+ workflow via the mike-plus MCP server — how to plan, copy, run, QA-gate, compare, plot, audit, and safely stop. Use FIRST whenever an agent is handed a MIKE+ model (.sqlite) or result (.res1d) plus a plain-language goal; it picks the operating mode and tells the agent which mike-* skill to open next and in what order.

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

This skill should be used when the user asks to "implement LLM-as-judge", "compare model outputs", "create evaluation rubrics", "mitigate evaluation bias", or mentions direct scoring, pairwise compari

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

Diff a live page's accessibility violations against a baseline — by default compares uncommitted changes (stash-based), or pass --branch [<name>] to diff against a branch. Reports only new violation

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

Discover AAS skills for an explicit task and compare their complete instructions without installing them.

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

Use when the user asks to "analyze influencer campaign performance", "compare influencers", or "find what content worked"; produces metric scorecards vs target and benchmark, platform/influencer/content rankings, engagement-quality and sentiment reads, conversion-attribution breakdowns, and ranked learnings. Not for dollar-level return math — use roi-calculator. 达人营销效果分析/投放复盘

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

Use when the user asks to "read back" a paid campaign change, "did this ad change work", or "compare ROAS/CPA before and after"; reads ROAS/CPA against a control over a fixed readback window and returns a Promote / Keep-testing / Rollback / Unproven readback decision with the math delegated to roi-calculator. Not for RQS scoring or veto adjudication — use ad-account-auditor; not for the ROI ratio math — use roi-calculator; not for cross-channel rollups — use performance-analyzer. 付费广告复盘/ROAS回看/投放效果归因

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

Use when the user asks to "run a launch retro / post-mortem", "compare launch results vs targets by channel", or "decide what to keep or kill for the next launch"; produces a structured D1/W1/M1 retrospective — a per-channel actual-vs-target table (UTM-attributed own analytics as the truth column, platform self-reported numbers as reference, every figure labeled Measured / User-provided / Estimated), a 5-Whys chain on the single largest miss, keep / kill / change decisions per channel, 3-5 actionable learnings for the next launch, and an outcome snapshot submitted to the launch registry. Not for return math (CPA / ROI) — use roi-calculator; not for the stakeholder-facing report writeup — use report-generator; not for a metric deep-dive — use performance-analyzer. 发布复盘/渠道归因/5-Whys/keep-kill

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

Update an installed Marketing Agent OS GEO skill set safely. Use when users ask to check for GEO workflow updates, compare an installation with its configured source, or refresh GEO skills without overwriting custom work silently.

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

Use when the user asks to "allocate my influencer budget", "optimize spend across tiers", or "compare budget scenarios"; produces a tier/platform/content allocation table, ROI and CPM/CPE projections, scenario comparisons, and mid-campaign reallocation moves. Not for building the full campaign plan — use campaign-planner. 达人预算分配/投放预算优化

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

Use when platform-reported conversions disagree with GA4/ecommerce, when you suspect Meta and Google are double-counting the same sales, or for a standing (monthly) reconciliation workbook that de-dups stacked credit against an order-ID truth set, normalizes attribution windows and currency, compares attribution models, and reads incrementality from a geo/holdout test. Not for the point-in-time R2 veto or RQS gate — use ad-account-auditor; not for the ROI/ROAS ratio math itself — use roi-calculator; not for organic dark-social share attribution or GA4 direct-traffic decomposition — use dark-social-attributor. 付费广告归因对账/去重/增量

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

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

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

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

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

Detect inconsistencies in ID formatting, date/time display, monetary amounts, and enum/status labels compared to existing patterns in the codebase.

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

Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

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

Deep, iterative internet research for current facts, source triangulation, contradiction checks, due diligence, competitive analysis, claim verification, "latest" lookups, and cited reports. Use when the user asks to browse, search, research the web, verify claims, compare sources, gather primary sources, investigate companies, people, products, technical topics, news, events, markets, or create AKBP-ready durable research evidence.

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

Use tsift for token-efficient repository navigation, code search and reading, call graphs, diffs, logs, tests, session context, and workspace memory. TRIGGER: exploring or changing a codebase with tsift installed, or working on the tsift repo. SKIP: plain file-level glob, non-code web search. VERSION CHECK: compare `tsift --version` against tsift-version below before trusting any command text copied from this file.

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

End-to-end eval-suite orchestration with the `eval` command: run -> grade -> compare -> calibrate, using strict JSON contracts and schema discovery.

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

Analyze graded `trial_result` JSONL outputs from the eval pipeline, including reliability and custom slicing.

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

Use when working with Aws Pricing — aWS pricing helper for cost queries. ALWAYS use get_aws_cost script for pricing questions. Use when: - User asks about AWS resource costs or pricing - User wants to compare pricing across regions - User needs spot, on-demand, or reserved pricing info Triggers: aws pricing, aws cost, how much does, ec2 price, rds cost, s3 pricing.

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

Stock quotes, history, search, compare, crypto via Yahoo.

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

Throwaway HTML mockups: 2-3 design variants to compare.

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

In each setting, LLM-based methods substantially outperform classical baselines, achieving up to 68% recall at 90% precision compared to near 0% for t

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

AI Agent Index Categories Find Agent + Submit Compare Alternatives Stacks Advertise API Home / AI Coding Agents Best AI Coding Agents (2026): IDEs, Te

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