[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718CE1SWWEH5HX7QDEQ4C0T":3,"skill-same:01M718CE1SWWEH5HX7QDEQ4C0T":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":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M718CE1SWWEH5HX7QDEQ4C0T","sox-testing",null,"Generate SOX sample selections, testing workpapers, and control assessments. Use when planning quarterly or annual SOX 404 testing, pulling a sample for a control (revenue, P2P, ITGC, close), building a testing workpaper template, or evaluating and classifying a control deficiency.","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35660,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Ffinance\u002Fskills\u002Fsox-testing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"testing","sox testing","sox","planning","for","use","when","sample","p2p","control","generate","revenue","template","close","2026-11-10 10:12:30",false,"---\nname: sox-testing\ndescription: Generate SOX sample selections, testing workpapers, and control assessments. Use when planning quarterly or annual SOX 404 testing, pulling a sample for a control (revenue, P2P, ITGC, close), building a testing workpaper template, or evaluating and classifying a control deficiency.\nargument-hint: \"\u003Ccontrol area> [period]\"\n---\n\n# SOX Compliance Testing\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\n**Important**: This command assists with SOX compliance workflows but does not provide audit or legal advice. All testing workpapers and assessments should be reviewed by qualified financial professionals before use in audit documentation.\n\nGenerate sample selections, create testing workpapers, document control assessments, and provide testing templates for SOX 404 internal controls over financial reporting.\n\n## Usage\n\n```\n\u002Fsox \u003Ccontrol-area> \u003Cperiod>\n```\n\n### Arguments\n\n- `control-area` — The control area to test:\n  - `revenue-recognition` — Revenue cycle controls (order-to-cash)\n  - `procure-to-pay` or `p2p` — Procurement and AP controls (purchase-to-pay)\n  - `payroll` — Payroll processing and compensation controls\n  - `financial-close` — Period-end close and reporting controls\n  - `treasury` — Cash management and treasury controls\n  - `fixed-assets` — Capital asset lifecycle controls\n  - `inventory` — Inventory valuation and management controls\n  - `itgc` — IT general controls (access, change management, operations)\n  - `entity-level` — Entity-level and monitoring controls\n  - `journal-entries` — Journal entry processing controls\n  - Any specific control ID or name\n- `period` — The testing period (e.g., `2024-Q4`, `2024`, `2024-H2`)\n\n## Workflow\n\n### 1. Identify Controls to Test\n\nBased on the control area, identify the key controls. Present the control matrix:\n\n| Control # | Control Description | Type | Frequency | Key\u002FNon-Key | Risk | Assertion |\n|-----------|-------------------|------|-----------|-------------|------|-----------|\n| [ID]      | [Description]     | Manual\u002FAutomated\u002FIT-Dependent | Daily\u002FWeekly\u002FMonthly\u002FQuarterly\u002FAnnual | Key | High\u002FMedium\u002FLow | [CEAVOP] |\n\n**Control types:**\n- **Automated:** System-enforced controls with no manual intervention\n- **Manual:** Controls performed by personnel with judgment\n- **IT-dependent manual:** Manual controls that rely on system-generated data\n\n**Assertions (CEAVOP):**\n- **C**ompleteness — All transactions are recorded\n- **E**xistence\u002FOccurrence — Transactions actually occurred\n- **A**ccuracy — Amounts are correctly recorded\n- **V**aluation — Assets\u002Fliabilities are properly valued\n- **O**bligations\u002FRights — Entity has rights to assets, obligations for liabilities\n- **P**resentation\u002FDisclosure — Properly classified and disclosed\n\n### 2. Determine Sample Size\n\nCalculate sample sizes based on control frequency and risk:\n\n| Control Frequency | Population Size (approx.) | Recommended Sample |\n|------------------|--------------------------|-------------------|\n| Annual           | 1                        | 1 (test the instance) |\n| Quarterly        | 4                        | 2 |\n| Monthly          | 12                       | 2-4 (based on risk) |\n| Weekly           | 52                       | 5-15 (based on risk) |\n| Daily            | ~250                     | 20-40 (based on risk) |\n| Per-transaction  | Varies                   | 25-60 (based on risk and volume) |\n\nAdjust for:\n- **Risk level:** Higher risk controls require larger samples\n- **Prior year results:** Controls with prior deficiencies need larger samples\n- **Reliance:** Controls relied upon by external auditors may need larger samples\n\n### 3. Generate Sample Selection\n\nSelect samples from the population using the appropriate method:\n\n**Random selection** (default for transaction-level controls):\n- Generate random numbers to select specific items from the population\n- Ensure coverage across the full period\n\n**Systematic selection** (for periodic controls):\n- Select items at fixed intervals with a random start point\n- Ensure representation across all sub-periods\n\n**Targeted selection** (supplement to random, for risk-based testing):\n- Select items with specific risk characteristics (high dollar, unusual, period-end)\n- Document rationale for targeted selections\n\nPresent the sample:\n\n```\nSAMPLE SELECTION\nControl: [Control ID] — [Description]\nPeriod: [Testing period]\nPopulation: [Count] items, $[Total value]\nSample size: [N] items\nSelection method: [Random\u002FSystematic\u002FTargeted]\n\n| Sample # | Transaction Date | Reference\u002FID | Amount | Selection Basis |\n|----------|-----------------|--------------|--------|-----------------|\n| 1        | [Date]          | [Ref]        | $X,XXX | Random          |\n| 2        | [Date]          | [Ref]        | $X,XXX | Random          |\n| ...      | ...             | ...          | ...    | ...             |\n```\n\n### 4. Create Testing Workpaper\n\nGenerate a testing template for each control:\n\n```\nSOX CONTROL TESTING WORKPAPER\n==============================\nControl #: [ID]\nControl Description: [Full description of the control activity]\nControl Owner: [Role\u002Ftitle — to be filled by tester]\nControl Type: [Manual\u002FAutomated\u002FIT-Dependent Manual]\nFrequency: [How often the control operates]\nKey Control: [Yes\u002FNo]\nRelevant Assertion(s): [CEAVOP]\nTesting Period: [Period]\n\nTEST OBJECTIVE:\nTo determine whether [control description] operated effectively throughout the testing period.\n\nTEST PROCEDURES:\n1. [Step 1 — What to inspect, examine, or re-perform]\n2. [Step 2 — What evidence to obtain]\n3. [Step 3 — What to compare or verify]\n4. [Step 4 — How to evaluate completeness of performance]\n5. [Step 5 — How to assess timeliness of performance]\n\nEXPECTED EVIDENCE:\n- [Document type 1 — e.g., signed approval form]\n- [Document type 2 — e.g., system screenshot showing review]\n- [Document type 3 — e.g., reconciliation with preparer sign-off]\n\nTEST RESULTS:\n\n| Sample # | Ref | Procedure 1 | Procedure 2 | Procedure 3 | Result | Exception? | Notes |\n|----------|-----|-------------|-------------|-------------|--------|------------|-------|\n| 1        |     | Pass\u002FFail   | Pass\u002FFail   | Pass\u002FFail   | Pass\u002FFail | Y\u002FN    |       |\n| 2        |     | Pass\u002FFail   | Pass\u002FFail   | Pass\u002FFail   | Pass\u002FFail | Y\u002FN    |       |\n\nEXCEPTIONS NOTED:\n| Sample # | Exception Description | Root Cause | Compensating Control | Impact |\n|----------|----------------------|------------|---------------------|--------|\n|          |                      |            |                     |        |\n\nCONCLUSION:\n[ ] Effective — Control operated effectively with no exceptions\n[ ] Effective with exceptions — Control operated effectively; exceptions are isolated\n[ ] Deficiency — Control did not operate effectively\n[ ] Significant Deficiency — Deficiency is more than inconsequential\n[ ] Material Weakness — Reasonable possibility of material misstatement not prevented\u002Fdetected\n\nTested by: ________________  Date: ________\nReviewed by: _______________  Date: ________\n```\n\n### 5. Provide Common Control Templates\n\nBased on the control area, provide pre-built test step templates:\n\n**Revenue Recognition:**\n- Verify sales order approval and authorization\n- Confirm delivery\u002Fperformance evidence\n- Test revenue recognition timing against contract terms\n- Verify pricing accuracy to contract\u002Fprice list\n- Test credit memo approval and validity\n\n**Procure to Pay:**\n- Verify purchase order approval and authorization limits\n- Confirm three-way match (PO, receipt, invoice)\n- Test vendor master data change controls\n- Verify payment approval and segregation of duties\n- Test duplicate payment prevention controls\n\n**Financial Close:**\n- Verify account reconciliation completeness and timeliness\n- Test journal entry approval and segregation of duties\n- Verify management review of financial statements\n- Test consolidation and elimination entries\n- Verify disclosure checklist completion\n\n**ITGC:**\n- Test user access provisioning and de-provisioning\n- Verify privileged access reviews\n- Test change management approval and testing\n- Verify batch job monitoring and exception handling\n- Test backup and recovery procedures\n\n### 6. Document Control Assessment\n\nClassify any identified deficiencies:\n\n**Deficiency:** A control does not allow management or employees to prevent or detect misstatements on a timely basis. Consider:\n- Likelihood of misstatement\n- Magnitude of potential misstatement\n- Whether compensating controls exist\n\n**Significant Deficiency:** A deficiency (or combination) that is less severe than a material weakness but important enough to merit attention by those responsible for oversight.\n\n**Material Weakness:** A deficiency (or combination) such that there is a reasonable possibility that a material misstatement will not be prevented or detected on a timely basis.\n\n### 7. Output\n\nProvide:\n1. Control matrix for the selected area\n2. Sample selections with methodology documentation\n3. Testing workpaper templates with pre-populated test steps\n4. Results documentation template\n5. Deficiency evaluation framework (if exceptions are identified)\n6. Suggested remediation actions for any noted deficiencies\n","# SOX Compliance Testing\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\n**Important**: This command assists with SOX compliance workflows but does not provide audit or legal advice. All testing workpapers and assessments should be reviewed by qualified financial professionals before use in audit documentation.\n\nGenerate sample selections, create testing workpapers, document control assessments, and provide testing templates for SOX 404 internal controls over financial reporting.\n\n## Usage\n\n```\n\u002Fsox \u003Ccontrol-area> \u003Cperiod>\n```\n\n### Arguments\n\n- `control-area` — The control area to test:\n  - `revenue-recognition` — Revenue cycle controls (order-to-cash)\n  - `procure-to-pay` or `p2p` — Procurement and AP controls (purchase-to-pay)\n  - `payroll` — Payroll processing and compensation controls\n  - `financial-close` — Period-end close and reporting controls\n  - `treasury` — Cash management and treasury controls\n  - `fixed-assets` — Capital asset lifecycle controls\n  - `inventory` — Inventory valuation and management controls\n  - `itgc` — IT general controls (access, change management, operations)\n  - `entity-level` — Entity-level and monitoring controls\n  - `journal-entries` — Journal entry processing controls\n  - Any specific control ID or name\n- `period` — The testing period (e.g., `2024-Q4`, `2024`, `2024-H2`)\n\n## Workflow\n\n### 1. Identify Controls to Test\n\nBased on the control area, identify the key controls. Present the control matrix:\n\n| Control # | Control Description | Type | Frequency | Key\u002FNon-Key | Risk | Assertion |\n|-----------|-------------------|------|-----------|-------------|------|-----------|\n| [ID]      | [Description]     | Manual\u002FAutomated\u002FIT-Dependent | Daily\u002FWeekly\u002FMonthly\u002FQuarterly\u002FAnnual | Key | High\u002FMedium\u002FLow | [CEAVOP] |\n\n**Control types:**\n- **Automated:** System-enforced controls with no manual intervention\n- **Manual:** Controls performed by personnel with judgment\n- **IT-dependent manual:** Manual controls that rely on system-generated data\n\n**Assertions (CEAVOP):**\n- **C**ompleteness — All transactions are recorded\n- **E**xistence\u002FOccurrence — Transactions actually occurred\n- **A**ccuracy — Amounts are correctly recorded\n- **V**aluation — Assets\u002Fliabilities are properly valued\n- **O**bligations\u002FRights — Entity has rights to assets, obligations for liabilities\n- **P**resentation\u002FDisclosure — Properly classified and disclosed\n\n### 2. Determine Sample Size\n\nCalculate sample sizes based on control frequency and risk:\n\n| Control Frequency | Population Size (approx.) | Recommended Sample |\n|------------------|--------------------------|-------------------|\n| Annual           | 1                        | 1 (test the instance) |\n| Quarterly        | 4                        | 2 |\n| Monthly          | 12                       | 2-4 (based on risk) |\n| Weekly           | 52                       | 5-15 (based on risk) |\n| Daily            | ~250                     | 20-40 (based on risk) |\n| Per-transaction  | Varies                   | 25-60 (based on risk and volume) |\n\nAdjust for:\n- **Risk level:** Higher risk controls require larger samples\n- **Prior year results:** Controls with prior deficiencies need larger samples\n- **Reliance:** Controls relied upon by external auditors may need larger samples\n\n### 3. Generate Sample Selection\n\nSelect samples from the population using the appropriate method:\n\n**Random selection** (default for transaction-level controls):\n- Generate random numbers to select specific items from the population\n- Ensure coverage across the full period\n\n**Systematic selection** (for periodic controls):\n- Select items at fixed intervals with a random start point\n- Ensure representation across all sub-periods\n\n**Targeted selection** (supplement to random, for risk-based testing):\n- Select items with specific risk characteristics (high dollar, unusual, period-end)\n- Document rationale for targeted selections\n\nPresent the sample:\n\n```\nSAMPLE SELECTION\nControl: [Control ID] — [Description]\nPeriod: [Testing period]\nPopulation: [Count] items, $[Total value]\nSample size: [N] items\nSelection method: [Random\u002FSystematic\u002FTargeted]\n\n| Sample # | Transaction Date | Reference\u002FID | Amount | Selection Basis |\n|----------|-----------------|--------------|--------|-----------------|\n| 1        | [Date]          | [Ref]        | $X,XXX | Random          |\n| 2        | [Date]          | [Ref]        | $X,XXX | Random          |\n| ...      | ...             | ...          | ...    | ...             |\n```\n\n### 4. Create Testing Workpaper\n\nGenerate a testing template for each control:\n\n```\nSOX CONTROL TESTING WORKPAPER\n==============================\nControl #: [ID]\nControl Description: [Full description of the control activity]\nControl Owner: [Role\u002Ftitle — to be filled by tester]\nControl Type: [Manual\u002FAutomated\u002FIT-Dependent Manual]\nFrequency: [How often the control operates]\nKey Control: [Yes\u002FNo]\nRelevant Assertion(s): [CEAVOP]\nTesting Period: [Period]\n\nTEST OBJECTIVE:\nTo determine whether [control description] operated effectively throughout the testing period.\n\nTEST PROCEDURES:\n1. [Step 1 — What to inspect, examine, or re-perform]\n2. [Step 2 — What evidence to obtain]\n3. [Step 3 — What to compare or verify]\n4. [Step 4 — How to evaluate completeness of performance]\n5. [Step 5 — How to assess timeliness of performance]\n\nEXPECTED EVIDENCE:\n- [Document type 1 — e.g., signed approval form]\n- [Document type 2 — e.g., system screenshot showing review]\n- [Document type 3 — e.g., reconciliation with preparer sign-off]\n\nTEST RESULTS:\n\n| Sample # | Ref | Procedure 1 | Procedure 2 | Procedure 3 | Result | Exception? | Notes |\n|----------|-----|-------------|-------------|-------------|--------|------------|-------|\n| 1        |     | Pass\u002FFail   | Pass\u002FFail   | Pass\u002FFail   | Pass\u002FFail | Y\u002FN    |       |\n| 2        |     | Pass\u002FFail   | Pass\u002FFail   | Pass\u002FFail   | Pass\u002FFail | Y\u002FN    |       |\n\nEXCEPTIONS NOTED:\n| Sample # | Exception Description | Root Cause | Compensating Control | Impact |\n|----------|----------------------|------------|---------------------|--------|\n|          |                      |            |                     |        |\n\nCONCLUSION:\n[ ] Effective — Control operated effectively with no exceptions\n[ ] Effective with exceptions — Control operated effectively; exceptions are isolated\n[ ] Deficiency — Control did not operate effectively\n[ ] Significant Deficiency — Deficiency is more than inconsequential\n[ ] Material Weakness — Reasonable possibility of material misstatement not prevented\u002Fdetected\n\nTested by: ________________  Date: ________\nReviewed by: _______________  Date: ________\n```\n\n### 5. Provide Common Control Templates\n\nBased on the control area, provide pre-built test step templates:\n\n**Revenue Recognition:**\n- Verify sales order approval and authorization\n- Confirm delivery\u002Fperformance evidence\n- Test revenue recognition timing against contract terms\n- Verify pricing accuracy to contract\u002Fprice list\n- Test credit memo approval and validity\n\n**Procure to Pay:**\n- Verify purchase order approval and authorization limits\n- Confirm three-way match (PO, receipt, invoice)\n- Test vendor master data change controls\n- Verify payment approval and segregation of duties\n- Test duplicate payment prevention controls\n\n**Financial Close:**\n- Verify account reconciliation completeness and timeliness\n- Test journal entry approval and segregation of duties\n- Verify management review of financial statements\n- Test consolidation and elimination entries\n- Verify disclosure checklist completion\n\n**ITGC:**\n- Test user access provisioning and de-provisioning\n- Verify privileged access reviews\n- Test change management approval and testing\n- Verify batch job monitoring and exception handling\n- Test backup and recovery procedures\n\n### 6. Document Control Assessment\n\nClassify any identified deficiencies:\n\n**Deficiency:** A control does not allow management or employees to prevent or detect misstatements on a timely basis. Consider:\n- Likelihood of misstatement\n- Magnitude of potential misstatement\n- Whether compensating controls exist\n\n**Significant Deficiency:** A deficiency (or combination) that is less severe than a material weakness but important enough to merit attention by those responsible for oversight.\n\n**Material Weakness:** A deficiency (or combination) such that there is a reasonable possibility that a material misstatement will not be prevented or detected on a timely basis.\n\n### 7. Output\n\nProvide:\n1. Control matrix for the selected area\n2. Sample selections with methodology documentation\n3. Testing workpaper templates with pre-populated test steps\n4. Results documentation template\n5. Deficiency evaluation framework (if exceptions are identified)\n6. Suggested remediation actions for any noted deficiencies\n",{"name":5,"description":7,"argument-hint":43},"\u003Ccontrol area> [period]","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","finance\u002Fskills\u002Fsox-testing",3944,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-14 06:21:52",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill sox-testing",{"tool":58,"command":59},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill sox-testing",{"tool":61,"command":62},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill sox-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Ffinance\u002Fskills\u002Fsox-testing\u002FSKILL.md",true,[],[67,93,118,140,169,195],{"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":38},"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",[],[74,75,76,77,78,79,80,30,81,82,83,84,85,86,87,88,89,90,91,92],"ticket","ticket deflector","mode","up","payments","open","writing","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past","read",{"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":38},"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",[],[100,101,102,103,104,105,106,107,108,109,30,110,111,112,113,114,92,115,116,117],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","run","request","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":38},"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,101,126,127,102,128,129,104,130,131,132,133,134,28,135,106,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":38},"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,30,165,166,83,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":38},"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,77,189,30,190,191,192,92,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":38},"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,28,135,206,79,207,109,139,208,209,210,211,212,190,213,87],"router","smb","smb router","do","front","single","you","vague","can","with","plugin","focus"]