使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/lilmgenius/paperthin --skill re0開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
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
- Identify the target from the user's request or active context.
- Read it end to end before editing.
- Check nearby artifacts that must stay aligned.
- Remove scaffolding residue, stale deltas, duplicated process noise, deprecated information, and over-specific history.
- Fold durable lessons into the place they should have lived from the start.
- Rewrite instead of appending when appending would preserve noise.
- Preserve useful voice and structure; simplify everything else.
- 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.
- 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--writejoins them only after proving the words and every fenced block unchanged. Make pointers to named sections or files followable, using links where supported. - 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=1for 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.