plugins/rephrase/skills/distil/SKILL.md
Rewrite a piece of text down to its core message, dropping whatever is peripheral to it — the result is the text itself rewritten shorter, not a summary written about it. Use when the user explicitly asks to distil, cut to the essentials, trim the fat, or strip a passage, document, or draft down to what matters, and is willing to lose secondary detail. Do not trigger as unprompted cleanup of text the user has not asked to change; when the user wants the text shorter but every point kept, use the tighten skill instead.
npx skillsauth add shihyuho/skills distilInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Re-examine a passage and rewrite it down to its core message. Peripheral content is dropped on purpose — distilling is lossy by design.
The user identifies the target — pasted text, a file path, or a passage in this conversation. If they invoke the skill without naming one, distil the last substantial passage you wrote. Ask only if the target is genuinely ambiguous.
A verbose passage does not get tighter by editing in place. Each editing pass tends to add a caveat or a transition and remove nothing, so length compounds. Do not patch the existing wording. Work out what the passage actually says, separate the core message from what merely supports or decorates it, then re-express the core from scratch in the fewest words that still land it.
Decide what counts as peripheral yourself and cut it directly, without pausing to confirm each cut — being trusted with that judgement is the point of this skill. Peripheral means secondary examples, asides, caveats that do not change the conclusion, and background the reader does not need; the core is what the passage would be useless without.
Do not chase a percentage. Distil to what matters and stop; a fixed ratio just forces arbitrary cuts or padding.
When the rewrite is done, read the original once more and confirm the core survived and nothing kept was distorted. Adjust if so.
Give the rewritten text, then a short report:
development
--- name: artifact-anatomy description: Defines where spec-driven working artifacts — the spec (e.g. `SPEC.md`), the plan, and the task list (e.g. `tasks/plan.md`, `tasks/todo.md`) — live on disk under `docs/specs/<id>-<slug>/`, and how those directories are numbered, scoped, and resolved so multiple specs can run in parallel without overwriting one another. Use this BEFORE creating, locating, or updating any spec, plan, or task/todo file: whenever a spec/plan/build workflow writes these artifac
development
Write a short author's briefing to hand to a code reviewer whose agent already has its own review skill, so it supplies the context that skill can't see instead of repeating how to review. Right after you finish a piece of work, it mines this session (and any kickoff implementation-notes) for what the reviewer most needs flagged — the easy-to-miss changes, the parts you're least sure about, the looks-wrong-but-intentional bits, and the blast radius — plus the exact commit range to review. Use when you've just finished work and want to hand the review off to another agent, chat, or teammate, when you want a "heads-up for the reviewer", or when packaging a change for review elsewhere. It does not perform the review and does not re-specify severity tiers or output format — that's the reviewer's own skill's job.
testing
Use when creating, rewriting, pruning, or reviewing `AGENTS.md` or `CLAUDE.md`, especially to remove repo summaries, stale rules, and other low-signal global instructions. Trigger when deciding what belongs in always-on agent files versus a task-specific skill.
development
Drive a structured tutoring workflow that turns Claude into a learning onramp accelerator — consultative diagnosis → custom syllabus → unit-by-unit guided lessons with notes/whiteboard → dynamic adjustment from an accumulating learner profile. Use when the user states a learning goal ("I want to systematically learn X", "teach me Y", "help me prep for Z exam"), uploads study materials and asks for a course plan, or signals sustained guided study (mentions tutor, syllabus, course, lessons, study plan, curriculum, 家教, 學習路徑). Skip for one-shot factual Q&A or quick code-context explanations.