Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →michael-denyer/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 plugin-dev:skill-development + unslop, optionally pulling fresh evidence from recent transcripts.
Passed 16 of 20 test cases with the skill, and 9 of 20 without it.
and 9 more in the full report
9 fixed7 passed either way2 still failing2 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/21/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to see if I already have a mode skill setup in this workspace or user profile for handle 'sam'. Check all standard location patterns recursively including personal handle category subdirectories in both repository and home skill directories, and report back where to look.
| Checked | Without skill | With skill |
|---|---|---|
| Searches recursively for mode skills inside personal handle category directories under .claude/skills/. | Missed | Passed |
| Checks the user home skills directory at ~/.claude/skills/ for matching mode files. | Missed | Passed |
The instructions your model reads when the skill loads.
On Codex, read the platform mapping, including its per-skill notes, before following this skill.
On GitHub Copilot, read the platform mapping, including its per-skill notes, before following this skill.
On Muse, read the platform mapping, including its per-skill notes, before following this skill.
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), the plugin-dev:skill-development skill (authoring), and the unslop skill (prose discipline). It sequences them. It doesn't replace them.
Look recursively for .claude/skills/**/*-mode/SKILL.md and ~/.claude/skills/*-mode/SKILL.md matching the user's handle. Mode skills can live in a personal category directory (.claude/skills/<handle>/), not only at the top level. If one exists, confirm intent with AskUserQuestion (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. Claude Code stores them at ${CLAUDE_CONFIG_DIR:-$HOME/.claude}/projects/<encoded-cwd>/*.jsonl, where <encoded-cwd> is the workspace's working directory with / → -. Use only that path. Don't glob across ${CLAUDE_CONFIG_DIR:-$HOME/.claude}/projects/. That crosses workspace boundaries and reads private chats from unrelated projects.
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 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:
Cross-check across slices before elevating a signal. Patterns seen in 2+ slices are high-confidence. Lone signals are weak and usually get dropped.
test cases passed, vs 9 / 20 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.