[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M715Z68C7KM85GGX23P7TH2T":3,"skill-same:01M715Z68C7KM85GGX23P7TH2T":65},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M715Z68C7KM85GGX23P7TH2T","oil-gas-operations-client-explanation",null,"Explain complex petroleum operations engineer matters to energy companies and regulators in plain, honest language.\nTRIGGERS - Use when a petroleum operations engineer needs a client explanation & communication guide for energy companies and regulators in offshore platforms and onshore terminals.","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\u002Foil-gas-operations-client-explanation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"gas","oil gas operations client explanation","operations","client","for","engineer","triggers","use","when","explain","energy","communication","plain","language","guide","2026-11-10 10:12:30",false,"---\nname: oil-gas-operations-client-explanation\ndescription: |\n  Explain complex petroleum operations engineer matters to energy companies and regulators in plain, honest language.\n  TRIGGERS - Use when a petroleum operations engineer needs a client explanation & communication guide for energy companies and regulators in offshore platforms and onshore terminals.\ncategory: Oil & Gas Operations\nlicense: MIT\nversion: 1.0\n---\n# Client Explanation & Communication Guide — Oil & Gas Operations\n\nExplain complex petroleum operations engineer matters to energy companies and regulators in plain, honest language. The deliverable is a communication pack: explanation script, FAQs and a written summary.\nThis skill is written for a petroleum operations engineer working with energy companies and regulators in offshore platforms and onshore terminals.\n\n## When to use\n- You are a petroleum operations engineer preparing, delivering or reviewing this part of your work in offshore platforms and onshore terminals.\n- You need a defensible, repeatable approach that produces a communication pack: explanation script, FAQs and a written summary.\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| Permit to work | a formal authorisation for hazardous work |\n| Well control | preventing uncontrolled flow from a well |\n| Shutdown | a planned or emergency stop of production |\n\n## Workflow\n1. **Step 1** - Identify what energy companies and regulators actually need to decide or understand, and the misconceptions to clear up first\n2. **Step 2** - Translate the technical content — including terms behind production reports — into plain language without losing accuracy\n3. **Step 3** - Structure the explanation: what we found, what it means, the options, the recommendation and the risks such as hydrocarbon releases\n4. **Step 4** - Check understanding by asking energy companies and regulators to play it back in their own words; correct gaps kindly\n5. **Step 5** - Follow up with a written summary the same day and record the conversation in the file\n\n## Profession-Specific Components\n| Component | Details for Oil & Gas Operations |\n|-----------|-------------------------------|\n| Core documentation | production reports; well records; maintenance logs; permit to work documents |\n| Core tools & equipment | drilling and production equipment; control systems; safety systems; inspection tools |\n| People involved | energy companies and regulators; the petroleum operations engineer; colleagues and other services in offshore platforms and onshore terminals |\n| Primary record | production reports — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in offshore platforms and onshore terminals] | **Objective:** [What this must achieve] | **Audience:** [energy companies and regulators and other stakeholders]\n\nThe finished output is a communication pack: explanation script, FAQs and a written summary, 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 production reports.\n2. **Short-term:** Complete the workflow steps and record outcomes against production rates.\n3. **Medium-term:** Review results, close actions, and update local procedures in offshore platforms and onshore terminals.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| production rates | Agree a local target and track the trend | Measured from production reports and reviewed on a set cycle |\n| shutdown performance | Agree a local target and track the trend | Measured from production reports and reviewed on a set cycle |\n| safety audits | Agree a local target and track the trend | Measured from production reports and reviewed on a set cycle |\n| maintenance backlog | Agree a local target and track the trend | Measured from production reports and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: hydrocarbon releases.\n- Never let this happen: well control incidents.\n- Never let this happen: permit breaches.\n- Work only within the competence and authority of a petroleum operations engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to offshore platforms and onshore terminals'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 petroleum operations engineer in offshore platforms and onshore terminals applies this workflow for energy companies and regulators: they open\nproduction reports, work through the five steps using drilling and production equipment, and close by recording\nthe outcome against production rates and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Client Explanation & Communication Guide — Oil & Gas Operations\n\nExplain complex petroleum operations engineer matters to energy companies and regulators in plain, honest language. The deliverable is a communication pack: explanation script, FAQs and a written summary.\nThis skill is written for a petroleum operations engineer working with energy companies and regulators in offshore platforms and onshore terminals.\n\n## When to use\n- You are a petroleum operations engineer preparing, delivering or reviewing this part of your work in offshore platforms and onshore terminals.\n- You need a defensible, repeatable approach that produces a communication pack: explanation script, FAQs and a written summary.\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| Permit to work | a formal authorisation for hazardous work |\n| Well control | preventing uncontrolled flow from a well |\n| Shutdown | a planned or emergency stop of production |\n\n## Workflow\n1. **Step 1** - Identify what energy companies and regulators actually need to decide or understand, and the misconceptions to clear up first\n2. **Step 2** - Translate the technical content — including terms behind production reports — into plain language without losing accuracy\n3. **Step 3** - Structure the explanation: what we found, what it means, the options, the recommendation and the risks such as hydrocarbon releases\n4. **Step 4** - Check understanding by asking energy companies and regulators to play it back in their own words; correct gaps kindly\n5. **Step 5** - Follow up with a written summary the same day and record the conversation in the file\n\n## Profession-Specific Components\n| Component | Details for Oil & Gas Operations |\n|-----------|-------------------------------|\n| Core documentation | production reports; well records; maintenance logs; permit to work documents |\n| Core tools & equipment | drilling and production equipment; control systems; safety systems; inspection tools |\n| People involved | energy companies and regulators; the petroleum operations engineer; colleagues and other services in offshore platforms and onshore terminals |\n| Primary record | production reports — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in offshore platforms and onshore terminals] | **Objective:** [What this must achieve] | **Audience:** [energy companies and regulators and other stakeholders]\n\nThe finished output is a communication pack: explanation script, FAQs and a written summary, 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 production reports.\n2. **Short-term:** Complete the workflow steps and record outcomes against production rates.\n3. **Medium-term:** Review results, close actions, and update local procedures in offshore platforms and onshore terminals.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| production rates | Agree a local target and track the trend | Measured from production reports and reviewed on a set cycle |\n| shutdown performance | Agree a local target and track the trend | Measured from production reports and reviewed on a set cycle |\n| safety audits | Agree a local target and track the trend | Measured from production reports and reviewed on a set cycle |\n| maintenance backlog | Agree a local target and track the trend | Measured from production reports and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: hydrocarbon releases.\n- Never let this happen: well control incidents.\n- Never let this happen: permit breaches.\n- Work only within the competence and authority of a petroleum operations engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to offshore platforms and onshore terminals'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 petroleum operations engineer in offshore platforms and onshore terminals applies this workflow for energy companies and regulators: they open\nproduction reports, work through the five steps using drilling and production equipment, and close by recording\nthe outcome against production rates 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":39,"category":40,"description":41},1,"Oil & Gas Operations","Explain complex petroleum operations engineer matters to energy companies and regulators in plain, honest language.\nTRIGGERS - Use when a petroleum operations engineer needs a client explanation & communication guide for energy companies and regulators in offshore platforms and onshore terminals.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Foil-gas-operations-client-explanation",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill oil-gas-operations-client-explanation",{"tool":57,"command":58},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill oil-gas-operations-client-explanation",{"tool":60,"command":61},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill oil-gas-operations-client-explanation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Foil-gas-operations-client-explanation\u002FSKILL.md",true,[],[66,86,99,112,129,143],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":34},"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",[],[73,74,75,76,33,77,23,78,79,80,27,81,26,82,25,83,84,85],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":34},"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",[],[93,74,94,95,27,81,26,96,82,25,97,23,85,98,78,79],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":100,"name":101,"nameZh":6,"description":102,"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":34},"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",[],[106,107,74,108,109,78,79,81,26,82,25,110,111,23,85,27],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":123,"publishedAt":34},"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",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[124,74,125,126,23,127,85,25,128,78,79,27,81,26,82],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":34},"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",[],[136,137,138,74,139,79,33,140,78,27,81,26,82,25,23,141,142,85],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":152,"publishedAt":34},"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",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000015","视觉设计",[74,153,154,155,23,25,82,156,157,85,79,78,81,26,27],"service","plan","youth work service plan","design","as"]