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

analyst-relations-brief

Prepare for an industry analyst briefing (Gartner, Forrester, IDC and similar). Use when asked to prep an analyst briefing, write an AR briefing document, build talking points for an analyst call, or prepare a Magic Quadrant / Wave submission narrative. Produces a briefing kit — objective, company/product narrative, differentiation, proof points, the demo storyline, anticipated questions, and follow-up commitments.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.2 KB

SKILL.md(原文)

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

Analyst Relations Brief Skill

Prepare a crisp, credible analyst briefing that lands the company's narrative and positions it well for evaluations. Analysts reward clear differentiation backed by evidence — not marketing gloss.

What This Skill Produces

  • A briefing objective and the one message to land
  • A tight company + product narrative and market framing
  • Differentiation and proof points an analyst can verify
  • A demo storyline mapped to the analyst's evaluation criteria
  • Anticipated tough questions with honest answers, plus follow-ups

Required Inputs

Ask for these if not provided:

  • The analyst / firm and their coverage area, plus any evaluation (Magic Quadrant, Wave, MarketScape) in play
  • Objective — inclusion in an evaluation, repositioning, launch awareness, feedback
  • Company & product basics — what it does, who it's for, traction
  • Differentiation and the proof (customers, metrics, architecture)
  • Roadmap themes you can share (and what's confidential)
  • Known analyst views or prior feedback, if any

Never fabricate metrics, customers, or roadmap dates — mark [to confirm] and flag anything under NDA.

Process

  1. Set the objective — what a good outcome looks like and the single message to land.
  2. Frame the market — the category, the shift, and where you play; align to the analyst's taxonomy.
  3. Tell the narrative — problem, approach, why now, why you.
  4. Prove it — evidence that survives scrutiny; concede limits honestly.
  5. Map the demo to the analyst's criteria — show, don't tell.
  6. Pre-empt hard questions — pricing, scale, competition, gaps; prepare honest answers.
  7. Plan follow-up — what you'll send, by when, and how you'll track the relationship.

Output Format


Analyst Briefing Kit — [Firm / Analyst]

Date: [date] · Objective: [outcome] · Evaluation in play: [MQ / Wave / none]

The One Message

[The single thing the analyst should remember.]

Market Framing

[The category shift and where you fit, in the analyst's language.]

Company & Product Narrative

  • What we do: [one line] · For: [ICP]
  • Why now: [market shift] · Traction: [customers / growth — or [to confirm]]

Differentiation & Proof

DifferentiatorWhy it mattersProof (verifiable)
[Point][analyst-relevant value][customer / metric / architecture]

Demo Storyline (mapped to evaluation criteria)

  1. [Criterion] → [what we show]
  2. [Criterion] → [what we show]

Anticipated Questions

Likely questionHonest answerWhere we're weak (and the plan)
[Question][answer][gap + roadmap theme]

Roadmap Themes to Share

  • [Theme] — [shareable direction] · [confidential: yes/no]

Follow-Ups

  • [Deliverable] — [owner] — [by when]

Quality Checks

  • The one message is explicit and repeated in the narrative
  • Differentiators map to the analyst's evaluation criteria
  • Every proof point is verifiable, or marked [to confirm]
  • Weak spots are acknowledged with a credible plan, not hidden
  • Confidential/NDA items are clearly flagged
  • Follow-ups have owners and dates

Anti-Patterns

  • Do not use marketing superlatives an analyst will discount
  • Do not dodge gaps — analysts probe them; own them with a plan
  • Do not invent metrics, logos, or roadmap dates
  • Do not ignore the analyst's taxonomy and force your own category
  • Do not overload the demo; map it to what's being evaluated

Example Trigger Phrases

  • "Prep me for a Gartner briefing next week"
  • "Write an analyst briefing document for our platform"
  • "Build talking points and anticipated questions for a Forrester Wave call"
  • "Prepare our narrative for a Magic Quadrant submission"

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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 のスキルをすべて見る

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