返回 Skill 列表
extension
分类: 营销与增长无需 API Key

competitors

识别给定市场(例如人力资源软件)中的新竞争对手和最近的功能发布,并提供证据、影响分析和可操作的战略响应。当用户要求竞争对手情报、市场动态或功能发布跟踪时使用。

person作者: jakexiaohubgithub

Competitors Skill

Identify new competitors and recent feature releases from existing competitors in a target market, with evidence, impact analysis, and actionable responses.

Scope

  • Identify 2–3 new competitors (startups or established players entering new segments).
  • Identify 2–3 feature releases or updates from existing competitors.
  • Focus on solutions relevant to the user’s segment (e.g. HR Directors and Talent Ops for HR software).
  • Default window: last 7 days unless the user specifies otherwise.

Evidence

  • Source from reputable outlets (e.g. TechCrunch, Gartner, SHRM, Capterra) or recent social posts with inline citations.
  • Mark speculation as (opinion).
  • Include quantitative data (e.g. “X% market share growth”) or qualitative insights where available.
  • If data is sparse, note limitations and ask for clarification.

Depth (per finding)

  • What – the company or feature.
  • Why – its market significance.
  • Impact – effect on competition or customer expectations.
  • Use first-principles reasoning and link to market trends (e.g. AI adoption, hybrid work).

Actionable insights

For each finding, propose one strategic response relevant to the user’s context. Quantify benefits where possible (e.g. “10% faster onboarding”). Include one short-term next step and resource estimate (e.g. “enhance API for analytics, 2 developer weeks”).

Forward projection

  • One tech-debt or execution risk.
  • One future opportunity (e.g. niche differentiation).

360° evaluation

Assess impact on: code (e.g. platform scalability), UX (e.g. adoption), GTM (e.g. positioning), culture (e.g. trust in tools).

Format

  • Concise report with 4–6 findings (mix of new competitors and feature releases).
  • Bullet points for clarity.
  • Close with one reflection question for continuous improvement.

Constraints

  • Avoid jargon; prioritize radical clarity.
  • Verify data via web or search when possible.
  • If insufficient data exists for the requested window, note the gap and ask for clarification before proceeding.