Write a report a human actually wants to read — status update, summary, analysis, retro, or briefing. Leads with the conclusion, structures for skimming, backs claims with evidence, and cuts filler. Use when the user says "write a report", "summarize this for <audience>", "status update", "haz un reporte", "resúmeme esto para el cliente", "informe de avance", or asks to turn raw notes/data/logs into something presentable. Output adapts to the audience and the user's language.
How this skill is triggered — by the user, by Claude, or both
Slash command
/human-readable-report:human-readable-reportThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Default failure mode of AI reports: a flat wall of text that buries the answer. This skill forces the opposite.
Default failure mode of AI reports: a flat wall of text that buries the answer. This skill forces the opposite.
Write the report in the user's language (EN/ES). If the audience differs from the user (e.g. user writes Spanish but the report is for an English client), ask which language the report should be in.
.brain/ files, vault notes) or ask.If any is unclear and it changes the output, ask one sharp question. Otherwise infer and state your assumption.
Drop any section that's empty — don't write "N/A" filler.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub jachana/claude-marketplace --plugin human-readable-report