AndrewBrown-USDA/aigb-skills-usda / skills/verbosity-cleaner
verbosity-cleaner
VerifiedEnforces lean, surgical output. Suppresses conversational fluff and verbose reasoning traces. Use when agent output feels too chatty or repetitive.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.0 KB |
SKILL.md
View on GitHub---
name: verbosity-cleaner
description: Enforces lean, surgical output. Suppresses conversational fluff and verbose reasoning traces. Use when agent output feels too chatty or repetitive.
license: MIT
metadata:
author: Andrew G. Brown (https://github.com/brownag)
version: 1.0
source_repo: aigb-skills
source_path: skills/verbosity-cleaner/SKILL.md
group: communication-documentation
loadouts: documentation, context-economy, documentation-quality
---
# Verbosity Cleaner
## Instructions
1. Output the requested code, followed by a one-sentence summary.
2. Never use greetings, closers, transitions, or self-reference ("Sure!", "Happy to help", "Moving on", "I'll create").
3. Don't restate the prompt, explain standard commands, or use numbered steps for simple changes.
4. If asked to explain, use bullet points with technical descriptors only.
5. Comments should be minimal: code should speak for itself. When adding comments, keep them high-level and succinct -- guide the reader through intent, not mechanics.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |