本文へ移動
cccskills
無料GitHub で公開

competitive-intelligence-monitor

Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/medium/low priority signals, roadmap implications, and a strategic landscape summary. For a single competitor announcement use competitor-signal-tracker; for a one-off deep dive use competitor-teardown.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Competitive Intelligence Monitor Skill

Turn scattered competitor updates into structured weekly intelligence — not just "what they did" but "what changed since last week and what it means for us."

Required Inputs

Work from what is given. If any of these is missing, still produce the complete output: fill each gap with a reasonable assumption marked (assumed, confirm) and list those assumptions at the end. Ask a question first only when the core subject itself is missing (there is nothing to write about).

  • Competitors to monitor (list of company names)
  • Your current roadmap or strategic priorities (to assess relevance of signals)
  • Previous brief or last run summary (for diff mode — what's new vs. last time)
  • Time period (this week, this month)

Signal Categories to Monitor

  • Product signals: New features, removals, UX changes, beta programmes
  • Pricing signals: Changes to tiers, free limits, enterprise terms
  • Hiring signals: Job postings revealing strategic bets
  • Partnership signals: Integrations, acquisitions, ecosystem moves
  • Messaging signals: Changes in positioning, audience, value proposition

Process

First Run (Full Report)

  1. For each competitor provided, scan all five signal categories
  2. Categorise each signal found
  3. Assess: reactive (responding to market) or proactive (setting direction)?
  4. Rate threat level: High / Medium / Low / Watch
  5. Connect each signal to a specific item on the provided roadmap
  6. Recommend response: Accelerate / Deprioritise / Monitor / Investigate
  7. Validate — Every High signal must have a specific recommended action and owner. "Monitor" is only acceptable for Low and Watch ratings.

Subsequent Runs (Diff Only)

  1. Compare current signals against previous run summary
  2. Output ONLY what is new or changed since last run
  3. Flag if a previously Low signal has escalated to High
  4. Keep output under 300 words — brevity is the point

Output Structure

Competitive Intelligence Brief — [Date]

New Since Last Run: [n signals]

🔴 High Priority

[Competitor]: [Signal] → [Implication] → [Recommended action + owner]

🟡 Watch

[Competitor]: [Signal] → [Why it matters now]

✅ No Change

[Competitors with no new signals this week]

This Week's Strategic Summary: [2 sentences max — what is the overall competitive landscape doing?]

Anti-Patterns

  • Do not mark a signal as Low priority simply because it is new and unfamiliar — unknown competitive moves often deserve investigation before dismissal
  • Do not provide "monitor" as the recommended response for a High-priority signal — High signals require a specific action with a named owner
  • Do not include signals from competitors that are not relevant to the stated roadmap or strategic priorities — noise reduces the brief's usefulness and trains the team to ignore it
  • Do not produce a diff-mode brief that is longer than the full report — if the diff output exceeds 300 words, it is a full report, not a diff

Quality Checks

  • Every High-priority signal has a specific response action and owner
  • Signals are categorised (not just listed as "they did X")
  • Roadmap connections are specific (not "generally relevant")
  • Diff mode output is under 300 words
  • Strategic summary describes the landscape trend, not just repeats individual signals

Example Trigger Phrases

  • "Monitor competitors."
  • "Track the competitive landscape."
  • "Produce a competitive briefing."
  • "Understand what has changed in the market this week."

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

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

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する