[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M735ATAWX2FZ49TP0EDXDAF7":3,"skill-same:01M735ATAWX2FZ49TP0EDXDAF7":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":50},"01M735ATAWX2FZ49TP0EDXDAF7","sup",null,"Send issue or fix upstream.","Morrison-Lab\u002Fai-config","Morrison-Lab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104235520?v=4","01M734G0451S2G35MN4HFQK7XP","Morrison Lab","01M734G059BYFDFQA8YTPDGPMH",4,"MIT","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fsup\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: sup\ndescription: \"Send issue or fix upstream.\"\nuser-invocable: true\nallowed-tools:\n  - Bash\n  - Read\n  - Edit\n  - Write\n---\n\n# SUP — Send to Upstream\n\nFile an issue or open a PR on an upstream repository — a fork's parent, a\ndependency, or any external project where you've found a bug, want to propose\na fix, or need to request a feature.\n\n## When this fires\n\n- User says \"sup\", \"send upstream\", \"file upstream\", \"report this upstream\"\n- User says \"contribute this fix back\", \"open a PR on \u003Cupstream>\"\n- User says \"file a bug on \u003Cpackage>\", \"upstream issue for this\"\n- After discovering a bug in a dependency during normal work\n- After implementing a workaround that should really be fixed at the source\n\n## Step 0 — read the repo's contribution policy first (do this BEFORE drafting)\n\nThe upstream repo is not ours; its rules bind us, and ignoring them can get the\nuser's account **banned**. Before drafting a title or body, read:\n\n- **`CODE_OF_CONDUCT.md`** — some projects (e.g. `quarto-dev\u002Fquarto-cli`)\n  **ban issues\u002FPRs from autonomous AI agents acting without human oversight**\n  and treat it as **account-bannable on first offense**. If the repo bans\n  AI-agent submissions, **stop — do not file.** Give the user the draft and let\n  *them* decide whether to submit it themselves.\n- **`CONTRIBUTING.md`** + **issue\u002FPR templates** (`.github\u002FISSUE_TEMPLATE\u002F`,\n  `.github\u002FPULL_REQUEST_TEMPLATE.md`) — follow the required template and fill in\n  every required field instead of the generic bodies below.\n- **Destination.** Many projects route **feature requests and questions to a\n  Discussions board**, not the issue tracker. Honor that — file in Discussions\n  when the guidelines say so; reserve the tracker for what it's meant for.\n\nPull these via the GitHub MCP `get_file_contents` (remote) or\n`gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fcontents\u002F\u003Cpath>` \u002F a quick clone (local). If a\nrequired check can't be read, say so and ask the user rather than guessing.\n\nThis is in addition to — not a replacement for — the human-approval gate in\nsteps 3A\u002F3B below.\n\n## Determine the action type\n\n| Situation | Action |\n|-----------|--------|\n| Bug report, feature request, question — no code to contribute | **Issue** (or **Discussion**, if the repo routes it there) |\n| You have a fix ready (patch, config change, doc fix) | **PR** |\n| You have a fix but aren't sure upstream wants it | **Issue first**, mention you have a fix ready |\n| Fork divergence — your fork has improvements the parent should get | **PR** |\n\nIf unclear, ask the user: \"Issue (report only) or PR (with fix)?\"\n\n## Procedure\n\n### 1. Identify the upstream repo\n\nTry these in order:\n\n```bash\n# Fork parent (GitHub)\ngh repo view --json parent --jq '.parent.owner.login + \"\u002F\" + .parent.name'\n\n# Fork parent (GitLab)\nglab repo view --output json | python3 -c \"import json,sys; r=json.load(sys.stdin); print(r.get('forked_from_project',{}).get('path_with_namespace',''))\"\n\n# Dependency — user must specify or you infer from context\n# e.g., \"the bug is in rlang\" → \"r-lib\u002Frlang\"\n```\n\nIf you can't determine the upstream repo, ask the user.\n\n### 2. Verify access\n\n```bash\n# Can you push\u002FPR to this repo?\ngh repo view \u003Cowner>\u002F\u003Crepo> --json viewerPermission --jq '.viewerPermission'\n# WRITE or ADMIN → can PR directly\n# READ → fork first, then PR from fork\n```\n\n### 3A. File an issue (report-only path)\n\nGather from context:\n- **Title**: short, specific, imperative. \"X breaks when Y\" not \"Problem with Z\"\n- **Description**: what happens, what should happen, how to reproduce\n- **Environment**: version of the package\u002Ftool, OS, relevant config\n- **Minimal reprex**: if you have one (prefer `reprexes` skill output)\n- **Workaround**: if you have one, mention it — helps others and shows you've investigated\n\n**Show the full draft (title + body) to the user and wait for explicit approval\nbefore posting.** Output the text as a markdown block, then ask \"OK to post?\"\nDo NOT run `gh issue create` until the user confirms.\n\n```bash\ngh issue create --repo \u003Cowner>\u002F\u003Crepo> \\\n  --title \"\u003Ctitle>\" \\\n  --body \"\u003Cbody>\"   # CREATE_ISSUE\n```\n\nOr for GitLab:\n```bash\nglab issue create --repo \u003Cowner>\u002F\u003Crepo> \\\n  --title \"\u003Ctitle>\" \\\n  --description \"\u003Cbody>\"\n```\n\nNo `ai-authored` \u002F `model:\u003Cmodel-id>` labels here.\n[`issue-first`](..\u002F..\u002Fshared\u002Fworkflow\u002Fissue-first.md)'s labelling rule is scoped\nto repos we administrate, and an upstream project's label taxonomy is not ours\nto extend --- see\n[`label-agent-filed-issues`](..\u002F..\u002Fshared\u002Fworkflow\u002Flabel-agent-filed-issues.md).\n\nAfter filing, report the issue URL back to the user.\n\n### 3B. Open a PR (fix path)\n\n**Show the full draft (title + body) to the user and wait for explicit approval\nbefore running `gh pr create`.** Same rule as issues — draft first, post after \"OK.\"\n\n#### If you have push access (collaborator\u002Forg member):\n\n```bash\n# Clone or add remote\ngit remote add upstream https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>.git 2>\u002Fdev\u002Fnull || true\ngit fetch upstream   # FETCH\n\n# Branch from upstream's default branch\ngit checkout -b fix\u002F\u003Cslug> upstream\u002Fmain  # CREATE_BRANCH — or upstream\u002Fmaster, upstream\u002Fdevelop\n\n# Apply your fix (copy from local workaround, write fresh, cherry-pick)\n# ... make edits ...\n\ngit add -A && git commit -m \"\u003Cconventional commit message>\"   # COMMIT\n```\n\nPush as a separate Bash call, per [`check-before-pushing`](..\u002F..\u002Fshared\u002Fworkflow\u002Fcheck-before-pushing.md)'s \"Keep the commit in its own Bash call\":\n\n```bash\ngit push upstream fix\u002F\u003Cslug>   # PUSH\n```\n\nOpen the PR in its own call:\n\n```bash\ngh pr create --repo \u003Cowner>\u002F\u003Crepo> \\\n  --base main \\\n  --head fix\u002F\u003Cslug> \\\n  --title \"\u003Ctitle>\" \\\n  --body \"\u003Cbody>\"   # CREATE_PR\n```\n\n#### If you need to fork first:\n\n```bash\n# Fork (idempotent — won't re-fork if already forked)\ngh repo fork \u003Cowner>\u002F\u003Crepo> --clone=false\n\n# Your fork is now at \u003Cyour-username>\u002F\u003Crepo>\ngh repo clone \u003Cyour-username>\u002F\u003Crepo> \u002Ftmp\u002Fupstream-fix\ncd \u002Ftmp\u002Fupstream-fix\n\n# Branch, fix, commit, push to YOUR fork\ngit checkout -b fix\u002F\u003Cslug>   # CREATE_BRANCH\n# ... make edits ...\ngit add -A && git commit -m \"\u003Cconventional commit message>\"   # COMMIT\n```\n\nPush as a separate Bash call, per [`check-before-pushing`](..\u002F..\u002Fshared\u002Fworkflow\u002Fcheck-before-pushing.md)'s \"Keep the commit in its own Bash call\":\n\n```bash\ngit -C \u002Ftmp\u002Fupstream-fix push origin fix\u002F\u003Cslug>   # PUSH -- absolute, so it does not depend on the caller's directory\n```\n\nOpen the PR in its own call:\n\n```bash\ngh pr create --repo \u003Cowner>\u002F\u003Crepo> \\\n  --base main \\\n  --head \u003Cyour-username>:fix\u002F\u003Cslug> \\\n  --title \"\u003Ctitle>\" \\\n  --body \"\u003Cbody>\"   # CREATE_PR\n```\n\n### 4. Link back to local context\n\nAfter filing the upstream issue\u002FPR:\n\n- If you have a local workaround, add a comment in the code:\n  `# WORKAROUND: upstream \u003Cowner>\u002F\u003Crepo>#\u003CN> — remove when fixed`\n- If you used `workaround-watcher`, set it to watch the new issue\u002FPR\n- If you deferred from a local MR review, update the ARD summary with the\n  upstream issue link\n\n### 5. Report to user\n\nProvide:\n- The upstream issue\u002FPR URL (clickable markdown link)\n- What was filed (issue vs PR, title)\n- Any next steps (watch for response, set up workaround-watcher, etc.)\n\n## PR body template\n\n```markdown\n## Problem\n\n\u003CWhat's broken \u002F missing — 2-3 sentences>\n\n## Reproduction\n\n\u003CMinimal steps or reprex>\n\n## Fix\n\n\u003CWhat this PR does — 1-2 sentences>\n\n## Notes\n\n- Found while working on \u003Ccontext> in \u003Cyour-repo>\n- Currently working around this with \u003Cworkaround description>\n```\n\n## Issue body template\n\n```markdown\n## Problem\n\n\u003CWhat's broken \u002F missing>\n\n## Reproduction\n\n\u003CMinimal steps, version info, reprex>\n\n## Expected behavior\n\n\u003CWhat should happen instead>\n\n## Workaround\n\n\u003CIf you have one — helps others and shows investigation>\n\n## Environment\n\n- Package version: X.Y.Z\n- R\u002FPython\u002FNode version: ...\n- OS: ...\n```\n\n## Relationship to other skills\n\n- **`prefer-upstream`** — discovers that an upstream solution exists; `sup`\n  contributes fixes back to it\n- **`workaround-watcher`** — watches an upstream issue for resolution; `sup`\n  creates that upstream issue in the first place\n- **`defer-issue`** — files issues on YOUR repo; `sup` files on THEIR repo\n- **`reprexes`** — creates minimal examples; `sup` includes them in the\n  upstream report\n\n## Anti-patterns\n\n- ❌ Filing **autonomously, without the user's explicit approval** — every\n  upstream submission needs the human contributor to review and verify it.\n  Some repos' Codes of Conduct make unattended AI-agent submissions\n  account-bannable on first offense.\n- ❌ Filing **before reading the repo's `CODE_OF_CONDUCT.md` \u002F `CONTRIBUTING.md`\n  \u002F templates** — you can't file correctly without knowing the rules.\n- ❌ Filing a **feature request as an issue** when the project routes feature\n  requests to a **Discussions** board.\n- ❌ Posting a **free-form body when the repo provides an issue\u002FPR template** —\n  use the template and fill in every required field.\n- ❌ Filing a vague issue (\"something is broken\") — always include a reprex\n  or clear reproduction steps\n- ❌ Sending a massive PR that mixes your fix with unrelated changes — keep\n  it minimal and focused\n- ❌ Not mentioning your workaround — upstream maintainers appreciate knowing\n  the impact and that you've investigated\n- ❌ Filing on the wrong repo (e.g., filing on a mirror instead of the\n  canonical source)\n","# SUP — Send to Upstream\n\nFile an issue or open a PR on an upstream repository — a fork's parent, a\ndependency, or any external project where you've found a bug, want to propose\na fix, or need to request a feature.\n\n## When this fires\n\n- User says \"sup\", \"send upstream\", \"file upstream\", \"report this upstream\"\n- User says \"contribute this fix back\", \"open a PR on \u003Cupstream>\"\n- User says \"file a bug on \u003Cpackage>\", \"upstream issue for this\"\n- After discovering a bug in a dependency during normal work\n- After implementing a workaround that should really be fixed at the source\n\n## Step 0 — read the repo's contribution policy first (do this BEFORE drafting)\n\nThe upstream repo is not ours; its rules bind us, and ignoring them can get the\nuser's account **banned**. Before drafting a title or body, read:\n\n- **`CODE_OF_CONDUCT.md`** — some projects (e.g. `quarto-dev\u002Fquarto-cli`)\n  **ban issues\u002FPRs from autonomous AI agents acting without human oversight**\n  and treat it as **account-bannable on first offense**. If the repo bans\n  AI-agent submissions, **stop — do not file.** Give the user the draft and let\n  *them* decide whether to submit it themselves.\n- **`CONTRIBUTING.md`** + **issue\u002FPR templates** (`.github\u002FISSUE_TEMPLATE\u002F`,\n  `.github\u002FPULL_REQUEST_TEMPLATE.md`) — follow the required template and fill in\n  every required field instead of the generic bodies below.\n- **Destination.** Many projects route **feature requests and questions to a\n  Discussions board**, not the issue tracker. Honor that — file in Discussions\n  when the guidelines say so; reserve the tracker for what it's meant for.\n\nPull these via the GitHub MCP `get_file_contents` (remote) or\n`gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fcontents\u002F\u003Cpath>` \u002F a quick clone (local). If a\nrequired check can't be read, say so and ask the user rather than guessing.\n\nThis is in addition to — not a replacement for — the human-approval gate in\nsteps 3A\u002F3B below.\n\n## Determine the action type\n\n| Situation | Action |\n|-----------|--------|\n| Bug report, feature request, question — no code to contribute | **Issue** (or **Discussion**, if the repo routes it there) |\n| You have a fix ready (patch, config change, doc fix) | **PR** |\n| You have a fix but aren't sure upstream wants it | **Issue first**, mention you have a fix ready |\n| Fork divergence — your fork has improvements the parent should get | **PR** |\n\nIf unclear, ask the user: \"Issue (report only) or PR (with fix)?\"\n\n## Procedure\n\n### 1. Identify the upstream repo\n\nTry these in order:\n\n```bash\n# Fork parent (GitHub)\ngh repo view --json parent --jq '.parent.owner.login + \"\u002F\" + .parent.name'\n\n# Fork parent (GitLab)\nglab repo view --output json | python3 -c \"import json,sys; r=json.load(sys.stdin); print(r.get('forked_from_project',{}).get('path_with_namespace',''))\"\n\n# Dependency — user must specify or you infer from context\n# e.g., \"the bug is in rlang\" → \"r-lib\u002Frlang\"\n```\n\nIf you can't determine the upstream repo, ask the user.\n\n### 2. Verify access\n\n```bash\n# Can you push\u002FPR to this repo?\ngh repo view \u003Cowner>\u002F\u003Crepo> --json viewerPermission --jq '.viewerPermission'\n# WRITE or ADMIN → can PR directly\n# READ → fork first, then PR from fork\n```\n\n### 3A. File an issue (report-only path)\n\nGather from context:\n- **Title**: short, specific, imperative. \"X breaks when Y\" not \"Problem with Z\"\n- **Description**: what happens, what should happen, how to reproduce\n- **Environment**: version of the package\u002Ftool, OS, relevant config\n- **Minimal reprex**: if you have one (prefer `reprexes` skill output)\n- **Workaround**: if you have one, mention it — helps others and shows you've investigated\n\n**Show the full draft (title + body) to the user and wait for explicit approval\nbefore posting.** Output the text as a markdown block, then ask \"OK to post?\"\nDo NOT run `gh issue create` until the user confirms.\n\n```bash\ngh issue create --repo \u003Cowner>\u002F\u003Crepo> \\\n  --title \"\u003Ctitle>\" \\\n  --body \"\u003Cbody>\"   # CREATE_ISSUE\n```\n\nOr for GitLab:\n```bash\nglab issue create --repo \u003Cowner>\u002F\u003Crepo> \\\n  --title \"\u003Ctitle>\" \\\n  --description \"\u003Cbody>\"\n```\n\nNo `ai-authored` \u002F `model:\u003Cmodel-id>` labels here.\n[`issue-first`](..\u002F..\u002Fshared\u002Fworkflow\u002Fissue-first.md)'s labelling rule is scoped\nto repos we administrate, and an upstream project's label taxonomy is not ours\nto extend --- see\n[`label-agent-filed-issues`](..\u002F..\u002Fshared\u002Fworkflow\u002Flabel-agent-filed-issues.md).\n\nAfter filing, report the issue URL back to the user.\n\n### 3B. Open a PR (fix path)\n\n**Show the full draft (title + body) to the user and wait for explicit approval\nbefore running `gh pr create`.** Same rule as issues — draft first, post after \"OK.\"\n\n#### If you have push access (collaborator\u002Forg member):\n\n```bash\n# Clone or add remote\ngit remote add upstream https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>.git 2>\u002Fdev\u002Fnull || true\ngit fetch upstream   # FETCH\n\n# Branch from upstream's default branch\ngit checkout -b fix\u002F\u003Cslug> upstream\u002Fmain  # CREATE_BRANCH — or upstream\u002Fmaster, upstream\u002Fdevelop\n\n# Apply your fix (copy from local workaround, write fresh, cherry-pick)\n# ... make edits ...\n\ngit add -A && git commit -m \"\u003Cconventional commit message>\"   # COMMIT\n```\n\nPush as a separate Bash call, per [`check-before-pushing`](..\u002F..\u002Fshared\u002Fworkflow\u002Fcheck-before-pushing.md)'s \"Keep the commit in its own Bash call\":\n\n```bash\ngit push upstream fix\u002F\u003Cslug>   # PUSH\n```\n\nOpen the PR in its own call:\n\n```bash\ngh pr create --repo \u003Cowner>\u002F\u003Crepo> \\\n  --base main \\\n  --head fix\u002F\u003Cslug> \\\n  --title \"\u003Ctitle>\" \\\n  --body \"\u003Cbody>\"   # CREATE_PR\n```\n\n#### If you need to fork first:\n\n```bash\n# Fork (idempotent — won't re-fork if already forked)\ngh repo fork \u003Cowner>\u002F\u003Crepo> --clone=false\n\n# Your fork is now at \u003Cyour-username>\u002F\u003Crepo>\ngh repo clone \u003Cyour-username>\u002F\u003Crepo> \u002Ftmp\u002Fupstream-fix\ncd \u002Ftmp\u002Fupstream-fix\n\n# Branch, fix, commit, push to YOUR fork\ngit checkout -b fix\u002F\u003Cslug>   # CREATE_BRANCH\n# ... make edits ...\ngit add -A && git commit -m \"\u003Cconventional commit message>\"   # COMMIT\n```\n\nPush as a separate Bash call, per [`check-before-pushing`](..\u002F..\u002Fshared\u002Fworkflow\u002Fcheck-before-pushing.md)'s \"Keep the commit in its own Bash call\":\n\n```bash\ngit -C \u002Ftmp\u002Fupstream-fix push origin fix\u002F\u003Cslug>   # PUSH -- absolute, so it does not depend on the caller's directory\n```\n\nOpen the PR in its own call:\n\n```bash\ngh pr create --repo \u003Cowner>\u002F\u003Crepo> \\\n  --base main \\\n  --head \u003Cyour-username>:fix\u002F\u003Cslug> \\\n  --title \"\u003Ctitle>\" \\\n  --body \"\u003Cbody>\"   # CREATE_PR\n```\n\n### 4. Link back to local context\n\nAfter filing the upstream issue\u002FPR:\n\n- If you have a local workaround, add a comment in the code:\n  `# WORKAROUND: upstream \u003Cowner>\u002F\u003Crepo>#\u003CN> — remove when fixed`\n- If you used `workaround-watcher`, set it to watch the new issue\u002FPR\n- If you deferred from a local MR review, update the ARD summary with the\n  upstream issue link\n\n### 5. Report to user\n\nProvide:\n- The upstream issue\u002FPR URL (clickable markdown link)\n- What was filed (issue vs PR, title)\n- Any next steps (watch for response, set up workaround-watcher, etc.)\n\n## PR body template\n\n```markdown\n## Problem\n\n\u003CWhat's broken \u002F missing — 2-3 sentences>\n\n## Reproduction\n\n\u003CMinimal steps or reprex>\n\n## Fix\n\n\u003CWhat this PR does — 1-2 sentences>\n\n## Notes\n\n- Found while working on \u003Ccontext> in \u003Cyour-repo>\n- Currently working around this with \u003Cworkaround description>\n```\n\n## Issue body template\n\n```markdown\n## Problem\n\n\u003CWhat's broken \u002F missing>\n\n## Reproduction\n\n\u003CMinimal steps, version info, reprex>\n\n## Expected behavior\n\n\u003CWhat should happen instead>\n\n## Workaround\n\n\u003CIf you have one — helps others and shows investigation>\n\n## Environment\n\n- Package version: X.Y.Z\n- R\u002FPython\u002FNode version: ...\n- OS: ...\n```\n\n## Relationship to other skills\n\n- **`prefer-upstream`** — discovers that an upstream solution exists; `sup`\n  contributes fixes back to it\n- **`workaround-watcher`** — watches an upstream issue for resolution; `sup`\n  creates that upstream issue in the first place\n- **`defer-issue`** — files issues on YOUR repo; `sup` files on THEIR repo\n- **`reprexes`** — creates minimal examples; `sup` includes them in the\n  upstream report\n\n## Anti-patterns\n\n- ❌ Filing **autonomously, without the user's explicit approval** — every\n  upstream submission needs the human contributor to review and verify it.\n  Some repos' Codes of Conduct make unattended AI-agent submissions\n  account-bannable on first offense.\n- ❌ Filing **before reading the repo's `CODE_OF_CONDUCT.md` \u002F `CONTRIBUTING.md`\n  \u002F templates** — you can't file correctly without knowing the rules.\n- ❌ Filing a **feature request as an issue** when the project routes feature\n  requests to a **Discussions** board.\n- ❌ Posting a **free-form body when the repo provides an issue\u002FPR template** —\n  use the template and fill in every required field.\n- ❌ Filing a vague issue (\"something is broken\") — always include a reprex\n  or clear reproduction steps\n- ❌ Sending a massive PR that mixes your fix with unrelated changes — keep\n  it minimal and focused\n- ❌ Not mentioning your workaround — upstream maintainers appreciate knowing\n  the impact and that you've investigated\n- ❌ Filing on the wrong repo (e.g., filing on a mirror instead of the\n  canonical source)\n",{"name":5,"description":7,"allowed-tools":24,"user-invocable":29},[25,26,27,28],"Bash","Read","Edit","Write",true,"main","0f720481f8ce3b3d9fef485f6e230d8b3035748e","skills\u002Fsup",1,"https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config","https:\u002F\u002Fmorrison-lab.github.io\u002Fai-config\u002F","https:\u002F\u002Fgithub.com\u002FMorrison-Lab","2026-11-15 04:39:15",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":29},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Morrison-Lab\u002Fai-config --skill sup",{"tool":44,"command":45},"bunx","bunx skills add Morrison-Lab\u002Fai-config --skill sup",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Morrison-Lab\u002Fai-config --skill sup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fsup\u002FSKILL.md",[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M735BVYCGR5VEC65AFDVSNKW","wrap-up","End-of-session verification and UMS.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M735BTH469T1CQ8G2Q9GENCR","workaround-watcher","Watch upstream issue for fix.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fworkaround-watcher\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M735BRKZWFANSQ0GM380B4TD","wn","→ whats-next.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwn\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M735BPE9V830B3B6NGXQ56J6","whats-next","Recommend concrete next step or action.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwhats-next\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M735BMHQ60EAD5B7QAWXC5A0","wait-for-results","Wait for pipeline\u002FCI results.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwait-for-results\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M735BKGZHPN1PEMJ7YBD5VJ8","wai","→ send-notes.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwai\u002FSKILL.md",[],[]]