green-pt/honey-for-devs

honey-compress

>- Rewrite a memory or context file (CLAUDE.md, AGENTS.md, a todo or notes file) into Honey-terse form so it costs fewer input tokens every session, without losing meaning. Backs up the original first. Use when asked to shrink or compress context files, trim CLAUDE.md, or cut per-session input cost. Prose only — never code, config, or data.

First seen Jun 26, 2026

Installation

$ npx skills add green-pt/honey-for-devs --skill honey-compress

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from green-pt/honey-for-devs · top by installs.

npx skills add green-pt/honey-for-devs

Browse all from green-pt/honey-for-devs

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 287
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,739 B
  • docs SUMMARY.md 363 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 33 installs

SKILL.md

Honey Compress

Apply Lever 2 to a file the agent re-reads every session. The cheapest token is the one not re-sent — a one-time rewrite that saves on every future load.

Do

  1. Back up first. Copy FILEFILE.original.md. If that backup already exists, stop and ask — never clobber a restore point. If no backup can be written, refuse.
  2. Rewrite the prose tersely — drop wind-up, hedging, narration, and redundancy; fragments over paragraphs; merge guidance that repeats.
  3. Preserve every distinct instruction — terser words, identical rules. If unsure whether a line changes behavior, keep it verbatim.
  4. Report original vs new line/byte count and the backup path.

Keep exact — never compress

  • Code blocks, commands, paths, identifiers, versions.
  • Any load-bearing directive — MUST/NEVER rules, and anything touching auth, secrets, money, migrations, or deletes. Compressing an instruction that changes behavior moves cost, it doesn't remove it.

Don't

  • Don't touch code, config, or data files — prose context only.
  • Don't merge two rules into one if they differ in effect.
  • Don't compress a file you can't back up.

Boundaries

Reversible by design — FILE.original.md is the restore path. Verify the rewrite still carries every rule before reporting done.