[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72BBNMDARCMSR35HS8REEKA":3,"skill-same:01M72BBNMDARCMSR35HS8REEKA":79},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M72BBNMDARCMSR35HS8REEKA","setup-matt-pocock-skills",null,"Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.","guhans6\u002Fagent-workbench","guhans6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104162539?v=4","01M72B46KNSP1Y4W32NAP9HSCS","Guhan","01M72B46MCE81N1B04M3PWX3P7",0,"MIT","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsetup-matt-pocock-skills\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: setup-matt-pocock-skills\ndescription: \"Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.\"\ndisable-model-invocation: true\n---\n\n# Setup Matt Pocock's Skills\n\nScaffold the per-repo configuration that the engineering skills assume:\n\n- **Issue tracker**: where issues live (GitHub by default; local markdown is also supported out of the box)\n- **Triage labels**: the strings used for the five canonical triage roles\n- **Domain docs**: where `GLOSSARY.md` and ADRs live, and the consumer rules for reading them\n- **Validated checkpoints**: a checked-in project protocol and relative instruction pointer for dependent increments or uncertain integration boundaries\n\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.\n\n## Process\n\n### 1. Explore\n\nLook at the current repo to understand its starting state. Read whatever exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig`: is this a GitHub repo? Which one?\n- `AGENTS.md` and `CLAUDE.md` at the repo root: does either exist? Is there already an `## Agent skills` section in either?\n- `GLOSSARY.md` and `GLOSSARY-MAP.md` at the repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` directories\n- `docs\u002Fagents\u002F`: does this skill's prior output already exist?\n- `.scratch\u002F`: a sign that a local-markdown issue tracker convention is already in use\n- Existing workflow\u002Fcheckpoint pointers and delivery references: identify the current authority before proposing adoption; inspect pending edits and preserve local adaptations.\n- [Shared checkpoint protocol](..\u002F..\u002Fworkflows\u002Fvalidated-checkpoints.md): resolve this relative to the installed skill folder and read the actual file. If missing, stop setup and report the missing reference plus the need to install the consuming skills with their shared `workflows\u002F` directory. Use the supplied protocol, not invented replacement contents. Record its SHA-256 content digest and available source revision for project-copy provenance.\n- Is the `triage` skill installed? (a `triage` skill folder alongside this one, or `triage` in your available skills.) This decides whether Section B runs at all.\n- Monorepo signals: a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages\u002F*` with its own `src\u002F`. These are present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then take the sections in order. One section, one answer, then the next.\n\nLead each section with the recommended answer so the user can accept it in a word. Give a one-line explainer only when the choice genuinely branches; skip the section entirely when exploration already settled it (Section B when `triage` isn't installed, Section C when there's no monorepo).\n\n**Section A: Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-tickets`, `triage`, and `to-spec` read from and write to it. They need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow some other workflow you describe. Pick the place you actually track work for this repo.\n\nDefault posture: these skills were designed for GitHub. If a `git remote` points at GitHub, propose that. If a `git remote` points at GitLab (`gitlab.com` or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:\n\n- **GitHub**: issues live in the repo's GitHub Issues (uses the `gh` CLI)\n- **GitLab**: issues live in the repo's GitLab Issues (uses the [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown**: issues live as files under `.scratch\u002F\u003Cfeature>\u002F` in this repo (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.): ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose\n\nRecord the choice in `docs\u002Fagents\u002Fissue-tracker.md`. The GitHub and GitLab templates carry a \"PRs as a request surface\" flag, defaulted **off**. Leave it off and don't raise it: a user who wants external PRs in the triage queue can flip the flag in the file later.\n\n**Section B: Triage label vocabulary.** Skip this section entirely if the `triage` skill isn't installed (exploration told you), since an uninstalled skill needs no labels.\n\nIf it is installed, ask exactly one question:\n\n> Do you want to keep the default triage labels? (recommended: **yes**)\n\nThe defaults are the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. On **yes**, write them as-is. Only if the user says no, usually because their tracker already uses other names (e.g. `bug:triage` for `needs-triage`), collect the overrides so `triage` applies existing labels instead of creating duplicates.\n\n**Section C: Domain docs.** Default to **single-context** (one `GLOSSARY.md` + `docs\u002Fadr\u002F` at the repo root). This fits almost every repo; write it without asking.\n\nOffer **multi-context** (a root `GLOSSARY-MAP.md` pointing to per-context `GLOSSARY.md` files) only when exploration found monorepo signals. Then confirm which layout they want.\n\n**Section D: Validated checkpoints.** Recommend reusing an existing equivalent\nproject reference and pointer. Otherwise propose a checked-in copy at\n`docs\u002Fagents\u002Fvalidated-checkpoints.md` with the provenance footer from\n[checkpoint-adoption.md](.\u002Fcheckpoint-adoption.md), and its relative pointer in the\nchosen instruction file. Resolve conflicting checkpoint pointers with the user\nbefore selecting one. For an existing copy, compare its recorded source digest\nwith the current project protocol body's digest (bytes before the adoption marker\ndefined in the seed) and the proposed source digest. A changed project body is a local modification:\nmerge the proposed update with those changes and preview the exact diff. If the\nrecorded source identity is missing or cannot establish the baseline, resolve that\ngap before replacing content. Identical source and approved project copy need no\nupdate. Consume existing delivery guidance; leave its Definition of\nDone and delivery authority with that reference. Establishing missing delivery\nagreements belongs to `setup-delivery-workflow`, a separate explicit setup.\n\n### 3. Confirm and edit\n\nShow the user a draft of:\n\n- The `## Agent skills` block to add to whichever of `CLAUDE.md` \u002F `AGENTS.md` is being edited (see step 4 for selection rules)\n- The contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Fdomain.md`, and `docs\u002Fagents\u002Ftriage-labels.md` (the last only when `triage` is installed)\n- The complete checkpoint copy and provenance footer (or proposed edits to the existing reference), and its exact relative pointer diff\n\nLet them edit, then obtain explicit approval for the exact proposed changes\nbefore any project write. If declined or unresolved, report the remaining gap and\nstop without writes. Recheck pending edits before applying approval; request a\nrevised approval if intervening changes conflict.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `CLAUDE.md` exists, edit it.\n- Else if `AGENTS.md` exists, edit it.\n- If neither exists, ask the user which one to create; don't pick for them.\n\nNever create `AGENTS.md` when `CLAUDE.md` already exists (or vice versa); always edit the one that's already there.\n\nIf an `## Agent skills` block already exists in the chosen file, update only the approved contents in-place rather than appending a duplicate. Preserve surrounding sections and local edits within the block. Reuse an existing workflow\u002Fcheckpoint pointer instead of creating a second one; identical approved setup is a no-op.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout: \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n\n```\n\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `triage` is installed and Section B ran. When it isn't, both are omitted.\n\nMerge the approved checkpoint pointer from\n[checkpoint-adoption.md](.\u002Fcheckpoint-adoption.md) into this block, or update the\nexisting workflow pointer once. When reusing another reference, point to its\nactual project-relative path. Copy the resolved shared\nprotocol into the approved project path and append completed provenance fields;\nkeep existing local changes unless their replacement was explicitly approved.\nThis skill configures project files only; global instructions, skill installation,\npublication and enablement are outside this setup.\n\nThen write the other docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md): GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md): GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md): local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md): label mapping (only if `triage` is installed)\n- [domain.md](.\u002Fdomain.md): domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nRead back every approved file and resolve the relative instruction pointer from\nthe chosen file's directory. Inspect the diff for preserved unrelated\u002Fpending\nedits and evaluate a rerun: identical setup must make no changes. Report the\nchanged paths (or already present), checkpoint source revision and digest, pointer\nreachability and unresolved gaps. Static inspection establishes the configured\nfiles, not host loading or live-model adherence; in a CLAUDE-only repo, retain\nCLAUDE-first selection and report any unverified host loading explicitly.\n\nTell the user which engineering skills now have project references. They can edit\n`docs\u002Fagents\u002F*.md` directly later; checkpoint copies retain their provenance and\nlocal adaptations when reviewed source updates are adopted. Setup is complete\nonly when approved files and their pointer agree and existing content is preserved.\n","# Setup Matt Pocock's Skills\n\nScaffold the per-repo configuration that the engineering skills assume:\n\n- **Issue tracker**: where issues live (GitHub by default; local markdown is also supported out of the box)\n- **Triage labels**: the strings used for the five canonical triage roles\n- **Domain docs**: where `GLOSSARY.md` and ADRs live, and the consumer rules for reading them\n- **Validated checkpoints**: a checked-in project protocol and relative instruction pointer for dependent increments or uncertain integration boundaries\n\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.\n\n## Process\n\n### 1. Explore\n\nLook at the current repo to understand its starting state. Read whatever exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig`: is this a GitHub repo? Which one?\n- `AGENTS.md` and `CLAUDE.md` at the repo root: does either exist? Is there already an `## Agent skills` section in either?\n- `GLOSSARY.md` and `GLOSSARY-MAP.md` at the repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` directories\n- `docs\u002Fagents\u002F`: does this skill's prior output already exist?\n- `.scratch\u002F`: a sign that a local-markdown issue tracker convention is already in use\n- Existing workflow\u002Fcheckpoint pointers and delivery references: identify the current authority before proposing adoption; inspect pending edits and preserve local adaptations.\n- [Shared checkpoint protocol](..\u002F..\u002Fworkflows\u002Fvalidated-checkpoints.md): resolve this relative to the installed skill folder and read the actual file. If missing, stop setup and report the missing reference plus the need to install the consuming skills with their shared `workflows\u002F` directory. Use the supplied protocol, not invented replacement contents. Record its SHA-256 content digest and available source revision for project-copy provenance.\n- Is the `triage` skill installed? (a `triage` skill folder alongside this one, or `triage` in your available skills.) This decides whether Section B runs at all.\n- Monorepo signals: a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages\u002F*` with its own `src\u002F`. These are present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then take the sections in order. One section, one answer, then the next.\n\nLead each section with the recommended answer so the user can accept it in a word. Give a one-line explainer only when the choice genuinely branches; skip the section entirely when exploration already settled it (Section B when `triage` isn't installed, Section C when there's no monorepo).\n\n**Section A: Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-tickets`, `triage`, and `to-spec` read from and write to it. They need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow some other workflow you describe. Pick the place you actually track work for this repo.\n\nDefault posture: these skills were designed for GitHub. If a `git remote` points at GitHub, propose that. If a `git remote` points at GitLab (`gitlab.com` or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:\n\n- **GitHub**: issues live in the repo's GitHub Issues (uses the `gh` CLI)\n- **GitLab**: issues live in the repo's GitLab Issues (uses the [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown**: issues live as files under `.scratch\u002F\u003Cfeature>\u002F` in this repo (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.): ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose\n\nRecord the choice in `docs\u002Fagents\u002Fissue-tracker.md`. The GitHub and GitLab templates carry a \"PRs as a request surface\" flag, defaulted **off**. Leave it off and don't raise it: a user who wants external PRs in the triage queue can flip the flag in the file later.\n\n**Section B: Triage label vocabulary.** Skip this section entirely if the `triage` skill isn't installed (exploration told you), since an uninstalled skill needs no labels.\n\nIf it is installed, ask exactly one question:\n\n> Do you want to keep the default triage labels? (recommended: **yes**)\n\nThe defaults are the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. On **yes**, write them as-is. Only if the user says no, usually because their tracker already uses other names (e.g. `bug:triage` for `needs-triage`), collect the overrides so `triage` applies existing labels instead of creating duplicates.\n\n**Section C: Domain docs.** Default to **single-context** (one `GLOSSARY.md` + `docs\u002Fadr\u002F` at the repo root). This fits almost every repo; write it without asking.\n\nOffer **multi-context** (a root `GLOSSARY-MAP.md` pointing to per-context `GLOSSARY.md` files) only when exploration found monorepo signals. Then confirm which layout they want.\n\n**Section D: Validated checkpoints.** Recommend reusing an existing equivalent\nproject reference and pointer. Otherwise propose a checked-in copy at\n`docs\u002Fagents\u002Fvalidated-checkpoints.md` with the provenance footer from\n[checkpoint-adoption.md](.\u002Fcheckpoint-adoption.md), and its relative pointer in the\nchosen instruction file. Resolve conflicting checkpoint pointers with the user\nbefore selecting one. For an existing copy, compare its recorded source digest\nwith the current project protocol body's digest (bytes before the adoption marker\ndefined in the seed) and the proposed source digest. A changed project body is a local modification:\nmerge the proposed update with those changes and preview the exact diff. If the\nrecorded source identity is missing or cannot establish the baseline, resolve that\ngap before replacing content. Identical source and approved project copy need no\nupdate. Consume existing delivery guidance; leave its Definition of\nDone and delivery authority with that reference. Establishing missing delivery\nagreements belongs to `setup-delivery-workflow`, a separate explicit setup.\n\n### 3. Confirm and edit\n\nShow the user a draft of:\n\n- The `## Agent skills` block to add to whichever of `CLAUDE.md` \u002F `AGENTS.md` is being edited (see step 4 for selection rules)\n- The contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Fdomain.md`, and `docs\u002Fagents\u002Ftriage-labels.md` (the last only when `triage` is installed)\n- The complete checkpoint copy and provenance footer (or proposed edits to the existing reference), and its exact relative pointer diff\n\nLet them edit, then obtain explicit approval for the exact proposed changes\nbefore any project write. If declined or unresolved, report the remaining gap and\nstop without writes. Recheck pending edits before applying approval; request a\nrevised approval if intervening changes conflict.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `CLAUDE.md` exists, edit it.\n- Else if `AGENTS.md` exists, edit it.\n- If neither exists, ask the user which one to create; don't pick for them.\n\nNever create `AGENTS.md` when `CLAUDE.md` already exists (or vice versa); always edit the one that's already there.\n\nIf an `## Agent skills` block already exists in the chosen file, update only the approved contents in-place rather than appending a duplicate. Preserve surrounding sections and local edits within the block. Reuse an existing workflow\u002Fcheckpoint pointer instead of creating a second one; identical approved setup is a no-op.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout: \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n\n```\n\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `triage` is installed and Section B ran. When it isn't, both are omitted.\n\nMerge the approved checkpoint pointer from\n[checkpoint-adoption.md](.\u002Fcheckpoint-adoption.md) into this block, or update the\nexisting workflow pointer once. When reusing another reference, point to its\nactual project-relative path. Copy the resolved shared\nprotocol into the approved project path and append completed provenance fields;\nkeep existing local changes unless their replacement was explicitly approved.\nThis skill configures project files only; global instructions, skill installation,\npublication and enablement are outside this setup.\n\nThen write the other docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md): GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md): GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md): local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md): label mapping (only if `triage` is installed)\n- [domain.md](.\u002Fdomain.md): domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nRead back every approved file and resolve the relative instruction pointer from\nthe chosen file's directory. Inspect the diff for preserved unrelated\u002Fpending\nedits and evaluate a rerun: identical setup must make no changes. Report the\nchanged paths (or already present), checkpoint source revision and digest, pointer\nreachability and unresolved gaps. Static inspection establishes the configured\nfiles, not host loading or live-model adherence; in a CLAUDE-only repo, retain\nCLAUDE-first selection and report any unverified host loading explicitly.\n\nTell the user which engineering skills now have project references. They can edit\n`docs\u002Fagents\u002F*.md` directly later; checkpoint copies retain their provenance and\nlocal adaptations when reviewed source updates are adopted. Setup is complete\nonly when approved files and their pointer agree and existing content is preserved.\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","46b2e9493d75c07ea357cf5ac24ec104afb55500","shared\u002Fskills\u002Fsetup-matt-pocock-skills","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench","https:\u002F\u002Fgithub.com\u002Fguhans6","2026-10-11 17:12:57",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":25},[34,37,40],{"tool":35,"command":36},"npx","npx skills add guhans6\u002Fagent-workbench --skill setup-matt-pocock-skills",{"tool":38,"command":39},"bunx","bunx skills add guhans6\u002Fagent-workbench --skill setup-matt-pocock-skills",{"tool":41,"command":42},"pnpm","pnpm dlx skills add guhans6\u002Fagent-workbench --skill setup-matt-pocock-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[45,51,55,59,63,67,71,75],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",152,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"checkpoint-adoption.md",1803,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fcheckpoint-adoption.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"domain.md",2042,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fdomain.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"issue-tracker-github.md",3731,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-github.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"issue-tracker-gitlab.md",3809,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-gitlab.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"issue-tracker-local.md",1810,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-local.md",{"path":72,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":16},"LICENSE","许可证",1068,{"path":76,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":77,"sourceHtmlUrl":78},"triage-labels.md",1045,"https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fsetup-matt-pocock-skills\u002Ftriage-labels.md",[80,89,97,105,113,120],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":20},"01M72BDFZ4DSFCX7RHGN6NTMMB","winui-app","Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":20},"01M72BD9EFCTBR28FEBJQQRVS8","vercel-deploy","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fvercel-deploy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fvercel-deploy\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M72BD5GWQYR251PE9T29GXFR","transcribe","Transcribe audio files to text with optional diarization and known-speaker hints. Use when a user asks to transcribe speech from audio\u002Fvideo, extract text from recordings, or label speakers in interviews or meetings.","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Ftranscribe\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Ftranscribe\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M72BD2GFD6AS2J1J24940AN4","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fto-tickets\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":20},"01M72BCN5R8AD3FQKFXRXKETJC","swiftui-pro","Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswiftui-pro\u002Fskills\u002Fswiftui-pro\u002FSKILL.md",[],[],{"skillNo":121,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":20},"01M72BCJXF6ZWD25F8FGASNSAK","https:\u002F\u002Fgithub.com\u002Fguhans6\u002Fagent-workbench\u002Fblob\u002Fmain\u002Fshared\u002Fskills\u002Fswiftui-pro\u002FSKILL.md",[],[]]