tell-case-study-story

Structure and write portfolio case studies with outcome-first narratives and verifiable proof.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill tell-case-study-story-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tell-case-study-story
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/tell-case-study-story
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill tell-case-study-story-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Portfolio case studies often bury outcomes under process theatre, inflate unverifiable numbers, and fail the 55-second first-pass review that decides whether a hiring manager invests further. This Skill structures shipped-work narratives so the outcome lands in line one, every claim is checkable, and NDA-constrained work stays honest without fabricated metrics. ## Core Features & Use Cases - Fact-sheet gate and proof ladder: Requires a verified fact sheet before writing, then selects proof from a strict hierarchy — live operable artifact, sourced metric, architectural guarantee, or NDA-honest names-plus-scale. - Fixed case skeleton: Produces tag strip, line-one outcome, problem, shown solution, sourced impact block, iteration ladder with deltas, 500-800 word trade-off narrative, role line, and link block. - NDA-honest and AI-work honesty patterns: Handles cases where numbers cannot be shown or never existed, including labeled recreations, early-signal qualifiers, and architecture-level guarantees instead of behavioral claims. - Use Case: A designer needs to turn a shipped AI chatbot project into a portfolio page. The Skill builds the fact sheet, names the single claim, writes a metric-led opening line with its source, and assembles the full case ready for a craft-critique ship review. ## Quick Start Write a portfolio case study for my shipped project, leading with the outcome and using only verifiable metrics with named sources.

Frequently Asked Questions about tell-case-study-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a portfolio case study that passes recruiter screening?

Put the outcome in line one with a number or scale anchor, keep proof on the page rather than behind links, and structure the case as decisions under constraint instead of a process-framework walkthrough. Reviewers spend about 55 seconds on a first pass, so depth must never delay the payoff.

How do I write a case study when my work is under NDA?

Use the NDA-honest pattern: name the client and the scale of the system, state plainly what did not ship, and never invent percentages to fill the impact slot. Absence of metrics, stated openly, makes every real number elsewhere on the site more believable.

What should the first line of a case study say?

Line one should combine an outcome number or scale anchor, what shipped, and whose hands it is in, with an honest qualifier if the data is early. It should never open with a method or a phrase like 'I led the design of'.

When should I not use this case study skill?

Do not use it for sentence-level prose polish, which belongs to writing-voice, or for a final ship verdict, which belongs to craft-critique. Live presentations go to present-and-defend-work, and portfolio-wide positioning belongs to position-product.

How do I present AI project metrics honestly in a portfolio?

Label recreated demos as recreated, keep early-signal qualifiers attached to the number itself, and claim guarantees as inspectable architecture rather than behavioral promises. Every displayed figure must come from a verified data source, never from memory or an old draft.