Semantic Compression
- 1 installs
- 21.9k repo stars
- Updated August 5, 2026
- can1357/oh-my-pi
Semantic Compression is an agent skill that removes predictable grammar while preserving semantics—usable whenever a solo builder needs to shrink LLM prompts and context before committing tokens.
About
Semantic Compression is an agent skill that strips predictable grammatical scaffolding from text while keeping meaning-bearing words, so developers can feed models smaller prompts and context windows without losing intent. It follows an aggressive compression stance: output may be fragments, deletion is the default, and function words stay only when removing them would change meaning. Tier 1 always removes articles, copulas, expletive openings, pure intensifiers, and obvious filler; Tier 2 trims auxiliaries and modals unless tense or modality matters. Use it whenever you are preparing LLM input, trimming long README or spec paste-ins, or tuning documentation for repeated agent runs. It is procedural knowledge packaged as SKILL.md—not a hosted API—so it runs inside your agent session with no extra permissions. Journey-wide placement reflects that any phase (idea notes, validate specs, build tickets, ship runbooks) benefits from leaner context before the model reads it.
- Two-tier deletion rules (always-delete vs delete-unless-meaning-changes) for articles, copulas, filler, and intensifiers
- Aggressive fragment output: noun stacks, list fragments, label:value—no requirement for full sentences
- LLM-aware stance: drop grammar LLMs reconstruct; keep semantic payload and timeline-critical tense
- Built for token reduction on prompts, bundled context, and token-inefficient documentation
Semantic Compression by the numbers
- 1 all-time installs (skills.sh)
- Ranked #14,102 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/can1357/oh-my-pi --skill semantic-compressionAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 21.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 5, 2026 |
| Repository | can1357/oh-my-pi ↗ |
What it does
Shrink prompts, specs, and docs before sending them to Claude, Codex, or Cursor without losing meaning.
Who is it for?
Best when you repeatedly paste specs, docs, or logs into agents and want a consistent compression ritual before each session.
Skip if: Human-facing copy that must stay grammatically polished, legal text where every auxiliary matters, or content where tone and cadence are the deliverable.
When should I use this skill?
Compressing text for prompts, reducing token count, preparing context for LLM input, or making documentation more token-efficient.
What you get
You get shorter, fragment-style text that preserves meaning for the model, with lower token use on the next agent turn.
- Compressed fragment-style text preserving semantic payload
- Token-reduced prompt or context block ready for LLM input
By the numbers
- Two deletion tiers: Tier 1 always-delete and Tier 2 delete-unless-meaning-changes
Files
Semantic Compression
LLMs reconstruct grammar from content words. Remove predictable glue; keep semantic payload. Prefer fragments over sentences.
Aggressive Stance
- Output can be noun/verb stacks, list fragments, or label:value phrases.
- Default to deletion; keep function words only when loss changes meaning.
- Prefer base verb forms; drop tense/aspect unless timeline is critical.
Deletion Tiers
Tier 1 — Always delete (even if fragments):
- Articles: a, an, the
- Copulas: is, are, was, were, am, be, been, being
- Expletive subjects: "There is/are...", "It is..."
- Complementizer: that (as clause marker)
- Pure intensifiers: very, quite, rather, really, extremely, somewhat
- Filler phrases: "in order to" → to, "due to the fact that" → because, "in terms of" → delete
- Infinitive "to" before verbs (unless it prevents noun/verb confusion)
- Conjunctions when list/contrast obvious: and, or, but
Tier 2 — Delete unless meaning changes:
- Auxiliary verbs: have/has/had, do/does/did, will/would (keep if tense/aspect matters)
- Modal verbs: can/could/may/might/should (keep when obligation/permission/possibility is critical; always keep must/must not)
- Pronouns: it/this/that/these/those/he/she/they (drop when referent obvious; replace with noun if ambiguous)
- Relative pronouns: which, that, who, whom
- Prepositions: of, for, to, in, on, at, by (keep for material, direction, agency, or disambiguation)
Tier 3 — Delete only if relation still clear:
- Remaining prepositions: with/without, between/among, within, after/before, over/under, through (drop only if relation obvious)
- Redundant adverbs: "shout loudly" → "shout"
Always Preserve
- Nouns, main verbs, meaning-bearing adjectives/adverbs
- Numbers, quantifiers: "at least 5", "approximately", "more than"
- Uncertainty markers: "appears", "seems", "reportedly", "what sounded like"
- Negation: not, no, never, without, none
- Temporal markers: dates, frequencies, durations
- Causality and conditionals: because, therefore, despite, although, if, unless
- Requirements/permissions: must, required, prohibited, allowed
- Proper nouns, titles, technical terms
- Prepositions encoding relationships: from/to (direction), with/without (inclusion), between/among/within (relation), after/before (temporal), by (agent if passive)
Structural Compression
- Passive → active when agent known: "was eaten by dog" → "dog ate"
- Nominalization → verb: "made a decision" → "decided"
- Drop implied subject when context allows: "System should log errors" → "Log errors"
- Redundant pairs → single: "each and every" → "every"
- Clause → modifier: "anomaly that was reported" → "reported anomaly"
Examples
| Original | Compressed |
|---|---|
| The system was designed to efficiently process incoming data from multiple sources | System design: efficient process incoming data, multiple sources |
| There were at least 20 people who appeared to be waiting | At least 20 people apparent waiting |
| It is important to note that the medication should not be taken without food | Medication: should not take without food |
| The researcher made a decision to investigate the anomaly that was reported | Researcher decided: investigate reported anomaly |
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Use instead of manual “delete fluff” editing in chat when you want repeatable LLM-aware deletion tiers in a skill.
FAQ
Who is semantic-compression for?
Developers using Claude Code, Cursor, Codex, or similar agents who need smaller prompts and context bundles without rewriting meaning by hand.
When should I use semantic-compression?
During build agent-tooling when trimming implementation context; during validate when condensing scope notes for a planning agent; during ship when compressing long test or review logs; during operate when summarizing incident threads for the next diagnostic turn; and anytime you
Is semantic-compression safe to install?
It is text-transformation guidance with no shell or network requirements by default; review the Security Audits panel on this Prism page before trusting any third-party skill package in your repo.