Loading
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 pe
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add michael-denyer/pstack-claude --skill automate-me -a cursor -y
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.
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.
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.
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/projects/<encoded-cwd>/*.jsonl, where <encoded-cwd> is the workspace's working directory with / β -. Use only that path. Don't glob across ~/.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.
Mining misses intent that hasn't come up yet. Use the AskUserQuestion tool (structured multi-choice) rather than asking the user to type from scratch.
Shape: one or two questions with 4-6 options each, allow_multiple: true for category questions. Start broad ("Which areas matter most?"), then follow up on selected areas with specific options. After the structured rounds, one free-form chat question catches anything the options missed.
Don't dump 20 questions.
Group the combined signals into sections. Common ones (use only what applies):
The poteto-mode skill shows the shape. Read it for granularity. Don't copy its content. The user's rules are not the same as poteto-mode's.
Use the plugin-dev:skill-development skill to author the skill. Placement:
.claude/skills/<handle>/<handle>-mode/SKILL.md when the repo has an established personal category for that handle. Otherwise default to .claude/skills/<handle>-mode/SKILL.md in the project (or ~/.claude/skills/<handle>-mode/ if the user prefers a personal skill).description: trigger on their name + /<handle>-mode + "work in their style", not on generic keywords like "write code" or "review PR".plugin-dev:skill-development's YAML rules. Keep description as one YAML scalar. Quote it or use description: >- with indented continuation lines when punctuation or wrapping requires it.disable-model-invocation: true by default. Opt out only if the user explicitly wants their mode to apply on every turn.Apply the unslop skill and plugin-dev:skill-development's writing guidelines to every line.
Show the draft to the user and take feedback. Expect multiple iterations. Cut ruthlessly. A mode skill is not a manual.
Work in a worktree off main. Commit and open a PR. Don't push to main directly.
A -mode skill is subjective output. A plugin-dev:skill-development-style test/iterate benchmark loop isn't useful here. Vibe-check with the user: does it read like them? Did it miss anything? Then ship.
Run a description-optimization loop only if the skill's trigger accuracy turns out to be a problem in practice.
plugin-dev:skill-development alone, no mining required.