[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78D13RXQ1FZP8CZ5CXBKCG3":3,"skill-same:01M78D13RXQ1FZP8CZ5CXBKCG3":50},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M78D13RXQ1FZP8CZ5CXBKCG3","automate-me",null,"Use for \"automate me\", \"create\u002Fupdate\u002Frefresh my -mode skill\", or turning the user's working style into a durable OMP or Pi skill. Mines local transcripts, writes through pstack's authoring playbook, and installs from the personal skills source.","emo-eth\u002Fskills","emo-eth","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6371847?v=4","01M78CWE28WS3JH2WXYPRNC26K","James","01M78CWE2YS6Y5883W8J0D60XA",0,"MIT","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fautomate-me\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fautomate-me\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: automate-me\ndescription: \"Use for \\\"automate me\\\", \\\"create\u002Fupdate\u002Frefresh my -mode skill\\\", or turning the user's working style into a durable OMP or Pi skill. Mines local transcripts, writes through pstack's authoring playbook, and installs from the personal skills source.\"\ndisable-model-invocation: true\n---\n\n# Automate me\n\nRead `pstack-runtime` before the first host-specific operation.\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 coordinates transcript mining, the **Authoring a skill** playbook, and the **unslop** skill.\n\n## Flow\n\n### 0. Check for an existing skill\n\nSearch `~\u002Fdev\u002Fskills\u002Fskills\u002F**\u002F*-mode\u002FSKILL.md` for the user's handle. If one exists and the user did not already say update or replace, use the OMP `ask` tool to choose:\n\n- Update the existing skill. Default for repeat runs.\n- Start fresh. Use only when the current shape is no longer useful.\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\nUse the exact current directory with `agent-conv read \u003Cworkspace> --source omp` and `agent-conv thread` when available. Otherwise inspect only this workspace under `~\u002F.omp\u002Fagent\u002Fsessions\u002F`. Never search another workspace unless the user names it.\n\nSurvey recent conversations for recurring patterns. Split a large time range into independent slices and launch all mining work as `scout` tasks in one OMP `task` batch. Each scout returns a short list with session IDs as evidence.\n\n- Response preferences (length, tone, format, \"dumb it down\" corrections)\n- Delegation habits (subagents, OMP agent types, 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 appeared in history. Use the OMP `ask` tool with one or two questions and 4-5 concise options. Set `multi: true` for category questions. Ask one free-form follow-up only when the choices cannot capture the missing preference.\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 agent types, parallelism, and 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\nRead `skill:\u002F\u002Fpoteto-mode\u002Fplaybooks\u002Fauthoring-a-skill.md` before drafting.\n\n- Path: preserve an existing category. New mode skills go in `~\u002Fdev\u002Fskills\u002Fskills\u002F\u003Chandle>-mode\u002FSKILL.md`.\n- Handle: the user's first name or chosen identifier.\n- Frontmatter `name`: equal the folder name.\n- Frontmatter `description`: trigger on the handle, `\u002F\u003Chandle>-mode`, and requests to work in that style. Avoid generic coding triggers.\n- Set `disable-model-invocation: true` unless the user explicitly wants automatic invocation.\n\n### 5. Iterate on prose\n\nApply the **unslop** rules and the **Authoring a skill** playbook to every line.\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\nFollow `~\u002Fdev\u002Fskills\u002FAGENTS.md`. Commit the skill, push `main` immediately, and install or refresh it with `npx skills`. Do not write directly into `~\u002F.agents\u002Fskills` or `~\u002F.omp\u002Fagent\u002Fskills`.\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. Ask whether the draft reads like the user's real rules and revise it. Run trigger evaluation only when invocation accuracy is the reported problem.\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: use the **Authoring a skill** playbook without transcript mining.\n- User wants one narrow workflow: write 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 **Authoring a skill** playbook: OMP skill authoring and invocation mechanics.\n","# Automate me\n\nRead `pstack-runtime` before the first host-specific operation.\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 coordinates transcript mining, the **Authoring a skill** playbook, and the **unslop** skill.\n\n## Flow\n\n### 0. Check for an existing skill\n\nSearch `~\u002Fdev\u002Fskills\u002Fskills\u002F**\u002F*-mode\u002FSKILL.md` for the user's handle. If one exists and the user did not already say update or replace, use the OMP `ask` tool to choose:\n\n- Update the existing skill. Default for repeat runs.\n- Start fresh. Use only when the current shape is no longer useful.\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\nUse the exact current directory with `agent-conv read \u003Cworkspace> --source omp` and `agent-conv thread` when available. Otherwise inspect only this workspace under `~\u002F.omp\u002Fagent\u002Fsessions\u002F`. Never search another workspace unless the user names it.\n\nSurvey recent conversations for recurring patterns. Split a large time range into independent slices and launch all mining work as `scout` tasks in one OMP `task` batch. Each scout returns a short list with session IDs as evidence.\n\n- Response preferences (length, tone, format, \"dumb it down\" corrections)\n- Delegation habits (subagents, OMP agent types, 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 appeared in history. Use the OMP `ask` tool with one or two questions and 4-5 concise options. Set `multi: true` for category questions. Ask one free-form follow-up only when the choices cannot capture the missing preference.\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 agent types, parallelism, and 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\nRead `skill:\u002F\u002Fpoteto-mode\u002Fplaybooks\u002Fauthoring-a-skill.md` before drafting.\n\n- Path: preserve an existing category. New mode skills go in `~\u002Fdev\u002Fskills\u002Fskills\u002F\u003Chandle>-mode\u002FSKILL.md`.\n- Handle: the user's first name or chosen identifier.\n- Frontmatter `name`: equal the folder name.\n- Frontmatter `description`: trigger on the handle, `\u002F\u003Chandle>-mode`, and requests to work in that style. Avoid generic coding triggers.\n- Set `disable-model-invocation: true` unless the user explicitly wants automatic invocation.\n\n### 5. Iterate on prose\n\nApply the **unslop** rules and the **Authoring a skill** playbook to every line.\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\nFollow `~\u002Fdev\u002Fskills\u002FAGENTS.md`. Commit the skill, push `main` immediately, and install or refresh it with `npx skills`. Do not write directly into `~\u002F.agents\u002Fskills` or `~\u002F.omp\u002Fagent\u002Fskills`.\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. Ask whether the draft reads like the user's real rules and revise it. Run trigger evaluation only when invocation accuracy is the reported problem.\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: use the **Authoring a skill** playbook without transcript mining.\n- User wants one narrow workflow: write 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 **Authoring a skill** playbook: OMP skill authoring and invocation mechanics.\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","556c6b2a01f1f75137a940333ffc8bd95cf0756e","skills\u002Fpstack\u002Fautomate-me","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills","https:\u002F\u002Fgithub.com\u002Femo-eth","I make music and write code","2026-11-13 05:13:04",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add emo-eth\u002Fskills --skill automate-me",{"tool":39,"command":40},"bunx","bunx skills add emo-eth\u002Fskills --skill automate-me",{"tool":42,"command":43},"pnpm","pnpm dlx skills add emo-eth\u002Fskills --skill automate-me","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fautomate-me\u002FSKILL.md",[46],{"path":47,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":16},"LICENSE","许可证",1067,[51,58,66,74,82,90],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":20},"01M78D75SMNM5JJXJGN9W6Z304","system-vibe","Personal operating-system contract for the home fleet, sync, SSH, skills, Herdr, and local inference. Use when diagnosing or changing machines, chezmoi, SSH, skill distribution, Windows sleep\u002Fwake, or the local model router. This is the qualitative list of what must stay true; agents invent enforcement from the clauses, not from tribal setup lore.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsystem-vibe\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":62,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":20},"01M78D65Z8HK3VTSAWKC59TR94","rubber-stamp-travel-field-note","Use for rubber-stamp travel field-note photo posters.","CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Frubber-stamp-travel-field-note\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":20},"01M78D5VXYSJZVTGETSYGZWQPQ","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\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fwhy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":20},"01M78D5SMN2NTGT19B2T5WY83T","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\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":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":20},"01M78D5PN73KA6B88JVHABNTKY","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftypescript-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M78D5JHTG4B6YPZ8TNN18Y6D","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FSKILL.md",[],[]]