[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71B27XB3CZX6J87RVB30FC8":3,"skill-same:01M71B27XB3CZX6J87RVB30FC8":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M71B27XB3CZX6J87RVB30FC8","solar-energy-troubleshooting-guide",null,"Diagnose and resolve common problems a solar PV engineer meets in rooftops, solar farms and offices.\nTRIGGERS - Use when a solar PV engineer needs a troubleshooting & problem solving for homeowners, businesses and energy companies in rooftops, solar farms and offices.","lionelsimai\u002Fclaude-skills-collection","lionelsimai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260158848?v=4","01M6CHZPS8G9TSB113TT0BBM6E","Lionel ","01M6CHZPXGW2SPE3BHQTGJ0S8J",38,"MIT","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fsolar-energy-troubleshooting-guide\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"solar energy troubleshooting guide","solar","energy","solar energy","troubleshooting","troubleshooting guide","guide","problem","diagnose","for","engineer","triggers","use","when","common","problem solving","2026-11-10 10:12:30",false,"---\nname: solar-energy-troubleshooting-guide\ndescription: |\n  Diagnose and resolve common problems a solar PV engineer meets in rooftops, solar farms and offices.\n  TRIGGERS - Use when a solar PV engineer needs a troubleshooting & problem solving for homeowners, businesses and energy companies in rooftops, solar farms and offices.\ncategory: Solar Energy\nlicense: MIT\nversion: 1.0\n---\n# Troubleshooting & Problem Solving — Solar Energy\n\nDiagnose and resolve common problems a solar PV engineer meets in rooftops, solar farms and offices. The deliverable is a troubleshooting guide: symptoms, likely causes, checks and fixes.\nThis skill is written for a solar PV engineer working with homeowners, businesses and energy companies in rooftops, solar farms and offices.\n\n## When to use\n- You are a solar PV engineer preparing, delivering or reviewing this part of your work in rooftops, solar farms and offices.\n- You need a defensible, repeatable approach that produces a troubleshooting guide: symptoms, likely causes, checks and fixes.\n- A colleague, auditor or client asks how this was done and what evidence supports it.\n\n## Key Concepts\n| Term | Meaning |\n|------|---------|\n| Inverter | the device converting panel DC output to usable AC |\n| Performance ratio | actual output compared with theoretical maximum |\n| Feed-in | electricity exported to the grid |\n\n## Workflow\n1. **Step 1** - Describe the problem precisely from the record in system designs — when it started, what changed, who it affects\n2. **Step 2** - Work from most likely and most dangerous causes first; rule out anything connected to falls from roofs early\n3. **Step 3** - Run checks in a logical order using PV panels and inverters, changing one variable at a time so the cause can be isolated\n4. **Step 4** - Apply the fix, then verify against system performance ratio that the problem is actually resolved, not just quieter\n5. **Step 5** - Document the diagnosis and fix so the next occurrence is faster, and flag recurring problems for root-cause work\n\n## Profession-Specific Components\n| Component | Details for Solar Energy |\n|-----------|-------------------------------|\n| Core documentation | system designs; performance reports; installation certificates; maintenance logs |\n| Core tools & equipment | PV panels and inverters; monitoring platforms; testing instruments; scaffolding |\n| People involved | homeowners, businesses and energy companies; the solar PV engineer; colleagues and other services in rooftops, solar farms and offices |\n| Primary record | system designs — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in rooftops, solar farms and offices] | **Objective:** [What this must achieve] | **Audience:** [homeowners, businesses and energy companies and other stakeholders]\n\nThe finished output is a troubleshooting guide: symptoms, likely causes, checks and fixes, structured as:\n1. Summary of position and evidence\n2. Detail, following the workflow above\n3. Decisions, actions, owners and dates\n4. Review point and escalation route\n\n### Action Plan\n1. **Immediate:** Confirm scope, consent and the evidence available in system designs.\n2. **Short-term:** Complete the workflow steps and record outcomes against system performance ratio.\n3. **Medium-term:** Review results, close actions, and update local procedures in rooftops, solar farms and offices.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| system performance ratio | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |\n| installation times | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |\n| fault response | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |\n| customer savings reported | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: falls from roofs.\n- Never let this happen: electrical faults.\n- Never let this happen: underperforming systems unnoticed.\n- Work only within the competence and authority of a solar PV engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to rooftops, solar farms and offices's rules.\n- Verify names, dates, figures and measurements twice before anything is issued or signed off.\n- Use only real, verified information from the case in hand — never invent results, credentials or evidence.\n\n## Example (illustrative)\nA solar PV engineer in rooftops, solar farms and offices applies this workflow for homeowners, businesses and energy companies: they open\nsystem designs, work through the five steps using PV panels and inverters, and close by recording\nthe outcome against system performance ratio and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Troubleshooting & Problem Solving — Solar Energy\n\nDiagnose and resolve common problems a solar PV engineer meets in rooftops, solar farms and offices. The deliverable is a troubleshooting guide: symptoms, likely causes, checks and fixes.\nThis skill is written for a solar PV engineer working with homeowners, businesses and energy companies in rooftops, solar farms and offices.\n\n## When to use\n- You are a solar PV engineer preparing, delivering or reviewing this part of your work in rooftops, solar farms and offices.\n- You need a defensible, repeatable approach that produces a troubleshooting guide: symptoms, likely causes, checks and fixes.\n- A colleague, auditor or client asks how this was done and what evidence supports it.\n\n## Key Concepts\n| Term | Meaning |\n|------|---------|\n| Inverter | the device converting panel DC output to usable AC |\n| Performance ratio | actual output compared with theoretical maximum |\n| Feed-in | electricity exported to the grid |\n\n## Workflow\n1. **Step 1** - Describe the problem precisely from the record in system designs — when it started, what changed, who it affects\n2. **Step 2** - Work from most likely and most dangerous causes first; rule out anything connected to falls from roofs early\n3. **Step 3** - Run checks in a logical order using PV panels and inverters, changing one variable at a time so the cause can be isolated\n4. **Step 4** - Apply the fix, then verify against system performance ratio that the problem is actually resolved, not just quieter\n5. **Step 5** - Document the diagnosis and fix so the next occurrence is faster, and flag recurring problems for root-cause work\n\n## Profession-Specific Components\n| Component | Details for Solar Energy |\n|-----------|-------------------------------|\n| Core documentation | system designs; performance reports; installation certificates; maintenance logs |\n| Core tools & equipment | PV panels and inverters; monitoring platforms; testing instruments; scaffolding |\n| People involved | homeowners, businesses and energy companies; the solar PV engineer; colleagues and other services in rooftops, solar farms and offices |\n| Primary record | system designs — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in rooftops, solar farms and offices] | **Objective:** [What this must achieve] | **Audience:** [homeowners, businesses and energy companies and other stakeholders]\n\nThe finished output is a troubleshooting guide: symptoms, likely causes, checks and fixes, structured as:\n1. Summary of position and evidence\n2. Detail, following the workflow above\n3. Decisions, actions, owners and dates\n4. Review point and escalation route\n\n### Action Plan\n1. **Immediate:** Confirm scope, consent and the evidence available in system designs.\n2. **Short-term:** Complete the workflow steps and record outcomes against system performance ratio.\n3. **Medium-term:** Review results, close actions, and update local procedures in rooftops, solar farms and offices.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| system performance ratio | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |\n| installation times | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |\n| fault response | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |\n| customer savings reported | Agree a local target and track the trend | Measured from system designs and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: falls from roofs.\n- Never let this happen: electrical faults.\n- Never let this happen: underperforming systems unnoticed.\n- Work only within the competence and authority of a solar PV engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to rooftops, solar farms and offices's rules.\n- Verify names, dates, figures and measurements twice before anything is issued or signed off.\n- Use only real, verified information from the case in hand — never invent results, credentials or evidence.\n\n## Example (illustrative)\nA solar PV engineer in rooftops, solar farms and offices applies this workflow for homeowners, businesses and energy companies: they open\nsystem designs, work through the five steps using PV panels and inverters, and close by recording\nthe outcome against system performance ratio and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n",{"name":5,"license":15,"version":40,"category":41,"description":42},1,"Solar Energy","Diagnose and resolve common problems a solar PV engineer meets in rooftops, solar farms and offices.\nTRIGGERS - Use when a solar PV engineer needs a troubleshooting & problem solving for homeowners, businesses and energy companies in rooftops, solar farms and offices.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fsolar-energy-troubleshooting-guide",5,"https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection","https:\u002F\u002Fgithub.com\u002Flionelsimai","www.theaicapitol.com","Founder at The AI Capitol | I help founders turn AI into 10X revenue through systems, not tools. Ex-Apple • Ex-TikTok 👉 http:\u002F\u002Flionelsim.substack.com","2026-11-09 07:48:48",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill solar-energy-troubleshooting-guide",{"tool":58,"command":59},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill solar-energy-troubleshooting-guide",{"tool":61,"command":62},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill solar-energy-troubleshooting-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fsolar-energy-troubleshooting-guide\u002FSKILL.md",true,[],[67,81,94,107,124,138],{"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":35},"01M71E7TB5HAR0K6EXB80YXBT7","youth-work-troubleshooting-guide","Diagnose and resolve common problems a youth worker meets in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a troubleshooting & problem solving for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-troubleshooting-guide\u002FSKILL.md",[],[74,75,23,24,25,34,28,76,77,33,32,78,31,79,30,27,26,80],"youth work troubleshooting guide","work","outreach","settings","people","worker","communities",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":35},"01M71E7R3YHK4RAQVCRPB4CTXN","youth-work-tools-equipment-checklist","Select, check and maintain the tools and equipment a youth worker relies on.\nTRIGGERS - Use when a youth worker needs a tools & equipment checklist for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-tools-equipment-checklist\u002FSKILL.md",[],[88,75,89,90,32,78,31,91,79,30,92,28,80,93,76,77],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":35},"01M71E7NX1BMFEFBH01KCRJDEP","youth-work-supplies-procurement","Specify, source and manage the supplies and materials used in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a supplies & procurement for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-supplies-procurement\u002FSKILL.md",[],[101,102,75,103,104,76,77,78,31,79,30,105,106,28,80,32],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":118,"publishedAt":35},"01M71E7JVFP6P96GAT2VT9JY0D","youth-work-stakeholder-presentation","Present youth worker findings and proposals to decision-makers and stakeholders.\nTRIGGERS - Use when a youth worker needs a stakeholder presentation for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-stakeholder-presentation\u002FSKILL.md",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[119,75,120,121,28,122,80,30,123,76,77,32,78,31,79],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":35},"01M71E7GE5VA1RG4XEM2GAZRFY","youth-work-session-delivery","Prepare for and deliver a professional session or appointment for young people and their communities in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a session delivery guide for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-session-delivery\u002FSKILL.md",[],[131,132,133,75,134,77,25,135,76,32,78,31,79,30,28,136,137,80],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":35},"01M71E7DQSMY2ZW1BF3A1Z0VJM","youth-work-service-plan","Design a realistic, measurable service plan for young people and their communities as a youth worker.\nTRIGGERS - Use when a youth worker needs a service plan design for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-service-plan\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000015","视觉设计",[75,148,149,150,28,30,79,151,152,80,77,76,78,31,32],"service","plan","youth work service plan","design","as"]