[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70WW56VQVJVWQRJSWNX0FSY":3,"skill-same:01M70WW56VQVJVWQRJSWNX0FSY":66},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M70WW56VQVJVWQRJSWNX0FSY","conservation-architecture-client-explanation",null,"Explain complex conservation architect matters to heritage bodies, owners of historic buildings and councils in plain, honest language.\nTRIGGERS - Use when a conservation architect needs a client explanation & communication guide for heritage bodies, owners of historic buildings and councils in historic buildings and design studios.","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\u002Fconservation-architecture-client-explanation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"conservation","architecture","client","conservation architecture client explanation","for","triggers","design","use","when","explain","communication","owners","plain","language","guide","architect","2026-11-10 10:12:30",false,"---\nname: conservation-architecture-client-explanation\ndescription: |\n  Explain complex conservation architect matters to heritage bodies, owners of historic buildings and councils in plain, honest language.\n  TRIGGERS - Use when a conservation architect needs a client explanation & communication guide for heritage bodies, owners of historic buildings and councils in historic buildings and design studios.\ncategory: Conservation Architecture\nlicense: MIT\nversion: 1.0\n---\n# Client Explanation & Communication Guide — Conservation Architecture\n\nExplain complex conservation architect matters to heritage bodies, owners of historic buildings and councils in plain, honest language. The deliverable is a communication pack: explanation script, FAQs and a written summary.\nThis skill is written for a conservation architect working with heritage bodies, owners of historic buildings and councils in historic buildings and design studios.\n\n## When to use\n- You are a conservation architect preparing, delivering or reviewing this part of your work in historic buildings and design studios.\n- You need a defensible, repeatable approach that produces a communication pack: explanation script, FAQs and a written summary.\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| Listed building | a building protected by law for its heritage value |\n| Fabric | the physical material of a historic building |\n| Reversibility | repairs that can be undone without harming original material |\n\n## Workflow\n1. **Step 1** - Identify what heritage bodies, owners of historic buildings and councils actually need to decide or understand, and the misconceptions to clear up first\n2. **Step 2** - Translate the technical content — including terms behind condition surveys — into plain language without losing accuracy\n3. **Step 3** - Structure the explanation: what we found, what it means, the options, the recommendation and the risks such as inappropriate repairs damaging fabric\n4. **Step 4** - Check understanding by asking heritage bodies, owners of historic buildings and councils to play it back in their own words; correct gaps kindly\n5. **Step 5** - Follow up with a written summary the same day and record the conversation in the file\n\n## Profession-Specific Components\n| Component | Details for Conservation Architecture |\n|-----------|-------------------------------|\n| Core documentation | condition surveys; conservation plans; specifications; grant applications |\n| Core tools & equipment | survey equipment; CAD software; material analysis; archives access |\n| People involved | heritage bodies, owners of historic buildings and councils; the conservation architect; colleagues and other services in historic buildings and design studios |\n| Primary record | condition surveys — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in historic buildings and design studios] | **Objective:** [What this must achieve] | **Audience:** [heritage bodies, owners of historic buildings and councils and other stakeholders]\n\nThe finished output is a communication pack: explanation script, FAQs and a written summary, 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 condition surveys.\n2. **Short-term:** Complete the workflow steps and record outcomes against survey turnaround.\n3. **Medium-term:** Review results, close actions, and update local procedures in historic buildings and design studios.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| survey turnaround | Agree a local target and track the trend | Measured from condition surveys and reviewed on a set cycle |\n| grant success rates | Agree a local target and track the trend | Measured from condition surveys and reviewed on a set cycle |\n| project outcomes | Agree a local target and track the trend | Measured from condition surveys and reviewed on a set cycle |\n| client satisfaction | Agree a local target and track the trend | Measured from condition surveys and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: inappropriate repairs damaging fabric.\n- Never let this happen: consent refusals.\n- Never let this happen: hidden defects.\n- Work only within the competence and authority of a conservation architect; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to historic buildings and design studios'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 conservation architect in historic buildings and design studios applies this workflow for heritage bodies, owners of historic buildings and councils: they open\ncondition surveys, work through the five steps using survey equipment, and close by recording\nthe outcome against survey turnaround and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Client Explanation & Communication Guide — Conservation Architecture\n\nExplain complex conservation architect matters to heritage bodies, owners of historic buildings and councils in plain, honest language. The deliverable is a communication pack: explanation script, FAQs and a written summary.\nThis skill is written for a conservation architect working with heritage bodies, owners of historic buildings and councils in historic buildings and design studios.\n\n## When to use\n- You are a conservation architect preparing, delivering or reviewing this part of your work in historic buildings and design studios.\n- You need a defensible, repeatable approach that produces a communication pack: explanation script, FAQs and a written summary.\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| Listed building | a building protected by law for its heritage value |\n| Fabric | the physical material of a historic building |\n| Reversibility | repairs that can be undone without harming original material |\n\n## Workflow\n1. **Step 1** - Identify what heritage bodies, owners of historic buildings and councils actually need to decide or understand, and the misconceptions to clear up first\n2. **Step 2** - Translate the technical content — including terms behind condition surveys — into plain language without losing accuracy\n3. **Step 3** - Structure the explanation: what we found, what it means, the options, the recommendation and the risks such as inappropriate repairs damaging fabric\n4. **Step 4** - Check understanding by asking heritage bodies, owners of historic buildings and councils to play it back in their own words; correct gaps kindly\n5. **Step 5** - Follow up with a written summary the same day and record the conversation in the file\n\n## Profession-Specific Components\n| Component | Details for Conservation Architecture |\n|-----------|-------------------------------|\n| Core documentation | condition surveys; conservation plans; specifications; grant applications |\n| Core tools & equipment | survey equipment; CAD software; material analysis; archives access |\n| People involved | heritage bodies, owners of historic buildings and councils; the conservation architect; colleagues and other services in historic buildings and design studios |\n| Primary record | condition surveys — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in historic buildings and design studios] | **Objective:** [What this must achieve] | **Audience:** [heritage bodies, owners of historic buildings and councils and other stakeholders]\n\nThe finished output is a communication pack: explanation script, FAQs and a written summary, 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 condition surveys.\n2. **Short-term:** Complete the workflow steps and record outcomes against survey turnaround.\n3. **Medium-term:** Review results, close actions, and update local procedures in historic buildings and design studios.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| survey turnaround | Agree a local target and track the trend | Measured from condition surveys and reviewed on a set cycle |\n| grant success rates | Agree a local target and track the trend | Measured from condition surveys and reviewed on a set cycle |\n| project outcomes | Agree a local target and track the trend | Measured from condition surveys and reviewed on a set cycle |\n| client satisfaction | Agree a local target and track the trend | Measured from condition surveys and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: inappropriate repairs damaging fabric.\n- Never let this happen: consent refusals.\n- Never let this happen: hidden defects.\n- Work only within the competence and authority of a conservation architect; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to historic buildings and design studios'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 conservation architect in historic buildings and design studios applies this workflow for heritage bodies, owners of historic buildings and councils: they open\ncondition surveys, work through the five steps using survey equipment, and close by recording\nthe outcome against survey turnaround 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":40,"category":41,"description":42},1,"Conservation Architecture","Explain complex conservation architect matters to heritage bodies, owners of historic buildings and councils in plain, honest language.\nTRIGGERS - Use when a conservation architect needs a client explanation & communication guide for heritage bodies, owners of historic buildings and councils in historic buildings and design studios.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fconservation-architecture-client-explanation",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill conservation-architecture-client-explanation",{"tool":58,"command":59},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill conservation-architecture-client-explanation",{"tool":61,"command":62},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill conservation-architecture-client-explanation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fconservation-architecture-client-explanation\u002FSKILL.md",true,[],[67,87,100,113,130,144],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":35},"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",[],[74,75,76,77,33,78,23,79,80,81,27,82,26,83,24,84,85,86],"youth work troubleshooting guide","work","troubleshooting","troubleshooting 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":35},"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,75,95,96,27,82,26,97,83,24,98,23,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":35},"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,75,109,110,79,80,82,26,83,24,111,112,23,86,27],"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":35},"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,75,126,127,23,128,86,24,129,79,80,27,82,26,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":35},"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,75,140,80,33,141,79,27,82,26,83,24,23,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":35},"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","视觉设计",[75,154,155,156,23,24,83,25,157,86,80,79,82,26,27],"service","plan","youth work service plan","as"]