[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74G5FXBVC8ZE1QXVZM83SPF":3,"skill-same:01M74G5FXBVC8ZE1QXVZM83SPF":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M74G5FXBVC8ZE1QXVZM83SPF","automate-me",null,"Use for \"automate me\", \"create\u002Fupdate\u002Frefresh my -mode skill\", \"turn\u002Fcapture 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 authoring + unslop, optionally pulling fresh evidence from recent transcripts.","casualjim\u002Fpi-mimir","casualjim","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F456109?v=4","01M74FWNWVYZQ29YNASRYNTCG4","Ivan Porto Carrero","01M74FWNXE5R8481XV0Q8Q7EY0",16,"MIT","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fautomate-me\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: automate-me\ndescription: \"Use for \\\"automate me\\\", \\\"create\u002Fupdate\u002Frefresh my -mode skill\\\", \\\"turn\u002Fcapture 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 authoring + unslop, optionally pulling fresh evidence from recent transcripts.\"\ndisable-model-invocation: true\n---\n\n# Automate me\n\nA 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`).\n\nThis skill orchestrates three others: an inline mining pass (see step 1), the Agent Skills standard (authoring), and the **unslop** skill (prose discipline). It sequences them; it doesn't replace them.\n\n## Flow\n\n### 0. Check for an existing skill\n\nLook recursively for a `*-mode\u002FSKILL.md` matching the user's handle in the active host's project and user skill roots (`.pi\u002Fskills\u002F` and `~\u002F.pi\u002Fagent\u002Fskills\u002F` under pi, `.omp\u002Fskills\u002F` and `~\u002F.omp\u002Fagent\u002Fskills\u002F` under omp). Mode skills can live in a personal category directory under that root (`\u003Croot>\u002F\u003Chandle>\u002F`), not only at the top level. If one exists, confirm intent with `a user question` (unless they already said \"update my skill\" or similar):\n\n- Update the existing skill (default for repeat runs)\n- Start fresh (rare; ask why before doing it)\n\nUpdate mode changes the rest of the flow:\n- Step 1 mines only history since the skill was last edited (`git log -1 --format=%cI \u003Cpath>`).\n- Step 2 asks what's changed or missing, not what to capture from zero.\n- 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.\n\n### 1. Mine their history\n\nLocate prior sessions for the current working directory with the `recall` tool before fanning out. Read only paths it returns. Never glob the host's global session directory, because that crosses project boundaries and may read unrelated private chats.\n\nSurvey 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 `thinking` 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:\n\n- Response preferences (length, tone, format, \"dumb it down\" corrections)\n- Delegation habits (subagents, models, specialized workflows, parallelism)\n- Verification posture (what \"done\" means; unit tests vs live repro; reviewers)\n- Code and prose discipline (style, principles cited, lint\u002Fformat tools)\n- Process conventions (worktrees, commits, PRs, review\u002Fmerge tooling)\n- Meta preferences (fixing skills mid-task, proposing new ones)\n\nCross-check across slices before elevating a signal. Patterns seen in 2+ slices are high-confidence; lone signals are weak and usually get dropped.\n\n### 2. Ask the user directly\n\nMining misses intent that has not come up yet. Ask one or two concise user questions with 4-6 concrete options, then one optional free-form follow-up. Do not block on questions that an experiment or repository evidence can answer.\n\nDon't dump 20 questions. Two structured rounds plus one open question is usually enough.\n\n### 3. Cluster findings\n\nGroup the combined signals into sections. Common ones (use only what applies):\n\n- **Response style**: length, tone, format.\n- **Autonomy**: how much to do without asking; MCP tool use.\n- **Understand first**: which skills to reach for when scoping or investigating a change.\n- **Subagents**: default, parallelism, model-to-task, specialized workflows.\n- **Prose \u002F code discipline**: principles, lint tools, style guides.\n- **Review and verify**: repro posture, verification skills, live-testing tools.\n- **Process**: git worktrees, commits, PRs, review\u002Fmerge tooling.\n- **Skills**: skill-authoring habits, fix-the-skill-first, proposing new skills.\n\nThe **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.\n\n### 4. Draft the skill\n\nUse the Agent Skills standard to author the skill. Placement:\n\n- Path: preserve an existing mode skill's category. For a new mode, use `\u003Cproject skill root>\u002F\u003Chandle>\u002F\u003Chandle>-mode\u002FSKILL.md` when the repo has an established personal category for that handle; otherwise default to `\u003Cproject skill root>\u002F\u003Chandle>-mode\u002FSKILL.md`, or the host's user skill root for a personal skill. The project root is `.pi\u002Fskills` under pi and `.omp\u002Fskills` under omp; the user root is `~\u002F.pi\u002Fagent\u002Fskills` under pi and `~\u002F.omp\u002Fagent\u002Fskills` under omp.\n- Handle: the user's first name or chosen identifier.\n- Frontmatter `description`: trigger on their name + `\u002F\u003Chandle>-mode` + \"work in their style\", not on generic keywords like \"write code\" or \"review PR\".\n- Frontmatter formatting: follow the Agent Skills standard's YAML rules. Keep `description` as one YAML scalar; quote it or use `description: >-` with indented continuation lines when punctuation or wrapping requires it.\n- Frontmatter `disable-model-invocation: true` by default. Mode skills are heavy and opinionated; they should only apply when the user explicitly invokes them (by name or slash command), not auto-trigger on description matching. Opt out only if the user explicitly wants their mode to apply on every turn.\n\n### 5. Iterate on prose\n\nApply the **unslop** skill and the Agent Skills standard's writing guidelines to every line. Both apply to any agent-read prose, not just skills.\n\nShow the draft to the user and take feedback. Expect multiple iterations. Cut ruthlessly; a mode skill is not a manual.\n\n### 6. Land it\n\nWork in a worktree off main. Commit and open a PR so the user can review it. Don't push to main directly.\n\n## Guardrails\n\n- **Don't overfit to one conversation.** A preference stated once and contradicted another time is noise. Require multiple instances before codifying it.\n- **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.\n- **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.\n- **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.\n- **Name conventions generic.** Use \"the user\" or \"the human\" in imperatives, not the author's first name. Others may read or adopt the skill.\n- **Don't force symmetry.** If a user has no process rules worth writing down, skip the Process section entirely. Sparse is fine; bloated is not.\n\n## Evaluation\n\nA `-mode` skill is subjective output. A the Agent Skills standard-style test\u002Fiterate benchmark loop isn't useful here. Vibe-check with the user: does it read like them? Did it miss anything? Then ship.\n\nRun a description-optimization loop only if the skill's trigger accuracy turns out to be a problem in practice.\n\n## When not to use\n\n- User wants a task-specific skill (not working conventions): the Agent Skills standard alone, no mining required.\n- User wants to capture one narrow workflow (e.g. \"how I write commit messages\"): that's a regular skill, not a mode skill.\n\n## Reference files\n\n- The **poteto-mode** skill: example of the output shape.\n- The **unslop** skill: prose discipline for every line.\n- the Agent Skills standard: skill authoring process and writing guidelines.\n","# Automate me\n\nA 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`).\n\nThis skill orchestrates three others: an inline mining pass (see step 1), the Agent Skills standard (authoring), and the **unslop** skill (prose discipline). It sequences them; it doesn't replace them.\n\n## Flow\n\n### 0. Check for an existing skill\n\nLook recursively for a `*-mode\u002FSKILL.md` matching the user's handle in the active host's project and user skill roots (`.pi\u002Fskills\u002F` and `~\u002F.pi\u002Fagent\u002Fskills\u002F` under pi, `.omp\u002Fskills\u002F` and `~\u002F.omp\u002Fagent\u002Fskills\u002F` under omp). Mode skills can live in a personal category directory under that root (`\u003Croot>\u002F\u003Chandle>\u002F`), not only at the top level. If one exists, confirm intent with `a user question` (unless they already said \"update my skill\" or similar):\n\n- Update the existing skill (default for repeat runs)\n- Start fresh (rare; ask why before doing it)\n\nUpdate mode changes the rest of the flow:\n- Step 1 mines only history since the skill was last edited (`git log -1 --format=%cI \u003Cpath>`).\n- Step 2 asks what's changed or missing, not what to capture from zero.\n- 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.\n\n### 1. Mine their history\n\nLocate prior sessions for the current working directory with the `recall` tool before fanning out. Read only paths it returns. Never glob the host's global session directory, because that crosses project boundaries and may read unrelated private chats.\n\nSurvey 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 `thinking` 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:\n\n- Response preferences (length, tone, format, \"dumb it down\" corrections)\n- Delegation habits (subagents, models, specialized workflows, parallelism)\n- Verification posture (what \"done\" means; unit tests vs live repro; reviewers)\n- Code and prose discipline (style, principles cited, lint\u002Fformat tools)\n- Process conventions (worktrees, commits, PRs, review\u002Fmerge tooling)\n- Meta preferences (fixing skills mid-task, proposing new ones)\n\nCross-check across slices before elevating a signal. Patterns seen in 2+ slices are high-confidence; lone signals are weak and usually get dropped.\n\n### 2. Ask the user directly\n\nMining misses intent that has not come up yet. Ask one or two concise user questions with 4-6 concrete options, then one optional free-form follow-up. Do not block on questions that an experiment or repository evidence can answer.\n\nDon't dump 20 questions. Two structured rounds plus one open question is usually enough.\n\n### 3. Cluster findings\n\nGroup the combined signals into sections. Common ones (use only what applies):\n\n- **Response style**: length, tone, format.\n- **Autonomy**: how much to do without asking; MCP tool use.\n- **Understand first**: which skills to reach for when scoping or investigating a change.\n- **Subagents**: default, parallelism, model-to-task, specialized workflows.\n- **Prose \u002F code discipline**: principles, lint tools, style guides.\n- **Review and verify**: repro posture, verification skills, live-testing tools.\n- **Process**: git worktrees, commits, PRs, review\u002Fmerge tooling.\n- **Skills**: skill-authoring habits, fix-the-skill-first, proposing new skills.\n\nThe **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.\n\n### 4. Draft the skill\n\nUse the Agent Skills standard to author the skill. Placement:\n\n- Path: preserve an existing mode skill's category. For a new mode, use `\u003Cproject skill root>\u002F\u003Chandle>\u002F\u003Chandle>-mode\u002FSKILL.md` when the repo has an established personal category for that handle; otherwise default to `\u003Cproject skill root>\u002F\u003Chandle>-mode\u002FSKILL.md`, or the host's user skill root for a personal skill. The project root is `.pi\u002Fskills` under pi and `.omp\u002Fskills` under omp; the user root is `~\u002F.pi\u002Fagent\u002Fskills` under pi and `~\u002F.omp\u002Fagent\u002Fskills` under omp.\n- Handle: the user's first name or chosen identifier.\n- Frontmatter `description`: trigger on their name + `\u002F\u003Chandle>-mode` + \"work in their style\", not on generic keywords like \"write code\" or \"review PR\".\n- Frontmatter formatting: follow the Agent Skills standard's YAML rules. Keep `description` as one YAML scalar; quote it or use `description: >-` with indented continuation lines when punctuation or wrapping requires it.\n- Frontmatter `disable-model-invocation: true` by default. Mode skills are heavy and opinionated; they should only apply when the user explicitly invokes them (by name or slash command), not auto-trigger on description matching. Opt out only if the user explicitly wants their mode to apply on every turn.\n\n### 5. Iterate on prose\n\nApply the **unslop** skill and the Agent Skills standard's writing guidelines to every line. Both apply to any agent-read prose, not just skills.\n\nShow the draft to the user and take feedback. Expect multiple iterations. Cut ruthlessly; a mode skill is not a manual.\n\n### 6. Land it\n\nWork in a worktree off main. Commit and open a PR so the user can review it. Don't push to main directly.\n\n## Guardrails\n\n- **Don't overfit to one conversation.** A preference stated once and contradicted another time is noise. Require multiple instances before codifying it.\n- **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.\n- **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.\n- **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.\n- **Name conventions generic.** Use \"the user\" or \"the human\" in imperatives, not the author's first name. Others may read or adopt the skill.\n- **Don't force symmetry.** If a user has no process rules worth writing down, skip the Process section entirely. Sparse is fine; bloated is not.\n\n## Evaluation\n\nA `-mode` skill is subjective output. A the Agent Skills standard-style test\u002Fiterate benchmark loop isn't useful here. Vibe-check with the user: does it read like them? Did it miss anything? Then ship.\n\nRun a description-optimization loop only if the skill's trigger accuracy turns out to be a problem in practice.\n\n## When not to use\n\n- User wants a task-specific skill (not working conventions): the Agent Skills standard alone, no mining required.\n- User wants to capture one narrow workflow (e.g. \"how I write commit messages\"): that's a regular skill, not a mode skill.\n\n## Reference files\n\n- The **poteto-mode** skill: example of the output shape.\n- The **unslop** skill: prose discipline for every line.\n- the Agent Skills standard: skill authoring process and writing guidelines.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","86a206d111fba4ffc9c47c363486479262e63513","packages\u002Fpi-pstack\u002Fskills\u002Fautomate-me",9,"https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir","https:\u002F\u002Fgithub.com\u002Fcasualjim","http:\u002F\u002Fflanders.co.nz","2026-11-10 15:32:15",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add casualjim\u002Fpi-mimir --skill automate-me",{"tool":39,"command":40},"bunx","bunx skills add casualjim\u002Fpi-mimir --skill automate-me",{"tool":42,"command":43},"pnpm","pnpm dlx skills add casualjim\u002Fpi-mimir --skill automate-me","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fautomate-me\u002FSKILL.md",[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M74GK3CG2X0988XMHBKNC0HG","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M74GK2A4034JSAN8BCGBEPVB","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M74GK13302GXTR58TM47BQY1","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M74GJYB1DJCA4AQH22MWYM9J","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Fskill:technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M74GJW7794XM60AKH76941T0","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M74GJPQN3RW4FN7G78W2NFR1","tdd","Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.","https:\u002F\u002Fgithub.com\u002Fcasualjim\u002Fpi-mimir\u002Fblob\u002Fmain\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]