[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BTTJST542D152XMYAX8E03":3,"skill-same:01M6BTTJST542D152XMYAX8E03":65},{"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":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":48},"01M6BTTJST542D152XMYAX8E03","ask-matt",null,"Ask which skill or flow fits your situation. A router over the skills in this repo.","merikan\u002F.dotfiles","merikan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60756?v=4","01M6BTTGAQHH68RYGENCRZ4X65","Peter Merikan","01M6BTTGFDDD744BTP3V4T2WMR",24,"MIT","https:\u002F\u002Fgithub.com\u002Fmerikan\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fask-matt\u002FSKILL.md",[],[19,20],"ask matt","flow","2026-11-10 10:12:30",false,"---\nname: ask-matt\ndescription: Ask which skill or flow fits your situation. A router over the skills in this repo.\ndisable-model-invocation: true\n---\n\n# Ask Matt\n\nYou don't remember every skill, so ask.\n\nA **flow** is a path through the skills. Most paths run along one **main flow**, and two **on-ramps** merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.\n\n## The main flow: idea → ship\n\nThe route most work travels. You have an idea and want it built.\n\n1. **`\u002Fgrill-with-docs`** sharpens the idea by interview. Start here whenever you are **working in a working directory**: it's stateful, retaining what it learns in `GLOSSARY.md` and ADRs. (No working directory? Use `\u002Fgrill-me` instead, covered under Standalone. Both run the same `\u002Fgrilling` primitive; `grill-with-docs` is the one that leaves a paper trail, which makes it the better of the two whenever a repo is there to leave it in.)\n2. **Branch: can you settle every question in conversation?** If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by **`\u002Fhandoff`** in both directions (a prototype lives in its own directory, which is exactly what `\u002Fhandoff` is for; see Phase boundaries):\n   - **`\u002Fhandoff`** out, then open a fresh session against that file,\n   - **`\u002Fprototype`** to answer the question with throwaway code,\n   - **`\u002Fhandoff`** back what you learned, and reference it from the original idea thread.\n3. **Branch: is this a multi-session build?**\n   - **Yes** → **`\u002Fto-spec`** (turn the thread into a spec), then **`\u002Fto-tickets`** to split it into tracer-bullet tickets, each declaring its **blocking edges**. Then work the tickets one of two ways:\n     - **`\u002Fimplement`** per ticket, **`\u002Fclear`ing context between each one**. On a local tracker that's one file per ticket under `.scratch\u002F\u003Cfeature>\u002Fissues\u002F`, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed. Each ticket is self-contained, so the last one's context is disposable.\n     - **`\u002Fimplement-spec`** for the whole spec in one run. It reads the tickets as a **task graph**, runs implementer subagents across the ready **frontier** in parallel, and lands everything on one **integration branch**. Reach for it when you'd rather orchestrate the build than drive each ticket yourself.\n   - **No** → **`\u002Fimplement`** right here, in the same context window.\n\n   Either way, the code gets built by driving **`\u002Ftdd`** (one red-green slice at a time) and closes out with **`\u002Fcode-review`**, a two-axis review (Standards + Spec) of the diff. `\u002Fimplement` runs both per ticket; `\u002Fimplement-spec`'s implementers each drive `\u002Ftdd`, and it runs one `\u002Fcode-review` over the integration branch. Reach for **`\u002Ftdd`** on its own when you just want to build a concrete behaviour test-first without a full spec, and **`\u002Fcode-review`** on its own whenever you want to review a branch or PR against a fixed point.\n\n   When the work goes up as a pull request, **`\u002Fpr`** shapes the body: the smallest visual that shows the change, before\u002Fafter evidence that it works, and a one-way or two-way door call. It's model-invoked, so the agent reaches for it whenever it writes a PR.\n\n4. **`\u002Fretro`** closes the loop. After a build, and especially one that went sideways, it looks back over the session and suggests changes to the agent's **environment**, not the code: navigation pointers, automated checks, the coding standards `\u002Fcode-review` enforces, steering files, tooling. Mechanical mistakes become deterministic checks; judgement calls become coding standards. The next build then starts from a better environment.\n\n### Context hygiene\n\nKeep steps 1–3 in **one unbroken context window** (don't compact or clear until after `\u002Fto-tickets`) so the grilling, spec, and tickets all build on the same thinking. Each `\u002Fimplement` then starts fresh, working from the ticket. Run `\u002Fretro` in the session it's looking back on, before you clear; after clearing, point it at that session's log instead.\n\nThe limit on this is the **[smart zone](https:\u002F\u002Fwww.aihero.dev\u002Fai-coding-dictionary\u002Fsmart-zone)**: the window (~150k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `\u002Fto-tickets`, don't push on degraded; `\u002Fcompact` at the nearest phase boundary and carry on (see Phase boundaries).\n\n## On-ramps\n\nA starting situation that generates work, then merges onto the main flow.\n\n- **Bugs and requests piling up** → **`\u002Ftriage`**. It moves issues through triage roles and produces agent-ready issues, which **`\u002Fimplement`** later picks up.\n\n  Triage is only for issues **you didn't create**: bug reports, incoming feature requests, anything that arrives raw. Tickets that `\u002Fto-tickets` produced are already agent-ready, so **don't triage them**.\n\n- **Something's broken** → **`\u002Fdiagnosing-bugs`**. For the hard ones: the bug that resists a first glance, the intermittent flake, the regression that crept in between two known-good states. It refuses to theorise until it has a **tight feedback loop** (one command that already goes red on *this* bug), then fixes with a regression test. Once the fix is in, run **`\u002Fretro`** in the same session to ask what would have prevented the bug; where the real finding is that there's no good seam to lock it down, that's a job for **`\u002Fimprove-codebase-architecture`**.\n\n- **A huge, foggy effort: a greenfield project or a huge feature build, too big for one session** → **`\u002Fwayfinder`**, the most cognitively demanding flow here. When the way from here to the destination isn't visible yet, it charts a **shared map** of **decision tickets** on the issue tracker and resolves them one at a time, producing **decisions, not deliverables**, until the fog is pushed back and the way is clear. Where **`\u002Fgrill-with-docs`** sharpens an idea you can hold in one session, wayfinder is for the idea you can't, and it's slower and denser, so save it for exactly that, never a well-scoped feature.\n\n  When the map clears, **it hands off, it doesn't build**: merge onto the main flow at **`\u002Fto-spec`**, which collapses the map's linked decisions into a buildable plan, then `\u002Fto-tickets` and `\u002Fimplement` as usual. Looping the map straight into `\u002Fimplement` skips that collapse and throws the linked detail away, so go straight to `\u002Fimplement` only when the effort turned out genuinely small.\n\n## Codebase health\n\nNot feature work, just upkeep.\n\n- **`\u002Fimprove-codebase-architecture`** runs whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces **deepening opportunities**; picking one _generates an idea_ you can take into the main flow at `\u002Fgrill-with-docs`. It's the survey that finds the candidates; **`\u002Fcodebase-design`** (below) is the bench you design the chosen one on.\n\n## Vocabulary underneath\n\nTwo model-invoked references that run *beneath* the other skills, each the single source of truth for its vocabulary. Reach for them directly when the **words**, not the process, are the problem; or let the skills above pull them in.\n\n- **`\u002Fdomain-modeling`**: sharpen the project's *domain* language: challenge a fuzzy term, resolve an overloaded word (\"account\" doing three jobs), record a hard-to-reverse decision as an ADR. It's the active discipline `\u002Fgrill-with-docs` drives to keep `GLOSSARY.md` a clean glossary.\n- **`\u002Fcodebase-design`** is the deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) for designing a module's *shape*: a lot of behaviour behind a small interface at a clean seam. `\u002Ftdd` and `\u002Fimprove-codebase-architecture` both speak it.\n\n## Phase boundaries\n\nA **phase** is a chunk of work inside a session: the grilling, the implementation, the QA. At the **boundary** between two of them you have five options, and picking between them is the fuzziest decision in this whole map:\n\n- **Continue**: stay put. Costs nothing, loses nothing.\n- **`\u002Fclear`**: empty the window, when nothing here matters to what's next.\n- **`\u002Fhandoff`** writes a portable markdown file. Narrow: only for a **new harness**, a **new directory**, a **colleague**, or forking a side task **mid-phase**. What it buys is portability.\n- **Subagent**: send a tightly-scoped task to its own window and get a report back.\n- **`\u002Fcompact`** compresses this context and seeds a fresh session with it. The **default**, at the bottom of the tree rather than the first reach.\n\nRead [PHASE-BOUNDARIES.md](PHASE-BOUNDARIES.md) for the ordered tree: the five questions, the reasoning behind each branch, and why the primary-source cost makes **Continue** the one to rule out first. Make the decision **at** a boundary; mid-phase, continue or split the rest into subagents.\n\n## Standalone\n\nOff the main flow entirely.\n\n- **`\u002Fgrill-me`**: the same relentless interview as `\u002Fgrill-with-docs`, but **stateless**: it saves nothing locally and builds no `GLOSSARY.md`. Reach for it when you are **not working in a working directory** (sharpening a plan, a design, a piece of writing, anything with no repo under it). If you are in a working directory, use `\u002Fgrill-with-docs` instead: it runs the same interview and leaves a paper trail, so it is strictly the better one.\n- **`\u002Fgrilling`** is the interview primitive itself: rounds, the frontier, facts are the agent's job and decisions are yours. `\u002Fgrill-me` and `\u002Fgrill-with-docs` are the two named ways in, and `\u002Ftriage`, `\u002Fwayfinder` and `\u002Fimprove-codebase-architecture` all run it internally. Reach for it directly only when you want the interview with no wrapper around it.\n- **`\u002Fprototype`** is a small, throwaway program that answers one design question: does this state model feel right, or what should this UI look like. Throwaway is a constraint on how the code is written, not a promise to destroy it: the answer folds into the real code, and the prototype itself is kept as a **primary source** on a `prototype\u002F\u003Cname>` branch out of main, pointed at from the implementation issue. It's the detour in step 2 of the main flow, but reach for it any time a design question is hard to settle on paper.\n- **`\u002Fresearch`**: delegate reading legwork to a **background agent**: it investigates a question against **primary sources**, then leaves a cited Markdown file in the repo. Keep working while it reads. The file it produces is something to take *into* the main flow at `\u002Fgrill-with-docs`, since research feeds the thinking rather than replacing it.\n- **`\u002Fto-questionnaire`** comes in when the thing blocking you isn't in your head or the codebase but in **someone else's**, and it writes them a questionnaire to fill in. It's the inverse of `\u002Fgrill-me`: instead of interviewing you about the subject, it interviews you about the **send** (who it's going to, what you need back) and aims the questions at the gap. What comes back is material for `\u002Fgrill-with-docs` or `\u002Fto-spec`.\n- **`\u002Fwizard`** is for the steps only a **human** can take: provisioning infrastructure, setting up credentials or CI secrets, clicking through an unfamiliar third-party dashboard, running a one-off migration or cutover. It generates an interactive bash script that opens each URL, captures each value, and writes it into `.env` and GitHub secrets, so the procedure stops being something you re-explain to an agent every time. Model-invoked, so the agent reaches for it the moment it hits a wall only you can pass. If the agent could just do it itself, it should; this is for where a human is genuinely in the loop.\n- **`\u002Fwait-what`** is the corrective for a message that didn't land. Use it mid-conversation, inside any other skill, and the agent re-pitches what it just said with the context you were missing, in plain English, using the `GLOSSARY.md` vocabulary. It works after the fact; `\u002Fgrill-with-docs` is the upfront cure, because a shared language agreed early is what stops the jargon arriving at all.\n- **`\u002Fteach`**: learn a concept over multiple sessions, using the current directory as a stateful workspace.\n- **`\u002Fwriting-for-agents`** is the reference for writing documents agents consume: skills, AGENTS.md, pointed-at docs.\n\n## Precondition\n\n**`\u002Fsetup-matt-pocock-skills`**: run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.\n","# Ask Matt\n\nYou don't remember every skill, so ask.\n\nA **flow** is a path through the skills. Most paths run along one **main flow**, and two **on-ramps** merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.\n\n## The main flow: idea → ship\n\nThe route most work travels. You have an idea and want it built.\n\n1. **`\u002Fgrill-with-docs`** sharpens the idea by interview. Start here whenever you are **working in a working directory**: it's stateful, retaining what it learns in `GLOSSARY.md` and ADRs. (No working directory? Use `\u002Fgrill-me` instead, covered under Standalone. Both run the same `\u002Fgrilling` primitive; `grill-with-docs` is the one that leaves a paper trail, which makes it the better of the two whenever a repo is there to leave it in.)\n2. **Branch: can you settle every question in conversation?** If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by **`\u002Fhandoff`** in both directions (a prototype lives in its own directory, which is exactly what `\u002Fhandoff` is for; see Phase boundaries):\n   - **`\u002Fhandoff`** out, then open a fresh session against that file,\n   - **`\u002Fprototype`** to answer the question with throwaway code,\n   - **`\u002Fhandoff`** back what you learned, and reference it from the original idea thread.\n3. **Branch: is this a multi-session build?**\n   - **Yes** → **`\u002Fto-spec`** (turn the thread into a spec), then **`\u002Fto-tickets`** to split it into tracer-bullet tickets, each declaring its **blocking edges**. Then work the tickets one of two ways:\n     - **`\u002Fimplement`** per ticket, **`\u002Fclear`ing context between each one**. On a local tracker that's one file per ticket under `.scratch\u002F\u003Cfeature>\u002Fissues\u002F`, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed. Each ticket is self-contained, so the last one's context is disposable.\n     - **`\u002Fimplement-spec`** for the whole spec in one run. It reads the tickets as a **task graph**, runs implementer subagents across the ready **frontier** in parallel, and lands everything on one **integration branch**. Reach for it when you'd rather orchestrate the build than drive each ticket yourself.\n   - **No** → **`\u002Fimplement`** right here, in the same context window.\n\n   Either way, the code gets built by driving **`\u002Ftdd`** (one red-green slice at a time) and closes out with **`\u002Fcode-review`**, a two-axis review (Standards + Spec) of the diff. `\u002Fimplement` runs both per ticket; `\u002Fimplement-spec`'s implementers each drive `\u002Ftdd`, and it runs one `\u002Fcode-review` over the integration branch. Reach for **`\u002Ftdd`** on its own when you just want to build a concrete behaviour test-first without a full spec, and **`\u002Fcode-review`** on its own whenever you want to review a branch or PR against a fixed point.\n\n   When the work goes up as a pull request, **`\u002Fpr`** shapes the body: the smallest visual that shows the change, before\u002Fafter evidence that it works, and a one-way or two-way door call. It's model-invoked, so the agent reaches for it whenever it writes a PR.\n\n4. **`\u002Fretro`** closes the loop. After a build, and especially one that went sideways, it looks back over the session and suggests changes to the agent's **environment**, not the code: navigation pointers, automated checks, the coding standards `\u002Fcode-review` enforces, steering files, tooling. Mechanical mistakes become deterministic checks; judgement calls become coding standards. The next build then starts from a better environment.\n\n### Context hygiene\n\nKeep steps 1–3 in **one unbroken context window** (don't compact or clear until after `\u002Fto-tickets`) so the grilling, spec, and tickets all build on the same thinking. Each `\u002Fimplement` then starts fresh, working from the ticket. Run `\u002Fretro` in the session it's looking back on, before you clear; after clearing, point it at that session's log instead.\n\nThe limit on this is the **[smart zone](https:\u002F\u002Fwww.aihero.dev\u002Fai-coding-dictionary\u002Fsmart-zone)**: the window (~150k tokens on state-of-the-art models) within which the model still reasons sharply. If a session approaches it before `\u002Fto-tickets`, don't push on degraded; `\u002Fcompact` at the nearest phase boundary and carry on (see Phase boundaries).\n\n## On-ramps\n\nA starting situation that generates work, then merges onto the main flow.\n\n- **Bugs and requests piling up** → **`\u002Ftriage`**. It moves issues through triage roles and produces agent-ready issues, which **`\u002Fimplement`** later picks up.\n\n  Triage is only for issues **you didn't create**: bug reports, incoming feature requests, anything that arrives raw. Tickets that `\u002Fto-tickets` produced are already agent-ready, so **don't triage them**.\n\n- **Something's broken** → **`\u002Fdiagnosing-bugs`**. For the hard ones: the bug that resists a first glance, the intermittent flake, the regression that crept in between two known-good states. It refuses to theorise until it has a **tight feedback loop** (one command that already goes red on *this* bug), then fixes with a regression test. Once the fix is in, run **`\u002Fretro`** in the same session to ask what would have prevented the bug; where the real finding is that there's no good seam to lock it down, that's a job for **`\u002Fimprove-codebase-architecture`**.\n\n- **A huge, foggy effort: a greenfield project or a huge feature build, too big for one session** → **`\u002Fwayfinder`**, the most cognitively demanding flow here. When the way from here to the destination isn't visible yet, it charts a **shared map** of **decision tickets** on the issue tracker and resolves them one at a time, producing **decisions, not deliverables**, until the fog is pushed back and the way is clear. Where **`\u002Fgrill-with-docs`** sharpens an idea you can hold in one session, wayfinder is for the idea you can't, and it's slower and denser, so save it for exactly that, never a well-scoped feature.\n\n  When the map clears, **it hands off, it doesn't build**: merge onto the main flow at **`\u002Fto-spec`**, which collapses the map's linked decisions into a buildable plan, then `\u002Fto-tickets` and `\u002Fimplement` as usual. Looping the map straight into `\u002Fimplement` skips that collapse and throws the linked detail away, so go straight to `\u002Fimplement` only when the effort turned out genuinely small.\n\n## Codebase health\n\nNot feature work, just upkeep.\n\n- **`\u002Fimprove-codebase-architecture`** runs whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces **deepening opportunities**; picking one _generates an idea_ you can take into the main flow at `\u002Fgrill-with-docs`. It's the survey that finds the candidates; **`\u002Fcodebase-design`** (below) is the bench you design the chosen one on.\n\n## Vocabulary underneath\n\nTwo model-invoked references that run *beneath* the other skills, each the single source of truth for its vocabulary. Reach for them directly when the **words**, not the process, are the problem; or let the skills above pull them in.\n\n- **`\u002Fdomain-modeling`**: sharpen the project's *domain* language: challenge a fuzzy term, resolve an overloaded word (\"account\" doing three jobs), record a hard-to-reverse decision as an ADR. It's the active discipline `\u002Fgrill-with-docs` drives to keep `GLOSSARY.md` a clean glossary.\n- **`\u002Fcodebase-design`** is the deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) for designing a module's *shape*: a lot of behaviour behind a small interface at a clean seam. `\u002Ftdd` and `\u002Fimprove-codebase-architecture` both speak it.\n\n## Phase boundaries\n\nA **phase** is a chunk of work inside a session: the grilling, the implementation, the QA. At the **boundary** between two of them you have five options, and picking between them is the fuzziest decision in this whole map:\n\n- **Continue**: stay put. Costs nothing, loses nothing.\n- **`\u002Fclear`**: empty the window, when nothing here matters to what's next.\n- **`\u002Fhandoff`** writes a portable markdown file. Narrow: only for a **new harness**, a **new directory**, a **colleague**, or forking a side task **mid-phase**. What it buys is portability.\n- **Subagent**: send a tightly-scoped task to its own window and get a report back.\n- **`\u002Fcompact`** compresses this context and seeds a fresh session with it. The **default**, at the bottom of the tree rather than the first reach.\n\nRead [PHASE-BOUNDARIES.md](PHASE-BOUNDARIES.md) for the ordered tree: the five questions, the reasoning behind each branch, and why the primary-source cost makes **Continue** the one to rule out first. Make the decision **at** a boundary; mid-phase, continue or split the rest into subagents.\n\n## Standalone\n\nOff the main flow entirely.\n\n- **`\u002Fgrill-me`**: the same relentless interview as `\u002Fgrill-with-docs`, but **stateless**: it saves nothing locally and builds no `GLOSSARY.md`. Reach for it when you are **not working in a working directory** (sharpening a plan, a design, a piece of writing, anything with no repo under it). If you are in a working directory, use `\u002Fgrill-with-docs` instead: it runs the same interview and leaves a paper trail, so it is strictly the better one.\n- **`\u002Fgrilling`** is the interview primitive itself: rounds, the frontier, facts are the agent's job and decisions are yours. `\u002Fgrill-me` and `\u002Fgrill-with-docs` are the two named ways in, and `\u002Ftriage`, `\u002Fwayfinder` and `\u002Fimprove-codebase-architecture` all run it internally. Reach for it directly only when you want the interview with no wrapper around it.\n- **`\u002Fprototype`** is a small, throwaway program that answers one design question: does this state model feel right, or what should this UI look like. Throwaway is a constraint on how the code is written, not a promise to destroy it: the answer folds into the real code, and the prototype itself is kept as a **primary source** on a `prototype\u002F\u003Cname>` branch out of main, pointed at from the implementation issue. It's the detour in step 2 of the main flow, but reach for it any time a design question is hard to settle on paper.\n- **`\u002Fresearch`**: delegate reading legwork to a **background agent**: it investigates a question against **primary sources**, then leaves a cited Markdown file in the repo. Keep working while it reads. The file it produces is something to take *into* the main flow at `\u002Fgrill-with-docs`, since research feeds the thinking rather than replacing it.\n- **`\u002Fto-questionnaire`** comes in when the thing blocking you isn't in your head or the codebase but in **someone else's**, and it writes them a questionnaire to fill in. It's the inverse of `\u002Fgrill-me`: instead of interviewing you about the subject, it interviews you about the **send** (who it's going to, what you need back) and aims the questions at the gap. What comes back is material for `\u002Fgrill-with-docs` or `\u002Fto-spec`.\n- **`\u002Fwizard`** is for the steps only a **human** can take: provisioning infrastructure, setting up credentials or CI secrets, clicking through an unfamiliar third-party dashboard, running a one-off migration or cutover. It generates an interactive bash script that opens each URL, captures each value, and writes it into `.env` and GitHub secrets, so the procedure stops being something you re-explain to an agent every time. Model-invoked, so the agent reaches for it the moment it hits a wall only you can pass. If the agent could just do it itself, it should; this is for where a human is genuinely in the loop.\n- **`\u002Fwait-what`** is the corrective for a message that didn't land. Use it mid-conversation, inside any other skill, and the agent re-pitches what it just said with the context you were missing, in plain English, using the `GLOSSARY.md` vocabulary. It works after the fact; `\u002Fgrill-with-docs` is the upfront cure, because a shared language agreed early is what stops the jargon arriving at all.\n- **`\u002Fteach`**: learn a concept over multiple sessions, using the current directory as a stateful workspace.\n- **`\u002Fwriting-for-agents`** is the reference for writing documents agents consume: skills, AGENTS.md, pointed-at docs.\n\n## Precondition\n\n**`\u002Fsetup-matt-pocock-skills`**: run before your first engineering flow to configure the issue tracker, triage labels, and doc layout the other skills assume. Custom issue trackers also work.\n",{"name":5,"description":7,"disable-model-invocation":26},true,"main","8a4d0d0c9cff41dc142e34ad04b7a5bbc5237e27","config\u002Fagents\u002Fskills\u002Fask-matt",5,"https:\u002F\u002Fgithub.com\u002Fmerikan\u002F.dotfiles","https:\u002F\u002Fgithub.com\u002Fmerikan","https:\u002F\u002Fmerikan.com","In software development, complexity might be admired but simplicity is always rewarded.\r\n@merikan:matrix.org","2026-11-13 01:58:46",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":26},[38,41,44],{"tool":39,"command":40},"npx","npx skills add merikan\u002F.dotfiles --skill ask-matt",{"tool":42,"command":43},"bunx","bunx skills add merikan\u002F.dotfiles --skill ask-matt",{"tool":45,"command":46},"pnpm","pnpm dlx skills add merikan\u002F.dotfiles --skill ask-matt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmerikan\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fask-matt\u002FSKILL.md",[49,55,59],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",137,"https:\u002F\u002Fgithub.com\u002Fmerikan\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fask-matt\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"PHASE-BOUNDARIES.md",4249,"https:\u002F\u002Fgithub.com\u002Fmerikan\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fask-matt\u002FPHASE-BOUNDARIES.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"scripts\u002Fbilling-summary.sh","SCRIPT","脚本",3265,"https:\u002F\u002Fgithub.com\u002Flaurigates\u002Fclaude-plugins\u002Fblob\u002Fmain\u002Ffinops-plugin\u002Fskills\u002Ffinops-overview\u002Fscripts\u002Fbilling-summary.sh",[66,100,110,120,131,141],{"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":6,"sourceHtmlUrl":70,"categories":71,"keywords":82,"publishedAt":21},"01M6M2D557KJ8JGQFPVV7VWBVZ","writing-review","Review a blog post or article draft and write numbered findings to a review file, then track the author's fixes across rounds. Use when the user asks to review, give feedback on, or suggest improvements to a blog post or article.","https:\u002F\u002Fgithub.com\u002Fmerikan\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fwriting-review\u002FSKILL.md",[72,77],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99],"writing review","review","writing","give feedback","track","use","draft","across","article","post","fixes","user","write","blog post","feedback","blog","file",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":108,"publishedAt":21},"01M6BTWQZM2ZSGTQ9N2ZSNTZBC","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Fmerikan\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[106,107],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[109,85],"writing shape",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":118,"publishedAt":21},"01M6BTWP834Z8KXFYVWCPFDA81","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Fmerikan\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fwriting-fragments\u002FSKILL.md",[116,117],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[119,85],"writing fragments",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":128,"publishedAt":21},"01M6BTWMQEDS6TBBDEWR59HYA9","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fmerikan\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[126,127],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[129,85,130],"writing for agents","documents",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":139,"publishedAt":21},"01M6BTWK4HTM6KQMW9WPR290JN","writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Fmerikan\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fwriting-beats\u002FSKILL.md",[137,138],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},[140,85],"writing beats",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":21},"01M6BTWGX31186Q23VXHJHAA48","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fmerikan\u002F.dotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fwizard\u002FSKILL.md",[],[143,148,149,150,151,152,153,154,155],"dashboard","Bash","secrets","credentials","provisioning","ci","generate","infrastructure"]