[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2R8017ABTYM1G50FNNFDZ":3,"skill-same:01M7B2R8017ABTYM1G50FNNFDZ":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":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":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7B2R8017ABTYM1G50FNNFDZ","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 create-skill + unslop, optionally pulling fresh evidence from recent transcripts.","deniial00\u002Fbigbrain","deniial00","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F67418167?v=4","01M7B2R0JNJCWRMCCDR5QDAMW4","Daniel Hofbauer","01M7B2R0K9SQC9R3QRBXSP6B07",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdeniial00\u002Fbigbrain\u002Fblob\u002Fmain\u002F.opencode\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 create-skill + unslop, optionally pulling fresh evidence from recent transcripts.\"\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), Cursor's built-in `create-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 `.cursor\u002Fskills\u002F**\u002F*-mode\u002FSKILL.md` and `~\u002F.cursor\u002Fskills\u002F*-mode\u002FSKILL.md` matching the user's handle. Mode skills can live in a personal category directory (`.cursor\u002Fskills\u002F\u003Chandle>\u002F`), not only at the top level. If one exists, confirm intent with `AskQuestion` (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. The system prompt names the workspace's `agent-transcripts\u002F` directory. Use only that path. Don't glob across `~\u002F.cursor\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 `AskQuestion` tool (structured multi-choice) rather than asking the user to type from scratch. Lower cognitive load, higher hit rate.\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. 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 **bigbrain** skill shows the shape. Read it for granularity. Don't copy its content; the user's rules are not the same as bigbrain's.\n\n### 4. Draft the skill\n\nUse Cursor's built-in `create-skill` skill to author the skill. Placement:\n\n- Path: preserve an existing mode skill's category. For a new mode, use `.cursor\u002Fskills\u002F\u003Chandle>\u002F\u003Chandle>-mode\u002FSKILL.md` when the repo has an established personal category for that handle; otherwise default to `.cursor\u002Fskills\u002F\u003Chandle>-mode\u002FSKILL.md` in the project (or `~\u002F.cursor\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 `create-skill`'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 `create-skill`'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 `create-skill`-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): `create-skill` 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 **bigbrain** skill: example of the output shape.\n- The **unslop** skill: prose discipline for every line.\n- Cursor's built-in `create-skill` skill: 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), Cursor's built-in `create-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 `.cursor\u002Fskills\u002F**\u002F*-mode\u002FSKILL.md` and `~\u002F.cursor\u002Fskills\u002F*-mode\u002FSKILL.md` matching the user's handle. Mode skills can live in a personal category directory (`.cursor\u002Fskills\u002F\u003Chandle>\u002F`), not only at the top level. If one exists, confirm intent with `AskQuestion` (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. The system prompt names the workspace's `agent-transcripts\u002F` directory. Use only that path. Don't glob across `~\u002F.cursor\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 `AskQuestion` tool (structured multi-choice) rather than asking the user to type from scratch. Lower cognitive load, higher hit rate.\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. 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 **bigbrain** skill shows the shape. Read it for granularity. Don't copy its content; the user's rules are not the same as bigbrain's.\n\n### 4. Draft the skill\n\nUse Cursor's built-in `create-skill` skill to author the skill. Placement:\n\n- Path: preserve an existing mode skill's category. For a new mode, use `.cursor\u002Fskills\u002F\u003Chandle>\u002F\u003Chandle>-mode\u002FSKILL.md` when the repo has an established personal category for that handle; otherwise default to `.cursor\u002Fskills\u002F\u003Chandle>-mode\u002FSKILL.md` in the project (or `~\u002F.cursor\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 `create-skill`'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 `create-skill`'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 `create-skill`-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): `create-skill` 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 **bigbrain** skill: example of the output shape.\n- The **unslop** skill: prose discipline for every line.\n- Cursor's built-in `create-skill` skill: skill authoring process and writing guidelines.\n",{"name":5,"description":7},"main","d5be559014149b38e4c6ad7aac677dfa4e3ffe18",".opencode\u002Fskills\u002Fautomate-me","https:\u002F\u002Fgithub.com\u002Fdeniial00\u002Fbigbrain","https:\u002F\u002Fgithub.com\u002Fdeniial00","Software developer with a keen interest in user-centered applications, geographic information systems (GIS) and artificial intelligence.","2026-09-02 02:43:58",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add deniial00\u002Fbigbrain --skill automate-me",{"tool":37,"command":38},"bunx","bunx skills add deniial00\u002Fbigbrain --skill automate-me",{"tool":40,"command":41},"pnpm","pnpm dlx skills add deniial00\u002Fbigbrain --skill automate-me","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdeniial00\u002Fbigbrain\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fautomate-me\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":14,"sourceHtmlUrl":49},".bigbrain-managed","OTHER","其他","https:\u002F\u002Fgithub.com\u002Fdeniial00\u002Fbigbrain\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fautomate-me\u002F.bigbrain-managed",[51,58,65,72,79,86],{"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":19},"01M7B2W160Y8QYXAXB7BP8YV0H","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\u002Fdeniial00\u002Fbigbrain\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fwhy\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":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7B2VZW645BYZARSFXB7BK9P","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fdeniial00\u002Fbigbrain\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7B2VYD4TRH86HSC7QKSPAS2","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fdeniial00\u002Fbigbrain\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7B2VV9P47RF84KM0YTB8G1H","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\u002Fdeniial00\u002Fbigbrain\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7B2VRV3SWT5EP0P1PS2EA21","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\u002Fdeniial00\u002Fbigbrain\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7B2VPD1A1NDT3E2XZEQA6E0","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\u002Fdeniial00\u002Fbigbrain\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]