Kharmanskyi Agent Skills
7 skills published by kharmanskyi across 1 repository. Together they weigh 19 848 tokens — that is what loading all of them at once would cost you in context.
7 skills 19 848 tokens total
>- ALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words" - or ask if something is worth doing or if something simpler would do, in any language. Rewrites the question in plain words and always ends with one marked recommendation. A simpler substitute, extra work later, lock-in, over-engineering, easy to undo. Doing nothing is always weighed.
>- ALWAYS invoke this skill when the user asks about work done outside this session - "check work", "check the others", "check other sessions" - or to each part against machine state, name every gap between claimed and true. Verified-ready work merges in the same pass. End with what is left, one next step, and any reply another session needs, ready to paste.
>- ALWAYS invoke this skill when work wraps up or the user asks how it went - "done or not", "are we done", "what happened", "report" - in any language, and when a Stop hook asks for a session report. Produces a ten-line plain- anything needed from you, new debt, safe to close. Every "yes" names its proof; unverified says "not checked". Saves the report so the next session starts from it instead of re-exploring the repo.
>- ALWAYS invoke this skill when the user asks for simpler or shorter about something said or written - "say it simply", "what does this mean", "I don't understand your answer", "too long", "wait, what?", "bro" - in any error. "I don't understand what to DO" is os-step-by-step; this skill the point, keeps every number, warning and caveat - no facts added, no bad news dropped. A number returns exactly that many points, most important first.
>- ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something "what do I do", "what should I do", "I don't understand what to do", "explain what I need to do", in any language. Picking which task comes next is os-whats-next; this skill is for doing the thing in front of you. First only they can do. Then one action per step, commands labelled by what they touch, no jargon. Commands are single lines that prompt for any value - typing hidden for secrets - and confirm in plain words. Afterwards verify their step.
>- ALWAYS invoke this skill before anything hard to undo gets agreed to - a contract, a purchase, a migration, a launch, a price change, a reorganisation - and whenever the user asks "what could go wrong", "what are we missing", "poke holes in this", or for a premortem or a red team, in any language. Assumes the decision already failed and works backwards to find out why, in a fresh agent that had no hand in making it. Sweeps nine areas go ahead, go but fix these first, try it small first, think again, do not do this.
>- ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is os-step-by-step. Reads the last report, local changes, verified-ready pull requests merge in the same pass. Then sorts the rest into doable-alone and needs-you, ending with one recommended next task in plain words - what it closes or unblocks. Never invents tasks.