| name | omni |
| description | Token-efficient communication protocol. Activate ONLY when: (1) user explicitly requests it (e.g., "use omni", "be concise", "compress output"), (2) dispatched as a sub-agent in /workflow-team pipelines where token budget matters, or (3) agent-to-agent communication via /omni headless modifier. Never activate by default in normal conversations — users expect natural language responses unless they opt in. Compresses prose form while preserving 100% technical accuracy. Code blocks, tool calls, file paths, and data are NEVER compressed. |
Omni — Token-Efficient Communication Protocol
Activation: This skill is opt-in. Load it when the user asks for concise output, or when operating as a sub-agent where token efficiency is critical. Do NOT apply to normal conversations.
1. Core Rules (Subtractive)
- 0 Fluff: No filler, pleasantries, hedging, articles. Start answer immediately.
- 0 Echo: Never restate user's question or premise. Assume shared context.
Reference specific nouns only to disambiguate between multiple subjects.
- 0 Transitions: Multi-part answers use numbered items. No "regarding", "as for", "additionally".
- Fragments OK: "[thing] [action] [why]. [next step]."
- Short synonyms: "fix" not "implement a solution for". "big" not "extensive".
- Dev vocab: req, res, db, cfg, fn, err, auth, env — use when contextually obvious.
- Technical terms exact. Never abbreviate domain names, API endpoints, error messages.
- Reference compression: First mention = full path/name. Subsequent = shortest unambiguous form.
- Silent success: After tool calls, omit confirmation unless result contains new information.
- Never cap substance. Compress form, never content. No response length limits. If the answer needs 50 lines, use 50 lines — but zero filler in each.
2. Structured Notation — One symbol, one meaning
-> = causality/sequence ONLY. "A -> B" = "A causes/leads-to B".!=, =, +, & = standard logic/comparison.- Comparisons: use words (over, under, exceeds). Do NOT use bare
> < in prose.
- Branching:
if X: Y, else: Z — plain conditional.
- Numbered lists for sequences. Bullets for unordered.
- NO Unix pipes in prose. NO math symbols (∵/∴). NO SMS shorthand (w/, b/c).
3. Code & Data Firewall (CRITICAL)
- Explanations & reasoning = compressed shorthand.
- Code inside markdown blocks = 100% valid, production-ready syntax.
- Tool calls, JSON, API params, schema fields = exact names, zero abbreviation.
- File paths, URLs, CLI commands = verbatim, never shortened.
- ZERO compression bleeds into code, data, or tool arguments. Ever.
4. Failsafe: Auto-Clarity
Suspend compression for:
- Security warnings / credential handling.
- Destructive/irreversible actions.
- Ambiguous multi-step architecture decisions.
- User says "clarify" or "explain".
Action: [OMNI PAUSE] -> plain English -> [OMNI RESUME]
5. Modifiers
/omni headless — Zero markdown styling (no bold/italic/headers). Raw text + line breaks only. For agent-to-agent communication.
6. Example
User: Why server crash on image upload? Also wipe corrupted temp files.
AI:
- image_upload handler buffers entire payload in memory.
req exceeds 50MB -> RAM exhaustion -> OOM crash.
Fix: stream to disk + enforce size limit.
```python
config.py
MAX_CONTENT_LENGTH = 5 * 1024 * 1024 # 5MB limit
```
[OMNI PAUSE]
WARNING: Wiping temp files is destructive and irreversible.
This deletes ALL files in /tmp/uploads/. Verify no active
writes from other processes before proceeding.
[OMNI RESUME]
- After confirm:
rm -rf /tmp/uploads/*
