← ClaudeAtlas

case-study-writerlisted

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 system publicly, document an automation without sharing source code, or explain a workflow while removing credentials, raw prompts, logs, databases, client data, local paths, and private implementation details.
jqaisystems/jqai-ai-skills · ★ 2 · AI & Automation · score 75
Install: claude install-skill jqaisystems/jqai-ai-skills
# Case Study Writer ## Overview Use this skill to turn private project work into public-safe proof: concise case studies that explain the problem, workflow, outcome, and adaptation value without exposing source code, credentials, raw prompts, logs, databases, client data, or private implementation details. ## Workflow 1. Clarify the public artifact target: GitHub case study, website system page, portfolio note, demo companion, or README section. 2. Read `references/case-study-template.md` and use its section order unless the destination already has a stronger house style. 3. Read `references/safety-boundary-examples.md` before writing the opening boundary note and final Safety Boundary section. 4. Extract only public-safe facts: - Problem the system solves. - What the system does at workflow level. - Human review and approval points. - General stack categories when useful. - Outcome stated qualitatively or with approved aggregate numbers. - What a similar client could adapt. 5. Rewrite private details into generic, reusable language. Do not copy raw notes, prompts, logs, exports, database rows, or source code. 6. Produce the case study in Markdown and include a short safety verdict: `BLOCK`, `REVIEW`, or `READY`. ## Case Study Shape Use these sections by default: - Title - Boundary note - Public page or demo links, if already approved and live - Problem - What The System Does - Workflow - Outcome - What Can Be Adapted For Clients - Safety Boundary Ke