'gap-analysis' 검색 결과

分析竞品账号的内容策略，拆解选题、格式、爆款规律和互动模式，输出差异化机会与行动建议。 当用户说"分析竞品""竞品账号""对标账号""拆解爆款""竞品在做什么""对手内容策略""竞争分析"时使用。 和 skill-content-gap-analysis 的区别：本 SKILL 拆解具体竞品账号的内容策略与爆款规律； content-gap-analysis 从赛道整体供需找"没人做好"的蓝海选题空白。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyse student work against criteria to identify specific gaps between current performance and learning objectives. Use when reviewing submissions, planning feedback, or diagnosing learning needs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides conducting privacy law gap analysis for market entry into new jurisdictions. Covers target jurisdiction assessment, existing compliance mapping, remediation effort estimation, and implementation timeline planning. Keywords: gap analysis, market entry, jurisdiction assessment, remediation planning, compliance mapping.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides systematic assessment of current state versus GDPR requirements across all chapters with prioritised remediation matrix. Activate when starting compliance programmes or conducting periodic reassessment. Keywords: gap analysis, compliance assessment, remediation matrix, GDPR readiness.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyse student work against criteria to identify specific gaps between current performance and learning objectives. Use when reviewing submissions, planning feedback, or diagnosing learning needs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Eliciting, documenting and structuring requirements for a Salesforce implementation: stakeholder discovery interviews, As-Is and To-Be process mapping, and gap analysis against standard Salesforce capability. Trigger keywords: requirements gathering, user story, As-Is To-Be, gap analysis, stakeholder interview, process mapping, business requirements, fit gap. NOT for authoring the user stories themselves - use admin/user-story-writing-for-salesforce. NOT for scoring requirements against a specific org - use admin/fit-gap-analysis-against-org. NOT for technical design decisions - use architect/solution-design-patterns. Also covers the requirements catalogue itself (one row per requirement, MoSCoW priority, source stakeholder, downstream target) and Salesforce non-functional requirements: record volume, sharing layer, integration pattern, reporting joins, mobile/offline, and licence implication.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when scoring a list of business or solution requirements against the *actual* capabilities of a specific Salesforce org so each row can be classified Standard / Configuration / Low-Code / Custom / Unfit, given an effort tier (S/M/L/XL), a risk tag, and an AppExchange suggestion when applicable. Trigger keywords: fit gap salesforce requirements, score requirements against salesforce capabilities, salesforce capability matrix, classify requirement as standard config custom, fit-gap effort tier, AppExchange alternative for requirement. NOT for requirements elicitation (use admin/requirements-gathering-for-sf). NOT for architecture decisions on the GAP rows (use architect/solution-design-patterns and standards/decision-trees/). NOT for license or edition selection (use architect/license-optimization-strategy and architect/org-edition-and-feature-licensing). NOT for OmniStudio-specific fit-gap (use architect/omnistudio-vs-standard-decision).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Compare new or changed privacy regulations with current policies and practices. Identify whether the rules apply, list missing requirements, and produce a prioritized remediation plan with owners and due dates, documenting compliant areas as well.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess whether a new privacy law applies to the company
• Identify gaps between regulatory guidance and current practices
• Plan corrective actions with owners and deadlines

Compare AI regulations or guidance with existing company policies and practices. Determine applicability, identify missing requirements, and create a prioritized remediation plan with owners and deadlines, while highlighting legal uncertainties that need attorney judgment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether a new AI regulation applies to the company
• Comparing EU AI Act requirements with current practices
• Assigning owners and deadlines to compliance gaps

Assess whether tests detect the wrong behavior relevant to a specific change, PR, or commit. Link findings to exact revisions, compare faulty and correct behavior when execution is authorized, and distinguish observed results from predictions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether a regression test detects the original bug
• Assess tests for a new feature
• Review behavior preservation during a refactor

Interpret .NET coverage reports, which show code exercised by tests, to explain missing coverage and stalled progress. Calculate the gains needed to reach a target and, when requested, combine coverage with complexity to rank risk.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explain Cobertura reports and partially covered conditions
• Find the code keeping coverage from improving
• Calculate line gains needed to reach a coverage target

Find changes in observable behavior that existing tests could miss. Map public results to test assertions, identify gaps in boundaries, permissions, and calculations, and propose focused tests, with optional verification when requested.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether existing tests would catch a bug
• Find missing boundary and permission-denial tests
• Review exact amounts and rounding in financial calculations

Review test files or suites for missing checks, hidden exceptions, unreliable timing, shared state, and maintenance problems. Get a severity-ranked report with specific locations, explanations, and concrete suggestions for improving the tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing whether existing tests meaningfully check results
• Investigating timing and execution-order risks in tests
• Prioritizing test improvements before editing code

Review existing tests to see whether their assertions, the checks that verify expected behavior, are meaningful and varied. Get metrics, examples of weak checks, and specific recommendations for improving verification.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing whether passing tests check meaningful behavior
• Finding tests with missing or trivial assertions
• Measuring the variety of checks across a test suite

Classify existing tests with standard tags for success cases, errors, boundaries, and other behaviors. Get a per-test mapping and distribution summary, or apply tags using supported framework syntax and verify compilation and test discovery.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing success-case and error-case test counts
• Adding standard tags to existing tests
• Reviewing the mix of boundary and integration tests

Calculate change risk for a specific .NET method, class, or file by combining code complexity with measured test coverage. Get ranked results and recommendations on where to add tests or simplify logic.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Calculate risk scores for a specific method
• Prioritize tests within a class
• Find complex, undertested methods in a file

Provide language-specific reference files for test analysis skills. The catalog helps agents recognize test methods, assertions, skipped tests, waiting patterns, setup and cleanup hooks, external dependencies, and tagging capabilities across different frameworks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Looking up assertion syntax for a test framework
• Checking skip annotations and setup or cleanup hooks
• Supporting test analysis across multiple languages

分析社媒赛道的内容空白，发现高需求低竞争的蓝海选题机会。 当用户说"蓝海选题""内容空白""没人做的选题""选题机会""高需求低竞争""差异化选题""内容缺口"时使用。 和 skill-competitor-analysis 的区别：本 SKILL 从赛道供需交叉验证找蓝海选题空白； competitor-analysis 拆解具体竞品账号的内容策略。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "build programmatic SEO pages", "generate pages at scale", "rank on a high-authority third-party site", "borrow domain authority", "build a vs / alternative page", "do local SEO", "optimize a Google Business Profile", or "fix NAP" — one page-build router with four modes: programmatic (template × dataset systems), parasite (barnacle publishing on Medium/Reddit/LinkedIn/GitHub), comparison (vs / alternative pages in four formats), and local (GBP + NAP + citations + location pages), each with its own thin/duplicate, honesty, or reputation-abuse guardrail. Not for finding what to target — use keyword-research or content-gap-analysis; not for drafting one standalone article — use content-writer; not for scoring a page for publish — use content-quality-auditor. 程序化SEO/批量页面/寄生SEO/借势权重/对比页/vs页/替代页/本地SEO/谷歌商家档案/NAP一致性

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "find keywords", "挖词", or "搜什么词"; prioritizes search volume, keyword difficulty, intent, and topic clusters from provided or connected data. Not for competitor-relative coverage gaps — use content-gap-analysis. 关键词研究/内容选题

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "analyze competitors" or "竞品分析"; benchmarks competitor keywords, content, backlinks, AI citations, and traffic share into strengths, weaknesses, and an action plan. Not for a pairwise topic-coverage gap map — use content-gap-analysis. 竞品分析/竞争对手

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "find content gaps", "竞品写了什么", or "还应该写什么"; builds a competitor-relative coverage map of missing topics, keyword gaps, and editorial-calendar opportunities. Not for raw keyword demand discovery — use keyword-research. 内容缺口/选题规划

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Map an organisation's risks against its insurance policy portfolio to find what's uncovered, underinsured, or double-covered. Use when asked to run a coverage gap analysis, review an insurance programme against a risk register, check what risks aren't insured, or audit a policy portfolio. Produces a risk-by-coverage matrix, flagged gaps and overlaps, a deductible stack review, and recommendations ranked by expected-loss severity.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identify underserved market gaps and unmet customer needs in e-commerce. Analyzes competitor blind spots, review pain points, search demand without adequate supply, and emerging customer segments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.