[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718ESNJEBHV59TYTDBX8JW9":3,"skill-same:01M718ESNJEBHV59TYTDBX8JW9":67},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M718ESNJEBHV59TYTDBX8JW9","change-request",null,"Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35379,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Foperations\u002Fskills\u002Fchange-request\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"request","change request","change","with","communications","stakeholder communications","review","rollback plan","analysis","rollout","when","use","impact","change management","impact analysis","system","deployment","for","planning","risk","2026-11-10 10:12:30",false,"---\nname: change-request\ndescription: Create a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.\nargument-hint: \"\u003Cchange description>\"\n---\n\n# \u002Fchange-request\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nCreate a structured change request with impact analysis, risk assessment, and rollback plan.\n\n## Usage\n\n```\n\u002Fchange-request $ARGUMENTS\n```\n\n## Change Management Framework\n\nApply the assess-plan-execute-sustain framework when building the request:\n\n### 1. Assess\n- What is changing?\n- Who is affected?\n- How significant is the change? (Low \u002F Medium \u002F High)\n- What resistance should we expect?\n\n### 2. Plan\n- Communication plan (who, what, when, how)\n- Training plan (what skills are needed, how to deliver)\n- Support plan (help desk, champions, FAQs)\n- Timeline with milestones\n\n### 3. Execute\n- Announce and explain the \"why\"\n- Train and support\n- Monitor adoption\n- Address resistance\n\n### 4. Sustain\n- Measure adoption and effectiveness\n- Reinforce new behaviors\n- Address lingering issues\n- Document lessons learned\n\n## Communication Principles\n\n- Explain the **why** before the **what**\n- Communicate early and often\n- Use multiple channels\n- Acknowledge what's being lost, not just what's being gained\n- Provide a clear path for questions and concerns\n\n## Output\n\n```markdown\n## Change Request: [Title]\n**Requester:** [Name] | **Date:** [Date] | **Priority:** [Critical\u002FHigh\u002FMedium\u002FLow]\n**Status:** Draft | Pending Approval | Approved | In Progress | Complete\n\n### Description\n[What is changing and why]\n\n### Business Justification\n[Why this change is needed — cost savings, compliance, efficiency, risk reduction]\n\n### Impact Analysis\n| Area | Impact | Details |\n|------|--------|---------|\n| Users | [High\u002FMed\u002FLow\u002FNone] | [Who is affected and how] |\n| Systems | [High\u002FMed\u002FLow\u002FNone] | [What systems are affected] |\n| Processes | [High\u002FMed\u002FLow\u002FNone] | [What workflows change] |\n| Cost | [High\u002FMed\u002FLow\u002FNone] | [Budget impact] |\n\n### Risk Assessment\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| [Risk] | [H\u002FM\u002FL] | [H\u002FM\u002FL] | [How to mitigate] |\n\n### Implementation Plan\n| Step | Owner | Timeline | Dependencies |\n|------|-------|----------|--------------|\n| [Step] | [Person] | [Date] | [What it depends on] |\n\n### Communication Plan\n| Audience | Message | Channel | Timing |\n|----------|---------|---------|--------|\n| [Who] | [What to tell them] | [How] | [When] |\n\n### Rollback Plan\n[Step-by-step plan to reverse the change if needed]\n- Trigger: [When to roll back]\n- Steps: [How to roll back]\n- Verification: [How to confirm rollback worked]\n\n### Approvals Required\n| Approver | Role | Status |\n|----------|------|--------|\n| [Name] | [Role] | Pending |\n```\n\n## If Connectors Available\n\nIf **~~ITSM** is connected:\n- Create the change request ticket automatically\n- Pull change advisory board schedule and approval workflows\n\nIf **~~project tracker** is connected:\n- Link to related implementation tasks and dependencies\n- Track change progress against milestones\n\nIf **~~chat** is connected:\n- Draft stakeholder notifications for the communication plan\n- Post change updates to the relevant team channels\n\n## Tips\n\n1. **Be specific about impact** — \"Everyone\" is not an impact assessment. \"200 users in the billing team\" is.\n2. **Always have a rollback plan** — Even if you're confident, plan for failure.\n3. **Communicate early** — Surprises create resistance. Previews create buy-in.\n","# \u002Fchange-request\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nCreate a structured change request with impact analysis, risk assessment, and rollback plan.\n\n## Usage\n\n```\n\u002Fchange-request $ARGUMENTS\n```\n\n## Change Management Framework\n\nApply the assess-plan-execute-sustain framework when building the request:\n\n### 1. Assess\n- What is changing?\n- Who is affected?\n- How significant is the change? (Low \u002F Medium \u002F High)\n- What resistance should we expect?\n\n### 2. Plan\n- Communication plan (who, what, when, how)\n- Training plan (what skills are needed, how to deliver)\n- Support plan (help desk, champions, FAQs)\n- Timeline with milestones\n\n### 3. Execute\n- Announce and explain the \"why\"\n- Train and support\n- Monitor adoption\n- Address resistance\n\n### 4. Sustain\n- Measure adoption and effectiveness\n- Reinforce new behaviors\n- Address lingering issues\n- Document lessons learned\n\n## Communication Principles\n\n- Explain the **why** before the **what**\n- Communicate early and often\n- Use multiple channels\n- Acknowledge what's being lost, not just what's being gained\n- Provide a clear path for questions and concerns\n\n## Output\n\n```markdown\n## Change Request: [Title]\n**Requester:** [Name] | **Date:** [Date] | **Priority:** [Critical\u002FHigh\u002FMedium\u002FLow]\n**Status:** Draft | Pending Approval | Approved | In Progress | Complete\n\n### Description\n[What is changing and why]\n\n### Business Justification\n[Why this change is needed — cost savings, compliance, efficiency, risk reduction]\n\n### Impact Analysis\n| Area | Impact | Details |\n|------|--------|---------|\n| Users | [High\u002FMed\u002FLow\u002FNone] | [Who is affected and how] |\n| Systems | [High\u002FMed\u002FLow\u002FNone] | [What systems are affected] |\n| Processes | [High\u002FMed\u002FLow\u002FNone] | [What workflows change] |\n| Cost | [High\u002FMed\u002FLow\u002FNone] | [Budget impact] |\n\n### Risk Assessment\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| [Risk] | [H\u002FM\u002FL] | [H\u002FM\u002FL] | [How to mitigate] |\n\n### Implementation Plan\n| Step | Owner | Timeline | Dependencies |\n|------|-------|----------|--------------|\n| [Step] | [Person] | [Date] | [What it depends on] |\n\n### Communication Plan\n| Audience | Message | Channel | Timing |\n|----------|---------|---------|--------|\n| [Who] | [What to tell them] | [How] | [When] |\n\n### Rollback Plan\n[Step-by-step plan to reverse the change if needed]\n- Trigger: [When to roll back]\n- Steps: [How to roll back]\n- Verification: [How to confirm rollback worked]\n\n### Approvals Required\n| Approver | Role | Status |\n|----------|------|--------|\n| [Name] | [Role] | Pending |\n```\n\n## If Connectors Available\n\nIf **~~ITSM** is connected:\n- Create the change request ticket automatically\n- Pull change advisory board schedule and approval workflows\n\nIf **~~project tracker** is connected:\n- Link to related implementation tasks and dependencies\n- Track change progress against milestones\n\nIf **~~chat** is connected:\n- Draft stakeholder notifications for the communication plan\n- Post change updates to the relevant team channels\n\n## Tips\n\n1. **Be specific about impact** — \"Everyone\" is not an impact assessment. \"200 users in the billing team\" is.\n2. **Always have a rollback plan** — Even if you're confident, plan for failure.\n3. **Communicate early** — Surprises create resistance. Previews create buy-in.\n",{"name":5,"description":7,"argument-hint":44},"\u003Cchange description>","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","operations\u002Fskills\u002Fchange-request",3918,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-11 11:16:59",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill change-request",{"tool":59,"command":60},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill change-request",{"tool":62,"command":63},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill change-request","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Foperations\u002Fskills\u002Fchange-request\u002FSKILL.md",true,[],[68,94,118,140,169,195],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":39},"01M718Y97HCGW12Q53PSJDY03W","ticket-deflector","Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says \"draft a response,\" \"answer this customer,\" \"where's my order,\" \"I want a refund,\" \"check my orders,\" or \"anything about to blow up.\"","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fticket-deflector\u002FSKILL.md",[],[75,76,77,78,79,80,81,29,82,83,84,85,86,87,88,89,90,91,92,93],"ticket","ticket deflector","mode","up","payments","open","writing","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past","read",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":39},"01M718Y55HFAN5705ME5VEDZ9K","tax-season-organizer","Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags.\nAny tax request routes first to \u002Ftax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: \"books are closed, now do the 1099s,\" \"run the quarterly estimate off the closed numbers,\" or \"just the contractor W-9 list.\"","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Ftax-season-organizer\u002FSKILL.md",[],[101,102,103,104,105,106,107,108,109,110,29,111,112,113,114,19,93,115,116,117],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","run","flags","list","stripe",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":39},"01M718Y13VVPHDD9NTDBVFJ2AZ","tax-prep","Prepares tax materials as a two-link chain — month-end-prep confirms the books are closed and reconciled first, then tax-season-organizer calculates the quarterly estimated payment or builds the year-end 1099-NEC list and accountant packet from those closed numbers. Requires a ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); uses Gusto, PayPal, and Stripe when connected, else CSV upload. US federal tax math; a non-US business gets the closed-books packet. Prep material for a CPA, never tax advice, nothing filed. Trigger on \"quarterly taxes,\" \"estimated tax payment,\" \"how much should I set aside,\" \"1099s,\" \"1099-NEC,\" \"W-9s,\" \"year-end tax prep,\" \"get my books ready for my accountant,\" any phrasing that suggests a tax deadline is coming, or a question about net profit or YTD income that sounds like worry about a tax bill. An owner who says the period's books are already closed routes to tax-season-organizer directly.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Ftax-prep\u002FSKILL.md",[],[125,102,126,127,103,128,129,105,130,131,132,133,134,36,135,107,136,137,138,139],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","trigger","material","question","paypal","business",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":151,"publishedAt":39},"01M718XWTWQZ01GYSG9T8RW8TW","speed-to-lead","Makes sure no inbound lead goes unanswered. Watches web forms, the shared inbox, and the CRM for new inquiries, qualifies each one against the owner's criteria, drafts a reply in the owner's voice with real meeting times for the owner to approve and send, routes anything hot to a human right away, and logs the whole thing to the CRM. Never sends on its own. Built to run on a schedule so overnight inquiries are drafted and sorted by morning, and works from forwarded or pasted inquiries when no connector is available. Use this whenever the owner is worried about inbound leads or response time — including phrasings like \"leads are going cold,\" \"did anyone answer that inquiry,\" \"I keep missing form submissions,\" \"nothing falls through the cracks,\" \"handle my inbound,\" \"respond to this lead,\" or \"we lose people because nobody gets back fast enough.\" Reach for it for a single unanswered inquiry as readily as for a standing setup.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fspeed-to-lead\u002FSKILL.md",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[152,153,154,155,156,157,130,158,159,160,161,162,163,164,29,165,166,84,167,168],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":178,"publishedAt":39},"01M718XQYMN1KY3TPS33967FK0","social-content-engine","Runs the owner's content operation as a standing thing rather than a one-off: keeps a rolling posting calendar, learns the owner's voice, generates on-brand Canva graphics, writes captions that sound like them, repurposes one asset into every channel format, and stages posts for approval instead of publishing on its own. Pulls product photos and prices from Shopify when connected; with no connectors, drafts the calendar and asset briefs for manual posting. Use this whenever the owner talks about posting, content, or social — including \"I need to post more,\" \"we've gone quiet on Instagram,\" \"what should we post this month,\" \"make the content,\" \"give me a month of posts,\" \"write this in my voice,\" \"repurpose this,\" or \"set up our content calendar.\" Reach for it for a single post as readily as for a full quarter. One handoff: a finished, approved campaign brief goes to canva-creator; this skill owns the standing operation.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fsocial-content-engine\u002FSKILL.md",[175],{"categoryNo":176,"categoryName":177,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000036","内容创作者",[179,180,181,182,183,184,127,185,186,187,188,78,189,29,190,191,192,93,193,194],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","me","product","calendar","write","drafts",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":39},"01M718XMPJVH0EVRVP998BVZPC","smb-router","The front door to the Small Business plugin. Listens to what the owner needs right now — vague or specific — and routes them to the best skill or slash command for the moment. Also serves as a guide: explains what's available, suggests what to try next, and adapts recommendations based on stored business context. Trigger whenever the owner asks \"what can you do,\" \"help me with my business,\" \"what should I focus on,\" \"I don't know where to start,\" or any open-ended business request that doesn't clearly match a single skill.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fsmall-business\u002Fskills\u002Fsmb-router\u002FSKILL.md",[],[202,203,204,128,205,36,135,206,80,207,110,139,208,209,210,22,211,190,212,88],"router","smb","smb router","do","front","single","you","vague","can","plugin","focus"]