Case study builder

Skill nahiddotai/operator-powers/plugins/operator-powers/skills/case-study-builder

AI skills to operate and grow. Twenty-eight practical powers for non-technical operators.

Install

npx -y skills add nahiddotai/operator-powers --skill case-study-builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Turn evidence about one customer, client, project, or outcome into a credible case study, success story, proof page, sales story, or short proof block.

SKILL.md

2.7 KB, as published. Nobody here has run it

Case Study Builder

Turn one real outcome into trustworthy proof without upgrading partial evidence into a miracle story.

Job contract

Owns: a publishable story about one customer or project.
Does not own: cross-customer patterns (customer-insight-synthesizer) or a general meeting analysis (meeting-miner).
Finished deliverable: a case study, clearly labelled project story, or evidence plan, plus a claim ledger and approval checklist where relevant.

Evidence gate

Classify the evidence before drafting:

Full case study: the starting situation, intervention, and meaningful outcome are all supported by traceable evidence. Proceed with the requested case-study format.
Project story: the work and process are supported, but the customer or business outcome is not. Produce a useful project story and state plainly that no outcome claim is being made.
Evidence plan: the work, change, or outcome cannot yet be verified. Do not manufacture a narrative. Return the missing evidence and the smallest practical plan for collecting it.

Quotes, metrics, customer names, logos, and claims of approval remain blocked until their source or permission is verified.

Workflow

Inventory the customer, starting situation, stakes, constraints, intervention, timeline, outcome, sources, permissions, and confidentiality needs.
Separate verified facts, customer statements, user interpretation, and missing evidence.
Run the evidence gate and tell the user which route the material supports.
Find the real change. Prefer a specific credible result over an inflated transformation.
Build the narrative: situation, tension, decision, work, result, meaning.
Attribute quotes and numbers. Mark anything requiring customer approval.
Produce the supported format: proof block, one-page story, sales-page section, full case study, project story, or evidence plan.

Output

# [Outcome-led title]

## At A Glance
[Customer, challenge, work, result]

## The Starting Point
[Specific context]

## What Changed
[Actions and mechanism]

## The Result
[Verified outcomes and limits]

## Why It Mattered
[Customer consequence]

## Claim Ledger
| Claim | Source | Status | Approval needed |

## Publication Checklist
[Name, logo, quote, metric, confidentiality approvals]

Guardrails

Never invent or round up results, dates, quotes, titles, logos, or customer approval.
An internal draft is not permission to publish.
Anonymise only when requested and ensure the remaining detail cannot re-identify the customer.