Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

case-study-writer案例研究作家

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

945

周安装

39

GitHub Stars

37

下载量

309
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:case-study-writer(案例研究作家)
来源仓库:https://github.com/majesticlabs-dev/majestic-marketplace
仓库路径:skills/case-study-writer
安装命令:
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill case-study-writer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill case-study-writer

简介

用于辅助测试设计、自动化测试、用例整理和回归验证。

  • 适合编写单元测试、端到端测试、测试计划或根据失败日志定位问题。
  • 使用时需确认项目测试框架、运行命令和夹具数据。
  • 涉及浏览器或外部服务时应区分本地模拟、测试环境与生产环境。
  • case-study-writer 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Customer Case Study Writer

Create compelling case studies that showcase customer success stories for marketing and sales enablement.

Information Gathering

Use AskUserQuestion to collect the following from the user:

Customer Details

  1. Company name and permission to use it (or anonymize?)
  2. Industry and company size
  3. Role of the person you worked with (decision maker, user, champion)

The Story

  1. What problem were they trying to solve? (Be specific - pain points, failed alternatives)
  2. Why did they choose your solution? (What made you stand out?)
  3. How did implementation go? (Timeline, challenges, support needed)
  4. What results did they achieve? (Metrics, quotes, before/after)

Supporting Evidence

  1. Do you have a customer quote? (Direct testimonial is gold)
  2. What metrics can you share? (%, $, time saved, etc.)
  3. Any surprising or unexpected benefits?

Case Study Structure

1. Headline + Executive Summary

Lead with the most impressive result:

[Company] Achieved [Result] with [Your Product]

Example: "Acme Corp Reduced Support Tickets by 73% with HelpDesk Pro"

2. Customer Background (2-3 sentences)

  • Who they are
  • What they do
  • Why they matter (size, reputation, relevance to reader)

3. The Challenge

  • What problem they faced
  • What they tried before (and why it didn't work)
  • What was at stake if they didn't solve it

4. The Solution

  • Why they chose you
  • How implementation worked
  • Key features/capabilities that made the difference

5. The Results

Present with specificity:

  • Primary metric (the headline number)
  • Secondary benefits (unexpected wins)
  • Timeline (how quickly they saw results)

6. Customer Quote

A direct quote that captures the transformation. Aim for emotional + factual:

"We went from drowning in support tickets to actually having time to build new features. Our team morale completely changed." - Jane Smith, VP Engineering

7. Call to Action

What should the reader do next?

Writing Guidelines

Lead with Results

  • Bad: "Company X implemented our solution..."
  • Good: "Company X cut costs by 40% in 3 months..."

Use Specific Numbers

  • Bad: "significantly improved"
  • Good: "improved by 73%"
  • Better: "improved from 2 hours to 32 minutes"

Include the Before/After

Paint the contrast between their old painful state and new better state.

Let the Customer Speak

Use their words where possible. Direct quotes are more credible than your paraphrase.

Keep It Scannable

  • Subheadings every 2-3 paragraphs
  • Bullet points for lists
  • Bold key metrics
  • Pull quotes for emphasis

Match Your Audience

  • For technical buyers: Include implementation details
  • For executives: Focus on ROI and strategic impact
  • For users: Emphasize day-to-day improvements

Output Formats

Full Case Study (1-2 pages)

Complete narrative with all sections. Good for website, PDF downloads, sales collateral.

One-Page Summary

Condensed version with:

  • Headline result
  • 3-bullet challenge
  • 3-bullet solution
  • Key metric + quote

Good for sales decks, email attachments.

Social Proof Snippet (2-3 sentences)

For landing pages and marketing materials:

"[Company] achieved [result] using [Product]. '[Quote]' - [Name, Title]"

LinkedIn/Social Post

Conversational version for social sharing:

[Company] was struggling with [problem].
After implementing [solution], they saw [result].
Here's what [Name] had to say: "[Quote]"

Example Output

# TechStart Reduced Customer Churn by 47% with RetainPro

## Executive Summary
TechStart, a B2B SaaS company with 500+ customers, was losing 8% of customers monthly due to poor onboarding. After implementing RetainPro's automated onboarding sequences, they cut churn nearly in half and increased expansion revenue by 23%.

## Customer Background
TechStart provides inventory management software to mid-market retailers. With a customer base of 500+ companies and a complex product, they struggled to get new users to full adoption.

## The Challenge
- 8% monthly churn rate (industry average: 5%)
- New users took 45+ days to reach "aha moment"
- Support team overwhelmed with basic "how do I..." questions
- Expansion revenue flat because users never discovered advanced features

## The Solution
TechStart implemented RetainPro to:
- Automate personalized onboarding sequences
- Trigger in-app guidance based on user behavior
- Identify at-risk accounts before they churned

Implementation took 2 weeks with dedicated support from the RetainPro team.

## The Results
After 90 days:
- **47% reduction in churn** (8% to 4.2% monthly)
- **Time to value cut from 45 days to 12 days**
- **23% increase in expansion revenue**
- Support ticket volume down 35%

## Customer Quote
> "RetainPro paid for itself in the first month. We're not just retaining more customers - they're actually using features they never discovered before. Our expansion revenue tells the story."
>
> — Sarah Chen, VP of Customer Success, TechStart

## Ready to reduce your churn?
[CTA button or link]

What This Skill Does NOT Do

  • Interview your customers (you need to gather the raw information)
  • Verify metrics or claims
  • Get customer approval for publication
  • Create visual designs or layouts

When to Use This vs. Other Skills

Use case-study-writer when...Use other skills when...
Showcasing customer successWriting landing page copy (landing-page-builder)
Building social proofCreating sales page (sales-page)
Sales enablement contentGeneral marketing copy (copy-editor)

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.35%
按下载量换算109

Claude

28.71%
按下载量换算89

Cursor

18.46%
按下载量换算57

Gemini CLI

10.21%
按下载量换算32

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills