# Build Case Study

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-feedspace-feedspace-cookbook-build-case-study`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Feedspace](https://agentstack.voostack.com/s/feedspace)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Feedspace](https://github.com/Feedspace)
- **Source:** https://github.com/Feedspace/Feedspace-Cookbook/tree/main/plugins/feedspace-reviews/skills/build-case-study
- **Website:** https://feedspace.io

## Install

```sh
agentstack add skill-feedspace-feedspace-cookbook-build-case-study
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Build case study

Turn one strong testimonial (or a few reviews from the same customer) into a clean, structured case
study draft: a customer snapshot, the challenge, the solution, the results, and a pull quote. Every
line is grounded in what the customer actually said - no invented metrics, timelines, or outcomes.
The source can be a Feedspace account through the Feedspace MCP, a CSV, or pasted text.

The full method lives in [references/case-study-method.md](references/case-study-method.md). Follow
it exactly. It runs entirely in this session and needs no API key; pulling reviews from the Feedspace
MCP is a separate, read-only connection.

## Steps

1. **Get the source testimonial.**
   - Feedspace MCP: first check whether it is already connected - are Feedspace tools (for example
     `list_workspaces`) available? If yes, just use them; do not ask the user to reconnect. Find a
     rich candidate (a detailed video or audio testimonial, or a long text review - `filter_reviews`
     by type and 4-5 stars, or search by the customer's name), then call `get_review` for the full
     detail, including the transcript and the reviewer's name, role, and company. Only if the tools
     are not available, point the user to setup in [references/mcp-source.md](references/mcp-source.md),
     which also covers how to find candidates and where each field lives.
   - Otherwise read a CSV (see [references/csv-format.md](references/csv-format.md)) or ask the user
     to paste the testimonial plus any known customer details (name, role, company).

2. **Run a completeness check, then confirm the subject.** A case study rests on four pillars: who
   the customer is, the challenge they faced, the solution, and the result. Tell the user which
   pillars the source actually supports and which are missing, so nothing gets invented to fill a
   gap. If the source has several different customers, build one at a time - ask which, or offer the
   richest.

3. **Build the case study** by following
   [references/case-study-method.md](references/case-study-method.md): headline options, customer
   snapshot, challenge, solution, results, and one verbatim pull quote - each traceable to the
   source, in the customer's own language.

4. **Offer one sensible next step, then stop.** Options: draft a short outreach message asking the
   customer to fill a missing pillar (for example the before-state or a metric), produce a shorter
   social-proof pull-quote version, or build a case study from a different testimonial. If the review
   came from the Feedspace MCP, you can also pull another candidate over the live connection.

## Guardrails

- Ground everything in the source. Never invent a challenge, a number, a timeline, a company detail,
  or an outcome the customer did not state. If a pillar is missing, say so - do not manufacture it.
- Quote the pull quote verbatim and attribute it. Do not turn a compliment into a metric or a
  feature into a result.
- If the source is too thin for a real case study (a one-liner like "Great product, love it"), say
  so and offer a short testimonial highlight instead, plus what to ask the customer for.
- Detect the language of the testimonial and write the case study in it.
- This skill only reads and drafts. The output is a draft for the user to review, edit, and publish
  themselves. The Feedspace MCP path is read-only - never modify, favourite, feature, or delete
  anything.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Feedspace](https://github.com/Feedspace)
- **Source:** [Feedspace/Feedspace-Cookbook](https://github.com/Feedspace/Feedspace-Cookbook)
- **License:** MIT
- **Homepage:** https://feedspace.io

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-feedspace-feedspace-cookbook-build-case-study
- Seller: https://agentstack.voostack.com/s/feedspace
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.