lilmgenius/paperthin

re0

Refresh an existing artifact into the current best v0.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/lilmgenius/paperthin --skill re0

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Refresh the target artifact as if it were the first clean version.

Goal

Make the artifact lighter, more current, and more accurate. It should read as a clean version without changelog language, cleanup notes, or patches over an older draft.

Workflow

  1. Identify the target from the user's request or active context.
  2. Read it end to end before editing.
  3. Check nearby artifacts that must stay aligned.
  4. Remove scaffolding residue, stale deltas, duplicated process noise, deprecated information, and over-specific history.
  5. Fold durable lessons into the place they should have lived from the start.
  6. Rewrite instead of appending when appending would preserve noise.
  7. Preserve useful voice and structure; simplify everything else.
  8. Smooth prose: give an interrupting parenthetical its own clause or cut it, keep nearby repeated words or points once, and remove padding that adds no meaning.
  9. Smooth source text: decide whether the artifact's paragraphs and list items should each sit on one source line, matching sibling formatting. Where they should, run node scripts/unwrap.mjs <paths...> [--json] [--write] from this skill's folder: it lists each hard-wrapped paragraph or list item (file, start line, line count), exits 3 when it finds any, and with --write joins them only after proving the words and every fenced block unchanged. Make pointers to named sections or files followable, using links where supported.
  10. Re-read the result and cut again.

Rules

  • Refresh to the current best v0. Within the de- family, remove shape-class machine-writing tells by rewriting across sentence boundaries. Never compress for its own sake or edit punctuation choice alone; the punctuation pass runs after any rewrite. Report an unsourced claim as an observation; never delete it or invent a source.
  • A pass that finds nothing to genuinely improve changes nothing.
  • Prefer editing existing sections over adding new ones.
  • Convert "what changed" into "what is true now".
  • Keep only details that improve future execution, accuracy, or recall.
  • Do not leave old/new traces unless the artifact is explicitly a changelog.
  • Fix machine-clear residue and surface judgment calls. Never auto-resolve ambiguity or "fix" a deliberate look-alike.
  • Repair from the canonical or sibling source of truth, not the damaged surface. Edit safely: assert the target exists and report a MISS rather than a silent no-op; read and write files as UTF-8 (PYTHONUTF8=1 for Python), replace positional targets per occurrence rather than by blanket sweep, and script large structural moves.
  • Do not create extra files unless the user asks.

Verification

A fresh reader sees a clean v0 with no trace of the older draft or signs of patching. If unsure, re-read as a stranger with no prior context. Report the noise removed and the durable truth kept.

dallo stesso repository

Altri Skills

Tutti gli Skills
lilmgenius
Community

re0-order

Move items only, reword nothing; realign a listing whose order has gone arbitrary (a list, table, catalog, sections, an enum) into a logical sequence under one stated principle. Nothing is added or removed. Use when the user names a listing, or a scope holding one, whose order no longer helps a reader follow the set, or when a pipeline the user invoked passes that scope on. Acts only inside that scope.

Installazioni / 1h
5
GitHub Stars
1,5K
Aggiornato
15 nov
lilmgenius
Community

readback

Verify the model's understanding of a user's instruction before spending non-trivial work. Use when a request is long, bundled, high-stakes, hard to undo, or has ambiguous scope or referents such as this, that, it, the other one, whatever is cleaner, or whichever order makes sense. Restate internally, cross-check against available context, proceed silently when resolved, and surface only a genuine surviving fork.

Installazioni / 1h
5
GitHub Stars
1,5K
Aggiornato
15 nov
lilmgenius
Community

whychk

Right after you pick an option, have a fresh outsider find the sharpest gap in the choice, then explain that gap in your own words, one gap at a time.

Installazioni / 1h
5
GitHub Stars
1,5K
Aggiornato
15 nov
lilmgenius
Community

aim

When data lands with a thin ask (files, a repo, a paste, a chat scrollback), read it and propose what the user is trying to do with it for them to confirm. Use the moment material arrives without a fully-formed ask, or when the ask reads thinner than the data suggests.

Installazioni / 1h
4
GitHub Stars
1,5K
Aggiornato
15 nov