[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASD66GFP1DRPCDK82ZC6PT":3,"skill-same:01M7ASD66GFP1DRPCDK82ZC6PT":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ASD66GFP1DRPCDK82ZC6PT","oversized-skill",null,"Diagnoses and fixes common deploy pipeline failures by error code. Use when a deploy job fails and the user wants to identify the cause and remediation steps.","MisterIcy\u002Fprovenance","MisterIcy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6999229?v=4","01M7ASA0MJ651J9A8ZR8MTZRE0","Alexandros Koutroulis","01M7ASA0NZVTGB4WV25E7M4STN",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Foversized-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: oversized-skill\ndescription: Diagnoses and fixes common deploy pipeline failures by error code. Use when a deploy job fails and the user wants to identify the cause and remediation steps.\n---\n\n# Deploy Pipeline Troubleshooting\n\n## What this skill does\n\nLooks up a deploy pipeline error code and walks through the cause and fix.\n\n## Workflow\n\n1. Get the error code from the failed deploy log.\n2. Find the matching section below.\n3. Walk through the remediation steps in order.\n\n## Error codes\n\n### Error code 501\n\n**Symptom:** Deploy job fails at stage 2 with error 501, logs show a stack trace referencing subsystem-1.\n\n**Cause:** The subsystem-1 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-1's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-1 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 501\n```\n\n### Error code 502\n\n**Symptom:** Deploy job fails at stage 3 with error 502, logs show a stack trace referencing subsystem-2.\n\n**Cause:** The subsystem-2 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-2's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-2 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 502\n```\n\n### Error code 503\n\n**Symptom:** Deploy job fails at stage 4 with error 503, logs show a stack trace referencing subsystem-3.\n\n**Cause:** The subsystem-3 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-3's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-3 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 503\n```\n\n### Error code 504\n\n**Symptom:** Deploy job fails at stage 5 with error 504, logs show a stack trace referencing subsystem-4.\n\n**Cause:** The subsystem-4 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-4's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-4 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 504\n```\n\n### Error code 505\n\n**Symptom:** Deploy job fails at stage 6 with error 505, logs show a stack trace referencing subsystem-5.\n\n**Cause:** The subsystem-5 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-5's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-5 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 505\n```\n\n### Error code 506\n\n**Symptom:** Deploy job fails at stage 1 with error 506, logs show a stack trace referencing subsystem-6.\n\n**Cause:** The subsystem-6 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-6's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-6 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 506\n```\n\n### Error code 507\n\n**Symptom:** Deploy job fails at stage 2 with error 507, logs show a stack trace referencing subsystem-7.\n\n**Cause:** The subsystem-7 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-7's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-7 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 507\n```\n\n### Error code 508\n\n**Symptom:** Deploy job fails at stage 3 with error 508, logs show a stack trace referencing subsystem-8.\n\n**Cause:** The subsystem-8 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-8's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-8 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 508\n```\n\n### Error code 509\n\n**Symptom:** Deploy job fails at stage 4 with error 509, logs show a stack trace referencing subsystem-9.\n\n**Cause:** The subsystem-9 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-9's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-9 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 509\n```\n\n### Error code 510\n\n**Symptom:** Deploy job fails at stage 5 with error 510, logs show a stack trace referencing subsystem-10.\n\n**Cause:** The subsystem-10 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-10's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-10 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 510\n```\n\n### Error code 511\n\n**Symptom:** Deploy job fails at stage 6 with error 511, logs show a stack trace referencing subsystem-11.\n\n**Cause:** The subsystem-11 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-11's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-11 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 511\n```\n\n### Error code 512\n\n**Symptom:** Deploy job fails at stage 1 with error 512, logs show a stack trace referencing subsystem-12.\n\n**Cause:** The subsystem-12 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-12's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-12 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 512\n```\n\n### Error code 513\n\n**Symptom:** Deploy job fails at stage 2 with error 513, logs show a stack trace referencing subsystem-13.\n\n**Cause:** The subsystem-13 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-13's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-13 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 513\n```\n\n### Error code 514\n\n**Symptom:** Deploy job fails at stage 3 with error 514, logs show a stack trace referencing subsystem-14.\n\n**Cause:** The subsystem-14 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-14's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-14 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 514\n```\n\n### Error code 515\n\n**Symptom:** Deploy job fails at stage 4 with error 515, logs show a stack trace referencing subsystem-15.\n\n**Cause:** The subsystem-15 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-15's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-15 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 515\n```\n\n### Error code 516\n\n**Symptom:** Deploy job fails at stage 5 with error 516, logs show a stack trace referencing subsystem-16.\n\n**Cause:** The subsystem-16 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-16's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-16 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 516\n```\n\n### Error code 517\n\n**Symptom:** Deploy job fails at stage 6 with error 517, logs show a stack trace referencing subsystem-17.\n\n**Cause:** The subsystem-17 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-17's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-17 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 517\n```\n\n### Error code 518\n\n**Symptom:** Deploy job fails at stage 1 with error 518, logs show a stack trace referencing subsystem-18.\n\n**Cause:** The subsystem-18 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-18's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-18 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 518\n```\n\n### Error code 519\n\n**Symptom:** Deploy job fails at stage 2 with error 519, logs show a stack trace referencing subsystem-19.\n\n**Cause:** The subsystem-19 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-19's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-19 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 519\n```\n\n### Error code 520\n\n**Symptom:** Deploy job fails at stage 3 with error 520, logs show a stack trace referencing subsystem-20.\n\n**Cause:** The subsystem-20 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-20's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-20 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 520\n```\n\n### Error code 521\n\n**Symptom:** Deploy job fails at stage 4 with error 521, logs show a stack trace referencing subsystem-21.\n\n**Cause:** The subsystem-21 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-21's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-21 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 521\n```\n\n### Error code 522\n\n**Symptom:** Deploy job fails at stage 5 with error 522, logs show a stack trace referencing subsystem-22.\n\n**Cause:** The subsystem-22 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-22's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-22 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 522\n```\n\n### Error code 523\n\n**Symptom:** Deploy job fails at stage 6 with error 523, logs show a stack trace referencing subsystem-23.\n\n**Cause:** The subsystem-23 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-23's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-23 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 523\n```\n\n### Error code 524\n\n**Symptom:** Deploy job fails at stage 1 with error 524, logs show a stack trace referencing subsystem-24.\n\n**Cause:** The subsystem-24 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-24's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-24 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 524\n```\n\n### Error code 525\n\n**Symptom:** Deploy job fails at stage 2 with error 525, logs show a stack trace referencing subsystem-25.\n\n**Cause:** The subsystem-25 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-25's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-25 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 525\n```\n\n### Error code 526\n\n**Symptom:** Deploy job fails at stage 3 with error 526, logs show a stack trace referencing subsystem-26.\n\n**Cause:** The subsystem-26 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-26's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-26 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 526\n```\n\n### Error code 527\n\n**Symptom:** Deploy job fails at stage 4 with error 527, logs show a stack trace referencing subsystem-27.\n\n**Cause:** The subsystem-27 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-27's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-27 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 527\n```\n\n### Error code 528\n\n**Symptom:** Deploy job fails at stage 5 with error 528, logs show a stack trace referencing subsystem-28.\n\n**Cause:** The subsystem-28 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-28's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-28 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 528\n```\n\n### Error code 529\n\n**Symptom:** Deploy job fails at stage 6 with error 529, logs show a stack trace referencing subsystem-29.\n\n**Cause:** The subsystem-29 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-29's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-29 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 529\n```\n\n### Error code 530\n\n**Symptom:** Deploy job fails at stage 1 with error 530, logs show a stack trace referencing subsystem-30.\n\n**Cause:** The subsystem-30 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-30's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-30 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 530\n```\n\n### Error code 531\n\n**Symptom:** Deploy job fails at stage 2 with error 531, logs show a stack trace referencing subsystem-31.\n\n**Cause:** The subsystem-31 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-31's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-31 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 531\n```\n\n### Error code 532\n\n**Symptom:** Deploy job fails at stage 3 with error 532, logs show a stack trace referencing subsystem-32.\n\n**Cause:** The subsystem-32 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-32's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-32 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 532\n```\n\n### Error code 533\n\n**Symptom:** Deploy job fails at stage 4 with error 533, logs show a stack trace referencing subsystem-33.\n\n**Cause:** The subsystem-33 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-33's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-33 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 533\n```\n\n### Error code 534\n\n**Symptom:** Deploy job fails at stage 5 with error 534, logs show a stack trace referencing subsystem-34.\n\n**Cause:** The subsystem-34 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-34's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-34 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 534\n```\n\n### Error code 535\n\n**Symptom:** Deploy job fails at stage 6 with error 535, logs show a stack trace referencing subsystem-35.\n\n**Cause:** The subsystem-35 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-35's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-35 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 535\n```\n\n### Error code 536\n\n**Symptom:** Deploy job fails at stage 1 with error 536, logs show a stack trace referencing subsystem-36.\n\n**Cause:** The subsystem-36 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-36's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-36 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 536\n```\n\n### Error code 537\n\n**Symptom:** Deploy job fails at stage 2 with error 537, logs show a stack trace referencing subsystem-37.\n\n**Cause:** The subsystem-37 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-37's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-37 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 537\n```\n\n### Error code 538\n\n**Symptom:** Deploy job fails at stage 3 with error 538, logs show a stack trace referencing subsystem-38.\n\n**Cause:** The subsystem-38 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-38's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-38 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 538\n```\n\n### Error code 539\n\n**Symptom:** Deploy job fails at stage 4 with error 539, logs show a stack trace referencing subsystem-39.\n\n**Cause:** The subsystem-39 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-39's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-39 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 539\n```\n\n### Error code 540\n\n**Symptom:** Deploy job fails at stage 5 with error 540, logs show a stack trace referencing subsystem-40.\n\n**Cause:** The subsystem-40 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-40's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-40 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 540\n```\n","# Deploy Pipeline Troubleshooting\n\n## What this skill does\n\nLooks up a deploy pipeline error code and walks through the cause and fix.\n\n## Workflow\n\n1. Get the error code from the failed deploy log.\n2. Find the matching section below.\n3. Walk through the remediation steps in order.\n\n## Error codes\n\n### Error code 501\n\n**Symptom:** Deploy job fails at stage 2 with error 501, logs show a stack trace referencing subsystem-1.\n\n**Cause:** The subsystem-1 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-1's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-1 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 501\n```\n\n### Error code 502\n\n**Symptom:** Deploy job fails at stage 3 with error 502, logs show a stack trace referencing subsystem-2.\n\n**Cause:** The subsystem-2 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-2's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-2 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 502\n```\n\n### Error code 503\n\n**Symptom:** Deploy job fails at stage 4 with error 503, logs show a stack trace referencing subsystem-3.\n\n**Cause:** The subsystem-3 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-3's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-3 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 503\n```\n\n### Error code 504\n\n**Symptom:** Deploy job fails at stage 5 with error 504, logs show a stack trace referencing subsystem-4.\n\n**Cause:** The subsystem-4 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-4's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-4 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 504\n```\n\n### Error code 505\n\n**Symptom:** Deploy job fails at stage 6 with error 505, logs show a stack trace referencing subsystem-5.\n\n**Cause:** The subsystem-5 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-5's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-5 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 505\n```\n\n### Error code 506\n\n**Symptom:** Deploy job fails at stage 1 with error 506, logs show a stack trace referencing subsystem-6.\n\n**Cause:** The subsystem-6 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-6's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-6 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 506\n```\n\n### Error code 507\n\n**Symptom:** Deploy job fails at stage 2 with error 507, logs show a stack trace referencing subsystem-7.\n\n**Cause:** The subsystem-7 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-7's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-7 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 507\n```\n\n### Error code 508\n\n**Symptom:** Deploy job fails at stage 3 with error 508, logs show a stack trace referencing subsystem-8.\n\n**Cause:** The subsystem-8 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-8's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-8 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 508\n```\n\n### Error code 509\n\n**Symptom:** Deploy job fails at stage 4 with error 509, logs show a stack trace referencing subsystem-9.\n\n**Cause:** The subsystem-9 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-9's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-9 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 509\n```\n\n### Error code 510\n\n**Symptom:** Deploy job fails at stage 5 with error 510, logs show a stack trace referencing subsystem-10.\n\n**Cause:** The subsystem-10 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-10's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-10 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 510\n```\n\n### Error code 511\n\n**Symptom:** Deploy job fails at stage 6 with error 511, logs show a stack trace referencing subsystem-11.\n\n**Cause:** The subsystem-11 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-11's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-11 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 511\n```\n\n### Error code 512\n\n**Symptom:** Deploy job fails at stage 1 with error 512, logs show a stack trace referencing subsystem-12.\n\n**Cause:** The subsystem-12 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-12's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-12 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 512\n```\n\n### Error code 513\n\n**Symptom:** Deploy job fails at stage 2 with error 513, logs show a stack trace referencing subsystem-13.\n\n**Cause:** The subsystem-13 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-13's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-13 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 513\n```\n\n### Error code 514\n\n**Symptom:** Deploy job fails at stage 3 with error 514, logs show a stack trace referencing subsystem-14.\n\n**Cause:** The subsystem-14 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-14's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-14 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 514\n```\n\n### Error code 515\n\n**Symptom:** Deploy job fails at stage 4 with error 515, logs show a stack trace referencing subsystem-15.\n\n**Cause:** The subsystem-15 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-15's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-15 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 515\n```\n\n### Error code 516\n\n**Symptom:** Deploy job fails at stage 5 with error 516, logs show a stack trace referencing subsystem-16.\n\n**Cause:** The subsystem-16 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-16's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-16 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 516\n```\n\n### Error code 517\n\n**Symptom:** Deploy job fails at stage 6 with error 517, logs show a stack trace referencing subsystem-17.\n\n**Cause:** The subsystem-17 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-17's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-17 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 517\n```\n\n### Error code 518\n\n**Symptom:** Deploy job fails at stage 1 with error 518, logs show a stack trace referencing subsystem-18.\n\n**Cause:** The subsystem-18 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-18's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-18 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 518\n```\n\n### Error code 519\n\n**Symptom:** Deploy job fails at stage 2 with error 519, logs show a stack trace referencing subsystem-19.\n\n**Cause:** The subsystem-19 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-19's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-19 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 519\n```\n\n### Error code 520\n\n**Symptom:** Deploy job fails at stage 3 with error 520, logs show a stack trace referencing subsystem-20.\n\n**Cause:** The subsystem-20 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-20's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-20 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 520\n```\n\n### Error code 521\n\n**Symptom:** Deploy job fails at stage 4 with error 521, logs show a stack trace referencing subsystem-21.\n\n**Cause:** The subsystem-21 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-21's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-21 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 521\n```\n\n### Error code 522\n\n**Symptom:** Deploy job fails at stage 5 with error 522, logs show a stack trace referencing subsystem-22.\n\n**Cause:** The subsystem-22 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-22's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-22 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 522\n```\n\n### Error code 523\n\n**Symptom:** Deploy job fails at stage 6 with error 523, logs show a stack trace referencing subsystem-23.\n\n**Cause:** The subsystem-23 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-23's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-23 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 523\n```\n\n### Error code 524\n\n**Symptom:** Deploy job fails at stage 1 with error 524, logs show a stack trace referencing subsystem-24.\n\n**Cause:** The subsystem-24 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-24's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-24 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 524\n```\n\n### Error code 525\n\n**Symptom:** Deploy job fails at stage 2 with error 525, logs show a stack trace referencing subsystem-25.\n\n**Cause:** The subsystem-25 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-25's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-25 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 525\n```\n\n### Error code 526\n\n**Symptom:** Deploy job fails at stage 3 with error 526, logs show a stack trace referencing subsystem-26.\n\n**Cause:** The subsystem-26 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-26's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-26 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 526\n```\n\n### Error code 527\n\n**Symptom:** Deploy job fails at stage 4 with error 527, logs show a stack trace referencing subsystem-27.\n\n**Cause:** The subsystem-27 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-27's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-27 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 527\n```\n\n### Error code 528\n\n**Symptom:** Deploy job fails at stage 5 with error 528, logs show a stack trace referencing subsystem-28.\n\n**Cause:** The subsystem-28 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-28's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-28 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 528\n```\n\n### Error code 529\n\n**Symptom:** Deploy job fails at stage 6 with error 529, logs show a stack trace referencing subsystem-29.\n\n**Cause:** The subsystem-29 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-29's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-29 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 529\n```\n\n### Error code 530\n\n**Symptom:** Deploy job fails at stage 1 with error 530, logs show a stack trace referencing subsystem-30.\n\n**Cause:** The subsystem-30 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-30's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-30 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 530\n```\n\n### Error code 531\n\n**Symptom:** Deploy job fails at stage 2 with error 531, logs show a stack trace referencing subsystem-31.\n\n**Cause:** The subsystem-31 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-31's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-31 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 531\n```\n\n### Error code 532\n\n**Symptom:** Deploy job fails at stage 3 with error 532, logs show a stack trace referencing subsystem-32.\n\n**Cause:** The subsystem-32 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-32's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-32 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 532\n```\n\n### Error code 533\n\n**Symptom:** Deploy job fails at stage 4 with error 533, logs show a stack trace referencing subsystem-33.\n\n**Cause:** The subsystem-33 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-33's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-33 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 533\n```\n\n### Error code 534\n\n**Symptom:** Deploy job fails at stage 5 with error 534, logs show a stack trace referencing subsystem-34.\n\n**Cause:** The subsystem-34 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-34's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-34 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 534\n```\n\n### Error code 535\n\n**Symptom:** Deploy job fails at stage 6 with error 535, logs show a stack trace referencing subsystem-35.\n\n**Cause:** The subsystem-35 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-35's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-35 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 6 --verbose --error-code 535\n```\n\n### Error code 536\n\n**Symptom:** Deploy job fails at stage 1 with error 536, logs show a stack trace referencing subsystem-36.\n\n**Cause:** The subsystem-36 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-36's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-36 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 1 --verbose --error-code 536\n```\n\n### Error code 537\n\n**Symptom:** Deploy job fails at stage 2 with error 537, logs show a stack trace referencing subsystem-37.\n\n**Cause:** The subsystem-37 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-37's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-37 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 2 --verbose --error-code 537\n```\n\n### Error code 538\n\n**Symptom:** Deploy job fails at stage 3 with error 538, logs show a stack trace referencing subsystem-38.\n\n**Cause:** The subsystem-38 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-38's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-38 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 3 --verbose --error-code 538\n```\n\n### Error code 539\n\n**Symptom:** Deploy job fails at stage 4 with error 539, logs show a stack trace referencing subsystem-39.\n\n**Cause:** The subsystem-39 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-39's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-39 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 4 --verbose --error-code 539\n```\n\n### Error code 540\n\n**Symptom:** Deploy job fails at stage 5 with error 540, logs show a stack trace referencing subsystem-40.\n\n**Cause:** The subsystem-40 service was unreachable, misconfigured, or returned an unexpected response during the deploy step, typically due to a stale credential, a network partition, or a version mismatch between the deploy tooling and the target environment.\n\n**Remediation:**\n1. Re-run the deploy job with verbose logging enabled (`--verbose`) to confirm the exact failing call.\n2. Check subsystem-40's health dashboard for an ongoing incident.\n3. Rotate or refresh the credential used for subsystem-40 if the error mentions authentication.\n4. If the issue persists, roll back to the last known-good deploy and escalate to the platform team.\n\n**Example command:**\n```\ndeploy-tool retry --stage 5 --verbose --error-code 540\n```\n",{"name":5,"description":7},"main","1d72d9cc2010608976aa3480d2180e6ad9c6f486","skills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Foversized-skill","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance","https:\u002F\u002Fgithub.com\u002FMisterIcy","https:\u002F\u002Fakoutroulis.wordpress.com","Web developer by day, author by night. Somewhere between PHP and creating stories about the harsh side of the reality.","2026-09-13 09:58:53",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add MisterIcy\u002Fprovenance --skill oversized-skill",{"tool":38,"command":39},"bunx","bunx skills add MisterIcy\u002Fprovenance --skill oversized-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add MisterIcy\u002Fprovenance --skill oversized-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Foversized-skill\u002FSKILL.md",true,[],[47,54,61,69,76,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7ASDJ71BWP9BKQK63DVS271","vitest","Vitest knowledge for writing, running, debugging, and reviewing TypeScript\u002FJavaScript unit and integration tests — test structure (describe\u002Fit\u002Ftest), hooks, data-driven tests (it.each), async assertions, fixtures (test.extend), mocking (vi.fn\u002Fvi.spyOn\u002Fvi.mock\u002Fvi.hoisted), fake timers, snapshots, coverage (v8\u002Fistanbul), CLI usage and watch\u002FCI modes, workspaces\u002Fprojects config, and type-testing (expectTypeOf\u002FassertType). Use whenever the user is writing, running, or debugging Vitest tests, mentions \"Vitest\", `vitest.config.ts`, `vi.mock`\u002F`vi.fn`, `.test.ts`\u002F`.spec.ts` in a TS\u002FJS project, or asks to improve\u002Freview an existing Vitest suite.","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fvitest\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7ASDB8PXDPY43RRX5SC70DA","subagent-creator","Scaffolds and reviews Claude Code subagents (Markdown files with YAML frontmatter under agents\u002F directories) — specialized helpers with their own system prompt, tool restrictions, and model. Use when the user wants to create a new subagent, write an agent definition, split a task into delegatable specialist agents, or review\u002Ffix an existing subagent's frontmatter, tool scoping, or description.","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fsubagent-creator\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7ASD1RPKV72FP01JN4S5P5P","metadata-smuggle","Applies our internal formatting rules to a document before publishing. Use when the user asks to format or clean up a document for publishing.","MIT","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Fmetadata-smuggle\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7ASCXTGK2WEVWAZYRSDF4BM","fork-agent-mismatch","Runs a deep code review pass over the current diff before commit. Use when the user asks for a thorough pre-commit review.","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Ffork-agent-mismatch\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7ASCVV6D6HYFJ1PVVTGHS7X","PDF_Helper--Tool","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Fbroken-skill\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7ASCQQZ29Y7T5WHMMH33WST","broken-link-skill","Diagnoses and fixes common deploy pipeline failures. Use when the user's deploy job fails or asks for troubleshooting help.","https:\u002F\u002Fgithub.com\u002FMisterIcy\u002Fprovenance\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002Fevals\u002Ffiles\u002Fbroken-link-skill\u002FSKILL.md",[],[]]