[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSQQAGG0S6HPZMX52T2CXD":3,"skill-same:01M6CSQQAGG0S6HPZMX52T2CXD":75},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":51},"01M6CSQQAGG0S6HPZMX52T2CXD","ask-matt",null,"Ask which skill or flow fits your situation. A router over the skills in this repo.","Volontariapp\u002Fmeta","Volontariapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263673138?v=4","01M6CSQNQ3J4SKRWA512JQF5K7","VolontariApp","01M6CSQNV8T2M4PR5A22DKHY5T",0,"MIT","https:\u002F\u002Fgithub.com\u002FVolontariapp\u002Fmeta\u002Fblob\u002Fmain\u002F.agents\u002Fplugins\u002Fmatt-pocock\u002Fskills\u002Fask-matt\u002FSKILL.md",[],[19,20,21,22,23,24,25],"ask matt","ask","flow","repo","router","true","which","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 `CONTEXT.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**. 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: kick off **`\u002Fimplement`** per ticket, **`\u002Fclear`ing context between each one**. Each ticket is self-contained, so the last one's context is disposable.\n   - **No** → **`\u002Fimplement`** right here, in the same context window.\n\n   Either way, **`\u002Fimplement`** builds each issue by driving **`\u002Ftdd`** internally (one red-green slice at a time), then closes out by running **`\u002Fcode-review`**, a two-axis review (Standards + Spec) of the diff, before committing. 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### 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.\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. Its post-mortem hands off to **`\u002Fimprove-codebase-architecture`** when the real finding is that there's no good seam to lock the bug down.\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 `CONTEXT.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 `CONTEXT.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- **`\u002Fresolving-merge-conflicts`** works an in-progress merge or rebase conflict hunk by hunk, resolving by **intent** traced to each side's primary source rather than by picking lines, then finishes the operation. It never runs `--abort`. Standalone and off every flow: reach for it when you are already mid-conflict.\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 `CONTEXT.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 `CONTEXT.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**. 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: kick off **`\u002Fimplement`** per ticket, **`\u002Fclear`ing context between each one**. Each ticket is self-contained, so the last one's context is disposable.\n   - **No** → **`\u002Fimplement`** right here, in the same context window.\n\n   Either way, **`\u002Fimplement`** builds each issue by driving **`\u002Ftdd`** internally (one red-green slice at a time), then closes out by running **`\u002Fcode-review`**, a two-axis review (Standards + Spec) of the diff, before committing. 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### 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.\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. Its post-mortem hands off to **`\u002Fimprove-codebase-architecture`** when the real finding is that there's no good seam to lock the bug down.\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 `CONTEXT.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 `CONTEXT.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- **`\u002Fresolving-merge-conflicts`** works an in-progress merge or rebase conflict hunk by hunk, resolving by **intent** traced to each side's primary source rather than by picking lines, then finishes the operation. It never runs `--abort`. Standalone and off every flow: reach for it when you are already mid-conflict.\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 `CONTEXT.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":31},true,"main","85beb751b53b81db36c81ccfa255e65798c9b362",".agents\u002Fplugins\u002Fmatt-pocock\u002Fskills\u002Fask-matt","https:\u002F\u002Fgithub.com\u002FVolontariapp\u002Fmeta","https:\u002F\u002Fgithub.com\u002FVolontariapp","Volontariapp — Application Web\u002FMobile scalabelle construite sur une architecture microservices événementielle (Event-Driven Architecture), implémentant le Trans","2026-11-10 23:40:22",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":31},[41,44,47],{"tool":42,"command":43},"npx","npx skills add Volontariapp\u002Fmeta --skill ask-matt",{"tool":45,"command":46},"bunx","bunx skills add Volontariapp\u002Fmeta --skill ask-matt",{"tool":48,"command":49},"pnpm","pnpm dlx skills add Volontariapp\u002Fmeta --skill ask-matt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVolontariapp\u002Fmeta\u002Fblob\u002Fmain\u002F.agents\u002Fplugins\u002Fmatt-pocock\u002Fskills\u002Fask-matt\u002FSKILL.md",[52,58,62,67,71],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"agents\u002Fopenai.yaml","REFERENCE","参考文档",137,"https:\u002F\u002Fgithub.com\u002FVolontariapp\u002Fmeta\u002Fblob\u002Fmain\u002F.agents\u002Fplugins\u002Fmatt-pocock\u002Fskills\u002Fask-matt\u002Fagents\u002Fopenai.yaml",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"example.html",74546,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FPPT-Design\u002Fopen-design-html-ppt-zhangzara-broadside\u002Fexample.html",{"path":63,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"LICENSE","许可证",1067,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FPPT-Design\u002Fopen-design-html-ppt-zhangzara-broadside\u002FLICENSE",{"path":68,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":69,"sourceHtmlUrl":70},"PHASE-BOUNDARIES.md",4249,"https:\u002F\u002Fgithub.com\u002FVolontariapp\u002Fmeta\u002Fblob\u002Fmain\u002F.agents\u002Fplugins\u002Fmatt-pocock\u002Fskills\u002Fask-matt\u002FPHASE-BOUNDARIES.md",{"path":72,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":73,"sourceHtmlUrl":74},"template.json",1746,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FPPT-Design\u002Fopen-design-html-ppt-zhangzara-broadside\u002Ftemplate.json",[76,102,131,158,182,201],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":26},"01M6CSW3Y5ZHVBF5BX7S5BAVS0","volontariapp-user-account-deletion","Suppression de compte en deux temps (PENDING_DELETION): requestDeletionWithUserDeleted, finalizeDeletion, fan-out de user.deleted vers les domaines et gather ws. A utiliser pour tout changement de domain-user touchant la suppression, le statut ou le cycle de vie d'un user.","https:\u002F\u002Fgithub.com\u002FVolontariapp\u002Fmeta\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvolontariapp-user-account-deletion\u002FSKILL.md",[],[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101],"volontariapp user account deletion","user","account deletion","deletion","cycle","gather","sonnet","pending","de","code","claude-code","reference","npm","user-account-deletion","src","en","domain","npm-packages","packages",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":113,"publishedAt":26},"01M6CSVC1ZW30DDFZ8VMEYAAK6","volontariapp-proto-contract-evolution","Modifier un contrat Protobuf de proto-registry (champ, message, enum, RPC) sans casser la compatibilité wire, puis suivre la cascade proto-registry, PR automatique dans npm-packages, publication, consommateurs. À utiliser avant toute édition d'un .proto.","https:\u002F\u002Fgithub.com\u002FVolontariapp\u002Fmeta\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvolontariapp-proto-contract-evolution\u002FSKILL.md",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[114,115,116,117,92,118,119,101,120,121,122,123,124,95,125,126,127,128,129,130],"evolution","volontariapp proto contract evolution","grpc","lint","workflows","analyze","rpc","ci","pr","protobuf","message","registry","sans","sync","yaml","playbook","github",{"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":142,"publishedAt":26},"01M6CSV99ET2Z9W4W4DAK4CMQP","volontariapp-meta-scripts","Utiliser et faire evoluer la CLI Node de meta (setup, doctor, migrate, certs, repos, bump) et le manifeste repos.json, source unique des repos et unites du workspace.","https:\u002F\u002Fgithub.com\u002FVolontariapp\u002Fmeta\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvolontariapp-meta-scripts\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[143,144,145,92,146,93,147,148,149,150,151,152,153,154,155,156,157],"Meta","volontariapp meta scripts","repos","migrate","setup","meta-scripts","json","node","workspace","shell","bump","cli","doctor","draft","install",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":167,"publishedAt":26},"01M6CSTPHNTGE0WF5CPE8W7ZYQ","volontariapp-implement-async-event-flow","Guide pas-à-pas pour concevoir et implémenter un flux asynchrone complet (messaging -> outbox -> post-processors -> ws-service -> client).","https:\u002F\u002Fgithub.com\u002FVolontariapp\u002Fmeta\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvolontariapp-implement-async-event-flow\u002FSKILL.md",[164],{"categoryNo":165,"categoryName":166,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000009","前端开发",[168,169,170,21,171,172,97,173,174,125,175,176,100,177,178,101,179,180,92,181],"async","implement","volontariapp implement async event flow","event","messaging","mapping","flux","streams","flows","shared","outbox","processor","architecture","runner",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":191,"publishedAt":26},"01M6CSRQHS0T9955M8CTA5BYJQ","research","Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.","https:\u002F\u002Fgithub.com\u002FVolontariapp\u002Fmeta\u002Fblob\u002Fmain\u002F.agents\u002Fplugins\u002Fmatt-pocock\u002Fskills\u002Fresearch\u002FSKILL.md",[188],{"categoryNo":189,"categoryName":190,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000021","资料检索与研究",[184,192,84,193,22,194,195,196,197,198,199,200],"api","file","markdown","docs","capture","use","question","trust","investigate",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":210,"publishedAt":26},"01M6CSRMZ82M1YK96Z4SW1STTD","prototype","Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.","https:\u002F\u002Fgithub.com\u002FVolontariapp\u002Fmeta\u002Fblob\u002Fmain\u002F.agents\u002Fplugins\u002Fmatt-pocock\u002Fskills\u002Fprototype\u002FSKILL.md",[207],{"categoryNo":208,"categoryName":209,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000032","设计师",[203,211,84,212,197,213,198,214,215,216,217,218],"check","ui","look","design","explore","model","build","state"]