compress-prompt
Compresses prompts/skills into minimal goal-focused instructions. Trusts the model, drops what it already knows, maximizes action space. Use when asked to compress, condense, or minimize a prompt.
What this skill does
# Compress Prompt
## Goal
Transform a prompt into the **minimal instruction** needed for the model to succeed. Not "preserve everything densely"—instead, "what's the least I need to say?"
Output: Display compressed result + stats. Optionally write to file with `--output <path>`.
## Input
`$ARGUMENTS` = prompt (file path or inline text) [--output path]
If file path: read content. If inline: use directly. If ambiguous: try as file first.
## Principles
1. **Trust capability, enforce discipline** - Models know HOW to do tasks. But they cut corners, forget context, skip verification, declare victory early. Drop capability instructions, keep discipline guardrails.
2. **Goal over process** - State WHAT to achieve, not HOW. Let the model choose its approach.
3. **Training filter** - "Would a competent person need to be told this?" If no → drop it. Models are trained on millions of examples.
4. **Maximize action space** - Fewer constraints = more freedom = better results. Each constraint should earn its place.
5. **Inline-typable brevity** - Short enough you could type it verbally to a capable colleague.
6. **Avoid arbitrary values** - "Max 4 rounds" or "2-3 examples" become rigid rules. State the principle, not the number. Constrain productively while giving flexibility.
## What to Keep vs Drop
| KEEP | DROP |
|------|------|
| Core goal/purpose | Process/phases (capability) |
| Acceptance criteria (success conditions) | Examples the model knows |
| Novel constraints (counter-intuitive rules) | Obvious constraints (model defaults) |
| Execution discipline (write before proceeding, verify before finalizing) | Edge case handling (model trained on these) |
| Output format if non-standard | Explanations and rationale |
**Execution discipline examples** (KEEP these):
- "Write findings to file BEFORE proceeding" — prevents context rot
- "Don't finalize until X confirmed" — prevents premature completion
- "Read full log before synthesis" — restores lost context
**Training-redundant examples** (DROP these):
- "Be thorough", "Handle errors gracefully", "Ask clarifying questions"
- "Consider edge cases", "Use professional tone"
## Constraints
**Create todo list** - Track: input validation, compression, verification iterations, output.
**Verify with agent** - Launch `prompt-compression-verifier` to check goal clarity, novel constraints preserved, no over-specification. Iterate until verification passes.
**Single paragraph output** - The compressed prompt must be one dense paragraph, not reformatted sections or bullets.
**Non-destructive** - Original file untouched. Display output + optional file save.
## Output Format
```
Compressed: {source}
Original: {tokens} tokens
Compressed: {tokens} tokens ({percentage}% reduction)
---
{compressed paragraph}
---
Verification: PASSED/INCOMPLETE ({iterations} iteration(s))
```
## Example
**Before** (1,247 tokens): Full code reviewer prompt with phases, edge cases, examples...
**After** (67 tokens):
```
Review code for bugs, security issues, performance problems; success = all critical issues identified with actionable fixes. Output JSON {file, line, issue, severity, fix}. Never approve code with critical issues.
```
**Kept**: Goal, acceptance criteria, output format, novel constraint (never approve with critical issues).
**Dropped**: Process phases, edge case handling, examples, obvious constraints.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.