case-study-plan

case-study-plan is a skill for Claude Code from indranilbanerjee/digital-marketing-pro. It costs 162 tokens per session (1,741 once invoked), scanned A, original, MIT.

A blueprint for creating a customer case study: a structured account of a customer's problem, the solution, and the results. It covers interviews, charts, formats such as PDF or web pages, and plans for sharing the finished story.

In plain words
What is it for?
Use it to plan customer interviews, choose evidence and visualisations, specify versions for sales and social media, and map out distribution.
Why use it?
It turns scattered project details and interview needs into one organised plan. It also prompts you to check whether the customer has approved using their name, data, and story.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

Part of the digital-marketing-pro plugin — 154 skills, 18 commands, 24 agents shipped together

Good fit Use it to plan customer interviews, choose evidence and visualisations, specify versions for sales and social media, and map out distribution.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/indranilbanerjee/digital-marketing-pro/case-study-plan
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 indranilbanerjee/digital-marketing-pro --skill case-study-plan
Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro

Made for: Claude Code.

Or install digital-marketing-pro, the plugin that ships this one along with the rest of its 154 skills, 18 commands, 24 agents.

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.

agentmods badge for case-study-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/case-study-plan/github.svg)](https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/case-study-plan)
Your own site
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/case-study-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/case-study-plan/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.

agentmods 80×15 button for case-study-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/case-study-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/case-study-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 162 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,741 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00162 $0.01741
Opus 5 $0.00081 $0.00870
Sonnet 5 $0.00032 $0.00348
Haiku 4.5 $0.00016 $0.00174

Measured 5d ago against content hash 021d7887d3b0, 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-plan 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 5d 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.

skills/case-study-plan/SKILL.md · 62 lines

How it starts

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

/digital-marketing-pro:case-study-plan

Purpose

Generate a structured case study creation plan with interview framework, data visualization approach, format variations, and distribution strategy. Produces a complete blueprint for building compelling proof-of-results content that drives sales enablement and builds credibility.

Input Required

The user must provide (or will be prompted for):

  • Client or project to feature: The specific client engagement, campaign, or project that will be showcased
  • Challenge or problem addressed: The business problem, market pressure, or growth obstacle the client was facing before the engagement
  • Solution implemented: The services, campaigns, strategies, or tools deployed to address the challenge
  • Results achieved: Quantitative outcomes (revenue lift, traffic growth, conversion improvement, cost reduction) and qualitative outcomes (brand perception, team capability, process improvement)
  • Timeline of engagement: Duration of the project or campaign — start date, key milestones, and current status
  • Permission status: Whether the client has approved public use of their name, data, and story — or if anonymization is required
  • Target audience for the case study: Who will read or watch it — prospects in the same industry, C-suite decision-makers, marketing managers, procurement teams, or general audience
  • Desired formats: Which output formats are needed — PDF white paper, website page, presentation deck, video testimonial, social media snippets, or sales one-pager
  • Industry vertical: The client's industry for contextual benchmarking and relevance targeting
  • Competitive context: What alternatives the client considered and why they chose this approach

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions and relevant category files. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
  2. Structure the CSR narrative: Build the Challenge-Solution-Results framework with sub-sections — situation overview, specific pain points, goals at project start, strategic approach, tactical execution, implementation timeline, quantitative results, qualitative impact, and future outlook. Identify the emotional arc that makes the story compelling, not just informative.
  3. Develop client interview questions: Create 15-20 interview questions organized by section — background and context (company size, industry pressures, previous attempts), challenge deep-dive (symptoms, root causes, business impact of inaction), solution experience (selection criteria, onboarding, collaboration quality), results and impact (measurable outcomes, unexpected benefits, team reaction), and forward-looking (ongoing plans, what they would tell peers).
  4. Plan internal team interview questions: Draft 10 questions for internal team members who worked on the engagement — strategic rationale, technical approach, challenges encountered during delivery, key turning points, and lessons learned that could inform future engagements.
  5. Identify data points and visualizations needed: Map every quantitative result to a visualization type — before/after bar charts, timeline growth curves, funnel improvement diagrams, ROI waterfall charts, and comparison tables. Specify which data needs to be collected, verified, and approved by the client before publication.
  6. Design format variations: Create specifications for each requested output format — PDF white paper (4-6 pages, designed layout with pull quotes and charts), web page (SEO-optimized with structured data markup), presentation deck (8-12 slides for sales meetings), video testimonial script (2-3 minute interview-based script outline), social media snippets (pull quotes, stat cards, carousel posts), and sales one-pager (front-and-back summary for leave-behinds).
  7. Create distribution strategy: Plan where and how the case study will be published and promoted — website case study library, sales enablement materials, email nurture sequences, social media campaigns, PR outreach, paid promotion, conference presentations, and partner co-marketing opportunities.
  8. Build approval workflow and permission checklist: Define the full approval process — internal review (legal, marketing, account team), client review (point of contact, legal, executive sign-off), data accuracy verification, quote approval, logo and brand usage permission, and timeline for each review stage.
  9. Write draft executive summary: Compose a 150-200 word executive summary that captures the full story arc — who the client is, what they faced, what was done, and what resulted. This summary serves as the foundation for all format variations and distribution copy.
  10. Plan visual assets needed: Specify all visual elements required — client logo (with usage permissions), data visualization charts, photography (team photos, office shots, product images), branded design templates, infographic elements, pull quote cards, and video b-roll if applicable.

Read the full file on GitHub · 62 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.

  1. 5d ago First seen · 62 lines · 162 tokens per session scan A 021d7887d3b0

Subscribe to this mod's changes

case-study-plan is a skill published in the GitHub repository indranilbanerjee/digital-marketing-pro (814 stars, last pushed 5d ago), licensed MIT. It adds 162 tokens to every session and 1,741 once invoked, about $0.0008 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-07.

Related

Other skills, from other repositories

cf-brief

Generate a research-backed content brief from a keyword or topic — keyword data with volume and difficulty, top-5 competitor and E-E-A-T analysis, search-intent classification, audience pain points, a section-by-section outline with word counts and citation targets, plus SEO and AEO/GEO strategy (AI Overview status…

indranilbanerjee/contentforge · 169 tokens

cf-style-guide

Import a brand voice profile from an existing style guide — a .docx/.pdf document, a URL, or manual input — extracting tone, formality, personality, approved/banned terminology, compliance guardrails, and author profiles into a structured brand-profile JSON at /.claude-marketing/{brand-slug}/Brand-Guidelines/, then…

indranilbanerjee/contentforge · 178 tokens

marketing-expert

Build comprehensive marketing technology solutions including automation workflows, campaign management, analytics tracking, and multi-channel orchestration. Use when the user mentions marketing automation, campaign management, SEO, email or content marketing, attribution, or multi-channel orchestration.

personamanagmentlayer/pcl · 51 tokens

cf-publish

Execute CMS publishing: push a finished, reviewed piece (Phase 8 complete, quality score >=7.0) to Webflow or WordPress via MCP connectors as draft, scheduled, or live — always showing a full publish preview and waiting for your explicit yes/no/edit confirmation before anything is pushed. Runs the EU AI Act Article 50…

indranilbanerjee/contentforge · 168 tokens

cf-template

Create and manage custom content-type templates beyond the 8 built-ins (article, blog, whitepaper, faq, research-paper, video-script, case-study, newsletter) — defining section structure, word-count allocations, readability targets, citation minimums, and quality standards, then validating the template against every…

indranilbanerjee/contentforge · 160 tokens

cf-variants

Generate 3-10 scored A/B test variations of a single content element — headline, hook, CTA, intro, or conclusion — each rated across 6 quality dimensions and ranked by your optimization goal (clicks, engagement, conversions, or readability), with top-3 recommendations and A/B test setup guidance (sample size…

indranilbanerjee/contentforge · 162 tokens