[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M712MH5FNPHEBQWN9CT96XXH":3,"skill-same:01M712MH5FNPHEBQWN9CT96XXH":69},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M712MH5FNPHEBQWN9CT96XXH","hotel-management-incident-report",null,"Respond to, record and learn from incidents involving guests, hotel teams and owners in hotels and resorts.\nTRIGGERS - Use when a hotel manager needs a incident reporting & response for guests, hotel teams and owners in hotels and resorts.","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\u002Fhotel-management-incident-report\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"hotel management incident report","incident report","hotel","report","management","incident","manager","owners","reporting","record","learn","when","use","teams","triggers","incident reporting","incidents","respond","for","2026-11-10 10:12:30",false,"---\nname: hotel-management-incident-report\ndescription: |\n  Respond to, record and learn from incidents involving guests, hotel teams and owners in hotels and resorts.\n  TRIGGERS - Use when a hotel manager needs a incident reporting & response for guests, hotel teams and owners in hotels and resorts.\ncategory: Hotel Management\nlicense: MIT\nversion: 1.0\n---\n# Incident Reporting & Response — Hotel Management\n\nRespond to, record and learn from incidents involving guests, hotel teams and owners in hotels and resorts. The deliverable is a factual incident report and a lessons-learned action list.\nThis skill is written for a hotel manager working with guests, hotel teams and owners in hotels and resorts.\n\n## When to use\n- You are a hotel manager preparing, delivering or reviewing this part of your work in hotels and resorts.\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| RevPAR | revenue per available room, a core hotel performance measure |\n| Occupancy | the percentage of rooms sold |\n| Yield management | adjusting prices to maximise revenue from capacity |\n\n## Workflow\n1. **Step 1** - Make the situation safe first; attend to people before paperwork, and escalate if guest safety incidents is still live\n2. **Step 2** - Record facts while they are fresh: what happened, when, who was involved, what was observed — in occupancy reports\n3. **Step 3** - Notify the people and bodies who must know, within the timeframes that apply in hotels and resorts\n4. **Step 4** - Support those affected, including honest communication with guests, hotel teams and owners 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 Hotel Management |\n|-----------|-------------------------------|\n| Core documentation | occupancy reports; guest feedback; departmental budgets; incident logs |\n| Core tools & equipment | property management systems; booking engines; housekeeping software; point of sale systems |\n| People involved | guests, hotel teams and owners; the hotel manager; colleagues and other services in hotels and resorts |\n| Primary record | occupancy reports — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in hotels and resorts] | **Objective:** [What this must achieve] | **Audience:** [guests, hotel teams and owners 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 occupancy reports.\n2. **Short-term:** Complete the workflow steps and record outcomes against occupancy rate.\n3. **Medium-term:** Review results, close actions, and update local procedures in hotels and resorts.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| occupancy rate | Agree a local target and track the trend | Measured from occupancy reports and reviewed on a set cycle |\n| guest satisfaction scores | Agree a local target and track the trend | Measured from occupancy reports and reviewed on a set cycle |\n| revenue per available room | Agree a local target and track the trend | Measured from occupancy reports and reviewed on a set cycle |\n| complaint resolution times | Agree a local target and track the trend | Measured from occupancy reports and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: guest safety incidents.\n- Never let this happen: overbooking crises.\n- Never let this happen: data breaches on guest records.\n- Work only within the competence and authority of a hotel manager; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to hotels and resorts'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 hotel manager in hotels and resorts applies this workflow for guests, hotel teams and owners: they open\noccupancy reports, work through the five steps using property management systems, and close by recording\nthe outcome against occupancy rate and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Incident Reporting & Response — Hotel Management\n\nRespond to, record and learn from incidents involving guests, hotel teams and owners in hotels and resorts. The deliverable is a factual incident report and a lessons-learned action list.\nThis skill is written for a hotel manager working with guests, hotel teams and owners in hotels and resorts.\n\n## When to use\n- You are a hotel manager preparing, delivering or reviewing this part of your work in hotels and resorts.\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| RevPAR | revenue per available room, a core hotel performance measure |\n| Occupancy | the percentage of rooms sold |\n| Yield management | adjusting prices to maximise revenue from capacity |\n\n## Workflow\n1. **Step 1** - Make the situation safe first; attend to people before paperwork, and escalate if guest safety incidents is still live\n2. **Step 2** - Record facts while they are fresh: what happened, when, who was involved, what was observed — in occupancy reports\n3. **Step 3** - Notify the people and bodies who must know, within the timeframes that apply in hotels and resorts\n4. **Step 4** - Support those affected, including honest communication with guests, hotel teams and owners 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 Hotel Management |\n|-----------|-------------------------------|\n| Core documentation | occupancy reports; guest feedback; departmental budgets; incident logs |\n| Core tools & equipment | property management systems; booking engines; housekeeping software; point of sale systems |\n| People involved | guests, hotel teams and owners; the hotel manager; colleagues and other services in hotels and resorts |\n| Primary record | occupancy reports — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in hotels and resorts] | **Objective:** [What this must achieve] | **Audience:** [guests, hotel teams and owners 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 occupancy reports.\n2. **Short-term:** Complete the workflow steps and record outcomes against occupancy rate.\n3. **Medium-term:** Review results, close actions, and update local procedures in hotels and resorts.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| occupancy rate | Agree a local target and track the trend | Measured from occupancy reports and reviewed on a set cycle |\n| guest satisfaction scores | Agree a local target and track the trend | Measured from occupancy reports and reviewed on a set cycle |\n| revenue per available room | Agree a local target and track the trend | Measured from occupancy reports and reviewed on a set cycle |\n| complaint resolution times | Agree a local target and track the trend | Measured from occupancy reports and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: guest safety incidents.\n- Never let this happen: overbooking crises.\n- Never let this happen: data breaches on guest records.\n- Work only within the competence and authority of a hotel manager; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to hotels and resorts'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 hotel manager in hotels and resorts applies this workflow for guests, hotel teams and owners: they open\noccupancy reports, work through the five steps using property management systems, and close by recording\nthe outcome against occupancy rate 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":43,"category":44,"description":45},1,"Hotel Management","Respond to, record and learn from incidents involving guests, hotel teams and owners in hotels and resorts.\nTRIGGERS - Use when a hotel manager needs a incident reporting & response for guests, hotel teams and owners in hotels and resorts.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fhotel-management-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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill hotel-management-incident-report",{"tool":61,"command":62},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill hotel-management-incident-report",{"tool":64,"command":65},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill hotel-management-incident-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fhotel-management-incident-report\u002FSKILL.md",true,[],[70,91,104,117,134,148],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":38},"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",[],[77,78,79,80,81,82,37,83,84,85,30,86,31,87,33,88,89,90],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":38},"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",[],[98,78,99,100,30,86,31,101,87,33,102,37,90,103,83,84],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":38},"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",[],[111,112,78,113,114,83,84,86,31,87,33,115,116,37,90,30],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":128,"publishedAt":38},"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",[123],{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[129,78,130,131,37,132,90,33,133,83,84,30,86,31,87],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":38},"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",[],[141,142,143,78,144,84,81,145,83,30,86,31,87,33,37,146,147,90],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":157,"publishedAt":38},"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",[154],{"categoryNo":155,"categoryName":156,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000015","视觉设计",[78,158,159,160,37,33,87,161,162,90,84,83,86,31,30],"service","plan","youth work service plan","design","as"]