[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FCTS2JG7BAF6NHCGDXFKXN":3,"skill-same:01M7FCTS2JG7BAF6NHCGDXFKXN":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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7FCTS2JG7BAF6NHCGDXFKXN","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 plugin-dev:skill-development + unslop, optionally pulling fresh evidence from recent transcripts.","Abhiman67\u002Fbatcave","Abhiman67","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F137296581?v=4","01M7FCTFR2F0WBMG11VKWGN0KB","ABHISHEK CHHANDAK","01M7FCTFRWXRGV9ZY0060XPK62",0,"MIT","https:\u002F\u002Fgithub.com\u002FAbhiman67\u002Fbatcave\u002Fblob\u002Fmaster\u002Fplugins\u002Fbatcave\u002Fskills\u002Fautomate-me\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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 plugin-dev:skill-development + unslop, optionally pulling fresh evidence from recent transcripts.\"\n---\n\n# Automate me\n\nOn Codex, read the [platform mapping](..\u002Fbatcave-mode\u002Freferences\u002Fcodex-tools.md), including its per-skill notes, before following this skill.\n\nOn GitHub Copilot, read the [platform mapping](..\u002Fbatcave-mode\u002Freferences\u002Fcopilot-tools.md), including its per-skill notes, before following this skill.\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 **plugin-dev:skill-development** 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. Claude Code stores them at `~\u002F.claude\u002Fprojects\u002F\u003Cencoded-cwd>\u002F*.jsonl`, where `\u003Cencoded-cwd>` is the workspace's working directory with `\u002F` → `-`. Use only that path. Don't glob across `~\u002F.claude\u002Fprojects\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). Pick each subagent's reasoning level for the job, per the Subagents section of the **batcave-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 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 4-6 options each, `allow_multiple: 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 **batcave-mode** skill shows the shape. Read it for granularity. Don't copy its content. The user's rules are not the same as batcave-mode's.\n\n### 4. Draft the skill\n\nUse the **plugin-dev:skill-development** 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 `plugin-dev:skill-development`'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 their mode to apply on every turn.\n\n### 5. Iterate on prose\n\nApply the **unslop** skill and `plugin-dev:skill-development`'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 `plugin-dev:skill-development`-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): `plugin-dev:skill-development` 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\nOn Codex, read the [platform mapping](..\u002Fbatcave-mode\u002Freferences\u002Fcodex-tools.md), including its per-skill notes, before following this skill.\n\nOn GitHub Copilot, read the [platform mapping](..\u002Fbatcave-mode\u002Freferences\u002Fcopilot-tools.md), including its per-skill notes, before following this skill.\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 **plugin-dev:skill-development** 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. Claude Code stores them at `~\u002F.claude\u002Fprojects\u002F\u003Cencoded-cwd>\u002F*.jsonl`, where `\u003Cencoded-cwd>` is the workspace's working directory with `\u002F` → `-`. Use only that path. Don't glob across `~\u002F.claude\u002Fprojects\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). Pick each subagent's reasoning level for the job, per the Subagents section of the **batcave-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 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 4-6 options each, `allow_multiple: 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 **batcave-mode** skill shows the shape. Read it for granularity. Don't copy its content. The user's rules are not the same as batcave-mode's.\n\n### 4. Draft the skill\n\nUse the **plugin-dev:skill-development** 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 `plugin-dev:skill-development`'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 their mode to apply on every turn.\n\n### 5. Iterate on prose\n\nApply the **unslop** skill and `plugin-dev:skill-development`'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 `plugin-dev:skill-development`-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): `plugin-dev:skill-development` 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},"master","ffa275487ca7faa89d4a38dbc6eecab994d812dd","plugins\u002Fbatcave\u002Fskills\u002Fautomate-me","https:\u002F\u002Fgithub.com\u002FAbhiman67\u002Fbatcave","https:\u002F\u002Fgithub.com\u002FAbhiman67","https:\u002F\u002Fabhishekchhandak.vercel.app\u002F","hehehehehe\r\n","2026-11-12 08:25:16",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Abhiman67\u002Fbatcave --skill automate-me",{"tool":38,"command":39},"bunx","bunx skills add Abhiman67\u002Fbatcave --skill automate-me",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Abhiman67\u002Fbatcave --skill automate-me","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAbhiman67\u002Fbatcave\u002Fblob\u002Fmaster\u002Fplugins\u002Fbatcave\u002Fskills\u002Fautomate-me\u002FSKILL.md",true,[],[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},"01M7FD1NSBZDQSC0TP75CQN7A8","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\u002FAbhiman67\u002Fbatcave\u002Fblob\u002Fmaster\u002Fplugins\u002Fbatcave\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},"01M7FD1KGG5Q5MZ3T8C0TQG7CN","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002FAbhiman67\u002Fbatcave\u002Fblob\u002Fmaster\u002Fplugins\u002Fbatcave\u002Fskills\u002Fwhat-did-i-get-done\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},"01M7FD1HZPM0F0YKYXMYASCPA7","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002FAbhiman67\u002Fbatcave\u002Fblob\u002Fmaster\u002Fplugins\u002Fbatcave\u002Fskills\u002Funslop\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},"01M7FD1FXWCE2MY0VZYZ0TRBMW","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002FAbhiman67\u002Fbatcave\u002Fblob\u002Fmaster\u002Fplugins\u002Fbatcave\u002Fskills\u002Ftypescript-best-practices\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},"01M7FD1D8QPK5VVKABPGX4CENW","thermos","Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug\u002Fsecurity and code-quality branch audits.","https:\u002F\u002Fgithub.com\u002FAbhiman67\u002Fbatcave\u002Fblob\u002Fmaster\u002Fplugins\u002Fbatcave\u002Fskills\u002Fthermos\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},"01M7FD18VJ6EGHPFKXFJB8PN3S","thermo-nuclear-review","Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch\u002FPR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.","https:\u002F\u002Fgithub.com\u002FAbhiman67\u002Fbatcave\u002Fblob\u002Fmaster\u002Fplugins\u002Fbatcave\u002Fskills\u002Fthermo-nuclear-review\u002FSKILL.md",[],[]]