Token导航 LogoToken导航

Agent Skill · 前端设计

case-study-plan(案例研究计划)

case-study-plan 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

case-study-plan 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 6,334。

总安装 523周安装 22GitHub Stars 66下载 183核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill case-study-plan

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

case-study-plan 用于生成结构化的案例研究创建计划,包含访谈框架、数据可视化方案、格式变体及分发策略。适合为具体项目或客户 engagement 制定可执行的证明成果内容蓝图,提升销售支持与可信度建设。使用时需提供客户或项目信息、所解决问题的背景,系统将输出完整的内容构建指引。

安装前请确认权限范围与维护状态,注意可能涉及联网调用与文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/case-study-plan

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

case-study-plan 怎么安装?

在终端执行 npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill case-stud…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

case-study-plan 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

case-study-plan 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

case-study-plan 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

case-study-plan 用的人多吗?

公开数据是累计安装 523 次,近一周安装 22 次,下载 183 次,GitHub 66 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

case-study-plan 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
case-study-plan

案例研究计划 · 本页

52366只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

/dm: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 (/dm: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.

Output

A structured case study creation plan containing:

  • CSR narrative framework — Challenge-Solution-Results structure with detailed sub-sections, emotional arc mapping, and story flow outline
  • Client interview question set — 15-20 questions organized by narrative section (background, challenge, solution, results, forward-looking) with follow-up prompts
  • Internal team interview questions — 10 questions covering strategic rationale, delivery experience, turning points, and retrospective insights
  • Data visualization plan — which metrics to highlight, chart types for each data point, before/after comparison designs, and data collection requirements
  • Format variation specifications — PDF (4-6 pages with layout notes), web page (SEO-optimized with schema markup), slides (8-12 with speaker notes), video (2-3 min script outline), social (pull quotes and stat cards), and one-pager (front-and-back layout)
  • Distribution strategy — publication channels (website, sales tools, social, email, PR), promotion plan, and audience targeting per channel
  • Permission and approval checklist — legal review, client sign-off stages, data verification steps, quote approval, logo usage, and review timeline
  • Executive summary draft — 150-200 word overview capturing the complete story arc for use across all formats
  • Visual asset list — photography needs, chart specifications, infographic elements, pull quote card designs, and video b-roll requirements
  • SEO metadata — optimized title tag, meta description, target keywords, and structured data recommendations for the web version
  • Sales enablement notes — where the case study fits in the sales funnel, which buyer objections it addresses, and how sales teams should use each format
  • Content repurposing plan — how to extract derivative content pieces (blog posts, social proof snippets, email testimonials, presentation slides) from the core case study

Agents Used

  • content-creator — Narrative structure, interview question development, executive summary drafting, format variation planning, visual asset specification, and content repurposing strategy
  • pr-outreach — Distribution strategy, PR angle identification, media pitch framework, partner co-marketing opportunities, and external publication targeting

平台分布

Codex

31.79%
按下载量换算58

Claude

31.58%
按下载量换算58

Cursor

20.02%
按下载量换算37

Gemini CLI

9.82%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills