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.
Install / Use
npx skills add michael-denyer/pstack-claude --skill automate-meInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of automate-me
automate-me scores 83/100 on our quality scale, 2145th of 2,768 Automation skills we index.
Its SKILL.md is 7.3 KB long, well organised into 12 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 557 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so automate-me is actively maintained.
- Our last check on 2026-11-07 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
automate-me compared with similar skills
All 4 of these similar skills score higher than automate-me; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| automate-me (this skill)by michael-denyer | 83 | 557 | 56d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 113.0k | 10d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 82.0k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 40.1k | 9d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 104.2k | 1d ago | MCP Server |
Frequently asked questions
- How do I install automate-me?
- Run
npx skills add michael-denyer/pstack-claude --skill automate-me. The install tabs above show the steps for each supported agent. - Which AI agents does automate-me work with?
- It is written for GitHub Copilot and OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is automate-me safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is automate-me still maintained?
- The repository was last updated about 2 months ago, so automate-me is actively maintained.
Skill content
View source on GitHubname: automate-me description: "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."
Automate me
On Codex, 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.
Flow
0. Check for an existing skill
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 the existing skill (default for repeat runs)
- Start fresh (rare, ask why before doing it)
Update mode changes the rest of the flow:
- Step 1 mines only history since the skill was last edited (
git log -1 --format=%cI <path>). - Step 2 asks what's changed or missing, not what to capture from zero.
- Step 4 edits the existing file in place. Preserve sections the user hasn't contradicted. Revise ones with new evidence. Add new sections only for genuinely new rules.
1. Mine their history
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). 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:
- Response preferences (length, tone, format, "dumb it down" corrections)
- Delegation habits (subagents, models, specialized workflows, parallelism)
- Verification posture (what "done" means, unit tests vs live repro, reviewers)
- Code and prose discipline (style, principles cited, lint/format tools)
- Process conventions (worktrees, commits, PRs, review/merge tooling)
- Meta preferences (fixing skills mid-task, proposing new ones)
Cross-check across slices before elevating a signal. Patterns seen in 2+ slices are high-confidence. Lone signals are weak and usually get dropped.
2. Ask the user directly
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.
3. Cluster findings
Group the combined signals into sections. Common ones (use only what applies):
- Response style: length, tone, format.
- Autonomy: how much to do without asking, MCP tool use.
- Understand first: which skills to reach for when scoping or investigating a change.
- Subagents: default, parallelism, model-to-task, specialized workflows.
- Prose / code discipline: principles, lint tools, style guides.
- Review and verify: repro posture, verification skills, live-testing tools.
- Process: git worktrees, commits, PRs, review/merge tooling.
- Skills: skill-authoring habits, fix-the-skill-first, proposing new skills.
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.
4. Draft the skill
Use the plugin-dev:skill-development skill to author the skill. Placement:
- Path: preserve an existing mode skill's category. For a new mode, use
.claude/skills/<handle>/<handle>-mode/SKILL.mdwhen the repo has an established personal category for that handle. Otherwise default to.claude/skills/<handle>-mode/SKILL.mdin the project (or~/.claude/skills/<handle>-mode/if the user prefers a personal skill). - Handle: the user's first name or chosen identifier.
- Frontmatter
description: trigger on their name +/<handle>-mode+ "work in their style", not on generic keywords like "write code" or "review PR". - Frontmatter formatting: follow
plugin-dev:skill-development's YAML rules. Keepdescriptionas one YAML scalar. Quote it or usedescription: >-with indented continuation lines when punctuation or wrapping requires it. - Frontmatter
disable-model-invocation: trueby default. Opt out only if the user explicitly wants their mode to apply on every turn.
5. Iterate on prose
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.
6. Land it
Work in a worktree off main. Commit and open a PR. Don't push to main directly.
Guardrails
- Don't overfit to one conversation. A preference stated once and contradicted another time is noise. Require multiple instances before codifying it.
- Don't be clever. Restating other skills' contents, inventing metaphors, or writing "poetic" prose for an agent reader is cost without benefit. Keep it operational.
- Reference, don't inline. Other skills the user relies on should appear as path references, not pasted excerpts. Same for any principle docs they maintain elsewhere.
- Keep sections minimal. Only add a section if the user has a specific, non-default rule there. "Communicate clearly" is not a section. "Short paragraphs. Tables when comparing options. Bullets only when items are genuinely parallel." is.
- Name conventions generic. Use "the user" or "the human" in imperatives, not the author's first name.
- Don't force symmetry. If a user has no process rules worth writing down, skip the Process section entirely.
Evaluation
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.
When not to use
- User wants a task-specific skill (not working conventions):
plugin-dev:skill-developmentalone, no mining required. - User wants to capture one narrow workflow (e.g. "how I write commit messages"). That's a regular skill, not a mode skill.
Related Skills
Agent-Reach
113.0kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.0k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
40.1kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
104.2k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
