upskill reads every prompt you typed to coding agents on one project, together with the project’s commits, pull requests and CI runs, and counts where your time and patience went. It ranks proposals by what each pattern cost you to recover from, and backs each with a count and dated quotes.
It chooses the lightest mechanism that would hold, from a failing check up to a skill or scheduled run, drops what is already covered, and then builds the ones you pick. You invoke it yourself by command, and a run is meant to take a while.
What You Get
- A report that opens with findings, each with a count of its own and dated quotes
- Numbered proposals ordered by cost, each marked small, medium or large, with some marked confirm first
- A short list of out-of-the-box ideas labelled as guesses, plus what the run would not build and why
- Built tools: skills, hooks, scripts or agent-doc rules placed by the project’s own conventions
- A scorecard in later runs showing whether each earlier tool reduced the pattern it targeted
Common Use Cases
- Finding the corrections you repeat to an agent and turning them into a hook or a rule
- Replacing a step-by-step procedure you dictate weekly with a skill
- Spotting CI failures and fix-up commits that a pre-commit check would catch
- Auditing which installed skills never get used
What Makes It Unique
Proposals rest on counts from the full history and the project record, and the agent re-counts anything a reader reported. A ladder of mechanisms from a failing check to a subagent makes it pick the lightest fix, and a rejection pass asks whether the pattern was the person exploring and not the agent failing. It also keeps your history local: working files go in a git-excluded folder with secrets masked.
Under The Hood
The skill is written instructions plus two reference files, one with the places each agent harness stores sessions and one with the brief given to readers. The agent reads local session logs under your home directory for Claude Code, Codex, Cursor and opencode, and reads the project’s git log, pull requests and CI runs, so it may use the git and GitHub command-line tools. It writes working files into a .upskill folder at the project root and adds that folder to the git exclude file. It masks keys and email addresses in those files and sends no history to outside services, though subagents of the same session read them. After you choose, it writes new skills, hooks, scripts or agent-doc edits into your project and runs hooks and scripts to test them.