Human Readable Reports
Use when writing an analysis, report, findings, or status doc for humans to read and share — not a spec an agent executes. Fights AI verbosity/slop and makes deep content easy to read.
Install
npx skills add SummerRiversound/human-readable-reports --skill human-readable-reportsgit clone --depth 1 https://github.com/SummerRiversound/human-readable-reports.git /tmp/human-readable-reports
mkdir -p ~/.claude/skills
cp -r /tmp/human-readable-reports/. ~/.claude/skills/human-readable-reportsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Human-Readable Reports
A report is read by people who were not in the session. Dense jargon, fragment
bullets, `file:line` dumps in the prose, coined terms, padding, and caveats
nobody asked for make the reader the bottleneck. Keep the content deep — make
the *reading* easy.
## Rules
1. **Reader-first.** Write in the reader's language, at their level. Name the
reader before writing. Default: a junior developer who was not in the
session. Two others recur: a non-developer client or operator (no file /
code / API / DB words at all) and a senior colleague (more formal
register). When the reader hands you a structure ("1. … 2. …"), it becomes
the heading skeleton.
2. **Point first (BLUF).** Each section opens with the takeaway in one plain
sentence — understandable from that line alone.
3. **Concrete before abstract — the right kind of concrete.** An unfamiliar
*concept word* gets one grounding line (a cache → "reusing a picture you
already drew"). A *situation, cause or change* is told as the sequence that
actually happens (1. the request comes in → 2. the template is called →
3. it returns empty) and as "now it is X → after this it is Y" — no invented
analogies, no comparisons to products the reader does not use. Examples the
reader gives are illustrations, not facts to verify.
4. **Full sentences, not fragments.** "Method A skips the redraw when nothing
changed," not "A · time-axis · skip render+send." Parallel items go inDetails
- Skill name
human-readable-reports- Repository
- SummerRiversound/human-readable-reports
- License
- MIT
- Repo updated
- 26 October 2026
FAQ
What does the Human Readable Reports skill do?
Use when writing an analysis, report, findings, or status doc for humans to read and share — not a spec an agent executes. Fights AI verbosity/slop and makes deep content easy to read.
How do I install the Human Readable Reports skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add SummerRiversound/human-readable-reports --skill human-readable-reports. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Human Readable Reports popular?
It lives in SummerRiversound/human-readable-reports, which has 14 GitHub stars and 1 forks.
Related skills
Humanizer Formal
14jiutianxvanyin/humanizer-formal
降低商务与学术文本的 AI 生成感,中英文均适用。Removes AI-writing patterns from business and academic prose, in both Chinese and English. 用于审校已写好的报告、备忘录、论文、摘要、执行摘要,或在起草时预防机器腔。当用户要求「去 AI 味」「让文字更像人写的」「润色成正式书面语」「检查这段像不像 AI 写的」,或提交商务、学术文本请求改写时使用。Use when the user asks to humanize, de-slop, or remove the AI tone from a report, memo, paper, abstract, or executive summary. 不适用于随笔、营销文案、社交媒体、创意写作。Not for essays, marketing copy, social media, or creative writing.
Hanxiaoyu Visual Story Comic
13rolfie-han/hanxiaoyu-visual-story-comic
Turn original, public-domain, or user-authorized stories, scripts, articles, and outlines into coherent multi-page comics with stable characters, scenes, props, page plans, image prompts, optional image generation, and continuity review. Use when the user asks for 漫画、条漫、绘本式故事页、连续分镜图、story comic、webtoon, comic pages, or a narrative image sequence. Do not use for a single unrelated illustration, a pure film storyboard, or unauthorized imitation of protected characters and living artists.
Ig Card Generator
14dean9703111/ig-card-generator
把知識素材(文章、講稿、筆記、逐字稿,或只有一個主題)提煉成 IG 輪播知識圖卡:封面 hook → 每卡一概念 → 結尾 CTA。以約定 Markdown DSL 撰寫,經 lint(criteria 全過)後由 build script 產出 1080×1350 PNG 系列圖(支援深/淺色主題)。當使用者說「做 IG 圖卡」「知識圖卡」「輪播圖」「carousel」「把這篇做成圖卡」「IG 貼文圖」「圖卡系列」時使用。出圖完成後可銜接 promo-writer 產生貼文 caption。
Working Backwards Coach
12nwadmark/working-backwards-coach
Create rigorous customer-first product documentation for product builders. Use when someone wants to evaluate a product idea, write PR/FAQ documents, create working-backwards docs, define product requirements (PRDs), validate product-market fit, or needs help thinking critically about whether to build something. Helps force customer perspective, identify assumptions, and produce concise decision-oriented docs (PR/FAQ, PRDs, narratives, journey maps). Triggers include requests for product strategy, feature proposals, "should we build", PRDs, "product requirements document", product validation,
Curious Kid
15rammcodes/Curious-Kid
Explains any technical or complex topic (programming, ML, networking, finance, medicine, science, etc.) using a very short, very simple story that a 5-year-old could follow, then maps the story back to the real concept. Use when the user asks to "explain like I'm 5", "ELI5", "Curious Kid", "explain with a story", or says they don't understand a technical concept and want it made simple and intuitive. Do not use for requests for precise technical detail, code review, or debugging.
Create Heartflow
13BboTTM/heartflow-skill
Create and evolve a HeartFlow skill. Supports archetype-based characters and real-person reconstruction from chats, screenshots, docs, exported social chat logs, and notes. | 创建并进化一个恋爱 skill。
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.