Skip to content

heymegabyte/agent-skills / 01-operating-system

operating-system

Verified

Supreme policy layer governing all agent behavior. Autonomy, one-line prompt interpretation, speed standards, emphasis signal processing, cross-skill coordination, done definitions, conflict resolution. Loaded every prompt.

FileKindSize
SKILL.mdskill md6.4 KB
ai-native-coding.mdmarkdown4.3 KB
architecture-thought-loop.mdmarkdown8.3 KB
autonomous-orchestrator.mdmarkdown9.2 KB
context-engineering.mdmarkdown3.2 KB
one-line-saas.mdmarkdown3.0 KB
output-compression.mdmarkdown3.5 KB

output-compression.md

View on GitHub
---
name: Output Compression
description: Token-efficient output patterns reducing response size 40-65% without losing information density
version: "2.0.0"
updated: "2026-04-23"
---

# Output Compression

## Core Technique: Caveman-Style Output

- Strip articles, prepositions, filler words from technical output
- Example: "The function returns a list of the available configurations" → "fn returns available configs list"
- Reference: 44K-star caveman repo pattern — same info, 40-65% fewer tokens

## Abbreviation Table

- **config** → cfg
- **function** → fn
- **application** → app
- **repository** → repo
- **dependency** → dep
- **environment** → env
- **development** → dev
- **production** → prod
- **authentication** → auth
- **authorization** → authz
- **parameter** → param
- **argument** → arg
- **directory** → dir
- **command** → cmd
- **document** → doc
- **template** → tmpl
- **library** → lib
- **message** → msg
- **request** → req
- **response** → res
- **database** → db
- **middleware** → mw
- **specification** → spec
- **implementation** → impl

## Symbol Grammar

- `→` — leads to / becomes
- `|` — or / separator
- `+` — and / with
- `>` — preferred over
- `<` — less than
- `::` — maps to / defines
- `~` — approximately
- `!=` — not equal / differs from
- `&&` — both required
- `||` — either works
- `**text**` — emphasis
- `` `code` `` — inline reference

## Compression Techniques

### 1. Pipe-Delimited Fragments

```
# BAD (67 tokens):
- The first step is to configure the environment
- Then you need to install the dependencies
- After that, run the test suite
- Finally, deploy to production

# GOOD (23 tokens):
cfg env → install deps → run tests → deploy prod
```

### 2. Tables Over Paragraphs

```
# BAD: "WebP quality should be set to 80 which gives SSIM of 0.98 and is visually lossless.
#       AVIF quality should be 70 for the same perceptual quality but 30-50% smaller."

# GOOD:
| Format | Quality | SSIM | Size |
|--------|---------|------|------|
| WebP   | 80      | 0.98 | baseline |
| AVIF   | 70      | 0.98 | -30-50%  |
```

### 3. Code Over Prose

```typescript
// BAD: "You should create an interface with name, email, and optional phone fields"
// GOOD:
interface User { name: string; email: string; phone?: string; }
```

### 4. Skip Prefixes

Never:

- "Let me..."
- "I'll now..."
- "Here's what I found..."
- "Based on my analysis..."

Just output the result directly.

### 5. Batch Tool Calls

- Parallel independent calls in single response
- 3-5 tool calls/response when no dependencies

### 6. Single-Line Lists

```
# BAD:
# - First item
# - Second item
# - Third item

# GOOD:
first | second | third
```

## When NOT to Compress

- User-facing copy (marketing, UI text, docs) — use full natural language
- Error messages — be specific + helpful
- Explanations to non-technical users — clarity > brevity
- Legal/compliance text — precision required

## Density Targets

- **Rules files** — pipe-delimited one-liners, `→` and `|` separators, no prose wrappers
- **Skill files** — dense paragraphs, abbreviations, match sibling density
- **Chat responses** — 2 sentences, 100-160 chars for descriptions
- **Code comments** — intent not mechanics, JSDoc for public API only

## Ownership

- **Owns** — token efficiency, output formatting, compression patterns, abbreviation standards, density targets
- **Never owns** — content quality (→09), code style (→code-style rule), copy writing (→copy-writing rule)
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall