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.
LilMGenius · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add LilMGenius/paperthin --skill aimAbout this skill
name: aim description: "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."
Read the data and propose the intent behind it, for the user to confirm.
Goal
Give the user a proposal to confirm, revise, or reject. Never make them compose an answer from scratch: proposing lets them answer yes to an intent they had not yet put into words. If they still have to write that intent themselves, the skill missed.
Workflow
- Read every piece of the handed-over data end to end before proposing anything.
- State the intent you read in one line grounded in what the data shows.
- Briefly state what you would do next on that intent.
- Ask only for confirmation: right, wrong, or adjust.
Rules
- Read before proposing. A proposal without reading is a guess.
- Ground it in the data. Point at what you read, not what you assumed.
- One intent per turn. If two are plausible, propose the likelier and name the other in a clause.
- Confirm, don't compose. If the turn ends with the user assembling a sentence, redo the proposal.
- If the data is too thin to propose from, say so and stop. Do not fall back to asking.
Verification
The user's next reply is short: a yes, a correction, or a small adjustment. If they had to explain what they wanted from scratch, the proposal was wrong or was a question in disguise.