2.2천건 · 관련도순
Compare competing plans from AI agents against the actual task and available evidence. Choose one, combine useful parts, or request revisions, then produce a single execution handoff with ordered steps, verification checks, and reasons for rejected alternatives.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare competitors’ public social profiles and posts to identify strong topics, formats, and posting patterns. Get an evidence-based brief with content gaps and suggested experiments, accounting for each account’s usual performance.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compare estimated AI model costs for a task using its complexity and expected text volume. Get a suitable low-cost recommendation, a cheaper but riskier alternative, and a premium option, with explicit assumptions behind the estimates.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
[omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics. Use when the user says: agent-evaluation, agent evaluation, agent eval, agent benchmark, executor evaluation, executor benchmark, compare agents, compare codex claude.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Forecast Azure spend and price planned resources or workloads. WHEN: "forecast Azure spending", "project next month cost", "compare forecast to my planning target", "how much will Azure cost", "estimate VM cost", "compare storage tiers", "compare Azure regions", "retail price", "EA rate card", "negotiated pricesheet". DO NOT USE FOR: configured budget health or alerts, bill analysis, cost spikes, rightsizing, or commitments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit external compatibility between two DSH (DeepSeek Harness) versions and detect reverts, producing an upgrade-report directory; compares git tags with a source checkout, or published npm packages without one. Use whenever the user asks to check/compare/audit two DSH versions or whether upgrading is safe — e.g. "more changes or reverts in dsh-vX -> dsh-vY", "compare the breaking changes" — even with only two version numbers and no source location. Read-only outside the report directory; npm mode installs in isolation with --ignore-scripts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Forecast Azure spend and price planned resources or workloads. WHEN: "forecast Azure spending", "project next month cost", "compare forecast to my planning target", "how much will Azure cost", "estimate VM cost", "compare storage tiers", "compare Azure regions", "retail price", "EA rate card", "negotiated pricesheet". DO NOT USE FOR: configured budget health or alerts, bill analysis, cost spikes, rightsizing, or commitments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when asked to compare two annual reports, put two companies from the same sector side by side, or check whether two companies' adjusted numbers mean the same thing. Takes two uploaded annual reports from one sector and compares them on five ratios computed with identical definitions from audited figures, flagging every place the companies define a metric differently. Produces a page-referenced comparison table, a definitions-differ section (adjusted vs statutory, inside vs outside the audited statements), and three questions to ask before believing either company's highlights. Educational, not financial advice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare UX patterns across multiple reference apps using pattern libraries produced by ux-extract. Reads 2+ pattern-library.md files, walks them category by category, identifies where apps converge (strong signal), where they diverge (genuine design choice), what's unique to one app, and what's absent across the set. Produces an opinionated comparison document with recommendations for a new build. No browser needed — pure markdown analysis. Trigger with 'compare UX patterns', 'how do top apps handle X', 'ux comparison', 'pattern comparison across reference apps'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare several Japanese NLP libraries, models, or datasets for a keyword (a specific tool name, or a function/task like '形態素解析') across a handful of criteria chosen for that comparison, rendered as a ○/△/✕ table. Use when the user wants a side-by-side comparison of multiple Japanese NLP tools/libraries/datasets, not just the single best one. Trigger phrases include 'X と Y と Z を比較して', '形態素解析ライブラリを比較', 'MeCab と Sudachi どっちがいい', 'どのツールを使うべき', 'compare japanese tokenizers', 'mecab vs sudachi vs janome', 'which embedding model should I use', '日本語NERライブラリの比較表', 'pros and cons of japanese OCR tools'. For a single ranked list use search; for alternatives to one specific tool (or contribution candidates) without a multi-axis table, use discover.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze website traffic, global rank, engagement metrics, and traffic sources for any domain. Use this skill to evaluate affiliate program websites, compare competitor traffic, assess advertiser strength, or understand where an audience comes from. Triggers on: "analyze traffic for [domain]", "how much traffic does [site] get", "compare traffic between [site A] and [site B]", "is [program] worth promoting based on traffic", "traffic analysis", "website analytics for [domain]", "where does [site] get traffic", "check if [advertiser] is legit", "evaluate [program] website health", "SimilarWeb analysis", "traffic sources for [domain]", "how popular is [site]", "website rank", "domain authority check", "compare affiliate program websites".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Offer 对比决策器。用户同时拿到两份（或多份）offer 纠结怎么选时，扮演 Senior Career Decision Advisor：结构化对比 comp / 成长 / AI 敞口 / 公司强度 / 团队风险 / 晋升速度 / 生活方式，识别 front-loaded vs long-term upside、resume value、switch-out 难度、hidden risks，最后给一条**明确、有立场、不中性**的推荐（并附「你是 X 类人选 A，你是 Y 类人选 B」的分叉判定）。三步：贴两份 offer → 补 priorities & 现状 → 自动生成并打开一份 HTML Offer Decision Report。是 offer-toolkit 里 JD Skill / Resume Skill / BQ Skill 拿到结果之后的下一环。关键词：offer compare, 选 offer, 两个 offer, offer decision, TC compare, 该去哪家, which offer, 4-year TC, RSU, sign-on, front-loaded, long-term upside, career decision。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare behavior across multiple versions of programs or repositories. Use when you need to analyze how functionality changes between versions, identify regressions, compare outputs and exceptions, or validate upgrades. The skill compares execution behavior, test results, outputs, exceptions, and observable states across versions, generating detailed reports showing behavioral divergences, potential regressions, added/removed functionality, and areas requiring validation. Supports multiple programming languages and can work with test suites or execution traces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Side-by-Side Property Comparison — takes two addresses and compares across price, specs, rental income, neighborhood, and investment potential with a winner per category and overall recommendation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish baseline → snapshot → compare → history monitoring for any KPI, config, or metric that can drift during PRD v0.8 Deployment & Ops. Triggers on requests to monitor drift, baseline a value for later comparison, or when user asks "how do we track if X changes?", "baseline this", "config drift", "performance regression", "metric drift", "compare to last week", "is this getting worse?". Outputs MON-DRIFT-* entries with baseline + comparison rules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare two images pixel-by-pixel and get a visual diff. Use when the user wants to compare their implementation against a design, spot differences between two screenshots, or verify visual regression.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Side-by-side comparison of two financial scenarios (buy vs rent, new job vs stay, payoff house vs invest, Roth vs Traditional, lease vs buy car, etc). Projects each scenario over 10 years, compares total cost, opportunity cost, risk profile, and produces a structured recommendation. Output saved as FINANCE-COMPARE.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Jurisdiction comparison for a legal requirement or contract clause. Use when asked "how does this differ by jurisdiction", "compare GDPR and CCPA on this", or "run a state law comparison".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Head-to-Head Stock Comparison — compares two stocks across valuation, growth, profitability, financial health, technical setup, sentiment, and risk with category winners and a weighted overall score. Triggered by "trade compare <TICKER1> <TICKER2>".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ascend cluster comparison tool. Invoke when user asks to compare two cluster datasets (DB or TEXT), or to generate cluster_analysis_output from raw profiling data via msprof-analyze and then compare.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Monthly delta tracking and progress reporting for GEO clients. Compares two GEO audits (baseline vs. current), calculates score improvements across all categories, tracks action item completion, and generates a "here's your progress" client report. Use when user says "compare", "delta", "monthly report", "progress", "confronta", "progressi", "report mensile", or when running a monthly client check-in.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare your data to a partner's data in the marketplace. Given a dataset you already own with person/edge data, this skill walks you through picking a partner data source to match against, choosing which identifier types to match on, optionally selecting which enrichment attributes to attach, and then submits the report — returning overlap, match counts, and demographic coverage. Use when: "how does my data compare to your marketplace", "compare my data to [partner]", "how much overlap do I have with [supplier]", "run a match report", "match my customers against 3P data", "see what enrichment is available for my dataset", or any open-ended question about marketplace overlap. (narrative-identity)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to send the same prompt to several LLMs and compare the answers - sequentially (stopwatch, clean per-lane timing) or in parallel (true race), with optional repetitions per model, judged by the starting model across quality, correctness, completeness, instruction fidelity and latency (time is only one dimension). Triggers on /compare-race, 'model race', 'vergleiche modelle', 'gleicher prompt an mehrere modelle'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cross-model benchmark for gstack skills. Runs the same prompt through Claude, GPT (via Codex CLI), and Gemini side-by-side — compares latency, tokens, cost, and optionally quality via LLM judge. Answers "which model is actually best for this skill?" with data instead of vibes. Separate from /benchmark, which measures web page performance. Use when: "benchmark models", "compare models", "which model is best for X", "cross-model comparison", "model shootout". (gstack) Voice triggers (speech-to-text aliases): "compare models", "model shootout", "which model is best".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.