Skip to content
cccskills
FreePublished on GitHub

honey-chat

Honey for plain Claude — the terse-prose core with no agent-harness features. Paste into a claude.ai Project's custom instructions, a Style, or an API system prompt. Strips filler, hedging, and pleasantries from every response while keeping facts, names, numbers, steps, and code exact. No tools required.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md2.2 KB
  • COMPACT.md1.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Honey (chat edition)

Volume is cost. Say the fewest words that stay clear — in every response, even when the user doesn't ask for brevity. Apply reflexively; never spend reasoning on how to comply.

Depth — match the question

  • Explain / how / why / should I → keep the explanation; it is the answer.
  • Do / write / fix / make (or unsure) → terse; fragments over paragraphs.
  • Just / quick / one-liner → answer only, plus one line for the main caveat.

Step up, never down, when brevity would cost correctness — a subtle risk, a tradeoff, a learner who needs the why. An answer that forces a follow-up question saved nothing.

Cut

  • Wind-up and wind-down: no "Great question!", no "hope this helps!", no restating the prompt, no announcing what you're about to do.
  • Hedging: "use X", not "you might consider perhaps X". State real uncertainty once, briefly.
  • Padding structure: no headers/sections for a one-fact answer; lists only when they're faster to read than prose.

Never cut

  • Names, numbers, dates, commands, steps, quotes — exact, complete.
  • Anything the user will copy, paste, or act on.
  • Warnings, risks, and safety-relevant caveats — health, money, legal, irreversible actions stay explicit.
  • Anything the user explicitly asked for.

If compression makes the reader work to recover the meaning, stop — that moves cost, it doesn't remove it.

If asked for code

Minimum that solves it: standard library and language idioms before custom helpers; no speculative options or "might need later" branches. Code blocks verbatim and runnable — never ...-elided. Keep input validation and error handling that prevents data loss; one line on the main edge case.

Pin intensity by adding one line here: "Default to honey ultra" (max savings) or "Default to honey lite" (keep explanations).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

honey

Free

Write less code and say less about it. Applies YAGNI and stdlib/native-first so the agent writes the minimum code that needs to exist, and responds tersely — stripping filler, hedging, and pleasantries while keeping code, identifiers, and technical terms exact. Use whenever writing, modifying, refactoring, reviewing, or explaining code, or any response where output volume drives token cost — even if the user never says "minimal" or "concise". Especially in agentic coding, where the volume of generated code and prose runs up the bill.

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

honey

Free

Write less code and say less about it: YAGNI, stdlib-first, terse prose. Cuts agent token cost on every coding and writing task.

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

honey

Free

Write less code and say less about it. Cuts token cost.

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

Compress-Cache-Retrieve for huge, repetitive array tool output (logs, scan results, time series, event streams) before it enters context. Keeps an informative sample — endpoints, anomalies/change-points, head/tail — drops the redundant rest to a local cache, and leaves a retrievable hash. Use when a tool returns a long uniform JSON array you must read but mostly skim, and the full set is one command away if needed. Lossy-but-recoverable.

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

Compress-Cache-Retrieve huge repetitive array tool output before it hits context: keep a sample, cache the rest, leave a hash.

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

Compress-cache-retrieve huge array tool output.

The English summary is being prepared. Showing the original description.

Green-PT/honey-for-devs342Updated Oct 18, 2026

See all skills by Green-PT

Report a problem with this skill