Customer Story Builder
gooseworks-ai/goose-skills
Take raw customer inputs — interview transcripts, survey responses, Slack quotes, support tickets, review excerpts — and generate a structured case study draft with problem/solution/result…
Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-case -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-case --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-case .claude/skills/ink-case && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ink-case" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-case into .claude/skills/ink-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-case", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-caseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-case -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-case --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-case .agents/skills/ink-case && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ink-case" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-case into .agents/skills/ink-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-case", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-case -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-case --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-case .cursor/skills/ink-case && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ink-case" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-case into .cursor/skills/ink-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-case", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/ai-agency/tonone/skills/ink-case--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-case -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-case --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-case .gemini/skills/ink-case && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ink-case" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-case into .gemini/skills/ink-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-case", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-caseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-case -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-case .github/skills/ink-case && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ink-case" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-case into .github/skills/ink-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-case", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-case -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace ink-case --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/ink-case .opencode/skills/ink-case && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ink-case" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/ink-case into .opencode/skills/ink-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ink-case", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
ink-caseWrite customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics.
Ink Case is an agent skill from jeremylongshore/tons-of-skills-marketplace. Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics. Use when asked to "write a case study", "document a customer success story", "create social proof content", or "write about how [customer] uses the product".
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Storytelling, Marketing psychology and Customer success. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashGlobGrepAskUserQuestionFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Ink Case loads about 1.3k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 340 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Bash, Glob, Grep, AskUserQuestionAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 340 words, ~1,282 tokens.
.claude/skills/ink-case/SKILL.md (or your agent's skills folder).You are Ink — the content marketing engineer on the Product Team. Write case studies that convert prospects — not testimonials that collect dust.
Before writing:
If no metrics, push for specifics: "What would you have needed to hire instead?", "How long did this take before?", "How many hours/week does this save?"
If interviewing the customer, use this guide:
Context and before:
1. "What was happening in your company when you started looking for a solution like this?"
2. "What were you doing before? What was broken about it?"
3. "How much time/money/risk was that costing you?"
4. "What other solutions did you evaluate?"
Decision:
5. "Why did you choose [Product]? What made it obvious?"
6. "Was there anything that almost made you choose something else?"
After:
7. "Walk me through what happened after you got started."
8. "What was the first thing that made you think 'this was worth it'?"
9. "What would you tell someone who was in your situation 6 months ago?"
Metrics:
10. "Can we put any numbers to the impact? Time saved, cost reduced, revenue or risk affected?"Use the StoryBrand structure — customer is hero, product is guide:
Before — The problem
"[Customer name] was [specific situation]. [Pain they experienced — concrete, not abstract].
Every [time period], they had to [tedious/broken/risky thing]. It wasn't sustainable."
Trigger — Why they changed
"When [trigger event], [customer] knew they needed a different approach."
Discovery — Finding the product
"They found [Product] while [looking for X / via Y]. What caught their attention was [specific thing]."
Implementation — Getting started
"Getting started took [N days/hours]. [One thing that stood out about setup]."
Results — The outcome
"[N] weeks later, [Customer] [specific outcome]. [Metric 1]. [Metric 2]. [Quote from champion]."
Future — What's next
"[Customer] is now [next step / expanding use]. '[Quote about why they recommend it].' — [Name, Role, Company]"Format A — Full case study (800-1,200 words) Full StoryBrand narrative. Used on dedicated case study page, in sales enablement.
Format B — One-page spotlight (300-500 words) Compressed version with metrics box. Used in proposals, in product pages.
Format C — Quote card (50-100 words) Pull quote + metrics + headshot + logo. Used in homepage social proof section.
Produce all three formats from the same story research.
Title should target commercial intent:
Include in the case study:
Deliver:
## Case Study: [Customer Name]
### Snapshot (for homepage/sales deck)
Company: [Name] | Industry: [X] | Size: [N employees]
Result: [Primary metric] | Time to value: [N days]
"[Best quote]" — [Name, Title]
### One-Page Spotlight
[300-500 words]
### Full Case Study
[800-1,200 words with StoryBrand structure]
### Approval Checklist
[ ] Customer has approved all metrics published
[ ] Customer has approved all quotes
[ ] Customer has approved company name and logo use
[ ] Customer has reviewed final draft
[ ] Publication date agreed
### Distribution Plan
- Add to /case-studies page
- Feature in sales proposal template
- Add to relevant landing pages as social proof
- Share as [customer name] announcement on social (if customer agrees)
- Include in next newsletterProduce all three formats (full, spotlight, quote card) and the approval checklist. Every piece must be publish-ready — no placeholder metrics or "TBD" sections.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. If output exceeds 40 lines, delegate to /atlas-report.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/ai-agency/tonone/skills/ink-case of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Ink Case next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ink Case this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.3k | Automated safety check: Notes | MIT | |
| Customer Story Buildergooseworks-ai/goose-skills | 1.2k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Customer Story Writerzapier/gtm-cheat-codes | 342 | — | ~438 | Automated safety check: Pass | MIT | |
| Behind The Scenes And Foundersocial-media-skills/skills | 134 | — | ~2.2k | Automated safety check: Pass | MIT | |
| User Generated Contentvivy-yi/xiaohongshu-skills | 481 | — | ~6.9k | Automated safety check: Pass | None | |
| Social Proof And Testimonialssocial-media-skills/skills | 134 | — | ~1.9k | Automated safety check: Pass | MIT |
gooseworks-ai/goose-skills
Take raw customer inputs — interview transcripts, survey responses, Slack quotes, support tickets, review excerpts — and generate a structured case study draft with problem/solution/result…
zapier/gtm-cheat-codes
Drafts customer stories or metric-led story pages from approved transcripts, notes and quotes, keeping verified claims apart from ones that still need approval.
social-media-skills/skills
The transparency content type — turn what's actually happening inside the business into founder/personal-brand content that builds trust: build-in-public updates, founder story, how-it's-made…
vivy-yi/xiaohongshu-skills
A skill your agent uses when leveraging, curating, encouraging, or amplifying user-generated content on Xiaohonghoushuj, building social proof through authentic customer stories, testimonials, and…
social-media-skills/skills
The proof content type — turn real customer reviews, testimonials, UGC, case studies, and results into believable, objection-matched social content that converts.
shawnpang/startup-founder-skills
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores, design save plays, or create win-back campaigns.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Categories
Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics. Ink Case is an agent skill from jeremylongshore/tons-of-skills-marketplace. Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics.
Ink Case fits situations like: asked to write a case study; document a customer success story; create social proof content; write about how [customer] uses the product.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-case -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/ink-case in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/ink-case in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-case -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/ink-case in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/ink-case in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill ink-case -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ink-case, .gemini/skills/ink-case, .github/skills/ink-case and .opencode/skills/ink-case in your project.
SKILL.md names no scripts, command-line tools or credentials: Ink Case is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, AskUserQuestion.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Ink Case is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Ink Case: Customer Story Builder (gooseworks-ai/goose-skills, 1.2k stars), Customer Story Writer (zapier/gtm-cheat-codes, 342 stars), Behind The Scenes And Founder (social-media-skills/skills, 134 stars) and User Generated Content (vivy-yi/xiaohongshu-skills, 481 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.