--- name: 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 skill-creator + unslop, optionally pulling fresh evidence from recent transcripts." disable-model-invocation: true --- # Automate me 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), Mixdog's `skill-creator` skill (authoring), and the **unslop** skill (prose discipline). It sequences them. It doesn't replace them. ## Flow ### 0. Check for an existing skill Look for `~/.mixdog/data/skills/*-mode/SKILL.md` matching the user's handle. If one exists, confirm intent with `ask_user` (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 (its modified time from `list` with `meta: true`). - 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 Mine Mixdog's memory yourself, with the `recall` tool loaded through `load_tool`, and keep to this Project's pool, its default. Don't read other Projects' conversations. That crosses workspace boundaries and reads private chats from unrelated projects. When `recall` is unavailable or reports that memory is off, stop and ask the user to turn on memory in Mixdog's settings, then run this skill again. Survey recent agent conversations within that scope for recurring patterns. Query `recall` with `category` set to `preference`, `rule`, `constraint`, and `decision`, and with a `query` per signal below, across slices of history (e.g. last 2-4 weeks, split into 3 `period` slices so each has enough material). Read the entries in the main thread and note, for each pattern, its entry ids and session ids as 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 `ask_user` tool (structured multi-choice) rather than asking the user to type from scratch. Shape: one or two questions with 2-4 options each, multi-select 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 `skill-creator` skill to author the skill. Placement: - Path: `~/.mixdog/data/skills/-mode/SKILL.md`. - Handle: the user's first name or chosen identifier. - Activation: have `skill-creator` write the trigger in `when_to_use`. Trigger on their name + `$-mode` + "work in their style", not on generic keywords like "write code" or "review PR". - Frontmatter formatting: follow `skill-creator`'s YAML rules. Keep `description` as one YAML scalar. Quote it or use `description: >-` with indented continuation lines when punctuation or wrapping requires it. - Leave out `disable-model-invocation`. Mixdog's skill validator rejects it. ### 5. Iterate on prose Apply the **unslop** skill and `skill-creator`'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 Write the approved draft to `~/.mixdog/data/skills/-mode/SKILL.md`. That folder is outside any repository, so there is no commit or PR. ## 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 `skill-creator`-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): `skill-creator` alone, 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.