Skip to content
Skills Library
Marketing & content · Writing

case-study-steps

/case-study-steps

Use when the owner says "summarize what I did", "turn this into steps", "case study steps", "the three steps", "one line on how I work", or dumps a messy account of their work and wants it boiled down for a website or an executive audience. Condenses it into at most three punchy steps (label, one sentence, icon), or a single headline line.

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the owner says "summarize what I did", "turn this into steps", "case study steps", "the three steps", "one line on how I work", or dumps a messy account of their work and wants it boiled down for a website or an executive audience. Condenses it into at most three punchy steps (label, one sentence, icon), or a single headline line.

Triggers from the description

summarize what I didturn this into stepscase study stepsthe three stepsone line on how I work

Arguments

/case-study-steps [an account of what was done, or a file path] [project name]
Original author description

Use when the owner says "summarize what I did", "turn this into steps", "case study steps", "the three steps", "one line on how I work", or dumps a messy account of their work and wants it boiled down for a website or an executive audience. Condenses it into at most three punchy steps (label, one sentence, icon), or a single headline line.

How it works

  1. Steps
  2. Example format (Aisle case study, approved by the owner)
  3. Rules
  4. One-line version (headlines and section intros)
Original SKILL.md headings · 33 lines, 547 words
SKILL.md preview
---
name: case-study-steps
description: Use when the owner says "summarize what I did", "turn this into steps", "case study steps", "the three steps", "one line on how I work", or dumps a messy account of their work and wants it boiled down for a website or an executive audience. Condenses it into at most three punchy steps (label, one sentence, icon), or a single headline line.
argument-hint: "[an account of what was done, or a file path] [project name]"
---

## Steps
1. Read what was given. Pull out the order of events: what was learned, what was built, how it was checked.
2. Group it into at most three steps. Default shape is learn, build, test. Merge or drop detail to fit. Three is the cap, two is fine.
3. Write each step as a label plus one sentence (format below).
4. Suggest a simple line icon per step and a pastel circle color (peach `#FFD9C2`, lavender `#CDBDEB`, sky `#BFD8EC`).
5. If the work is unfinished, add one "Up next" line. If the product is unpublished or unvalidated, add a one-line disclaimer under it.
6. Show it as a table and flag anything marked [CONFIRM]. Do not publish or edit a page until the owner says so.

## Example format (Aisle case study, approved by the owner)
- **Cracked the florist math**: Scanned the market, learned how florists really price, and interviewed other brides to see if they felt the same sticker shock.
- **Built the formula**: Turned that research into a pricing model using public wholesale prices, adjusted for city costs and florist markup.
- **Put it to the test**: Ran Pinterest bouquets through it, then had friends poke holes, from pricing errors to images that looked too AI.
- Up next: Checking the prices with real florists, and surveying brides to see if they would actually use the website.
- Disclaimer: Aisle is an unpublished prototype. Estimates are illustrative and not quotes. Aisle is a working name.

## Rules
- **No step numbers and no big stats column.** Label and sentence sit together beside an icon.
- **Label:** 2 to 4 words, past tense, a little playful, starts with a strong verb. Says what was done, not the topic.
- **Sentence:** one sentence, about 25 words at most, starts with a verb, no "I". Reads as if presented to an executive: no detail the owner would have to defend line by line.
- **Plain words.** No em dashes, no consultant-speak, no rule-of-three lists in the sentence.
- **Only claim what the files and the owner's words support.** Nothing validated, no accuracy, savings or user numbers unless the owner gave a source. Say "prototype", not "launched".
- **Leave out third parties** (named experts, competitors) unless the owner asks.
- **Mark anything uncertain** as [CONFIRM], such as counts of interviews.
- Check the owner's wording against what they actually did. If their edit introduces a typo or a leftover word, point it out and leave their text alone.

## One-line version (headlines and section intros)
- Same rules, compressed into one sentence of about 10 words. Plain, warm, first person, starts with what the owner does.
- Approved example, a home page services headline: "I start by listening, then work as part of your team."
- Give one pick plus two alternates, and say why the pick fits.
- **Service straplines:** say what the owner does, then what it becomes (input to outcome). Name a concrete object, not "answers" or "the work". About 10 to 14 words.
  - Approved: "Turn a complex project into a clear plan, then run it through delivery." / "Analyze the market and competitors, then recommend the move worth making." / "Turn dense analysis into the executive deck that gets a decision."

Versions

The database has no other skills named case-study-steps.

Database snapshot: 13.11.2026 · package version f3ccf8faf1d6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100gtm-case-study
    When the user wants to turn a customer win into proof — a case study, a customer story, a reference narrative. Use for 'write a case study', 'customer story', 'success story', 'turn this win into proof'. Uses only user-supplied, verified results.
  • 100sangines-storytelling-case-study
    Turn founder interviews and verified client outcomes into four-part Storytelling Case Study posts within a people-led content system. Use for B2B founder or executive LinkedIn case studies, interview planning, and evidence-based revisions.
  • 90case-study
    Write a customer case study or quote pack from a call transcript and verified numbers, with a quote-approval checklist. Use when "write the Acme case study", "customer spotlight", "quote pack".
  • 100graphic-case-study
    Generates a professionally designed case study PDF for B2B SaaS sales and marketing. Supports 7 page layouts, 9 style presets, 1-4 page output. Trigger when user says "create a case study", "write a customer story", "make a case study PDF", "design a success story", "turn this…
  • 100case-study-builder
    Creates professional case studies, engagement summaries, and project summaries. Use when the user wants to create a 'case study,' 'client success story,' 'engagement summary,' 'project summary,' or 'portfolio piece.
  • 100case-study-writer
    Write public-safe case studies from private projects, automations, agent workflows, internal tools, demos, or client-facing systems. Use when the user asks to turn project work into a case study, create client proof, write a sanitized GitHub case study, summarize an internal…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.