[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M781HEPWCKPZX4GJMEQBVC37":3,"skill-same:01M781HEPWCKPZX4GJMEQBVC37":92},{"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":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M781HEPWCKPZX4GJMEQBVC37","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.","TheAngryPit\u002FTheAngrySkills","TheAngryPit","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7040636?v=4","01M7803EENA9ATXJ46S9268QJX","Vitor Cepeda Lopes","01M7803EF9FMF4G4420XE4DV7Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm only choices that are still open, 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- The active harness's documented instruction file (for example `AGENTS.md` or `CLAUDE.md`): does it already contain an `## Agent skills` section?\n- `GLOSSARY.md` and `GLOSSARY-MAP.md` at the repo root\n- Also inspect legacy `CONTEXT.md` \u002F `CONTEXT-MAP.md`. If present, offer the upstream `GLOSSARY` migration and update `docs\u002Fagents\u002Fdomain.md` only when the repository's established naming and the user's decision support it.\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- 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`. Treat these as package-layout evidence; their absence does not rule out multiple documented contexts.\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Record choices already established by repository files or the active harness, then ask only for choices that remain open. Take the sections in order, one section and one answer at a time when an answer is needed.\n\nLead each open 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 the layout is already documented).\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`. If that file already exists, preserve its repo-specific conventions and edit only what the confirmed choice requires. 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\nA GitHub or GitLab tracker needs a reachable repo. When the user picks one and no `git remote` points at that host, get the repo URL from them and wire it up (`git init` if needed, `git remote add origin \u003Curl>`) before going further. Done when `gh repo view` \u002F `glab repo view` prints the project from inside this directory; if it can't, stop and tell the user what's missing.\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 and the label vocabulary is not already determined by the repo or harness, 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. If the repo or harness already determines the vocabulary, preserve it and do not ask again.\n\n**Section C: Domain docs.** Use the existing documented single- or multi-context layout when it is settled. If it is not settled, propose the layout from the repository's actual domains, structure, and context-map signals; do not choose single-context merely because multiple-context documentation is absent. Confirm only when that choice remains open.\n\nWhen the layout is not settled, a repository without existing multiple-context documentation may still choose multi-context if its actual domains and structure warrant it; do not default from the absence of a `GLOSSARY-MAP.md` alone.\n\n### 3. Confirm and edit\n\nShow the user a draft of the intended changes when a real choice or material edit remains. When the harness or the user's request already determines the target, show the edit and proceed without adding an approval ritual:\n\n- The `## Agent skills` block to add to the instruction file actually consumed by the active harness (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\nWhen a choice remains open, let them edit before writing. When the target is already determined, proceed with the shown edit without inventing another approval ritual.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- Edit the instruction file the active harness actually consumes, using its documented precedence. For Codex, create or edit `AGENTS.md` when that is the documented repo-instruction file, even if `CLAUDE.md` also exists; preserve the other file.\n- If exactly one existing instruction file is compatible with the harness, use it without asking. If both exist and the harness documents no precedence, report the gap and ask only that real choice.\n- If neither instruction file exists and the harness names its target, create that target; otherwise ask the user which one to create.\n\nIf an `## Agent skills` block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.\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\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\nWhen Section B ran on GitHub or GitLab, create each configured label the tracker lacks (`gh label create` \u002F `glab label create`).\n\nThen write the 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\nTell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later; re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.\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\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm only choices that are still open, 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- The active harness's documented instruction file (for example `AGENTS.md` or `CLAUDE.md`): does it already contain an `## Agent skills` section?\n- `GLOSSARY.md` and `GLOSSARY-MAP.md` at the repo root\n- Also inspect legacy `CONTEXT.md` \u002F `CONTEXT-MAP.md`. If present, offer the upstream `GLOSSARY` migration and update `docs\u002Fagents\u002Fdomain.md` only when the repository's established naming and the user's decision support it.\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- 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`. Treat these as package-layout evidence; their absence does not rule out multiple documented contexts.\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Record choices already established by repository files or the active harness, then ask only for choices that remain open. Take the sections in order, one section and one answer at a time when an answer is needed.\n\nLead each open 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 the layout is already documented).\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`. If that file already exists, preserve its repo-specific conventions and edit only what the confirmed choice requires. 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\nA GitHub or GitLab tracker needs a reachable repo. When the user picks one and no `git remote` points at that host, get the repo URL from them and wire it up (`git init` if needed, `git remote add origin \u003Curl>`) before going further. Done when `gh repo view` \u002F `glab repo view` prints the project from inside this directory; if it can't, stop and tell the user what's missing.\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 and the label vocabulary is not already determined by the repo or harness, 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. If the repo or harness already determines the vocabulary, preserve it and do not ask again.\n\n**Section C: Domain docs.** Use the existing documented single- or multi-context layout when it is settled. If it is not settled, propose the layout from the repository's actual domains, structure, and context-map signals; do not choose single-context merely because multiple-context documentation is absent. Confirm only when that choice remains open.\n\nWhen the layout is not settled, a repository without existing multiple-context documentation may still choose multi-context if its actual domains and structure warrant it; do not default from the absence of a `GLOSSARY-MAP.md` alone.\n\n### 3. Confirm and edit\n\nShow the user a draft of the intended changes when a real choice or material edit remains. When the harness or the user's request already determines the target, show the edit and proceed without adding an approval ritual:\n\n- The `## Agent skills` block to add to the instruction file actually consumed by the active harness (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\nWhen a choice remains open, let them edit before writing. When the target is already determined, proceed with the shown edit without inventing another approval ritual.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- Edit the instruction file the active harness actually consumes, using its documented precedence. For Codex, create or edit `AGENTS.md` when that is the documented repo-instruction file, even if `CLAUDE.md` also exists; preserve the other file.\n- If exactly one existing instruction file is compatible with the harness, use it without asking. If both exist and the harness documents no precedence, report the gap and ask only that real choice.\n- If neither instruction file exists and the harness names its target, create that target; otherwise ask the user which one to create.\n\nIf an `## Agent skills` block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.\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\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\nWhen Section B ran on GitHub or GitLab, create each configured label the tracker lacks (`gh label create` \u002F `glab label create`).\n\nThen write the 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\nTell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later; re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","f31e1d2df163b90a48e30d0a3df67285f6641418","skills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills",1,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills","https:\u002F\u002Fgithub.com\u002FTheAngryPit","www.vitorcepedalopes.com","Creative Director | Executive Producer | Storyteller | Narrative Worlds & Creative Production Systems\r\nFounder @TheHive-Mind ","2026-11-14 21:48:38",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":25},[37,40,43],{"tool":38,"command":39},"npx","npx skills add TheAngryPit\u002FTheAngrySkills --skill setup-matt-pocock-skills",{"tool":41,"command":42},"bunx","bunx skills add TheAngryPit\u002FTheAngrySkills --skill setup-matt-pocock-skills",{"tool":44,"command":45},"pnpm","pnpm dlx skills add TheAngryPit\u002FTheAngrySkills --skill setup-matt-pocock-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[48,54,60,64,68,72,76,80,84,88],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"ADAPTATIONS.patch","OTHER","其他",9024,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002FADAPTATIONS.patch",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"agents\u002Fopenai.yaml","REFERENCE","参考文档",152,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002Fagents\u002Fopenai.yaml",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"domain.md",2042,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002Fdomain.md",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"issue-tracker-github.md",5082,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-github.md",{"path":69,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":70,"sourceHtmlUrl":71},"issue-tracker-gitlab.md",3979,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-gitlab.md",{"path":73,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":74,"sourceHtmlUrl":75},"issue-tracker-local.md",1810,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-local.md",{"path":77,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":16},"LICENSE","许可证",1068,{"path":81,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":82,"sourceHtmlUrl":83},"PROVENANCE.md",1872,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002FPROVENANCE.md",{"path":85,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":86,"sourceHtmlUrl":87},"triage-labels.md",1057,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002Ftriage-labels.md",{"path":89,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":90,"sourceHtmlUrl":91},"UPSTREAM.json",1991,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-mattpocock\u002Fsetup-matt-pocock-skills\u002FUPSTREAM.json",[93,100,107,114,121,128],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M782GJ4CTPNKZN0WXTASXXZ4","X MCP guide","ALWAYS read this before using any X tool (the X plugin, any X MCP, or Grok Bot's built-in public X reads) and again on any X error. X tools are included in Grok Bot at no cost: never estimate costs, check credits, or tell the user to buy credits. tools=0 \u002F user-X-* not found is a setup failure, not a paywall. Covers Spaces, communities, and Lists (reads and list writes), X Chat (XChat, inbox, DMs, unread, message requests, Chat PIN, juicebox, xchat_lite: clone xchat-grokbot-helper yourself and decrypt locally), scheduled X calls (schedule_call, list_scheduled_calls and the other call tools), and livestreams (stream sources, broadcasts, scheduled broadcasts, broadcast chat, moderators, mutes). Chat, call, livestream, Spaces, or Lists tools missing while other X tools work: reconnect the X plugin.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx\u002Fskills\u002Fx-api-mcp-guide\u002FSKILL.md",[],[],{"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":106,"publishedAt":20},"01M782GBW77901ESC9PD3XAM6V","X Money guide","Read this before the first X Money action in a session and again on any X Money error, refusal, or missing capability. Covers the approval rule for every action that moves money (always ask, every time, no exceptions), how the connection works (connection code plus passkey in the X app), how to guide the user through connect, reconnect, and revoke at x.com\u002Fi\u002Fmoney\u002Fsettings\u002Fconnections, and what each failure message means.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx-money\u002Fskills\u002Fx-money-guide\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M782G7CMYD2JSVT3RX81QRB8","google-slides","Build and edit Google Slides through the google-slides MCP tools - slides, grids of cards and columns, text boxes, shapes, images, tables, styling, layout inspection, and per-slide PNG rendering. Use when creating a deck, laying out slide elements, matching a template, or verifying how a slide looks.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-slides\u002Fskills\u002Fgoogle-slides\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M782G4DDAJ4SMGJEF13HTX69","google-sheets","Build and edit Google Sheets with the google-sheets tools - values, formatting, charts, conditional formatting, structure, validation, named and protected ranges. Use when creating a spreadsheet or dashboard, formatting cells, adding or fixing charts, or reorganizing tabs and rows.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-sheets\u002Fskills\u002Fgoogle-sheets\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M782G1F8QNMNKRSY6M3Y0QG6","google-drive","Work with Google Drive through its MCP tools - search, read, create, organize, share, comment, and export files. Use when creating files in specific folders, moving or renaming, converting Markdown\u002FCSV into Docs\u002FSheets, managing comments, or exporting a rendered PDF.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-drive\u002Fskills\u002Fgoogle-drive\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":20},"01M782FYVJ5XTP2R0B446RRYTX","google-docs","Author and edit Google Docs with the google-docs tools - structured writing, character and paragraph styling, lists, tables, images, headers\u002Ffooters. Use when creating a formatted document, editing document content, or applying styles.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-docs\u002Fskills\u002Fgoogle-docs\u002FSKILL.md",[],[]]