agentleFS
Sign inStart free
tidycatc132tidycatc132/claude-skills/skills/case-study/SKILL.md

case-study

Skill0 starsChanged 34 days agoNo licenceView on GitHub

Writes the WISE case study narrative and the showcase design brief for a launched website build, from the build's own files. A script counts pages built by type, words written, keywords targeted and old URLs redirected, fills the snapshot, stats, screenshot list, before and after pairs and brand colours, and checks that every number matches a count or a source file, that a client quote is used only when approved for public use, and that Results waits for 90-day metrics. Use when the AM or PM asks for a case study, showcase write-up, portfolio piece or success story for a client whose site has launched, the design brief behind the showcase assets, or a refresh of a case study with 90-day results. Do NOT use for the Growth Blueprint (use growth-blueprint) or its deck (use blueprint-deck), design briefs for the site itself (use homepage-design-brief or page-type-design-briefs), the close-out package or transition email (use project-close-out), or the go-live email (use week-6-go-live-email).

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use audit.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    audit

    Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free