無料GitHub で公開

case-study-writer

Use this skill when you need a B2B customer case study or success story that sales can use: "write a case study", "turn this customer interview into a story", "customer success story for our website", "one-pager for sales". Plans the interview, structures the story (before, trigger, decision, rollout, results, what's next), writes it with real numbers and quotes, and produces versions for the website, a sales one-pager, a cold email paragraph and a LinkedIn post. Every claim is approved by the customer.

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

prosyo-ai/gtm-skillスター 11(GitHub 11 + cccskills 0)

連携ツールLinkedIn

実行スコア未検証

インストール方法を見る

含まれるファイル（1）

SKILL.md3.5 KB

SKILL.md（原文）

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

Use this when a customer has a result worth sharing. The best case studies read like a story a peer would tell, with the buyer's doubts left in.

Inputs

Interview transcript or notes with the customer (or run the guide below).
Results data: before and after numbers, time frames.
What the customer has approved for publication: name, logo, quotes, numbers.

The play

1. Interview for the story, not the praise

Ask:

What was happening before? What did it cost you?
What made you look for a change then?
What else did you consider? What almost stopped you?
How did the rollout actually go, including the bumps?
What changed, in numbers, and how do you measure it?
What would you tell a peer considering it?

2. Structure it

Headline: the result, with the number. "How Northwind filled 15% more chairs in 90 days."
Snapshot: company, size, use case, top 3 results.
Before: the situation and its cost, in their words.
Trigger and decision: why now, what they compared, why they chose.
Rollout: what it took, honestly.
Results: numbers with time frames and how they were measured.
What's next.

3. Use quotes well

Two to four quotes, each doing a job: the pain, the decision, the result. Edit for length, never for meaning, and get approval on the final wording.

4. Make the versions

Website: 600-900 words with the structure above.
Sales one-pager: snapshot, before and after, three results, one quote.
Cold email paragraph: one sentence of before, one of after.
LinkedIn post: the story in 150 words with the turning point.

What good looks like

The headline number is specific, time-bound and approved.
The "before" is vivid enough that a prospect recognises themselves.
Doubts and bumps are included; they make the result credible.
The common mistake is a page of praise ("They're a great partner!") with no numbers and no story.

Rules

MUST get customer approval for name, quotes and numbers before publishing.
MUST state how and over what period results were measured.
NEVER round up results or combine customers into one story.
NEVER publish an anonymised story with details that identify the customer anyway.

Example prompts

"Turn this interview transcript with Northwind into a case study and a one-pager."
"Write interview questions for a customer who cut onboarding time by half."
"Make a cold email paragraph and a LinkedIn post from our Contoso case study."

レビュー

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

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

同じリポジトリのスキル

abm-account-plan

無料

Use this skill when you run account-based marketing or sales on a short list of named accounts: "build an ABM plan", "account plan for our top 20", "how do we break into this enterprise account", "1:1 ABM program". Picks the accounts and the ABM tier (1:1, 1:few, 1:many), maps the buying group, writes the account insight and value hypothesis, plans coordinated sales and marketing plays by stage, and sets the metrics (engagement, meetings, pipeline) that show it is working.

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