[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M713RM3AGX0VFAM3BF0TSVBK":3,"skill-same:01M713RM3AGX0VFAM3BF0TSVBK":64},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M713RM3AGX0VFAM3BF0TSVBK","landscape-architecture-emergency-procedure",null,"Respond to emergencies in design studios and outdoor sites calmly, in role and in the right order.\nTRIGGERS - Use when a landscape architect needs a emergency response procedure for developers, councils and private clients in design studios and outdoor 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\u002Flandscape-architecture-emergency-procedure\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"landscape","architecture","landscape architecture emergency procedure","for","respond","triggers","sites","design","use","when","calmly","clients","role","architect","2026-11-10 10:12:30",false,"---\nname: landscape-architecture-emergency-procedure\ndescription: |\n  Respond to emergencies in design studios and outdoor sites calmly, in role and in the right order.\n  TRIGGERS - Use when a landscape architect needs a emergency response procedure for developers, councils and private clients in design studios and outdoor sites.\ncategory: Landscape Architecture\nlicense: MIT\nversion: 1.0\n---\n# Emergency Response Procedure — Landscape Architecture\n\nRespond to emergencies in design studios and outdoor 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 landscape architect working with developers, councils and private clients in design studios and outdoor sites.\n\n## When to use\n- You are a landscape architect preparing, delivering or reviewing this part of your work in design studios and outdoor 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| Planting plan | the layout and specification of plants for a site |\n| SuDS | sustainable drainage systems managing rainwater naturally |\n| Hard landscape | the built elements of a landscape, such as paving |\n\n## Workflow\n1. **Step 1** - Recognise the emergency early: know the presentations that matter for developers, councils and private clients, especially planting failures\n2. **Step 2** - Take the immediate actions a landscape architect is trained and authorised for, using CAD software as drilled\n3. **Step 3** - Call for help with a structured message: location in design studios and outdoor sites, situation, what has been done, what is needed\n4. **Step 4** - Keep developers, councils and private clients and bystanders informed and safe while help arrives; hand over with a concise summary\n5. **Step 5** - Record the event fully in design concepts afterwards, debrief the team, and update the procedure with lessons learned\n\n## Profession-Specific Components\n| Component | Details for Landscape Architecture |\n|-----------|-------------------------------|\n| Core documentation | design concepts; planting plans; site analyses; specifications |\n| Core tools & equipment | CAD software; GIS tools; site survey equipment; plant databases |\n| People involved | developers, councils and private clients; the landscape architect; colleagues and other services in design studios and outdoor sites |\n| Primary record | design concepts — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in design studios and outdoor sites] | **Objective:** [What this must achieve] | **Audience:** [developers, councils and private clients 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 design concepts.\n2. **Short-term:** Complete the workflow steps and record outcomes against design approval rates.\n3. **Medium-term:** Review results, close actions, and update local procedures in design studios and outdoor sites.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| design approval rates | Agree a local target and track the trend | Measured from design concepts and reviewed on a set cycle |\n| project delivery | Agree a local target and track the trend | Measured from design concepts and reviewed on a set cycle |\n| planting survival rates | Agree a local target and track the trend | Measured from design concepts and reviewed on a set cycle |\n| client satisfaction | Agree a local target and track the trend | Measured from design concepts and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: planting failures.\n- Never let this happen: drainage problems overlooked.\n- Never let this happen: inaccessible designs.\n- Work only within the competence and authority of a landscape architect; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to design studios and outdoor 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 landscape architect in design studios and outdoor sites applies this workflow for developers, councils and private clients: they open\ndesign concepts, work through the five steps using CAD software, and close by recording\nthe outcome against design approval rates and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Emergency Response Procedure — Landscape Architecture\n\nRespond to emergencies in design studios and outdoor 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 landscape architect working with developers, councils and private clients in design studios and outdoor sites.\n\n## When to use\n- You are a landscape architect preparing, delivering or reviewing this part of your work in design studios and outdoor 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| Planting plan | the layout and specification of plants for a site |\n| SuDS | sustainable drainage systems managing rainwater naturally |\n| Hard landscape | the built elements of a landscape, such as paving |\n\n## Workflow\n1. **Step 1** - Recognise the emergency early: know the presentations that matter for developers, councils and private clients, especially planting failures\n2. **Step 2** - Take the immediate actions a landscape architect is trained and authorised for, using CAD software as drilled\n3. **Step 3** - Call for help with a structured message: location in design studios and outdoor sites, situation, what has been done, what is needed\n4. **Step 4** - Keep developers, councils and private clients and bystanders informed and safe while help arrives; hand over with a concise summary\n5. **Step 5** - Record the event fully in design concepts afterwards, debrief the team, and update the procedure with lessons learned\n\n## Profession-Specific Components\n| Component | Details for Landscape Architecture |\n|-----------|-------------------------------|\n| Core documentation | design concepts; planting plans; site analyses; specifications |\n| Core tools & equipment | CAD software; GIS tools; site survey equipment; plant databases |\n| People involved | developers, councils and private clients; the landscape architect; colleagues and other services in design studios and outdoor sites |\n| Primary record | design concepts — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in design studios and outdoor sites] | **Objective:** [What this must achieve] | **Audience:** [developers, councils and private clients 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 design concepts.\n2. **Short-term:** Complete the workflow steps and record outcomes against design approval rates.\n3. **Medium-term:** Review results, close actions, and update local procedures in design studios and outdoor sites.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| design approval rates | Agree a local target and track the trend | Measured from design concepts and reviewed on a set cycle |\n| project delivery | Agree a local target and track the trend | Measured from design concepts and reviewed on a set cycle |\n| planting survival rates | Agree a local target and track the trend | Measured from design concepts and reviewed on a set cycle |\n| client satisfaction | Agree a local target and track the trend | Measured from design concepts and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: planting failures.\n- Never let this happen: drainage problems overlooked.\n- Never let this happen: inaccessible designs.\n- Work only within the competence and authority of a landscape architect; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to design studios and outdoor 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 landscape architect in design studios and outdoor sites applies this workflow for developers, councils and private clients: they open\ndesign concepts, work through the five steps using CAD software, and close by recording\nthe outcome against design approval 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":38,"category":39,"description":40},1,"Landscape Architecture","Respond to emergencies in design studios and outdoor sites calmly, in role and in the right order.\nTRIGGERS - Use when a landscape architect needs a emergency response procedure for developers, councils and private clients in design studios and outdoor sites.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Flandscape-architecture-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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill landscape-architecture-emergency-procedure",{"tool":56,"command":57},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill landscape-architecture-emergency-procedure",{"tool":59,"command":60},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill landscape-architecture-emergency-procedure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Flandscape-architecture-emergency-procedure\u002FSKILL.md",true,[],[65,86,99,112,129,143],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":33},"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",[],[72,73,74,75,76,77,22,78,79,80,28,81,27,82,24,83,84,85],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","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":33},"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,73,94,95,28,81,27,96,82,24,97,22,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":33},"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,73,108,109,78,79,81,27,82,24,110,111,22,85,28],"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":33},"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,73,125,126,22,127,85,24,128,78,79,28,81,27,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":33},"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,73,139,79,76,140,78,28,81,27,82,24,22,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":33},"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","视觉设计",[73,153,154,155,22,24,82,26,156,85,79,78,81,27,28],"service","plan","youth work service plan","as"]