By bacoco
The upward-compiler — reads your git history, PRs, and tickets, then generates manager-adapted reports, Q&A prep, call scripts, and tracks your history. 10 archetypes, 6 formats, 1 command.
Analyzes a manager's communication style from messages, emails, Slack threads, PR comments, or meeting notes and outputs a structured communication profile: archetype name, confidence score, observed evidence, recommended communication strategy, and what to avoid. Use this skill when the user pastes manager messages and wants to adapt their communication, when preparing a status report that needs to land well, when starting the useless-report workflow, or any time the user asks "how should I write this for my manager", "what kind of manager is this", or "how does my boss communicate". Also triggers on "my manager always asks for...", "my boss never reads...", "my manager wants everything in meetings", or similar complaints about upward communication friction. This is the entry point for the entire useless-report workflow.
Generates a natural call preparation document — talking points, opening hook, key messages, objection responses, and closing ask — adapted to both the manager's archetype and the user's own communication persona. Not a script: a structured guide that sounds like you. Covers status calls, idea pitches, crisis management, and general check-ins. Use when the user says "I have a call with my manager", "help me pitch this idea", "I need talking points", "prepare me for this conversation", or "what do I say on this call".
Converts a markdown manager report (the output of any useless-report generate-* skill) into an email-safe HTML file with fully inlined CSS — compatible with Gmail, Outlook, Apple Mail, and any webmail. No CSS variables, no external resources, no JavaScript. Colors and typography derived from DESIGN.md if present (tokens inlined as literal values, not CSS variables). Use this skill when the user wants to send the report directly by email, asks for "email-ready", "copy-paste into Gmail", "forward to my team", or needs a format that survives email client rendering. Triggers after any generate-* skill when the output destination is an email client.
Converts a markdown manager report (the output of any useless-report generate-* skill) into a standalone styled HTML file ready to email, share, or save. Includes embedded CSS derived from the project's DESIGN.md brand tokens — no hardcoded themes, no external dependencies. If no DESIGN.md is found, runs the generate-design flow first. Use this skill when the user wants to send a report by email, share a polished version, generate a printable artifact, or asks for "the HTML version", "make it look nice", "I need to send this to my boss", "format this for email". Triggers after any generate-* skill when the user wants a more polished output.
Generates a Q&A preparation document from a manager report — all the questions the manager is likely to ask (based on their archetype), with prepared answers derived strictly from the report data. Includes "danger questions" (the ones that catch you off guard), objection responses, and a quick-reference cheat sheet. Output is a collapsible HTML file to review before a meeting or call. Use when the user asks "what will my manager ask?", "help me prepare for my meeting", "I have a review tomorrow", or "Q&A prep".
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Your work is real. Make sure it reads that way.
One command. Your git history. Every manager, covered.
Get started · How it works · Archetypes · Formats · Before the meeting
You shipped. You fixed. You unblocked three people and made a call that saved the quarter.
Then someone asked for "a quick update" — and you spent two hours writing a report nobody read the same way.
Same week. Ten different managers. Ten different expectations.
Then came the meeting. They asked questions you didn't see coming. You had the data. You just didn't have it in the right shape for that room.
useless-report reads your codebase — commits, PRs, tickets — and writes the report they want to read.
Not a summary. Not a template. A report adapted to how your manager thinks, decides, and worries.
The report. The Q&A. The call script. All from the same source.
"Different style. Same truth."
In Claude Code, just say it:
"Generate my weekly report"
Set up once. Run forever. No questions after the first time.
One week of work. One run. Everything ready.
For Alice — control-oriented
For Bob — risk-sensitive
And in the background: history saved, open requests tracked.
23 commits read. Nothing invented.
|
① Read Your git log. Real data, nothing invented. |
② Understand Who is reading this? 10 manager archetypes. |
③ Generate The report they'll actually read. One fact base. N reports. |
④ Deliver Report. Q&A. Call prep. Ready for anything. |
Every manager has a pattern. Pick theirs — or let useless-report figure it out.
| Archetype | What they always say | |
|---|---|---|
| 🔬 | Control-oriented | "Can you send a quick detailed breakdown?" |
| 🛡️ | Risk-sensitive | "Are we sure about this?" |
| 📋 | Process-heavy | "Is this in the tracking system?" |
| 🎭 | Stakeholder-oriented | "How does this look to the committee?" |
| 🌀 | Low-context | "Sorry catching up — what did we decide?" |
| 🎯 | Volatile-priority | "Actually, forget what I said last week" |
| ⏰ | Deadline-reactive | "We need this by tomorrow, right?" |
| 🔍 | Quality-maximalist | "Did we consider all the edge cases?" |
| 🌊 | Ambiguity-tolerant | "Yeah just run with it" |
| 📞 | Synchronous-first | "Let's jump on a quick call" |
Don't know which fits? Just ask:
"Help me figure out my manager's communication style"
Every report, in the format they'll actually open.
|
Markdown Slack. GitHub. |
HTML One file. |
Inline CSS. |
Slides Marp deck. |
Visual identity driven by your DESIGN.md — the Google Labs open standard for brand tokens. Pass a URL, a CSS file, a screenshot, or nothing — useless-report handles it.
The report gets you through the week. These get you through the room.
|
Q&A Prep Every question they'll ask. Read it on your phone. |
Call Prep Your words. Not a script. |
History What you promised. Never lose track |
Just ask:
npx claudepluginhub bacoco/useless-report --plugin useless-reportA roulette that picks a random useless skill each session. 8 absurd skills, combos, plot twists, and chaos mode. Community-driven — add your own via PR.
CLoClo — Dev pipeline (Claude+Codex reviews) + project bootstrap (CLAUDE.md, hooks, memory, skills, wiki) + LLM wiki (persistent knowledge base) + behavioral patterns.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Frontend design skill for UI/UX implementation
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Memory compression system for Claude Code - persist context across sessions
Marketing skills for AI agents — conversion optimization, copywriting, SEO, paid ads, ad creative, and growth
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.