Compress verbose text into token-efficient pseudo-code
View on GitHubEladAriel/pseudo-code-prompting-plugin
pseudo-code-prompting
February 1, 2026
Select agents to install to:
npx add-skill https://github.com/EladAriel/pseudo-code-prompting-plugin/blob/main/skills/context-compressor/SKILL.md -a claude-code --skill context-compressorInstallation paths:
.claude/skills/context-compressor/# Context Compressor
Convert verbose requirements into concise pseudo-code format.
## WHAT THIS DOES
Transforms long-winded descriptions into compact function-call syntax:
```text
Before (150 tokens):
"We need to build a user authentication system. It should support
multiple providers like Google and GitHub. Users should be able
to sign in with OAuth. We need JWT tokens that expire after 1 hour.
Also add refresh token support. Make sure passwords are hashed."
After (35 tokens):
implement_auth(
type="oauth",
providers=["google", "github"],
tokens={"type": "jwt", "expiry": "1h", "refresh": true},
password_hashing="bcrypt"
)
```
**Compression: 76% reduction**
## COMPRESSION RULES
### Rule 1: Extract Actions → Function Names
```text
"Build a REST API" → build_rest_api(...)
"Add user authentication" → add_authentication(...)
"Implement caching" → implement_caching(...)
```
### Rule 2: Extract Details → Parameters
```text
"Support Google and GitHub" → providers=["google", "github"]
"Expire after 1 hour" → expiry="1h"
"Use Redis for caching" → cache_type="redis"
```
### Rule 3: Group Related Info → Objects
```text
"JWT tokens that expire after 1 hour with refresh support"
→ tokens={"type": "jwt", "expiry": "1h", "refresh": true}
```
### Rule 4: Remove Filler Words
Remove: "we need to", "should", "make sure", "also", "it would be nice"
## OUTPUT FORMAT
```text
# Compressed Pseudo-Code
[function_call]
## Compression Stats
Original: [N] tokens
Compressed: [N] tokens
Reduction: [N]% ([N] tokens saved)
```
## EXAMPLE
### Input (Verbose)
```text
We're building a task management application. Users should be able
to create, read, update, and delete tasks. Each task has a title,
description, due date, and priority level. We need to implement
user authentication so only logged-in users can access their tasks.
Use JWT tokens for authentication. The API should be RESTful with
proper HTTP status codes. We also need to add input validation to
make sure tas