「comparison」の検索結果

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.

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

Compares the performance of two or more audience segments across key metrics side by side. Use this skill when someone wants to compare audiences, cohorts, or groups — for example, "how do mobile users compare to desktop users on conversion," "compare new vs. returning visitors," "show me the difference between these two segments," "compare these audiences on our KPIs," or "which segment performs better." Also trigger for "segment comparison," "audience comparison," or "cohort comparison."

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

Generate SEO-optimized competitor comparison and alternatives pages. Covers "X vs Y" layouts, "alternatives to X" pages, feature matrices, schema markup, and conversion optimization. Use when user says "comparison page", "vs page", "alternatives page", "competitor comparison", "X vs Y", "versus", "compare competitors", or "alternative to".

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

Compares the performance of two or more audience segments across key metrics side by side. Use this skill when someone wants to compare audiences, cohorts, or groups — for example, "how do mobile users compare to desktop users on conversion," "compare new vs. returning visitors," "show me the difference between these two segments," "compare these audiences on our KPIs," or "which segment performs better." Also trigger for "segment comparison," "audience comparison," or "cohort comparison."

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

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,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.

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

編集前後の文章やパッチから、変更箇所を比較できる画面とPNG・PDFを作るスキル。共有用URLや添付ファイルで、修正内容を具体的に伝えられます。

• 文章の変更箇所をURLで共有したいとき
• 差分をPNGやPDFで添付したいとき
• 修正確認用の高品質な資料作成

候補の探索や比較を繰り返し、試行の根拠と判断を追記型の台帳に残すスキル。前回との整合性や再検証の結果を確認し、実取引や本番操作へ進む条件を明確にします。

• 試行を重ねて候補を比較したいとき
• 判断の根拠を記録したいとき
• 新情報で前回の採用候補を見直したいとき

売上・返金・重複課金を請求データから整理し、チーム課金や利用権限の実装まで確認するスキル。料金表示と実際の動作を照合し、運営の判断材料をまとめます。

• 売上と契約状況を把握したいとき
• 重複課金や返金の原因調査
• チーム課金の実装を確認したいとき

類似企業の売上・利益率・評価倍率を比較するExcelを作成します。計算式、中央値や四分位、データの出典をまとめ、投資や買収の検討に使う比較資料を整えます。

• 同業他社との企業価値比較
• 買収検討用の比較資料作成
• 業界の成長性・収益性比較

記事・論文・メモを要約し、相互リンク付きのMarkdown知識集として蓄積。出典を残しながら質問への回答や比較をまとめ、矛盾やリンク切れも点検します。

• 記事や論文から調査用の知識集を作成
• 新しい資料を既存のノートに追加
• 出典付きの回答や比較を保存

Side-by-side comparison of ruflo vs HAL vs other GAIA harnesses — capability gaps, design decisions, and improvement roadmap

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

Create "[Competitor] alternative" and comparison pages for developer tools. Build honest, high-converting comparison content that ranks for competitive search terms.

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

Analyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.

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

Compares two or more dotnet new templates side by side to help users choose between them based on parameters, feature support, frameworks, and classifications. USE FOR: deciding between similar templates (webapi vs webapp, blazor vs blazorwasm, console vs worker), producing a side-by-side comparison of parameters and feature support, understanding how templates differ before creating a project. DO NOT USE FOR: creating a project from a template (use template-instantiation), authoring or validating custom templates (use template-authoring and template-validation), general single-template discovery (use template-discovery).

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

Helps find, inspect, and compare (at a high level) .NET project templates. Resolves natural-language project descriptions to ranked template matches with pre-filled parameters. USE FOR: finding the right dotnet new template for a task, inspecting a template's parameters and constraints, understanding what a template produces before creating a project, resolving intent like "web API with auth" to concrete template + parameters. DO NOT USE FOR: actually creating projects (use template-instantiation), authoring custom templates (use template-authoring), producing a detailed side-by-side comparison (use template-comparison), choosing cross-parameter defaults during creation (use template-smart-defaults), MSBuild or build issues (use dotnet-msbuild plugin), NuGet package management unrelated to template packages.

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

Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect Directory.Packages.props (CPM), composing multi-project solutions (API + tests + library), getting latest NuGet package versions in newly created projects. DO NOT USE FOR: finding templates (use template-discovery), producing a detailed side-by-side comparison of templates (use template-comparison), authoring custom templates (use template-authoring), deciding cross-parameter defaults such as which framework to pair with native AOT or whether to keep HTTPS when auth is enabled (use template-smart-defaults), modifying existing projects or adding NuGet packages to existing projects.

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

Opinionated Bayesian modeling workflow with PyMC and ArviZ. Contains critical guardrails (nutpie sampler, prior/posterior predictive checks, LOO-PIT calibration, prior sensitivity checks, 94% HDI, non-centered parameterizations, reproducible seeds) that agents won't apply unprompted — always consult before writing Bayesian model code. Trigger on: building probabilistic/Bayesian models, prior elicitation, MCMC inference, convergence diagnostics (divergences, R-hat, ESS), model comparison (LOO-CV, ELPD, stacking weights), hierarchical/multilevel models, count regressions, logistic regression with uncertainty, prior sensitivity analysis, reporting Bayesian results, or mentions of PyMC, ArviZ, InferenceData, credible intervals, posterior distributions, shrinkage, uncertainty quantification. Also trigger for model comparison, diagnosing sampling problems, choosing priors, or presenting stats to non-technical audiences.

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

Programmatic SEO planning and audit: building or evaluating large sets of template-generated pages that target long-tail query patterns (e.g. "[service] in [city]", "[product] vs [product]", "[tool] for [use-case]"). Covers data-source and template design, thin/duplicate-content and doorway-page risks, per-page uniqueness and value thresholds, internal linking and hubs, indexation management (publish vs. noindex), and scaling without a manual action. Use whenever the user wants to generate many pages from a template/dataset, build location/comparison/use-case pages at scale, or asks why generated pages aren't indexing. Trigger on: "programmatic SEO", "pSEO", "generate pages at scale", "templated pages", "location pages at scale", "comparison pages", "[city] pages", "my generated pages aren't indexed", "doorway pages", "scale content". For one-off content use /content-writer; for keyword discovery use /keyword-research.

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

Evaluate trained machine learning models with the right metrics and comparison logic. Use for benchmark review, threshold selection, calibration, validation, and model comparison; not for feature engineering or leakage auditing.

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

Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake. Answers questions about storage access tiers (hot, cool, cold, archive), when to use each tier, and tier comparison. Provides object storage, SMB file shares, async messaging, NoSQL key-value, and big data analytics. Includes lifecycle management. USE FOR: blob storage, file shares, queue storage, table storage, data lake, upload files, download blobs, storage accounts, access tiers, storage tiers, hot cool cold archive, storage tier comparison, when to use storage tiers, lifecycle management, Azure Storage concepts. DO NOT USE FOR: SQL databases, Cosmos DB (use azure-prepare), messaging with Event Hubs or Service Bus (use azure-messaging).

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

PHP type juggling and weak comparison (`==`) bypass. Use when authentication, HMAC/signature checks, or token validation uses loose equality, numeric coercion, or hash comparisons without strict types — common in legacy PHP and CTF-style code paths.

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

Answers a business question with data without fooling yourself — framing the question so an answer would change something, choosing the right comparison, checking the data before trusting it, recognizing the traps that produce confident wrong answers (aggregation reversals, survivorship, regression to the mean, multiple comparisons), and reporting uncertainty honestly. Use this to run an analysis, review one before acting on it, or work out why two people looking at the same data reached opposite conclusions.

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

Gets a product listed where buyers and crawlers look — directories, marketplaces, review sites, comparison pages, and aggregators. Use this to plan a submission push, choose which directories are worth the effort, prepare listing assets, build comparison and alternative pages, or manage presence on review platforms.

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

Generates complete FAERS-style pharmacovigilance disproportionality research designs from a user-provided drug class, comparator strategy, adverse-event domain, and patient-group stratification. Always use this skill whenever a user wants to design, plan, or build a spontaneous-report safety signal study using FAERS or a similar pharmacovigilance database, especially when the article logic includes product selection, indication-group stratification, MedDRA-based adverse-event extraction, serious-case filtering, suspect-drug and concomitant-exclusion logic, reporting odds ratio analysis, comparator-drug benchmarking, cross-drug comparison, and cautious signal interpretation without causal overclaiming. Covers five study patterns (single-drug disproportionality workflow, multi-drug class comparison workflow, indication-stratified workflow, comparator-controlled signal screening workflow...

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