[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EKWNXZB72XCF55GES0R10E":3,"skill-same:01M7EKWNXZB72XCF55GES0R10E":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":42},"01M7EKWNXZB72XCF55GES0R10E","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-creator + unslop, optionally pulling fresh evidence from recent transcripts.","anas-yousef\u002Fpstack-claude","anas-yousef","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44998563?v=4","01M7EKWDK1H83ZT5PKXWXAVFPD","01M7EKWDKNREGX0H27EY81D3QS",0,"MIT","https:\u002F\u002Fgithub.com\u002Fanas-yousef\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fskills\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\\\", \\\"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-creator + 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 `skill-creator` skill (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 `.claude\u002Fskills\u002F**\u002F*-mode\u002FSKILL.md` and `~\u002F.claude\u002Fskills\u002F*-mode\u002FSKILL.md` matching the user's handle. Mode skills can live in a personal category directory (`.claude\u002Fskills\u002F\u003Chandle>\u002F`), not only at the top level. If one exists, confirm intent with `AskUserQuestion` (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 the active workspace's transcripts before fanning out. They live in `~\u002F.claude\u002Fprojects\u002F\u003Ccwd-slug>\u002F`, one `\u003Csession-id>.jsonl` per session, where `\u003Ccwd-slug>` is the session's absolute working directory with every character other than a letter, digit, or `-` replaced by `-`. A git worktree is its own working directory with its own slug. Use only that directory. Don't glob across `~\u002F.claude\u002Fprojects\u002F*\u002F`. That crosses workspace boundaries and reads private chats from unrelated projects.\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). 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 hasn't come up yet. Use the `AskUserQuestion` tool (structured multi-choice) rather than asking the user to type from scratch.\n\nShape: one or two questions with up to 4 options each, `multiSelect: 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.\n\nDon't dump 20 questions.\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 `skill-creator` skill to author the skill. Placement:\n\n- Path: preserve an existing mode skill's category. For a new mode, use `.claude\u002Fskills\u002F\u003Chandle>\u002F\u003Chandle>-mode\u002FSKILL.md` when the repo has an established personal category for that handle. Otherwise default to `.claude\u002Fskills\u002F\u003Chandle>-mode\u002FSKILL.md` in the project (or `~\u002F.claude\u002Fskills\u002F\u003Chandle>-mode\u002F` if the user prefers a personal skill).\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 `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.\n- Frontmatter `disable-model-invocation: true` by default. Opt out only if the user explicitly wants the model to apply their mode without being asked. A line in `CLAUDE.md` that tells the model to apply the mode works only with the flag off.\n\n### 5. Iterate on prose\n\nApply the **unslop** skill and `skill-creator`'s writing guidelines 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\nWork in a worktree off main. Commit and open a PR. 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.\n- **Don't force symmetry.** If a user has no process rules worth writing down, skip the Process section entirely.\n\n## Evaluation\n\nA `-mode` skill is subjective output. A `skill-creator`-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): `skill-creator` 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","# 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 `skill-creator` skill (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 `.claude\u002Fskills\u002F**\u002F*-mode\u002FSKILL.md` and `~\u002F.claude\u002Fskills\u002F*-mode\u002FSKILL.md` matching the user's handle. Mode skills can live in a personal category directory (`.claude\u002Fskills\u002F\u003Chandle>\u002F`), not only at the top level. If one exists, confirm intent with `AskUserQuestion` (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 the active workspace's transcripts before fanning out. They live in `~\u002F.claude\u002Fprojects\u002F\u003Ccwd-slug>\u002F`, one `\u003Csession-id>.jsonl` per session, where `\u003Ccwd-slug>` is the session's absolute working directory with every character other than a letter, digit, or `-` replaced by `-`. A git worktree is its own working directory with its own slug. Use only that directory. Don't glob across `~\u002F.claude\u002Fprojects\u002F*\u002F`. That crosses workspace boundaries and reads private chats from unrelated projects.\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). 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 hasn't come up yet. Use the `AskUserQuestion` tool (structured multi-choice) rather than asking the user to type from scratch.\n\nShape: one or two questions with up to 4 options each, `multiSelect: 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.\n\nDon't dump 20 questions.\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 `skill-creator` skill to author the skill. Placement:\n\n- Path: preserve an existing mode skill's category. For a new mode, use `.claude\u002Fskills\u002F\u003Chandle>\u002F\u003Chandle>-mode\u002FSKILL.md` when the repo has an established personal category for that handle. Otherwise default to `.claude\u002Fskills\u002F\u003Chandle>-mode\u002FSKILL.md` in the project (or `~\u002F.claude\u002Fskills\u002F\u003Chandle>-mode\u002F` if the user prefers a personal skill).\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 `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.\n- Frontmatter `disable-model-invocation: true` by default. Opt out only if the user explicitly wants the model to apply their mode without being asked. A line in `CLAUDE.md` that tells the model to apply the mode works only with the flag off.\n\n### 5. Iterate on prose\n\nApply the **unslop** skill and `skill-creator`'s writing guidelines 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\nWork in a worktree off main. Commit and open a PR. 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.\n- **Don't force symmetry.** If a user has no process rules worth writing down, skip the Process section entirely.\n\n## Evaluation\n\nA `-mode` skill is subjective output. A `skill-creator`-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): `skill-creator` 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",{"name":5,"description":7,"disable-model-invocation":23},true,"main","583cb36363b11545f389fa22000a98fc84ae8692","skills\u002Fautomate-me","https:\u002F\u002Fgithub.com\u002Fanas-yousef\u002Fpstack-claude","https:\u002F\u002Fgithub.com\u002Fanas-yousef","2026-10-14 11:57:47",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":23},[32,35,38],{"tool":33,"command":34},"npx","npx skills add anas-yousef\u002Fpstack-claude --skill automate-me",{"tool":36,"command":37},"bunx","bunx skills add anas-yousef\u002Fpstack-claude --skill automate-me",{"tool":39,"command":40},"pnpm","pnpm dlx skills add anas-yousef\u002Fpstack-claude --skill automate-me","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanas-yousef\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fskills\u002Fautomate-me\u002FSKILL.md",[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7EM8H03WR2E8E9B31AG8YQE","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\u002Fanas-yousef\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7EM8E8WV7GVW3JHBRGPC3EC","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fanas-yousef\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7EM8AHBT0QTDXQ8FAGKB9V0","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fanas-yousef\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7EM85R63HJ6QBQG3W4X28YG","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\u002Fanas-yousef\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7EM83CFA42BZF9K6F4H3GYG","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\u002Fanas-yousef\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7EM80V499CGYA0CFC9PMFEW","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\u002Fanas-yousef\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fupstream\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]