[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CT4HFZBG85W5EEW4BDP2SY":3,"skill-same:01M6CT4HFZBG85W5EEW4BDP2SY":66},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":65},"01M6CT4HFZBG85W5EEW4BDP2SY","self-update",null,"Update this junior-prod app to the latest published Junior release. Use when asked to self-update Junior, bump @sentry\u002Fjunior and @sentry\u002Fjunior-* dependencies, run safety checks, and open a PR ready for review.","getsentry\u002Fjunior","getsentry","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1396951?v=4","01M6CHRN2S1A588Q46ASWA5335","Sentry","01M6CT1V0TF72B1X0MQT5MSYXF",413,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fpackages\u002Fjunior-maintenance\u002Fskills\u002Fself-update\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"self","update","self update","when","latest","junior","app","Safety","release","dependencies","run","draft","use","open","draft pr","bump","pr","sentry","2026-11-10 10:12:30",false,"---\nname: self-update\ndescription: Update this junior-prod app to the latest published Junior release. Use when asked to self-update Junior, bump @sentry\u002Fjunior and @sentry\u002Fjunior-* dependencies, run safety checks, and open a PR ready for review.\ndisable-model-invocation: true\n---\n\n## Workflow\n\n### 1. Preflight\n\n```bash\ngit status --short\ngit branch --show-current\n```\n\nStop if `package.json`, `pnpm-lock.yaml`, or `pnpm-workspace.yaml` has unrelated uncommitted changes.\n\n### 2. Inventory and target\n\nInventory direct Junior deps from `package.json`: `@sentry\u002Fjunior` and `@sentry\u002Fjunior-*`. Record package, current exact version, and dependency section. Keep all Junior deps on one version and do not move packages between sections.\n\nResolve the target:\n\n```bash\npnpm view @sentry\u002Fjunior dist-tags.latest\n```\n\nIf user requests a specific version, use that. If already on latest, stop.\n\nVerify the target exists for every inventoried package before mutating files:\n\n```bash\npnpm view \u003Cpackage>@\u003Ctarget> version\n```\n\nAllow for npm security scanning and propagation delays after publication:\n\n- Confirm missing versions with cache-busted npm metadata and the direct version endpoint. Continue only when every package's exact target version and tarball are available. Do not retry auth failures as publication delays.\n- If any package is missing, leave app files unchanged. Call `watchTimer` with `after_ms: 900000` (15 minutes). Start its intent with `Run $self-update for target \u003Ctarget>`, so the timer Turn loads this skill, then name the missing packages and the wait number (for example `wait 1 of 4`). After `watchTimer` succeeds, end the Turn without a message in a separate call: in an Automation run, call `finishAutomationRun` with `no_action`; otherwise call `noReply`. If `watchTimer` fails, report the failure instead. When the timer fires, check the same target again.\n- Wait at most 4 times (one hour). If a package is still missing after the fourth wait, do not open an update PR. Report \"not yet available on npm\" with the target, affected packages, and checks. Missing packages alone do not prove a failed publish or a scanning delay; do not republish or cut another release.\n\n### 3. Build release context\n\nSummarize changes between `old_version` and `target_version` (exclusive of old, inclusive of target) from GitHub release notes. Do not read `CHANGELOG.md` or scrape PRs — release bodies carry the authoritative release context.\n\nTags match package versions with no `v` prefix (for example `0.107.1`):\n\nAsk npm to resolve the semver range to the exact tags, then fetch only those releases:\n\n```bash\npnpm view '@sentry\u002Fjunior@>\u003Cold_version> \u003C=\u003Ctarget_version>' version --json\ngh release view \u003Cversion> --repo getsentry\u002Fjunior --json tagName,name,body,publishedAt,url\n```\n\nCollect the corresponding release bodies. Stop if any expected GitHub release is missing; do not substitute another source. Save the target release's `publishedAt` as `target_published_at` for step 7. Save total change count, breaking changes (`Breaking Changes`, `!`, or `BREAKING CHANGE`), and config-relevant items (`config`, `plugins`, `nitro`, `createApp`, `runtime`, `credentials`, `egress`, `example`). If any breaking change exists, call out manual review, but continue the update.\n\n### 4. Create or reuse branch\n\n`build\u002Fupdate-junior-\u003Ctarget>`. All file mutations happen on this branch.\n\n### 5. Sync `minimumReleaseAgeExclude`\n\nIf `pnpm-workspace.yaml` has a `minimumReleaseAgeExclude` list, ensure every Junior package from step 2 is covered by an exact entry or an existing package pattern. Add missing entries before `pnpm add`, but do not add exact entries already covered by `@sentry\u002F*`. Append at end and preserve existing order.\n\n### 6. Update deps (section-preserving)\n\nGroup `pnpm add` by dependency section:\n\n```bash\npnpm add -E \u003Cdeps-packages>@\u003Ctarget> ...\npnpm add -D -E \u003CdevDeps-packages>@\u003Ctarget> ...\npnpm add -O -E \u003CoptDeps-packages>@\u003Ctarget> ...\n```\n\nDo not manually edit versions in `package.json`. Do not use local `..\u002Fjunior` linking scripts.\n\n### 7. Sync local config\n\nIf a new standalone `@sentry\u002Fjunior-*` plugin package was added, add it to the app `plugins.ts` set passed to `defineJuniorPlugins(...)` and keep `juniorNitro({ plugins: \".\u002Fplugins\" })` pointed at that module. Exclude the base\u002Fruntime utility packages: `@sentry\u002Fjunior`, `@sentry\u002Fjunior-plugin-api`, `@sentry\u002Fjunior-testing`.\n\n```bash\nnode scripts\u002Fcheck-plugin-packages.mjs\n```\n\nCompare the consumer config with `apps\u002Fexample` at `target_ref` to catch shape drift. Call `github_cloneRepository` with `repo: \"getsentry\u002Fjunior\"`, `directory: \"repos\u002Fjunior-upstream\"`, and `allow_ad_hoc: true`. Do not switch to a `junior` Workspace: the switch replaces the sandbox and removes this app checkout. Use the returned `path` as `\u003Cupstream>`. Choose `target_ref` from the version bump commit, then the publish timestamp, then `origin\u002Fmain` as approximate:\n\n```bash\ngit -C \u003Cupstream> fetch --deepen=200 origin main\ngit -C \u003Cupstream> log --oneline -S'\"version\": \"\u003Ctarget_version>\"' -- packages\u002Fjunior\u002Fpackage.json\ngit -C \u003Cupstream> rev-list -n 1 --before=\"\u003Ctarget_published_at>\" origin\u002Fmain\ngit -C \u003Cupstream> checkout \u003Ctarget_ref>\ngit diff --no-index -- \u003Cupstream>\u002Fapps\u002Fexample\u002Fnitro.config.ts nitro.config.ts\ngit diff --no-index -- \u003Cupstream>\u002Fapps\u002Fexample\u002Fplugins.ts plugins.ts\ngit diff --no-index -- \u003Cupstream>\u002Fapps\u002Fexample\u002Fserver.ts server.ts\n```\n\nIgnore app-local values. Apply only obvious low-risk fixes; put ambiguous drift in the PR body. For `package.json`, compare only build tooling (`nitro`, `jiti`, `typescript`), not plugin dependency lists or pins.\n\nFor `vercel.json`, do not normalize the whole file against the example. Use upstream diff-backed changes when possible:\n\n```bash\ngit -C \u003Cupstream> diff \u003Cold_ref>..\u003Ctarget_ref> -- apps\u002Fexample\u002Fvercel.json\n```\n\nOnly act on Junior-owned deployment requirements proven by that diff or by release notes\u002Fdocs. If `old_ref` is unavailable, target-only example entries are context, not proof; mark the review approximate and leave a manual review item when needed.\n\n### 8. Verify\n\n```bash\ngit diff --name-only\npnpm install --frozen-lockfile\npnpm check\npnpm typecheck\npnpm build\n```\n\nExpected changed files: `package.json`, `pnpm-lock.yaml`, optional `pnpm-workspace.yaml`, optional `nitro.config.ts`, optional `vercel.json`. Confirm every Junior dep is exactly `\u003Ctarget>`. If the frozen install fails, repair with `pnpm install --lockfile-only` and rerun. Fix update-related check failures; disclose pre-existing or environment failures.\n\n### 9. Commit\n\n```text\nbuild(deps): Update Junior packages to \u003Ctarget>\n\nUpdate the Junior runtime and plugin packages to \u003Ctarget> and refresh the pnpm lockfile.\n```\n\nMention `minimumReleaseAgeExclude` sync if `pnpm-workspace.yaml` changed.\n\n### 10. Push and open\u002Fupdate PR\n\nOpen the PR ready for review, not as a draft. If an existing update PR is a draft, mark it ready for review. Include version change, release summary with links to the GitHub releases, config comparison findings, optional workspace\u002Fplugin\u002Fvercel changes, and unexpected diffs. Do not put `Checks`, `Verification`, `Test plan`, or similar validation sections in the PR body; put local check results in the final user report only. Add **Manual review required** when breaking changes, unresolved config drift, approximate Vercel review, or failed checks exist.\n\nWhen PR creation returns a subscribable resource hint, watch the PR for suggested review and CI events. After merge, if deployment follow-up is needed, use `github_getDeployment` for the merged commit and watch the suggested deployment events.\n\n## Stop conditions\n\n- Any Junior package still lacks the target version or tarball after one hour of waits in step 2.\n- Any npm version in `(old_version, target_version]` lacks a matching GitHub release.\n- `pnpm install --frozen-lockfile` fails after repair.\n- Checks fail for non-pre-existing, non-environment reasons and no safe config fix is available from step 7.\n- `package.json` changed but `pnpm-lock.yaml` did not.\n- Example app comparison reveals a breaking plugin signature change whose required values cannot be inferred from the existing consumer config.\n","## Workflow\n\n### 1. Preflight\n\n```bash\ngit status --short\ngit branch --show-current\n```\n\nStop if `package.json`, `pnpm-lock.yaml`, or `pnpm-workspace.yaml` has unrelated uncommitted changes.\n\n### 2. Inventory and target\n\nInventory direct Junior deps from `package.json`: `@sentry\u002Fjunior` and `@sentry\u002Fjunior-*`. Record package, current exact version, and dependency section. Keep all Junior deps on one version and do not move packages between sections.\n\nResolve the target:\n\n```bash\npnpm view @sentry\u002Fjunior dist-tags.latest\n```\n\nIf user requests a specific version, use that. If already on latest, stop.\n\nVerify the target exists for every inventoried package before mutating files:\n\n```bash\npnpm view \u003Cpackage>@\u003Ctarget> version\n```\n\nAllow for npm security scanning and propagation delays after publication:\n\n- Confirm missing versions with cache-busted npm metadata and the direct version endpoint. Continue only when every package's exact target version and tarball are available. Do not retry auth failures as publication delays.\n- If any package is missing, leave app files unchanged. Call `watchTimer` with `after_ms: 900000` (15 minutes). Start its intent with `Run $self-update for target \u003Ctarget>`, so the timer Turn loads this skill, then name the missing packages and the wait number (for example `wait 1 of 4`). After `watchTimer` succeeds, end the Turn without a message in a separate call: in an Automation run, call `finishAutomationRun` with `no_action`; otherwise call `noReply`. If `watchTimer` fails, report the failure instead. When the timer fires, check the same target again.\n- Wait at most 4 times (one hour). If a package is still missing after the fourth wait, do not open an update PR. Report \"not yet available on npm\" with the target, affected packages, and checks. Missing packages alone do not prove a failed publish or a scanning delay; do not republish or cut another release.\n\n### 3. Build release context\n\nSummarize changes between `old_version` and `target_version` (exclusive of old, inclusive of target) from GitHub release notes. Do not read `CHANGELOG.md` or scrape PRs — release bodies carry the authoritative release context.\n\nTags match package versions with no `v` prefix (for example `0.107.1`):\n\nAsk npm to resolve the semver range to the exact tags, then fetch only those releases:\n\n```bash\npnpm view '@sentry\u002Fjunior@>\u003Cold_version> \u003C=\u003Ctarget_version>' version --json\ngh release view \u003Cversion> --repo getsentry\u002Fjunior --json tagName,name,body,publishedAt,url\n```\n\nCollect the corresponding release bodies. Stop if any expected GitHub release is missing; do not substitute another source. Save the target release's `publishedAt` as `target_published_at` for step 7. Save total change count, breaking changes (`Breaking Changes`, `!`, or `BREAKING CHANGE`), and config-relevant items (`config`, `plugins`, `nitro`, `createApp`, `runtime`, `credentials`, `egress`, `example`). If any breaking change exists, call out manual review, but continue the update.\n\n### 4. Create or reuse branch\n\n`build\u002Fupdate-junior-\u003Ctarget>`. All file mutations happen on this branch.\n\n### 5. Sync `minimumReleaseAgeExclude`\n\nIf `pnpm-workspace.yaml` has a `minimumReleaseAgeExclude` list, ensure every Junior package from step 2 is covered by an exact entry or an existing package pattern. Add missing entries before `pnpm add`, but do not add exact entries already covered by `@sentry\u002F*`. Append at end and preserve existing order.\n\n### 6. Update deps (section-preserving)\n\nGroup `pnpm add` by dependency section:\n\n```bash\npnpm add -E \u003Cdeps-packages>@\u003Ctarget> ...\npnpm add -D -E \u003CdevDeps-packages>@\u003Ctarget> ...\npnpm add -O -E \u003CoptDeps-packages>@\u003Ctarget> ...\n```\n\nDo not manually edit versions in `package.json`. Do not use local `..\u002Fjunior` linking scripts.\n\n### 7. Sync local config\n\nIf a new standalone `@sentry\u002Fjunior-*` plugin package was added, add it to the app `plugins.ts` set passed to `defineJuniorPlugins(...)` and keep `juniorNitro({ plugins: \".\u002Fplugins\" })` pointed at that module. Exclude the base\u002Fruntime utility packages: `@sentry\u002Fjunior`, `@sentry\u002Fjunior-plugin-api`, `@sentry\u002Fjunior-testing`.\n\n```bash\nnode scripts\u002Fcheck-plugin-packages.mjs\n```\n\nCompare the consumer config with `apps\u002Fexample` at `target_ref` to catch shape drift. Call `github_cloneRepository` with `repo: \"getsentry\u002Fjunior\"`, `directory: \"repos\u002Fjunior-upstream\"`, and `allow_ad_hoc: true`. Do not switch to a `junior` Workspace: the switch replaces the sandbox and removes this app checkout. Use the returned `path` as `\u003Cupstream>`. Choose `target_ref` from the version bump commit, then the publish timestamp, then `origin\u002Fmain` as approximate:\n\n```bash\ngit -C \u003Cupstream> fetch --deepen=200 origin main\ngit -C \u003Cupstream> log --oneline -S'\"version\": \"\u003Ctarget_version>\"' -- packages\u002Fjunior\u002Fpackage.json\ngit -C \u003Cupstream> rev-list -n 1 --before=\"\u003Ctarget_published_at>\" origin\u002Fmain\ngit -C \u003Cupstream> checkout \u003Ctarget_ref>\ngit diff --no-index -- \u003Cupstream>\u002Fapps\u002Fexample\u002Fnitro.config.ts nitro.config.ts\ngit diff --no-index -- \u003Cupstream>\u002Fapps\u002Fexample\u002Fplugins.ts plugins.ts\ngit diff --no-index -- \u003Cupstream>\u002Fapps\u002Fexample\u002Fserver.ts server.ts\n```\n\nIgnore app-local values. Apply only obvious low-risk fixes; put ambiguous drift in the PR body. For `package.json`, compare only build tooling (`nitro`, `jiti`, `typescript`), not plugin dependency lists or pins.\n\nFor `vercel.json`, do not normalize the whole file against the example. Use upstream diff-backed changes when possible:\n\n```bash\ngit -C \u003Cupstream> diff \u003Cold_ref>..\u003Ctarget_ref> -- apps\u002Fexample\u002Fvercel.json\n```\n\nOnly act on Junior-owned deployment requirements proven by that diff or by release notes\u002Fdocs. If `old_ref` is unavailable, target-only example entries are context, not proof; mark the review approximate and leave a manual review item when needed.\n\n### 8. Verify\n\n```bash\ngit diff --name-only\npnpm install --frozen-lockfile\npnpm check\npnpm typecheck\npnpm build\n```\n\nExpected changed files: `package.json`, `pnpm-lock.yaml`, optional `pnpm-workspace.yaml`, optional `nitro.config.ts`, optional `vercel.json`. Confirm every Junior dep is exactly `\u003Ctarget>`. If the frozen install fails, repair with `pnpm install --lockfile-only` and rerun. Fix update-related check failures; disclose pre-existing or environment failures.\n\n### 9. Commit\n\n```text\nbuild(deps): Update Junior packages to \u003Ctarget>\n\nUpdate the Junior runtime and plugin packages to \u003Ctarget> and refresh the pnpm lockfile.\n```\n\nMention `minimumReleaseAgeExclude` sync if `pnpm-workspace.yaml` changed.\n\n### 10. Push and open\u002Fupdate PR\n\nOpen the PR ready for review, not as a draft. If an existing update PR is a draft, mark it ready for review. Include version change, release summary with links to the GitHub releases, config comparison findings, optional workspace\u002Fplugin\u002Fvercel changes, and unexpected diffs. Do not put `Checks`, `Verification`, `Test plan`, or similar validation sections in the PR body; put local check results in the final user report only. Add **Manual review required** when breaking changes, unresolved config drift, approximate Vercel review, or failed checks exist.\n\nWhen PR creation returns a subscribable resource hint, watch the PR for suggested review and CI events. After merge, if deployment follow-up is needed, use `github_getDeployment` for the merged commit and watch the suggested deployment events.\n\n## Stop conditions\n\n- Any Junior package still lacks the target version or tarball after one hour of waits in step 2.\n- Any npm version in `(old_version, target_version]` lacks a matching GitHub release.\n- `pnpm install --frozen-lockfile` fails after repair.\n- Checks fail for non-pre-existing, non-environment reasons and no safe config fix is available from step 7.\n- `package.json` changed but `pnpm-lock.yaml` did not.\n- Example app comparison reveals a breaking plugin signature change whose required values cannot be inferred from the existing consumer config.\n",{"name":5,"description":7,"disable-model-invocation":42},true,"main","e64188d9ad21af2fbacc60e3c6a0f6ed50679898","packages\u002Fjunior-maintenance\u002Fskills\u002Fself-update",45,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior","https:\u002F\u002Fjunior.sentry.dev","https:\u002F\u002Fgithub.com\u002Fgetsentry","https:\u002F\u002Fsentry.io","Real-time crash reporting for your web apps, mobile apps, and games.","2026-11-12 03:57:34",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":42},[55,58,61],{"tool":56,"command":57},"npx","npx skills add getsentry\u002Fjunior --skill self-update",{"tool":59,"command":60},"bunx","bunx skills add getsentry\u002Fjunior --skill self-update",{"tool":62,"command":63},"pnpm","pnpm dlx skills add getsentry\u002Fjunior --skill self-update","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fpackages\u002Fjunior-maintenance\u002Fskills\u002Fself-update\u002FSKILL.md",[],[67,96,124,147,170,189],{"skillNo":68,"name":24,"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":77,"publishedAt":37},"01M6CT5E87W8P93FGAVYDWD6RD","Build, review, or update Junior extension skills and plugins. Use when users ask to create a Junior SKILL.md, app skill, plugin, plugin.yaml, packaged plugin, MCP-backed plugin, OAuth or credentialed plugin, or to validate Junior extension files. Do not use for ordinary Junior usage, provider workflows, generic code editing, or non-Junior agent-skill authoring.","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fskills\u002Fjunior\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,78,79,80,81,82,83,31,84,85,86,87,88,89,90,91,20,25,92,93,94,95,22],"do","provider","editing","skill authoring","files","MCP","OAuth","workflows","ask","code","review","create","plugin","build","usage","users","generic","for",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":106,"publishedAt":37},"01M6CT5AQRDSG19SBJACXGPMY9","junior-qa","Validate Junior changes through local app-facing paths. Use for local client or agent QA, dashboard mock reporting UI QA, sharing a preview URL of a running UI, Docker sandbox provider QA (also from inside a Vercel Sandbox), PR readiness, plugin CLI commands, skill\u002Ftool\u002Fprompt\u002Fplugin behavior, and behavior that tests do not cover well but can be exercised with `pnpm cli -- chat ...`, another `pnpm cli` command, or `JUNIOR_DASHBOARD_MOCK_CONVERSATIONS=true pnpm dev`.","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fskills\u002Fjunior-qa\u002FSKILL.md",[102,105],{"categoryNo":103,"categoryName":104,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[107,108,24,25,109,110,111,112,113,114,115,116,117,118,119,120,121,122,62,123],"qa","junior qa","conversations","local","URL","preview","dashboard","cli","command","reporting","pr readiness","commands","paths","cover","ui","but","running",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":37},"01M6CT58D1SJNFZ19ZXK64ZX0R","eval-auth","Use for `\u002Feval-auth` requests in MCP auth-resume integration tests. Always connect through the disclosed MCP tool before answering, then continue the user's actual request using prior thread context when needed.","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fpackages\u002Fjunior\u002Ftests\u002Ffixtures\u002Fplugins\u002Feval-auth\u002Fskills\u002Feval-auth\u002FSKILL.md",[130],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[132,133,134,135,136,137,138,139,83,31,140,141,142,143,95,144,145,146,22],"eval auth","auth","eval","resume","integration tests","tool","integration","continue","connect","user","context","requests","request","tests","thread",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":37},"01M6CT55MZKCVBJH2X7T1HCRPX","jr-rpc","Manage low-level config and plugin introspection flows via jr-rpc bash commands. Use only when the user explicitly asks to read or update provider defaults\u002Fconfig or list installed plugins. Do not use for PR, branch, push, or auth-order questions; load the matching provider skill instead.","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fpackages\u002Fjunior\u002Fskills\u002Fjr-rpc\u002FSKILL.md",[],[154,155,78,156,90,157,35,158,133,79,159,20,160,161,162,163,164,31,165,141,95,166,167,22,168,169],"jr rpc","rpc","branch","push","introspection","manage","read","config","plugins","only","list","Bash","flows","load","via","questions",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":37},"01M6PQN1EZPHRJ5XAJP2J3ZS2T","xdotcom","Read public X (Twitter) data through the read-only X API v2. Use when users share an x.com or twitter.com link, or ask what someone posted on X, what people are saying about a topic, product, or launch on X, how much chatter something got, or for a post's text, metrics, replies, or an account's recent posts. Do not use it to post, reply, like, repost, follow, or send DMs, or to read private or protected data.","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fpackages\u002Fjunior-xdotcom\u002Fskills\u002Fxdotcom\u002FSKILL.md",[],[172,78,177,95,178,179,180,181,163,182,31,183,86,165,184,185,186,93,187,188,22],"posts","read-only","x api","send","twitter","chatter","people","api","share","replies","text","post",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":37},"01M6CT5386D90KE6YH8Q8WGQZ0","vercel","Deploy and inspect Vercel apps, assign aliases, delete deployments, investigate logs, and monitor deployment outcomes. Use for Vercel deployment and log requests, not GitHub code changes or other cloud providers.","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fpackages\u002Fjunior-vercel\u002Fskills\u002Fvercel\u002FSKILL.md",[],[191,196,197,198,199,200,201,202,203,204,205,31,206,87,207,208,209,95,210,211,212,213,143],"investigate","delete","outcomes","github","deployment","monitor","vercel deployment","github code","deployments","cloud","deploy","Providers","logs","log","inspect","assign","apps","changes"]