'competitors' 검색 결과

Competitive positioning diagnostic — figures out where you actually stand relative to competitors and whether that position is defensible. Use this skill when someone needs to understand their real competitive position (not the one on the slide deck), when a new competitor has entered the market, when customers are switching and nobody can explain why, when pricing power is eroding, when a strategic investment depends on knowing whether the moat is real, or when leadership says "we're differentiated" but can't explain how. Draws on Playing to Win, Porter's generic strategies, and Blue Ocean thinking — applied as diagnosis, not planning. Based on practice by Eterdis (eterdis.com).

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

Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging. Use when starting work with a new brand or customer.

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

Use when screenshots, websites, moodboards, competitors, or visual examples are provided and the task needs design DNA extraction, comparison, remixing, or translation into an original design direction.

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

Perform comprehensive, multi-source research on any topic using AI-powered web search and analysis. Covers deep_research for broad discovery and semantic_content_search for site-specific knowledge retrieval. Use when you need to research brands, markets, competitors, or trends with citations — before creating content, planning campaigns, or making strategic decisions.

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

Use when the user asks to "track our share of voice", "what share of the conversation do we own vs competitors", or "trend our SOV this quarter"; computes SOV% = brand mentions ÷ (brand + competitor panel mentions) per platform per period on a LOCKED competitor panel — a panel switch invalidates the trend (restart the series and log the break; the ECHO O3 rule) — plus a sentiment-weighted SOV variant (sentiment labeled Estimated unless human-coded) and a Wikipedia-pageviews attention-share alternative; built from keyless listening connectors, gdelt.py news echo, and user exports — public counts only, closed platforms are never scraped. Not for backlink or offsite SEO signals — use offsite-signal-analyzer. 声量份额/竞品声量对比/提及份额/注意力份额

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

Analyze SE Ranking organic and AI-visibility data when an authorized connector is available. Use for rankings, competitors, backlinks, SERP features, and cross-platform AI share-of-voice evidence.

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

Compatibility skill for seo competitor pages. Use when a user or upstream workflow invokes this name; route the task to `competitors` while preserving the requested scope and source-specific intent.

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

Build or update the shared product-marketing context: product, audience, positioning, competitors, jobs-to-be-done, objections, customer language, proof and goals. Use before downstream execution when context is missing.

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

Compatibility skill for competitor alternatives. Use when a user or upstream workflow invokes this name; route the task to `competitors` while preserving the requested scope and source-specific intent.

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

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.

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

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 "map the category narrative", "tear down how competitors tell their story", or "find the language conventions in our market"; produces a category narrative map — the dominant stories and points of view in the category, its language conventions and framing clichés, and a per-competitor narrative teardown (arc, claimed onlyness, proof pattern) plus how each rival's messaging has shifted over time (scraped copy vs archived copy). Not for the positioning canvas itself — use positioning-mapper; not for the beachhead's beliefs and objections — use audience-belief-mapper; not for SERP keyword targeting — use keyword-research; not for claim adjudication — use offer-claims-registry. 品类叙事/竞争叙事拆解/语言惯例/叙事演变

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

This skill should be used when the user asks to \\\"analyze competitors", "assess competitive landscape", "identify differentiation", "evaluate market positioning", "apply Porter's Five Forces",...

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

Reverse-engineer why a design decision was made. Move from observation to inference. Use when studying products you admire, learning from competitors, or building analytical design thinking.

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

When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. Use when the user mentions "competitor monitoring", "track competitors", "competitor alert", "competitor changed their title", "watch a competitor app", "competitor weekly report", "competitive intelligence", or "what changed in competitor's listing". For a one-time deep competitive analysis, see competitor-analysis. For market-wide chart movements, see market-movers.

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

Comprehensive backlink analysis using DataForSEO API. Analyze backlink profiles, find link building opportunities, detect toxic links, compare with competitors, and identify link gaps. Use when user says "backlinks", "link building", "referring domains", "link profile", "toxic links", "link gap", "competitor links", or "domain authority".

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

Deep web research skill using Firecrawl MCP. Use when estimating market size (TAM/SAM/SOM), analyzing trends, or scraping competitors. For competitor teardowns, see competitor-analysis.

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

Generates and maintains competitive battlecards from win/loss data, competitor intel, G2 reviews, and sales feedback. Use when building battlecards for a specific competitor, updating existing battlecards with new intel, preparing BDRs or AEs for competitive deals, analyzing win/loss patterns against a competitor, or responding to a competitor's product launch or pricing change. Also use when asked to "build a battlecard," "update competitive intel," "how do we beat [competitor]," "what do we say when a prospect mentions [competitor]," or "analyze our win/loss against [competitor]." Designed for B2B SaaS teams selling against known competitors in deals with multi-persona buying committees.

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

Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.

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

Research customer pain points, trends, and competitors through the OMA market engine. Use for market discovery or voice-of-customer analysis.

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

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.

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

Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".

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

Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.

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

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".

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