A process for writing a case study, a customer success story that explains a problem, the work done, and the measurable result. It uses the STAR structure: situation, task, action, and result.

Use it to create customer stories for a website, sales material, or professional networks. Gather customer details, results, interviews, and before-and-after evidence when available.

It helps turn customer interviews and evidence into a credible story without placing a large burden on the customer. Permission and pre-publication approval are part of the process.

case-study — Skill for Claude Code by komunite

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add komunite/kalfa --skill case-study

Clone the repo

git clone --depth 1 https://github.com/komunite/kalfa

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/komunite/kalfa/case-study/github.svg)](https://agentmods.dev/skills/komunite/kalfa/case-study)

Your own site

<a href="https://agentmods.dev/skills/komunite/kalfa/case-study"><img src="https://agentmods.dev/badge/skills/komunite/kalfa/case-study/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/komunite/kalfa/case-study"><img src="https://agentmods.dev/badge/skills/komunite/kalfa/case-study.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,391 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.02391
Opus 5	$0.00012	$0.01196
Sonnet 5	$0.00005	$0.00478
Haiku 4.5	$0.00002	$0.00239

Measured 9d ago against content hash 6b0bd44dc986, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

case-study scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/content/case-study/SKILL.md · 200 lines

How it starts

The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Müşteri Başarı Hikayesi (Case Study) Yazma Tarifi

Amaç

Potansiyel müşterilerin "Bu benim için de işe yarar mı?" sorusuna somut kanıtla yanıt veren bir case study üret. Solopreneur'lar için: müşteriyi yormadan, hızlı onay alarak, maksimum dağıtım değeri sağlayacak şekilde.

Kategori: İçerik ve Metin Yazarlığı

Girdiler

Zorunlu

Müşteri Bilgisi: İsim, şirket, sektör (izinli)
Sonuç Metrikleri: Ölçülebilir başarı (gelir artışı, zaman tasarrufu, dönüşüm oranı vb.)

İsteğe Bağlı

Müşteri Röportajı: Yapıldıysa notlar veya transkript
Öncesi/Sonrası Verileri: Ekran görüntüleri, dashboard'lar

Adım 1: Müşteriden İzin ve Malzeme Toplama

İzin Alma Şablonu (Kopyala-Yapıştır)

Merhaba [İsim],

Sizinle çalışmamızın harika sonuçlarını bir başarı hikayesi olarak
paylaşmak istiyorum. Bu sizi de öne çıkarır — sitenize/LinkedIn'inize
bağlantı veririm.

Gerekli olan: 15 dakikalık kısa bir görüşme (veya yazılı 5 soru).
Yayından önce onayınızı alırım, son söz sizde.

Uygun musunuz?

Kural: Müşterinin işini kolay tut. 15 dakikadan fazla isteme. Yazılı yanıt seçeneği sun. Yayın öncesi onay garantisi ver.

Adım 2: Müşteri Röportajı — 7 Kritik Soru

Bu sorular STAR (Situation → Task → Action → Result) formatının iskeletini oluşturur:

Situation (Durum)

"Bize ulaşmadan önce en büyük sorununuz neydi?" — Acı noktasını kendi ağzından al
"Bu sorunu çözmek için daha önce ne denediniz?" — Başarısız alternatifleri gösterir

Task (Görev)

"Bizden tam olarak ne bekliyordunuz? Başarı sizin için ne anlama geliyordu?" — Beklenti çerçevesini kurar

Action (Eylem)

"Birlikte çalışma sürecini nasıl tanımlarsınız?" — Süreç güvenilirliğini gösterir
"Hangi özellik/yaklaşım en çok fark yarattı?" — Differentiator'ını müşteriye söylet

Result (Sonuç)

"Somut olarak ne değişti? Rakam verebilir misiniz?" — %40 gelir artışı, 10 saat/hafta tasarruf gibi
"Bu ürünü/hizmeti kime tavsiye edersiniz ve neden?" — Doğal referans + hedef kitle tanımı

Read the full file on GitHub · 200 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 200 lines · 24 tokens per session scan A 6b0bd44dc986

Subscribe to this mod's changes

case-study is a skill published in the GitHub repository komunite/kalfa (244 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 2,391 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Claude Code Marketing and SEO Writing and docs business-operating-system skills turkish

claude-md-improver

Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…

anthropics/claude-plugins-official · 82 tokens

gke-workload-security

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…

google/skills · 181 tokens

case-study