roles/omp/files/skills/semantic-compression/SKILL.md
Aggressively remove grammatical scaffolding LLMs reconstruct while preserving meaning-carrying content. Output may be fragments. Use when compressing text for prompts, reducing token count, preparing context for LLM input, or making documentation more token-efficient. Applies LLM-aware compression rules that delete predictable grammar while preserving semantics.
npx skillsauth add techdufus/dotfiles semantic-compressionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
LLMs reconstruct grammar from content words. Remove predictable glue; keep semantic payload. Prefer fragments over sentences.
Tier 1 — Always delete (even if fragments):
Tier 2 — Delete unless meaning changes:
Tier 3 — Delete only if relation still clear:
| 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 |
testing
Preparing and creating git commits when explicitly requested; covers staged diff review, secrets checks, and conventional commit messages.
testing
Verifying implementation work before claiming completion; covers tests, affected artifacts, evidence, and unresolved risks.
testing
Use when the user explicitly invokes $work or asks for execution strategy for complex engineering work with unclear scope, dependent steps, or separable workstreams.
testing
Extract the underlying intent behind a request, issue, PR, or diff. Focus on problem and desired outcome; do not propose implementation, testing strategy, or rollout plans.