[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CT36CSS45MYNZJ44D5VW9C":3,"skill-same:01M6CT36CSS45MYNZJ44D5VW9C":96},{"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":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6CT36CSS45MYNZJ44D5VW9C","datadog",null,"Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository\u002Fsource-code work, or ticketing.","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-datadog\u002Fskills\u002Fdatadog\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"work","when","sentry issues","for","hosts","pup","incidents","users","query","do","up","use","behavior","ask","cli","investigate","ticketing","services","repository","logs","sentry","issues","code","monitor","telemetry","status","2026-11-10 10:12:30",false,"---\nname: datadog\ndescription: Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository\u002Fsource-code work, or ticketing.\n---\n\n# Datadog Operations\n\nUse this skill for read-only Datadog observability investigations.\n\n## Reference loading\n\nLoad references conditionally based on the request:\n\n| Need                                               | Read                                                                                                                       |\n| -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |\n| Any Datadog operation                              | [references\u002Fapi-surface.md](references\u002Fapi-surface.md)                                                                     |\n| Log search, metric query, trace lookup, incidents  | [references\u002Fcommon-use-cases.md](references\u002Fcommon-use-cases.md), [references\u002Fquery-syntax.md](references\u002Fquery-syntax.md) |\n| Auth failures, permission errors, or tool failures | [references\u002Ftroubleshooting-workarounds.md](references\u002Ftroubleshooting-workarounds.md)                                     |\n\n## Workflow\n\n1. Resolve the operation and target:\n\n- Determine whether the request is a log search, metric query, trace\u002Fspan inspection, monitor lookup, incident lookup, dashboard\u002Fnotebook lookup, service\u002Fhost listing, or service-dependency map.\n- Prefer explicit env, service, host, monitor\u002Fincident IDs, trace IDs, or Datadog URLs when the user provides them.\n- When the user did not specify a scope, treat `datadog.env` and `datadog.service` conversation config as optional defaults. Explicit user input always wins over config.\n- Only set or change `datadog.env` and `datadog.service` when the user explicitly asks to store a default for this conversation or channel.\n- If the request refers to an earlier telemetry item indirectly, inspect the current thread for the existing ID or URL before asking the user to restate it.\n- Ask one concise follow-up only when a search is genuinely under-specified, for example when the user asks about \"errors\" with no env, service, or time window hint and the thread has no prior context.\n\n- If an active repository context exists (cloned repo or configured `github.repo`), check the repo root for `TELEMETRY.md` before forming queries. When present, use its query recipes, service\u002Fenv mappings, and investigation pivots as repo-specific guidance. Explicit user targets, IDs, URLs, and conversation config still win. If absent, continue normally.\n\n2. Use Pup:\n\n- Run Datadog commands with `pup --read-only --agent ...`. The plugin also sets read-only\u002Fagent env vars, but include the flags so command transcripts show the intended mode.\n- If you are unsure about a command or flag, inspect Pup's schema with `pup --read-only --agent agent schema --compact` or the relevant `pup --read-only --agent \u003Cgroup> --help` output before guessing.\n- Start narrow: pick the single most direct command for the request before broader search.\n  - Known incident ID: `pup --read-only --agent incidents get \u003Cincident_id>`\n  - Known monitor ID: `pup --read-only --agent monitors get \u003Cmonitor_id>`\n  - Known notebook ID: `pup --read-only --agent notebooks get \u003Cnotebook_id>`\n  - Known metric name: `pup --read-only --agent metrics query --query=\"avg:\u003Cmetric>{...}\" --from=\"15m\" --to=\"now\"`; use `metrics metadata get` or `metrics tags list` when the user wants available tags or dimensions.\n- For exploratory questions, prefer one focused Pup search\u002Flist\u002Faggregate command, then one follow-up fetch if needed.\n- For \"current error rate \u002F log volume \u002F top offenders\" questions, prefer `pup logs aggregate` over pulling raw log pages back through `pup logs search`.\n- For service-topology questions (\"what calls checkout?\", \"what does the payment API depend on?\"), prefer `pup apm dependencies list` or `pup apm flow-map` over stitching spans together manually.\n- Use `pup monitors search` or `pup monitors list` for \"is this alerting?\" and `pup incidents list` \u002F `pup incidents get` for incident context.\n- Use RUM commands only when the user asks about real-user \u002F browser telemetry, not for backend issues.\n\n3. Bound every query:\n\n- Always constrain time windows. Default to the last 15 minutes for \"right now\" questions and the last 24 hours for retrospective questions; otherwise use the window the user named.\n- Always include `env:` when `datadog.env` is set or the user named an env.\n- Always include `service:` when the user named a service or `datadog.service` is set and the command is service-scoped.\n- Cap result size. Prefer the default or small page sizes; do not page through thousands of logs when an aggregate command answers the question.\n\n4. Report the result:\n\n- Return the concrete answer first (counts, status, incident severity, trace timing, top offenders), then a short evidence block.\n- Include Datadog deep links when Pup returns them or when you can construct a stable app link from an ID. Do not fabricate links from incomplete identifiers.\n- Preserve interesting spans, log lines, or metric values inline only when they are evidence for the answer. Do not dump raw command output.\n- Keep routine tool chatter silent. Do not narrate every Pup search or fetch step.\n\n## Guardrails\n\n- Read-only only in this skill. Do not create, edit, mute, delete, import, submit, or resolve monitors, incidents, notebooks, dashboards, SLOs, metrics, API keys, RUM resources, or other Datadog objects.\n- Log, RUM, APM, and incident payloads can contain PII or sensitive customer data. Quote only the minimum needed to answer the question. Do not paste full raw log bodies or span payloads when a summary plus a deep link is enough.\n- If Pup returns `403`, `permission denied`, or similar, stop and tell the user the Datadog credentials could not access the requested resource. Do not guess at missing RBAC scopes.\n- If Datadog responds with `429 Too Many Requests`, wait briefly and retry the same query once. If it still fails, report the throttle and stop.\n- For large traces or span responses that are incomplete, report that fact; do not pretend the shown spans are complete.\n- Do not use this skill for Sentry issues, Linear\u002FGitHub ticketing, or source-code investigation. Hand those off to the matching skill.\n","# Datadog Operations\n\nUse this skill for read-only Datadog observability investigations.\n\n## Reference loading\n\nLoad references conditionally based on the request:\n\n| Need                                               | Read                                                                                                                       |\n| -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |\n| Any Datadog operation                              | [references\u002Fapi-surface.md](references\u002Fapi-surface.md)                                                                     |\n| Log search, metric query, trace lookup, incidents  | [references\u002Fcommon-use-cases.md](references\u002Fcommon-use-cases.md), [references\u002Fquery-syntax.md](references\u002Fquery-syntax.md) |\n| Auth failures, permission errors, or tool failures | [references\u002Ftroubleshooting-workarounds.md](references\u002Ftroubleshooting-workarounds.md)                                     |\n\n## Workflow\n\n1. Resolve the operation and target:\n\n- Determine whether the request is a log search, metric query, trace\u002Fspan inspection, monitor lookup, incident lookup, dashboard\u002Fnotebook lookup, service\u002Fhost listing, or service-dependency map.\n- Prefer explicit env, service, host, monitor\u002Fincident IDs, trace IDs, or Datadog URLs when the user provides them.\n- When the user did not specify a scope, treat `datadog.env` and `datadog.service` conversation config as optional defaults. Explicit user input always wins over config.\n- Only set or change `datadog.env` and `datadog.service` when the user explicitly asks to store a default for this conversation or channel.\n- If the request refers to an earlier telemetry item indirectly, inspect the current thread for the existing ID or URL before asking the user to restate it.\n- Ask one concise follow-up only when a search is genuinely under-specified, for example when the user asks about \"errors\" with no env, service, or time window hint and the thread has no prior context.\n\n- If an active repository context exists (cloned repo or configured `github.repo`), check the repo root for `TELEMETRY.md` before forming queries. When present, use its query recipes, service\u002Fenv mappings, and investigation pivots as repo-specific guidance. Explicit user targets, IDs, URLs, and conversation config still win. If absent, continue normally.\n\n2. Use Pup:\n\n- Run Datadog commands with `pup --read-only --agent ...`. The plugin also sets read-only\u002Fagent env vars, but include the flags so command transcripts show the intended mode.\n- If you are unsure about a command or flag, inspect Pup's schema with `pup --read-only --agent agent schema --compact` or the relevant `pup --read-only --agent \u003Cgroup> --help` output before guessing.\n- Start narrow: pick the single most direct command for the request before broader search.\n  - Known incident ID: `pup --read-only --agent incidents get \u003Cincident_id>`\n  - Known monitor ID: `pup --read-only --agent monitors get \u003Cmonitor_id>`\n  - Known notebook ID: `pup --read-only --agent notebooks get \u003Cnotebook_id>`\n  - Known metric name: `pup --read-only --agent metrics query --query=\"avg:\u003Cmetric>{...}\" --from=\"15m\" --to=\"now\"`; use `metrics metadata get` or `metrics tags list` when the user wants available tags or dimensions.\n- For exploratory questions, prefer one focused Pup search\u002Flist\u002Faggregate command, then one follow-up fetch if needed.\n- For \"current error rate \u002F log volume \u002F top offenders\" questions, prefer `pup logs aggregate` over pulling raw log pages back through `pup logs search`.\n- For service-topology questions (\"what calls checkout?\", \"what does the payment API depend on?\"), prefer `pup apm dependencies list` or `pup apm flow-map` over stitching spans together manually.\n- Use `pup monitors search` or `pup monitors list` for \"is this alerting?\" and `pup incidents list` \u002F `pup incidents get` for incident context.\n- Use RUM commands only when the user asks about real-user \u002F browser telemetry, not for backend issues.\n\n3. Bound every query:\n\n- Always constrain time windows. Default to the last 15 minutes for \"right now\" questions and the last 24 hours for retrospective questions; otherwise use the window the user named.\n- Always include `env:` when `datadog.env` is set or the user named an env.\n- Always include `service:` when the user named a service or `datadog.service` is set and the command is service-scoped.\n- Cap result size. Prefer the default or small page sizes; do not page through thousands of logs when an aggregate command answers the question.\n\n4. Report the result:\n\n- Return the concrete answer first (counts, status, incident severity, trace timing, top offenders), then a short evidence block.\n- Include Datadog deep links when Pup returns them or when you can construct a stable app link from an ID. Do not fabricate links from incomplete identifiers.\n- Preserve interesting spans, log lines, or metric values inline only when they are evidence for the answer. Do not dump raw command output.\n- Keep routine tool chatter silent. Do not narrate every Pup search or fetch step.\n\n## Guardrails\n\n- Read-only only in this skill. Do not create, edit, mute, delete, import, submit, or resolve monitors, incidents, notebooks, dashboards, SLOs, metrics, API keys, RUM resources, or other Datadog objects.\n- Log, RUM, APM, and incident payloads can contain PII or sensitive customer data. Quote only the minimum needed to answer the question. Do not paste full raw log bodies or span payloads when a summary plus a deep link is enough.\n- If Pup returns `403`, `permission denied`, or similar, stop and tell the user the Datadog credentials could not access the requested resource. Do not guess at missing RBAC scopes.\n- If Datadog responds with `429 Too Many Requests`, wait briefly and retry the same query once. If it still fails, report the throttle and stop.\n- For large traces or span responses that are incomplete, report that fact; do not pretend the shown spans are complete.\n- Do not use this skill for Sentry issues, Linear\u002FGitHub ticketing, or source-code investigation. Hand those off to the matching skill.\n",{"name":5,"description":7},"main","5abc4b2bad9bd5ffe7b7fe0352f0999c6ca9c601","packages\u002Fjunior-datadog\u002Fskills\u002Fdatadog",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add getsentry\u002Fjunior --skill datadog",{"tool":66,"command":67},"bunx","bunx skills add getsentry\u002Fjunior --skill datadog",{"tool":69,"command":70},"pnpm","pnpm dlx skills add getsentry\u002Fjunior --skill datadog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fpackages\u002Fjunior-datadog\u002Fskills\u002Fdatadog\u002FSKILL.md",true,[74,80,84,88,92],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"README.md","REFERENCE","参考文档",7402,"https:\u002F\u002Fgithub.com\u002FMishit18\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnaming-analyzer\u002FREADME.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fapi-surface.md",5789,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fpackages\u002Fjunior-datadog\u002Fskills\u002Fdatadog\u002Freferences\u002Fapi-surface.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fcommon-use-cases.md",5575,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fpackages\u002Fjunior-datadog\u002Fskills\u002Fdatadog\u002Freferences\u002Fcommon-use-cases.md",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fquery-syntax.md",5120,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fpackages\u002Fjunior-datadog\u002Fskills\u002Fdatadog\u002Freferences\u002Fquery-syntax.md",{"path":93,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Ftroubleshooting-workarounds.md",3259,"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fjunior\u002Fblob\u002Fmain\u002Fpackages\u002Fjunior-datadog\u002Fskills\u002Fdatadog\u002Freferences\u002Ftroubleshooting-workarounds.md",[97,124,151,174,198,217],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":108,"publishedAt":45},"01M6CT5E87W8P93FGAVYDWD6RD","junior","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",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[99,28,109,110,111,112,113,30,114,115,32,41,116,117,118,119,120,121,122,26,123,22,20],"provider","editing","skill authoring","files","MCP","OAuth","workflows","review","create","plugin","build","update","app","usage","generic",{"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":134,"publishedAt":45},"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",[130,133],{"categoryNo":131,"categoryName":132,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},[135,136,99,121,137,138,139,140,141,33,142,143,144,145,146,147,148,149,69,150],"qa","junior qa","conversations","local","URL","preview","dashboard","command","reporting","pr readiness","commands","paths","cover","ui","but","running",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":45},"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",[157],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},[159,160,161,162,163,164,165,166,113,30,167,168,169,170,22,171,172,173,20],"eval auth","auth","eval","resume","integration tests","tool","integration","continue","connect","user","context","requests","request","tests","thread",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":45},"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",[],[181,182,28,183,118,184,185,186,160,109,187,120,188,189,190,191,192,30,193,168,22,194,195,20,196,197],"jr rpc","rpc","branch","push","pr","introspection","manage","read","config","plugins","only","list","Bash","flows","load","via","questions",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":45},"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",[],[200,28,205,22,206,207,208,209,191,210,30,211,32,193,212,213,214,26,215,216,20],"posts","read-only","x api","send","twitter","chatter","people","api","share","replies","text","post",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":45},"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",[],[219,34,224,225,226,227,42,228,229,230,231,30,232,41,233,38,234,22,235,236,237,238,170],"delete","outcomes","github","deployment","vercel deployment","github code","deployments","cloud","deploy","Providers","log","inspect","assign","apps","changes"]