Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →backnotprop/automate-me
Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via create-skill + unslop, optionally pulling fresh evidence from recent transcripts.
Passed 12 of 17 test cases with the skill, and 5 of 17 without it.
and 6 more in the full report
9 fixed6 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am running Claude Code in project directory `/Users/dev/work/my-app`. I want to mine my chat history to build a mode skill. Which transcript log directory path should be read?
| Checked | Without skill | With skill |
|---|---|---|
| Reads transcript files from `~/.claude/projects/-Users-dev-work-my-app/*.jsonl`. | Missed | Passed |
The instructions your model reads when the skill loads.
A guided flow for turning the user's working conventions into a skill agents will follow. The output is one -mode skill tailored to them (e.g. jay-mode, priya-mode).
This skill orchestrates three others: an inline mining pass (see step 1), your harness's skill-authoring skill (authoring), and the unslop skill (prose discipline). It sequences them. It doesn't replace them.
The skill-authoring skill is create-skill in Cursor (built in) or Anthropic's skill-creator. If you have neither, follow the Agent Skills format at agentskills.io. "create-skill" below means whichever of these you use.
Look recursively for *-mode/SKILL.md matching the user's handle in your harness's skill folders. In the project: .cursor/skills/ (Cursor), .claude/skills/ (Claude Code), .pi/skills/ (Pi), or .agents/skills/ (Codex, OpenCode, and others). For the user: ~/.cursor/skills/, ~/.claude/skills/, ~/.pi/agent/skills/, ~/.codex/skills/, ~/.config/opencode/skills/, or ~/.agents/skills/. Mode skills can live in a personal category directory (<skills>/<handle>/), not only at the top level. If one exists, confirm intent with your structured-question tool (AskQuestion in Cursor, AskUserQuestion in Claude Code, question in OpenCode) unless they already said "update my skill" or similar:
Update mode changes the rest of the flow:
git log -1 --format=%cI <path>).Locate the active workspace's transcripts before fanning out. Use only that workspace's directory. Don't glob across every project's directory. That crosses workspace boundaries and reads private chats from unrelated projects. Where they live depends on your harness:
agent-transcripts/ directory under ~/.cursor/projects/.~/.claude/projects/<slug>/*.jsonl, where <slug> is the workspace path with every character that isn't a letter or digit turned into "-".~/.pi/agent/sessions/--<slug>--/*.jsonl, where <slug> is the workspace path with the leading slash dropped and each "/" turned into "-".~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl. Keep only files whose first line has payload.cwd equal to the workspace path.Survey recent agent conversations within that scope for recurring patterns. Run multiple parallel subagents across slices of history (e.g. last 2-4 weeks, split into 3 slices so each has enough material). Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the poteto-mode skill. Each slice mining subagent reads transcripts from the workspace-scoped path the parent provides, looks for the signals below, and returns a short structured list of patterns it saw with evidence pointers. Default signals worth hunting:
test cases passed, vs 5 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.