[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M713S45FFAD98WT4HXDP6755":3,"skill-same:01M713S45FFAD98WT4HXDP6755":70},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M713S45FFAD98WT4HXDP6755","landscape-architecture-incident-report",null,"Respond to, record and learn from incidents involving developers, councils and private clients in design studios and outdoor sites.\nTRIGGERS - Use when a landscape architect needs a incident reporting & response 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-incident-report\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"incident report","landscape","architecture","landscape architecture incident report","report","incident","architect","clients","reporting","record","learn","when","use","design","sites","triggers","incident reporting","incidents","respond","for","2026-11-10 10:12:30",false,"---\nname: landscape-architecture-incident-report\ndescription: |\n  Respond to, record and learn from incidents involving developers, councils and private clients in design studios and outdoor sites.\n  TRIGGERS - Use when a landscape architect needs a incident reporting & response for developers, councils and private clients in design studios and outdoor sites.\ncategory: Landscape Architecture\nlicense: MIT\nversion: 1.0\n---\n# Incident Reporting & Response — Landscape Architecture\n\nRespond to, record and learn from incidents involving developers, councils and private clients in design studios and outdoor sites. The deliverable is a factual incident report and a lessons-learned action list.\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 a factual incident report and a lessons-learned action list.\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** - Make the situation safe first; attend to people before paperwork, and escalate if planting failures is still live\n2. **Step 2** - Record facts while they are fresh: what happened, when, who was involved, what was observed — in design concepts\n3. **Step 3** - Notify the people and bodies who must know, within the timeframes that apply in design studios and outdoor sites\n4. **Step 4** - Support those affected, including honest communication with developers, councils and private clients about what happened and what happens next\n5. **Step 5** - Analyse causes without blame, agree preventive actions with owners and dates, and track them to closure\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 a factual incident report and a lessons-learned action list, 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","# Incident Reporting & Response — Landscape Architecture\n\nRespond to, record and learn from incidents involving developers, councils and private clients in design studios and outdoor sites. The deliverable is a factual incident report and a lessons-learned action list.\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 a factual incident report and a lessons-learned action list.\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** - Make the situation safe first; attend to people before paperwork, and escalate if planting failures is still live\n2. **Step 2** - Record facts while they are fresh: what happened, when, who was involved, what was observed — in design concepts\n3. **Step 3** - Notify the people and bodies who must know, within the timeframes that apply in design studios and outdoor sites\n4. **Step 4** - Support those affected, including honest communication with developers, councils and private clients about what happened and what happens next\n5. **Step 5** - Analyse causes without blame, agree preventive actions with owners and dates, and track them to closure\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 a factual incident report and a lessons-learned action list, 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":44,"category":45,"description":46},1,"Landscape Architecture","Respond to, record and learn from incidents involving developers, councils and private clients in design studios and outdoor sites.\nTRIGGERS - Use when a landscape architect needs a incident reporting & response for developers, councils and private clients in design studios and outdoor sites.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Flandscape-architecture-incident-report",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill landscape-architecture-incident-report",{"tool":62,"command":63},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill landscape-architecture-incident-report",{"tool":65,"command":66},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill landscape-architecture-incident-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Flandscape-architecture-incident-report\u002FSKILL.md",true,[],[71,79,86,93,100,107],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":78},"01M72JZQ95YCSXV9YDQGP0SRCW","commercial-piloting-troubleshooting-guide","Diagnose and resolve common problems a commercial pilot meets in cockpits and flight operations.\nTRIGGERS - Use when a commercial pilot needs a troubleshooting & problem solving for airlines, passengers and cargo customers in cockpits and flight operations.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fcommercial-piloting-troubleshooting-guide\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":78},"01M72JZMFHP0Y2FKSKEAT2Y97Y","commercial-piloting-tools-equipment-checklist","Select, check and maintain the tools and equipment a commercial pilot relies on.\nTRIGGERS - Use when a commercial pilot needs a tools & equipment checklist for airlines, passengers and cargo customers in cockpits and flight operations.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fcommercial-piloting-tools-equipment-checklist\u002FSKILL.md",[],[],{"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":78},"01M72JZHMXR147J9D2R9NPS45X","commercial-piloting-supplies-procurement","Specify, source and manage the supplies and materials used in cockpits and flight operations.\nTRIGGERS - Use when a commercial pilot needs a supplies & procurement for airlines, passengers and cargo customers in cockpits and flight operations.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fcommercial-piloting-supplies-procurement\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":78},"01M72JZE4K4EFXAPV2GJRMKXR8","commercial-piloting-stakeholder-presentation","Present commercial pilot findings and proposals to decision-makers and stakeholders.\nTRIGGERS - Use when a commercial pilot needs a stakeholder presentation for airlines, passengers and cargo customers in cockpits and flight operations.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fcommercial-piloting-stakeholder-presentation\u002FSKILL.md",[],[],{"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":78},"01M72JZB450H80C1X56C57XE9W","commercial-piloting-session-delivery","Prepare for and deliver a professional session or appointment for airlines, passengers and cargo customers in cockpits and flight operations.\nTRIGGERS - Use when a commercial pilot needs a session delivery guide for airlines, passengers and cargo customers in cockpits and flight operations.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fcommercial-piloting-session-delivery\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":78},"01M72JZ7NTHR2NDVGVWR33C05H","commercial-piloting-service-plan","Design a realistic, measurable service plan for airlines, passengers and cargo customers as a commercial pilot.\nTRIGGERS - Use when a commercial pilot needs a service plan design for airlines, passengers and cargo customers in cockpits and flight operations.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fcommercial-piloting-service-plan\u002FSKILL.md",[],[]]