// Compress an MCP tools/list manifest so downstream agents see shorter tool descriptions without losing inputSchema semantics. Use before forwarding a large tools/list to a secondary agent or storing it in context.
| name | compress-mcp-manifest |
| description | Compress an MCP tools/list manifest so downstream agents see shorter tool descriptions without losing inputSchema semantics. Use before forwarding a large tools/list to a secondary agent or storing it in context. |
| version | 1.0.0 |
Use this skill when you have retrieved a tools/list response from an MCP
server and want to reduce the token cost of forwarding it to another agent,
storing it in memory, or including it in a prompt.
This is especially useful when orchestrating multi-agent pipelines where each sub-agent needs to know what tools are available but does not need the full verbose description of every parameter.
tools/list response from the target MCP server.gc_compress_manifest with the manifest as input:
{
"manifest": {
"tools": [{ "name": "...", "description": "...", "inputSchema": {} }]
}
}
{"input_tokens": N, "output_tokens": M, "savings_pct": P}.inputSchema is preserved byte-for-byte (JSON-equivalent). Schema
validation in downstream agents will not break.gc_compress_manifest is available on Pro and above. Free users will
receive an upgrade prompt.
Atlassian's mcp-compressor compresses tool schemas. gotcontext compresses
tool descriptions while preserving schemas, and also provides full payload
compression, OAuth 2.1 auth, usage telemetry, and self-hosted licensing —
a superset of what mcp-compressor offers.
Pre-flight check before sending an expensive LLM prompt. Returns a verdict (send_as_is, send_compressed, warn_context_limit, clear_first), the compressed prompt body inline, a cost preview against on-demand list pricing, and a cache hit likelihood. Use this skill whenever an agent is about to submit a prompt above ~1000 tokens or when context fill is unknown. Trigger phrases include "estimate cost before sending", "should I compress this prompt", "am I about to run out of context", "preview compression savings".
Compresses a git diff before review so noise (lockfile bumps, generated files, whitespace churn) doesn't crowd out the actual logic changes. Use this skill whenever the user asks you to review a pull request, explain a diff, summarize changes, or comment on recent commits. Trigger phrases include "review this PR", "what changed", "explain this diff", "summarize the changes", "look at my diff", "check this branch against main". Uses gotcontext's code-aware compression at fidelity=detailed — detailed because a character dropped in a security fix matters more than a character dropped in prose.
Compress a session's conversation history into a portable summary that can be re-injected after /clear. Use this skill when context is filling up and the agent needs to recover state after clearing. Works even when Claude Code's own auto-compact has failed because gotcontext runs the summarization on its own infra. Trigger phrases include "summarize this session", "I need to clear context but keep what we built", "compact failed help me recover", "save this conversation before reset".
Bulk compression of a file corpus — up to 50 documents per call — for later queries rather than one-off reads. Use this skill whenever the user wants to pre-process a directory, a support-ticket dump, meeting notes, or any sizable corpus before Q&A. Trigger phrases include "compress all these files", "pre-process this corpus", "shrink everything in /path", "bulk-compress for Q&A", or when onboarding Claude to a large project that needs a lot of ingested context. Submits an async job to gotcontext's batch queue and returns a job id; the job processes in the background with per-item error reporting so one bad file doesn't block the batch. Pro, Team, or Enterprise plan required.
Extracts the public API of a codebase — class names, function signatures, exported types, module docstrings — without loading every file. Use this skill whenever the user asks to understand, explore, navigate, or describe a codebase, library, repository, or package at the overview level. Trigger phrases include "help me understand this codebase", "what does this library do", "what's the API of X", "how is this project structured", "give me an overview of Y", "explain this repo". Calls gotcontext's AST-aware skeleton extraction so you read the shape of the code, not the implementation bodies.
Query-guided compression of a documentation site, docs folder, README, wiki, or specification for Q&A. Use this skill whenever the user points you at multi-page reference material and wants to find something in it. Trigger phrases include "help me find X in these docs", "what does the Y docs say about Z", "search the Stripe/AWS/Anthropic docs for", "summarize this reference", "check the docs for". Passes the user's question as a query parameter so gotcontext weights relevant sections heavier and compresses off-topic sections more aggressively — keeps answers grounded without loading every page.