[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71BPGPP673WQC2PHTV77MXS":3,"skill-same:01M71BPGPP673WQC2PHTV77MXS":67},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M71BPGPP673WQC2PHTV77MXS","structural-engineering-emergency-procedure",null,"Respond to emergencies in design offices and construction sites calmly, in role and in the right order.\nTRIGGERS - Use when a structural engineer needs a emergency response procedure for architects, builders and building owners in design offices and construction sites.","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\u002Fstructural-engineering-emergency-procedure\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"structural engineering","structural engineering emergency procedure","engineering","structural","role","owners","structural engineer","order","calmly","when","use","design","sites","triggers","engineer","respond","for","2026-11-10 10:12:30",false,"---\nname: structural-engineering-emergency-procedure\ndescription: |\n  Respond to emergencies in design offices and construction sites calmly, in role and in the right order.\n  TRIGGERS - Use when a structural engineer needs a emergency response procedure for architects, builders and building owners in design offices and construction sites.\ncategory: Structural Engineering\nlicense: MIT\nversion: 1.0\n---\n# Emergency Response Procedure — Structural Engineering\n\nRespond to emergencies in design offices and construction sites calmly, in role and in the right order. The deliverable is an emergency procedure card: recognition, first actions, escalation and recording.\nThis skill is written for a structural engineer working with architects, builders and building owners in design offices and construction sites.\n\n## When to use\n- You are a structural engineer preparing, delivering or reviewing this part of your work in design offices and construction sites.\n- You need a defensible, repeatable approach that produces an emergency procedure card: recognition, first actions, escalation and recording.\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| Deflection | the bending or sagging of a structure under load |\n| Foundation | the part of a structure transferring loads to the ground |\n| Moment | a rotational force acting on a structure |\n\n## Workflow\n1. **Step 1** - Recognise the emergency early: know the presentations that matter for architects, builders and building owners, especially calculation errors\n2. **Step 2** - Take the immediate actions a structural engineer is trained and authorised for, using structural analysis software as drilled\n3. **Step 3** - Call for help with a structured message: location in design offices and construction sites, situation, what has been done, what is needed\n4. **Step 4** - Keep architects, builders and building owners and bystanders informed and safe while help arrives; hand over with a concise summary\n5. **Step 5** - Record the event fully in structural calculations afterwards, debrief the team, and update the procedure with lessons learned\n\n## Profession-Specific Components\n| Component | Details for Structural Engineering |\n|-----------|-------------------------------|\n| Core documentation | structural calculations; drawings; site reports; inspection reports |\n| Core tools & equipment | structural analysis software; CAD tools; testing equipment; survey tools |\n| People involved | architects, builders and building owners; the structural engineer; colleagues and other services in design offices and construction sites |\n| Primary record | structural calculations — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in design offices and construction sites] | **Objective:** [What this must achieve] | **Audience:** [architects, builders and building owners and other stakeholders]\n\nThe finished output is an emergency procedure card: recognition, first actions, escalation and recording, 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 structural calculations.\n2. **Short-term:** Complete the workflow steps and record outcomes against calculation check completion.\n3. **Medium-term:** Review results, close actions, and update local procedures in design offices and construction sites.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| calculation check completion | Agree a local target and track the trend | Measured from structural calculations and reviewed on a set cycle |\n| defects at inspection | Agree a local target and track the trend | Measured from structural calculations and reviewed on a set cycle |\n| design query turnaround | Agree a local target and track the trend | Measured from structural calculations and reviewed on a set cycle |\n| project delivery | Agree a local target and track the trend | Measured from structural calculations and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: calculation errors.\n- Never let this happen: construction deviations unnoticed.\n- Never let this happen: building movement.\n- Work only within the competence and authority of a structural engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to design offices and construction sites'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 structural engineer in design offices and construction sites applies this workflow for architects, builders and building owners: they open\nstructural calculations, work through the five steps using structural analysis software, and close by recording\nthe outcome against calculation check completion and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Emergency Response Procedure — Structural Engineering\n\nRespond to emergencies in design offices and construction sites calmly, in role and in the right order. The deliverable is an emergency procedure card: recognition, first actions, escalation and recording.\nThis skill is written for a structural engineer working with architects, builders and building owners in design offices and construction sites.\n\n## When to use\n- You are a structural engineer preparing, delivering or reviewing this part of your work in design offices and construction sites.\n- You need a defensible, repeatable approach that produces an emergency procedure card: recognition, first actions, escalation and recording.\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| Deflection | the bending or sagging of a structure under load |\n| Foundation | the part of a structure transferring loads to the ground |\n| Moment | a rotational force acting on a structure |\n\n## Workflow\n1. **Step 1** - Recognise the emergency early: know the presentations that matter for architects, builders and building owners, especially calculation errors\n2. **Step 2** - Take the immediate actions a structural engineer is trained and authorised for, using structural analysis software as drilled\n3. **Step 3** - Call for help with a structured message: location in design offices and construction sites, situation, what has been done, what is needed\n4. **Step 4** - Keep architects, builders and building owners and bystanders informed and safe while help arrives; hand over with a concise summary\n5. **Step 5** - Record the event fully in structural calculations afterwards, debrief the team, and update the procedure with lessons learned\n\n## Profession-Specific Components\n| Component | Details for Structural Engineering |\n|-----------|-------------------------------|\n| Core documentation | structural calculations; drawings; site reports; inspection reports |\n| Core tools & equipment | structural analysis software; CAD tools; testing equipment; survey tools |\n| People involved | architects, builders and building owners; the structural engineer; colleagues and other services in design offices and construction sites |\n| Primary record | structural calculations — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in design offices and construction sites] | **Objective:** [What this must achieve] | **Audience:** [architects, builders and building owners and other stakeholders]\n\nThe finished output is an emergency procedure card: recognition, first actions, escalation and recording, 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 structural calculations.\n2. **Short-term:** Complete the workflow steps and record outcomes against calculation check completion.\n3. **Medium-term:** Review results, close actions, and update local procedures in design offices and construction sites.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| calculation check completion | Agree a local target and track the trend | Measured from structural calculations and reviewed on a set cycle |\n| defects at inspection | Agree a local target and track the trend | Measured from structural calculations and reviewed on a set cycle |\n| design query turnaround | Agree a local target and track the trend | Measured from structural calculations and reviewed on a set cycle |\n| project delivery | Agree a local target and track the trend | Measured from structural calculations and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: calculation errors.\n- Never let this happen: construction deviations unnoticed.\n- Never let this happen: building movement.\n- Work only within the competence and authority of a structural engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to design offices and construction sites'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 structural engineer in design offices and construction sites applies this workflow for architects, builders and building owners: they open\nstructural calculations, work through the five steps using structural analysis software, and close by recording\nthe outcome against calculation check completion 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":41,"category":42,"description":43},1,"Structural Engineering","Respond to emergencies in design offices and construction sites calmly, in role and in the right order.\nTRIGGERS - Use when a structural engineer needs a emergency response procedure for architects, builders and building owners in design offices and construction sites.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fstructural-engineering-emergency-procedure",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill structural-engineering-emergency-procedure",{"tool":59,"command":60},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill structural-engineering-emergency-procedure",{"tool":62,"command":63},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill structural-engineering-emergency-procedure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fstructural-engineering-emergency-procedure\u002FSKILL.md",true,[],[68,89,102,115,132,146],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":36},"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",[],[75,76,77,78,79,80,35,81,82,83,28,84,29,85,32,86,87,88],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":36},"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",[],[96,76,97,98,28,84,29,99,85,32,100,35,88,101,81,82],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":36},"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",[],[109,110,76,111,112,81,82,84,29,85,32,113,114,35,88,28],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":126,"publishedAt":36},"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",[121],{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[127,76,128,129,35,130,88,32,131,81,82,28,84,29,85],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":36},"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",[],[139,140,141,76,142,82,79,143,81,28,84,29,85,32,35,144,145,88],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":36},"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",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000015","视觉设计",[76,156,157,158,35,32,85,30,159,88,82,81,84,29,28],"service","plan","youth work service plan","as"]