playbooks

home / skills / nickcrew / claude-cortex / token-efficiency

token-efficiency skill

/skills/token-efficiency

This skill enables concise communication using symbolic notation to optimize token usage in limited-context workflows.

npx playbooks add skill nickcrew/claude-cortex --skill token-efficiency

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.3 KB
---
name: token-efficiency
description: Compressed communication using symbols and abbreviations. Use when context is limited or brevity is needed.
---

# Token Efficiency

Compressed communication for limited context windows.

## Symbol System

### Logic & Flow
| Symbol | Meaning |
|--------|---------|
| → | leads to, implies |
| ⇒ | transforms to |
| ← | rollback |
| & | and |
| \| | or |
| » | sequence/then |
| ∴ | therefore |
| ∵ | because |

### Status
| Symbol | Meaning |
|--------|---------|
| ✅ | complete/pass |
| ❌ | failed/error |
| ⚠️ | warning |
| 🔄 | in progress |
| ⏳ | pending |

### Domains
| Symbol | Domain |
|--------|--------|
| ⚡ | performance |
| 🔍 | analysis |
| 🛡️ | security |
| 🏗️ | architecture |

## Abbreviations
- `cfg` config
- `impl` implementation
- `deps` dependencies
- `val` validation
- `perf` performance
- `sec` security
- `err` error

## Examples

**Standard:**
> "The authentication system has a security vulnerability in the user validation function"

**Compressed:**
> `auth.js:45 → 🛡️ sec risk in user val()`

**Standard:**
> "Build completed, now running tests, then deploying"

**Compressed:**
> `build ✅ » test 🔄 » deploy ⏳`

## When to Use
- Context >75% full
- Large codebase analysis
- Complex multi-step workflows
- User requests brevity

Overview

This skill compresses communication using a compact symbol and abbreviation system to save tokens and speed comprehension. It is designed for contexts with limited window size or when concise, machine-friendly messages are required. The system encodes logic, status, domains, and common terms into short symbols and shorthand. Use it to reduce verbosity without losing structured meaning.

How this skill works

The skill maps common concepts to a small set of symbols (arrows, status icons, domain markers) and abbreviations (cfg, impl, deps, val, perf, sec, err). It transforms full sentences into compact lines that preserve intent and flow, like sequencing (»), implications (→), and domain tags (🛡️ for security). It supports status tracking (✅, 🔄, ❌) and compact conditionals (|, &). Outputs are single-line, readable tokens suitable for logs, CLIs, and terse reports.

When to use it

  • When context is already >75% known and you need brevity
  • Large codebase scans or automated analysis summaries
  • Pipeline and CI logs to reduce noise and token cost
  • Multi-step workflows where sequence and status matter
  • CLI tools, TUI displays, or chat systems with tight limits

Best practices

  • Keep compressed lines independent and self-contained where possible
  • Include a legend in initial session or help command for new users
  • Use domain symbols to prioritize attention (e.g., 🛡️ for security)
  • Prefer consistent abbreviations (cfg, impl, deps, val) across teams
  • Avoid over-compression when clarity for non-experts is required

Example use cases

  • CI output: build ✅ » test 🔄 » deploy ⏳
  • Security alert: auth.js:45 → 🛡️ sec risk in user val()
  • Performance note: cache.impl → ⚡ perf boost after cfg change
  • Debug snapshot: payment svc ← rollback ⏳ due to err 502
  • Analysis summary: scan ⇒ 🔍 coverage low ∴ add tests

FAQ

Will newcomers understand the symbols?

Provide a one-time legend or help command; frequent users learn the symbols quickly.

When should I avoid token compression?

Avoid it for external documentation, onboarding docs, or when full narrative context is required.