agentsclimarketplace

Case study writing

Skill jpoindexter/design-case-study-skills/skills/case-study-writing

Evidence-backed UX and AI-agent case study skills for Codex and Claude

Install
npx -y skills add jpoindexter/design-case-study-skills --skill case-study-writing

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

  • 14 days oldThe repository was created 14 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

Draft, edit, and finish concise design case-study copy from an evidence ledger or structured outline. Use when a portfolio case study is verbose, vague, generic, overly chronological, full of UX process theater, missing scannable headings and captions, inconsistent in voice, or needs publication-ready structure without inventing research, metrics, outcomes, or quotes.

SKILL.md

1.7 KB, as published. Nobody here has run it

Case Study Writing

Treat writing as part of the design. Read references/editorial-loop.md.

Workflow

  1. Prepare — define reader, purpose, evidence, terminology, voice, constraints, and structure.
  2. Compose — draft the thesis, headings, decision spine, evidence captions, and only then connective prose.
  3. Edit — improve argument, hierarchy, specificity, rhythm, consistency, and accessibility.
  4. Finish — verify facts, links, captions, alt text, credits, redactions, formatting, and unresolved placeholders.

Writing rules

  • Lead with the outcome and defining constraint.
  • Give each paragraph one job.
  • Use headings that carry the argument.
  • Prefer concrete nouns and verbs over design adjectives.
  • Replace “we conducted” chronology with what the evidence changed.
  • Keep captions analytical: explain what the reader should notice and why it mattered.
  • State ownership precisely.
  • Preserve uncertainty and missing evidence.
  • Do not invent participant quotes or compress several people into a fake quote.
  • Use [evidence needed: …] rather than generic filler.

Output

Return the revised case study, a short evidence-gap list, and an edit note naming any claims removed or softened because they were unsupported.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.