[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EQPZJEK7CYVTZSS5N5KBVZ":3,"skill-same:01M6EQPZJEK7CYVTZSS5N5KBVZ":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6EQPZJEK7CYVTZSS5N5KBVZ","sap-doctor",null,"Use when diagnosing plugin health, MCP server connectivity, SAP system connection issues, or configuration problems. Runs systematic health checks and produces a diagnostic report.","vigneshbarani24\u002Fsap-superpowers","vigneshbarani24","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20842962?v=4","01M6EQKRW2KZ2M0H75J985XGDX","Vignesh Barani Sivakumar","01M6EQKS0E6EWFSXP4XWK6Y760",11,"MIT","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fmeta\u002Fsap-doctor\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"doctor","sap","sap doctor","MCP","mcp server","plugin","report","issues","server","health","system","use","configuration","connectivity","systematic","2026-11-10 10:12:30",false,"---\nname: sap-doctor\ndescription: Use when diagnosing plugin health, MCP server connectivity, SAP system connection issues, or configuration problems. Runs systematic health checks and produces a diagnostic report.\n---\n\n# SAP Doctor — System Diagnostics\n\nThis skill diagnoses issues with the SAP Superpowers plugin, MCP server connection, and SAP system health. It runs systematic checks and produces a clear diagnostic report with remediation steps.\n\n## Iron Laws\n\n1. **ALWAYS CHECK ALL LAYERS.** Problems cascade — a MCP issue looks like a SAP issue which looks like a code issue. Check every layer systematically: plugin → MCP → SAP → data.\n\n2. **NEVER GUESS THE ROOT CAUSE.** Run the diagnostic. Read the output. The error message tells you what's wrong — your guess about what's wrong is often incorrect.\n\n3. **ALWAYS PRODUCE A DIAGNOSTIC REPORT.** Even if the fix is obvious, document the finding. The next person to hit this issue needs the diagnostic trail.\n\n\u003CHARD-GATE>\nBefore suggesting any fix: complete the full diagnostic checklist. Premature fixes based on incomplete diagnosis create new problems.\n\u003C\u002FHARD-GATE>\n\n## Diagnostic Layers\n\n### Layer 1 — Plugin Health\nCheck the SAP Superpowers plugin installation:\n\n| Check | How | Expected |\n|-------|-----|----------|\n| Plugin loaded | Check CLAUDE.md accessible | File exists and readable |\n| Skills available | Count .md files in skills\u002F | ≥ 46 files |\n| Agents available | Count .md files in agents\u002F | ≥ 10 files |\n| Hooks registered | Read hooks\u002Fhooks.json | All hooks defined |\n| Config valid | Read .sap-superpowers\u002Fconfig.json | Valid JSON with required fields |\n| Exceptions loaded | Count files in exceptions\u002F | 8 blocklist files |\n| Knowledge available | Check knowledge\u002Findexes\u002F | Index files present |\n\n### Layer 2 — MCP Server Health\nCheck the MCP ABAP ADT server:\n\n| Check | How | Expected |\n|-------|-----|----------|\n| Node.js version | `node --version` | ≥ 20.0.0 |\n| MCP server installed | `npx abap-mcp-adt-powerup --version` | Version string returned |\n| MCP config | Check .mcp.json or mcp config | Server configured |\n| Bridge script | Check bridge\u002Fmcp-server.cjs | File exists |\n| Transport protocol | Config mcpTransport | stdio\u002Fhttp\u002Fsse |\n\n### Layer 3 — SAP Connection Health\nCheck the connection to the SAP system:\n\n| Check | How | Expected |\n|-------|-----|----------|\n| Env file exists | Check .sap-superpowers\u002Fsap.env | File present |\n| Host configured | SAP_HOST in env | Valid hostname |\n| Client configured | SAP_CLIENT in env | 3-digit client number |\n| ADT accessible | HTTP GET to \u002Fsap\u002Fbc\u002Fadt\u002Fdiscovery | 200 OK |\n| User authorized | Login test | Successful auth |\n| System info | \u002Fsap\u002Fbc\u002Fadt\u002Fcore\u002Fsysteminfo | Version and release |\n\n### Layer 4 — SAP System Health\nCheck common SAP system issues:\n\n| Check | How | Expected |\n|-------|-----|----------|\n| Work processes | SM50 equivalent via ADT | Sufficient free WPs |\n| Transport status | STMS equivalent | Transport routes active |\n| ATC available | ATC run possible | Check variant accessible |\n| ICF services active | \u002Fsap\u002Fbc\u002Fadt\u002F* nodes | All ADT services active |\n\n## Diagnostic Report Template\n\n```\nSAP DOCTOR — DIAGNOSTIC REPORT\n================================\nDate: [Timestamp]\nPlugin Version: 3.0\nConfig: [SAP version] \u002F [ABAP release]\n\nLAYER 1: PLUGIN HEALTH\n───────────────────────\n[✅\u002F❌] Plugin loaded: [status]\n[✅\u002F❌] Skills: [count] available\n[✅\u002F❌] Agents: [count] available\n[✅\u002F❌] Hooks: [status]\n[✅\u002F❌] Config: [status]\n[✅\u002F❌] Exceptions: [count] loaded\n[✅\u002F❌] Knowledge: [status]\n\nLAYER 2: MCP SERVER\n───────────────────\n[✅\u002F❌] Node.js: [version]\n[✅\u002F❌] MCP server: [version\u002Fnot found]\n[✅\u002F❌] Config: [status]\n[✅\u002F❌] Bridge: [status]\n\nLAYER 3: SAP CONNECTION\n───────────────────────\n[✅\u002F❌] Env file: [status]\n[✅\u002F❌] ADT access: [status]\n[✅\u002F❌] Auth: [status]\n[✅\u002F❌] System: [version]\n\nLAYER 4: SAP SYSTEM\n───────────────────\n[✅\u002F❌] Work processes: [status]\n[✅\u002F❌] Transports: [status]\n[✅\u002F❌] ATC: [status]\n\nFINDINGS\n────────\n[Finding 1]: [Description] → [Remediation]\n[Finding 2]: [Description] → [Remediation]\n\nOVERALL STATUS: [HEALTHY \u002F DEGRADED \u002F CRITICAL]\n```\n\n## Common Issues & Fixes\n\n| Symptom | Likely Cause | Fix |\n|---------|-------------|-----|\n| \"MCP tool not found\" | MCP server not installed | `npm i -g abap-mcp-adt-powerup` |\n| \"Connection refused\" | SAP ADT ICF service inactive | Activate \u002Fsap\u002Fbc\u002Fadt\u002F* in SICF |\n| \"401 Unauthorized\" | Wrong credentials in sap.env | Check SAP_USER and SAP_PASSWORD |\n| \"Timeout\" | Network\u002Ffirewall issue | Check SAP_HOST accessibility |\n| \"No transport\" | Transport route not configured | Check STMS transport routes |\n| Skills not loading | Plugin not installed correctly | Reinstall via plugin marketplace |\n\n## Verification\n\n- [ ] All 4 diagnostic layers checked\n- [ ] Diagnostic report produced\n- [ ] All findings have remediation steps\n- [ ] Overall status assessed\n\n## Cross-References\n\n- `troubleshooting` — For runtime SAP issues (not plugin\u002Fconnection issues)\n- `autopilot` — Calls sap-doctor before starting pipeline if connection issues suspected\n","# SAP Doctor — System Diagnostics\n\nThis skill diagnoses issues with the SAP Superpowers plugin, MCP server connection, and SAP system health. It runs systematic checks and produces a clear diagnostic report with remediation steps.\n\n## Iron Laws\n\n1. **ALWAYS CHECK ALL LAYERS.** Problems cascade — a MCP issue looks like a SAP issue which looks like a code issue. Check every layer systematically: plugin → MCP → SAP → data.\n\n2. **NEVER GUESS THE ROOT CAUSE.** Run the diagnostic. Read the output. The error message tells you what's wrong — your guess about what's wrong is often incorrect.\n\n3. **ALWAYS PRODUCE A DIAGNOSTIC REPORT.** Even if the fix is obvious, document the finding. The next person to hit this issue needs the diagnostic trail.\n\n\u003CHARD-GATE>\nBefore suggesting any fix: complete the full diagnostic checklist. Premature fixes based on incomplete diagnosis create new problems.\n\u003C\u002FHARD-GATE>\n\n## Diagnostic Layers\n\n### Layer 1 — Plugin Health\nCheck the SAP Superpowers plugin installation:\n\n| Check | How | Expected |\n|-------|-----|----------|\n| Plugin loaded | Check CLAUDE.md accessible | File exists and readable |\n| Skills available | Count .md files in skills\u002F | ≥ 46 files |\n| Agents available | Count .md files in agents\u002F | ≥ 10 files |\n| Hooks registered | Read hooks\u002Fhooks.json | All hooks defined |\n| Config valid | Read .sap-superpowers\u002Fconfig.json | Valid JSON with required fields |\n| Exceptions loaded | Count files in exceptions\u002F | 8 blocklist files |\n| Knowledge available | Check knowledge\u002Findexes\u002F | Index files present |\n\n### Layer 2 — MCP Server Health\nCheck the MCP ABAP ADT server:\n\n| Check | How | Expected |\n|-------|-----|----------|\n| Node.js version | `node --version` | ≥ 20.0.0 |\n| MCP server installed | `npx abap-mcp-adt-powerup --version` | Version string returned |\n| MCP config | Check .mcp.json or mcp config | Server configured |\n| Bridge script | Check bridge\u002Fmcp-server.cjs | File exists |\n| Transport protocol | Config mcpTransport | stdio\u002Fhttp\u002Fsse |\n\n### Layer 3 — SAP Connection Health\nCheck the connection to the SAP system:\n\n| Check | How | Expected |\n|-------|-----|----------|\n| Env file exists | Check .sap-superpowers\u002Fsap.env | File present |\n| Host configured | SAP_HOST in env | Valid hostname |\n| Client configured | SAP_CLIENT in env | 3-digit client number |\n| ADT accessible | HTTP GET to \u002Fsap\u002Fbc\u002Fadt\u002Fdiscovery | 200 OK |\n| User authorized | Login test | Successful auth |\n| System info | \u002Fsap\u002Fbc\u002Fadt\u002Fcore\u002Fsysteminfo | Version and release |\n\n### Layer 4 — SAP System Health\nCheck common SAP system issues:\n\n| Check | How | Expected |\n|-------|-----|----------|\n| Work processes | SM50 equivalent via ADT | Sufficient free WPs |\n| Transport status | STMS equivalent | Transport routes active |\n| ATC available | ATC run possible | Check variant accessible |\n| ICF services active | \u002Fsap\u002Fbc\u002Fadt\u002F* nodes | All ADT services active |\n\n## Diagnostic Report Template\n\n```\nSAP DOCTOR — DIAGNOSTIC REPORT\n================================\nDate: [Timestamp]\nPlugin Version: 3.0\nConfig: [SAP version] \u002F [ABAP release]\n\nLAYER 1: PLUGIN HEALTH\n───────────────────────\n[✅\u002F❌] Plugin loaded: [status]\n[✅\u002F❌] Skills: [count] available\n[✅\u002F❌] Agents: [count] available\n[✅\u002F❌] Hooks: [status]\n[✅\u002F❌] Config: [status]\n[✅\u002F❌] Exceptions: [count] loaded\n[✅\u002F❌] Knowledge: [status]\n\nLAYER 2: MCP SERVER\n───────────────────\n[✅\u002F❌] Node.js: [version]\n[✅\u002F❌] MCP server: [version\u002Fnot found]\n[✅\u002F❌] Config: [status]\n[✅\u002F❌] Bridge: [status]\n\nLAYER 3: SAP CONNECTION\n───────────────────────\n[✅\u002F❌] Env file: [status]\n[✅\u002F❌] ADT access: [status]\n[✅\u002F❌] Auth: [status]\n[✅\u002F❌] System: [version]\n\nLAYER 4: SAP SYSTEM\n───────────────────\n[✅\u002F❌] Work processes: [status]\n[✅\u002F❌] Transports: [status]\n[✅\u002F❌] ATC: [status]\n\nFINDINGS\n────────\n[Finding 1]: [Description] → [Remediation]\n[Finding 2]: [Description] → [Remediation]\n\nOVERALL STATUS: [HEALTHY \u002F DEGRADED \u002F CRITICAL]\n```\n\n## Common Issues & Fixes\n\n| Symptom | Likely Cause | Fix |\n|---------|-------------|-----|\n| \"MCP tool not found\" | MCP server not installed | `npm i -g abap-mcp-adt-powerup` |\n| \"Connection refused\" | SAP ADT ICF service inactive | Activate \u002Fsap\u002Fbc\u002Fadt\u002F* in SICF |\n| \"401 Unauthorized\" | Wrong credentials in sap.env | Check SAP_USER and SAP_PASSWORD |\n| \"Timeout\" | Network\u002Ffirewall issue | Check SAP_HOST accessibility |\n| \"No transport\" | Transport route not configured | Check STMS transport routes |\n| Skills not loading | Plugin not installed correctly | Reinstall via plugin marketplace |\n\n## Verification\n\n- [ ] All 4 diagnostic layers checked\n- [ ] Diagnostic report produced\n- [ ] All findings have remediation steps\n- [ ] Overall status assessed\n\n## Cross-References\n\n- `troubleshooting` — For runtime SAP issues (not plugin\u002Fconnection issues)\n- `autopilot` — Calls sap-doctor before starting pipeline if connection issues suspected\n",{"name":5,"description":7},"main","cf5d032baea1657808fa74369439ea7e9c7e0a20","skills\u002Fmeta\u002Fsap-doctor",3,"https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers","https:\u002F\u002Fsap-superpowers.vercel.app\u002F","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24","2026-08-23 17:03:43",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add vigneshbarani24\u002Fsap-superpowers --skill sap-doctor",{"tool":58,"command":59},"bunx","bunx skills add vigneshbarani24\u002Fsap-superpowers --skill sap-doctor",{"tool":61,"command":62},"pnpm","pnpm dlx skills add vigneshbarani24\u002Fsap-superpowers --skill sap-doctor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fmeta\u002Fsap-doctor\u002FSKILL.md",true,[],[67,93,100,109,118,127],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":39},"01M6EQTMCBV605ETS5WWEQX209","s4hana-migration","Use when advising on S\u002F4HANA migration approach, assessing greenfield vs brownfield vs selective data transition options, analyzing custom code impact, reviewing simplification items, or building a migration business case or timeline.","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Fs4hana-migration\u002FSKILL.md",[],[74,75,76,77,78,79,80,81,82,83,84,85,35,86,87,88,89,90,91,92],"migration","s4hana migration","data","case","impact","discover","simplification","project","brownfield","options","business case","project manager","business","technical","architect","timeline","analyzing","code","prepare",{"skillNo":94,"name":95,"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":96,"categories":97,"keywords":98,"publishedAt":39},"01M6EQTGJHSYYQDMBJY0APE19X","rise-licensing","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Frise-licensing\u002FSKILL.md",[],[99],"rise licensing",{"skillNo":101,"name":102,"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":103,"categories":104,"keywords":105,"publishedAt":39},"01M6EQTCVAJPYQ7A8SA49A1Y72","joule-strategy","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Fjoule-strategy\u002FSKILL.md",[],[106,107,108],"joule strategy","joule","strategy",{"skillNo":110,"name":111,"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":112,"categories":113,"keywords":114,"publishedAt":39},"01M6EQTA7RMJ6RNFDTK1E2E9YY","clean-core-strategy","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Fclean-core-strategy\u002FSKILL.md",[],[115,116,117,108],"clean core strategy","clean","core",{"skillNo":119,"name":120,"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":121,"categories":122,"keywords":123,"publishedAt":39},"01M6EQT6QCR8MJ7J62ZP8WZ578","activate-methodology","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Factivate-methodology\u002FSKILL.md",[],[124,125,126],"methodology","activate","activate methodology",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":39},"01M6EQT3XFHC6Y2F0EWQ62PHSR","strategic","strategic skills category for SAP Superpowers. Contains 5 sub-skills.","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002FSKILL.md",[],[129,134,25],"superpowers"]