AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Compress Context

skill-0-uddeshya-0-agent-skills-compress-context · by 0-uddeshya-0

A Claude skill from 0-uddeshya-0/agent-skills.

No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-0-uddeshya-0-agent-skills-compress-context

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-0-uddeshya-0-agent-skills-compress-context)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Compress Context? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

skill: compress-context

purpose

Shrink a long conversation or document context 60–75% while keeping everything needed for the current task. Prevents token bloat across multi-turn sessions without losing decisions or facts.

whentouse

  • Conversation exceeds ~3,000 tokens and will continue for more turns
  • Passing context from one agent step to the next and most of it is irrelevant
  • Long document needs repeated reference across multiple calls

whennotto_use

  • Context is under 1,000 tokens — overhead not worth it
  • Task requires verbatim quoting (legal, transcription)
  • First turn — nothing to compress

input

context: string        # Full context to compress
current_task: string   # What the agent needs to do next — determines what's relevant

output

{
  "compressed": "string",
  "original_tokens": "int  // estimate",
  "compressed_tokens": "int  // estimate",
  "dropped": ["category of removed content"]
}

instructions

First check: if context is under ~1,000 tokens, return it as-is with a note that compression overhead isn't worth it at this size.

Compress context for a specific task. Keep only what is needed to complete that task.

Rules:
1. Convert verbose explanations to one-line facts
2. Remove pleasantries, filler, agent meta-commentary ("Sure, I'd be happy to...")
3. Merge repeated or restated information into one canonical statement
4. Remove content that does not affect the current task
5. Preserve: decisions made, data values, constraints, errors, user preferences stated
6. Use shorthand: "User: cancel sub" not "The user indicated they would like to cancel their subscription"

Never drop decisions, confirmed facts, active constraints, or error states.
Never hallucinate — if uncertain whether something is relevant, keep it.
Target 60–75% reduction. More than that risks losing signal.

Return JSON only.

constraints

  • Max output tokens: 600
  • Never drop: decisions, confirmed facts, constraints, errors
  • Never compress below 25% of original — over-compression loses signal

example

Input:

context: "User: Hi, trouble with my account. Agent: Happy to help! What's the issue? User: API key stopped working. Been using it 6 months. Agent: Can you share first 6 chars? User: sk-abc1. Agent: Key was revoked Jan 14 due to billing issue — card 4242 declined. User: Card expired. Updated it, new card ends 9191. Agent: Payment should process in 2–15 min, key reactivated then. User: How long exactly? Agent: Usually 2–5 min, up to 15."
current_task: "Check if the API key has been reactivated"

Output:

{
  "compressed": "API key sk-abc1*** revoked Jan 14 — failed payment (card 4242 expired). User updated to card 9191. Reactivation pending, expected 2–15 min. Task: check reactivation status.",
  "original_tokens": 120,
  "compressed_tokens": 38,
  "dropped": ["pleasantries", "back-and-forth confirmation dialogue", "agent offers"]
}

feedback_log

2026-05-29 | invoked on a 3-turn conversation (~180 tokens) | ran full compression pipeline on trivially small context, added overhead for no gain | added: early-return guard in instructions — skip compression if context < ~1,000 tokens

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.