[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71BPPCCGEBC3AM58FYHTEBH":3,"skill-same:01M71BPPCCGEBC3AM58FYHTEBH":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},"01M71BPPCCGEBC3AM58FYHTEBH","structural-engineering-feedback-complaints",null,"Collect feedback from architects, builders and building owners and handle complaints fairly and visibly.\nTRIGGERS - Use when a structural engineer needs a feedback & complaints handling 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-feedback-complaints\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"feedback","structural","structural engineering","structural engineering feedback complaints","engineering","for","collect","engineer","triggers","sites","design","use","when","structural engineer","owners","2026-11-10 10:12:30",false,"---\nname: structural-engineering-feedback-complaints\ndescription: |\n  Collect feedback from architects, builders and building owners and handle complaints fairly and visibly.\n  TRIGGERS - Use when a structural engineer needs a feedback & complaints handling for architects, builders and building owners in design offices and construction sites.\ncategory: Structural Engineering\nlicense: MIT\nversion: 1.0\n---\n# Feedback & Complaints Handling — Structural Engineering\n\nCollect feedback from architects, builders and building owners and handle complaints fairly and visibly. The deliverable is a feedback and complaints process with response standards and learning log.\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 a feedback and complaints process with response standards and learning log.\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** - Invite feedback routinely — not only when things go wrong — and make it easy to give in design offices and construction sites\n2. **Step 2** - Acknowledge complaints quickly, thank the person, and explain the process and timeframe honestly\n3. **Step 3** - Investigate from evidence in structural calculations; separate the facts from the feelings, and respect both\n4. **Step 4** - Respond with findings, an apology where warranted, and concrete remedies or explanations\n5. **Step 5** - Log themes and feed them into quality work — repeated complaints about calculation errors are an early-warning system, not a nuisance\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 a feedback and complaints process with response standards and learning log, 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","# Feedback & Complaints Handling — Structural Engineering\n\nCollect feedback from architects, builders and building owners and handle complaints fairly and visibly. The deliverable is a feedback and complaints process with response standards and learning log.\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 a feedback and complaints process with response standards and learning log.\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** - Invite feedback routinely — not only when things go wrong — and make it easy to give in design offices and construction sites\n2. **Step 2** - Acknowledge complaints quickly, thank the person, and explain the process and timeframe honestly\n3. **Step 3** - Investigate from evidence in structural calculations; separate the facts from the feelings, and respect both\n4. **Step 4** - Respond with findings, an apology where warranted, and concrete remedies or explanations\n5. **Step 5** - Log themes and feed them into quality work — repeated complaints about calculation errors are an early-warning system, not a nuisance\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 a feedback and complaints process with response standards and learning log, 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":39,"category":40,"description":41},1,"Structural Engineering","Collect feedback from architects, builders and building owners and handle complaints fairly and visibly.\nTRIGGERS - Use when a structural engineer needs a feedback & complaints handling for architects, builders and building owners in design offices and construction sites.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fstructural-engineering-feedback-complaints",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 structural-engineering-feedback-complaints",{"tool":57,"command":58},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill structural-engineering-feedback-complaints",{"tool":60,"command":61},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill structural-engineering-feedback-complaints","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fstructural-engineering-feedback-complaints\u002FSKILL.md",true,[],[66,87,100,113,130,144],{"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,77,78,24,79,80,81,31,82,30,83,27,84,85,86],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[94,74,95,96,31,82,30,97,83,27,98,24,86,99,79,80],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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",[],[107,108,74,109,110,79,80,82,30,83,27,111,112,24,86,31],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":124,"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",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[125,74,126,127,24,128,86,27,129,79,80,31,82,30,83],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"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",[],[137,138,139,74,140,80,77,141,79,31,82,30,83,27,24,142,143,86],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":153,"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",[150],{"categoryNo":151,"categoryName":152,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000015","视觉设计",[74,154,155,156,24,27,83,29,157,86,80,79,82,30,31],"service","plan","youth work service plan","as"]