agentsclimarketplace

Cavemenko compress

Skill ruslanlap/cavemenko/skills/cavemenko-compress

Compress documents, notes, specs to ultra-short version. Use when user asks to compress, shorten, or summarize text, or calls /cavemenko-compress.From its SKILL.md

Install
npx -y skills add ruslanlap/cavemenko --skill cavemenko-compress

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, as published. Nobody here has run it

Compress provided text to minimum size. Keep ALL key info. Target: ≤30% of original length.

Rules

  1. Apply ALL cavemenko compression techniques simultaneously
  2. Use abbreviations aggressively: БД, API, UI, auth, config, env, deps, etc
  3. English terms where shorter: deploy, fix, run, check, update, delete
  4. Arrows for causality: X → Y → Z
  5. Numbers always as digits
  6. Drop ALL filler, hedging, politeness, repetition
  7. Merge related points into one line
  8. Tables > paragraphs where applicable

Keep

  • Numbers, dates, deadlines
  • Names, identifiers, URLs
  • Tech terms exactly
  • Code snippets verbatim
  • Action items / decisions

Drop

  • Introductions ("В цьому документі...")
  • Conclusions ("Підсумовуючи...")
  • Repetition of same point in different words
  • Hedging ("можливо", "ймовірно")
  • Politeness ("будь ласка зверніть увагу")
  • Obvious context

Example

Input:

Шановні колеги! Хотілося б звернути вашу увагу на те, що в нашому проєкті
виникла досить серйозна проблема з продуктивністю бази даних. Після проведення
детального аналізу було встановлено, що основною причиною є відсутність індексів
на таблиці users для полів email та created_at. Рекомендується якнайшвидше додати
відповідні індекси, оскільки це може призвести до серйозних проблем у production.

Output:

БД perf issue: missing indexes on `users` (email, created_at). Add ASAP — prod risk.

Process

  1. Read full text
  2. Extract key facts, decisions, action items
  3. Apply all compression techniques
  4. Output compressed version
  5. If asked — show compression ratio

Keep looking

Skills are one crate of 610,045. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.