# Automate Me

> Create or refine a personal Codex mode skill from the user's demonstrated working preferences. Use for $automate-me or requests to capture a recurring working style as a skill.

- Skill: `vaibtan/automate-me` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add vaibtan/automate-me`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vaibtan/automate-me/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Vaibtan (https://skillmd.com/u/vaibtan)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/vaibtan/automate-me

---


# Automate my working style

Use `$skill-creator` for the artifact and `$unslop` for prose quality.

1. Search the current project and `$CODEX_HOME/skills` for an existing matching mode skill. Preserve its location and invocation policy when updating.
2. Mine only evidence already in scope: the current conversation, explicit user preferences, relevant repository instructions, and task or memory records available through Codex tools. Do not scan unrelated conversations.
3. Extract decisions that recur across tasks: autonomy, verification, change scope, tool use, architecture preferences, communication, and review boundaries.
4. Ask the user only about a preference that materially changes the skill and has no evidence. Present a recommended answer with the question.
5. Create the smallest skill that changes future behavior. Keep common rules in `SKILL.md`; route conditional detail to references. Do not copy system policy or encode one-off project facts as universal guidance.
6. Validate the skill with the skill-creator validator and show the user the concrete behavior it will change.

Default to a project-local `.codex/skills/<name>-mode/` only when the user wants repository-specific behavior. Otherwise use `$CODEX_HOME/skills/<name>-mode/`.