Trim

Cut a document down to its load-bearing ideas. This skill is not for summarizing and not for rewriting in a different style. It removes the parts that make readers stop reading, in the author's own words.

Resolving the target file

The user runs /trim with an optional file path. Resolve in this order:

1. Argument given, path exists, file is text → use it.
2. Argument given, path does not exist → ask the user to confirm the path. Do not search the filesystem.
3. No argument → ask the user which file to trim. Do not guess from cwd or recent edits.
4. User pasted raw text instead of a path → offer to save it to /tmp/trim-input-<unix_epoch>.md first, then proceed against that file.
5. File is binary, a data file, or source code (detect via extension: .png, .jpg, .pdf, .zip, .csv, .json, .py, .ts, .go, etc., or by reading the first 4KB and seeing non-text bytes) → abort with a one-line note. This skill is for prose.

Workflow

1. Read and size the document

Read the entire file into the parent context only long enough to size it and forward to the sub-agent. Do not analyze it here.