[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7182F8PAC5SWB3B11JEWY0Y":3,"skill-same:01M7182F8PAC5SWB3B11JEWY0Y":69},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M7182F8PAC5SWB3B11JEWY0Y","port-operations-safety-protocol",null,"Work safely in ports and container terminals: a practical safety protocol for a port operations manager and shipping lines, hauliers and cargo owners.\nTRIGGERS - Use when a port operations manager needs a safety protocol for shipping lines, hauliers and cargo owners in ports and container 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\u002Fport-operations-safety-protocol\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"port","operations","port operations safety protocol","protocol","Safety","port operations","manager","owners","shipping","work","operations manager","when","use","container","triggers","cargo","for","practical","ports","2026-11-10 10:12:30",false,"---\nname: port-operations-safety-protocol\ndescription: |\n  Work safely in ports and container terminals: a practical safety protocol for a port operations manager and shipping lines, hauliers and cargo owners.\n  TRIGGERS - Use when a port operations manager needs a safety protocol for shipping lines, hauliers and cargo owners in ports and container terminals.\ncategory: Port Operations\nlicense: MIT\nversion: 1.0\n---\n# Safety Protocol — Port Operations\n\nWork safely in ports and container terminals: a practical safety protocol for a port operations manager and shipping lines, hauliers and cargo owners. The deliverable is a written safety protocol with checks, responsibilities and emergency actions.\nThis skill is written for a port operations manager working with shipping lines, hauliers and cargo owners in ports and container terminals.\n\n## When to use\n- You are a port operations manager preparing, delivering or reviewing this part of your work in ports and container terminals.\n- You need a defensible, repeatable approach that produces a written safety protocol with checks, responsibilities and emergency actions.\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| Berth | the place where a vessel moors to load or unload |\n| TEU | a standard unit equal to a twenty-foot container |\n| Turnaround | the time a vessel or truck spends in port |\n\n## Workflow\n1. **Step 1** - Identify the hazards present in ports and container terminals for staff, shipping lines, hauliers and cargo owners and visitors, starting with crane accidents\n2. **Step 2** - Write controls in order: eliminate, substitute, engineer, administrate, then protective equipment such as terminal operating systems\n3. **Step 3** - Set pre-start checks and stop-work authority — anyone can halt work that looks unsafe, without penalty\n4. **Step 4** - Define what happens when something goes wrong: first response, escalation, recording in berth plans\n5. **Step 5** - Review the protocol after every incident and at least annually; brief and re-brief everyone it covers\n\n## Profession-Specific Components\n| Component | Details for Port Operations |\n|-----------|-------------------------------|\n| Core documentation | berth plans; cargo manifests; equipment logs; incident reports |\n| Core tools & equipment | terminal operating systems; cranes; handling equipment; gate systems |\n| People involved | shipping lines, hauliers and cargo owners; the port operations manager; colleagues and other services in ports and container terminals |\n| Primary record | berth plans — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in ports and container terminals] | **Objective:** [What this must achieve] | **Audience:** [shipping lines, hauliers and cargo owners and other stakeholders]\n\nThe finished output is a written safety protocol with checks, responsibilities and emergency actions, 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 berth plans.\n2. **Short-term:** Complete the workflow steps and record outcomes against berth utilisation.\n3. **Medium-term:** Review results, close actions, and update local procedures in ports and container terminals.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| berth utilisation | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |\n| container turnaround | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |\n| crane productivity | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |\n| safety incident rates | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: crane accidents.\n- Never let this happen: cargo damage.\n- Never let this happen: berth congestion.\n- Work only within the competence and authority of a port operations manager; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to ports and container 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 port operations manager in ports and container terminals applies this workflow for shipping lines, hauliers and cargo owners: they open\nberth plans, work through the five steps using terminal operating systems, and close by recording\nthe outcome against berth utilisation and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Safety Protocol — Port Operations\n\nWork safely in ports and container terminals: a practical safety protocol for a port operations manager and shipping lines, hauliers and cargo owners. The deliverable is a written safety protocol with checks, responsibilities and emergency actions.\nThis skill is written for a port operations manager working with shipping lines, hauliers and cargo owners in ports and container terminals.\n\n## When to use\n- You are a port operations manager preparing, delivering or reviewing this part of your work in ports and container terminals.\n- You need a defensible, repeatable approach that produces a written safety protocol with checks, responsibilities and emergency actions.\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| Berth | the place where a vessel moors to load or unload |\n| TEU | a standard unit equal to a twenty-foot container |\n| Turnaround | the time a vessel or truck spends in port |\n\n## Workflow\n1. **Step 1** - Identify the hazards present in ports and container terminals for staff, shipping lines, hauliers and cargo owners and visitors, starting with crane accidents\n2. **Step 2** - Write controls in order: eliminate, substitute, engineer, administrate, then protective equipment such as terminal operating systems\n3. **Step 3** - Set pre-start checks and stop-work authority — anyone can halt work that looks unsafe, without penalty\n4. **Step 4** - Define what happens when something goes wrong: first response, escalation, recording in berth plans\n5. **Step 5** - Review the protocol after every incident and at least annually; brief and re-brief everyone it covers\n\n## Profession-Specific Components\n| Component | Details for Port Operations |\n|-----------|-------------------------------|\n| Core documentation | berth plans; cargo manifests; equipment logs; incident reports |\n| Core tools & equipment | terminal operating systems; cranes; handling equipment; gate systems |\n| People involved | shipping lines, hauliers and cargo owners; the port operations manager; colleagues and other services in ports and container terminals |\n| Primary record | berth plans — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in ports and container terminals] | **Objective:** [What this must achieve] | **Audience:** [shipping lines, hauliers and cargo owners and other stakeholders]\n\nThe finished output is a written safety protocol with checks, responsibilities and emergency actions, 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 berth plans.\n2. **Short-term:** Complete the workflow steps and record outcomes against berth utilisation.\n3. **Medium-term:** Review results, close actions, and update local procedures in ports and container terminals.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| berth utilisation | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |\n| container turnaround | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |\n| crane productivity | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |\n| safety incident rates | Agree a local target and track the trend | Measured from berth plans and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: crane accidents.\n- Never let this happen: cargo damage.\n- Never let this happen: berth congestion.\n- Work only within the competence and authority of a port operations manager; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to ports and container 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 port operations manager in ports and container terminals applies this workflow for shipping lines, hauliers and cargo owners: they open\nberth plans, work through the five steps using terminal operating systems, and close by recording\nthe outcome against berth utilisation 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":43,"category":44,"description":45},1,"Port Operations","Work safely in ports and container terminals: a practical safety protocol for a port operations manager and shipping lines, hauliers and cargo owners.\nTRIGGERS - Use when a port operations manager needs a safety protocol for shipping lines, hauliers and cargo owners in ports and container terminals.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fport-operations-safety-protocol",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill port-operations-safety-protocol",{"tool":61,"command":62},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill port-operations-safety-protocol",{"tool":64,"command":65},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill port-operations-safety-protocol","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fport-operations-safety-protocol\u002FSKILL.md",true,[],[70,90,103,116,133,147],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":38},"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",[],[77,28,78,79,80,81,35,82,83,84,30,85,31,86,33,87,88,89],"youth work troubleshooting guide","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":38},"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",[],[97,28,98,99,30,85,31,100,86,33,101,35,89,102,82,83],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":38},"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",[],[110,111,28,112,113,82,83,85,31,86,33,114,115,35,89,30],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":127,"publishedAt":38},"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",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[128,28,129,130,35,131,89,33,132,82,83,30,85,31,86],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":38},"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",[],[140,141,142,28,143,83,80,144,82,30,85,31,86,33,35,145,146,89],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":156,"publishedAt":38},"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",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000015","视觉设计",[28,157,158,159,35,33,86,160,161,89,83,82,85,31,30],"service","plan","youth work service plan","design","as"]