[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718CC1SZQ7PRBE8XFYCBEJA":3,"skill-same:01M718CC1SZQ7PRBE8XFYCBEJA":57},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M718CC1SZQ7PRBE8XFYCBEJA","reconciliation",null,"Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.","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\u002Freconciliation\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28],"reconciliations","balances","use","when","bank","party","reconcile","data","third-party","performing","2026-11-10 10:12:30",false,"---\nname: reconciliation\ndescription: Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.\nargument-hint: \"\u003Caccount> [period]\"\n---\n\n# Reconciliation\n\n**Important**: This skill assists with reconciliation workflows but does not provide financial advice. All reconciliations should be reviewed by qualified financial professionals before sign-off.\n\nMethodology and best practices for account reconciliation, including GL-to-subledger, bank reconciliations, and intercompany. Covers reconciling item categorization, aging analysis, and escalation.\n\n## Reconciliation Types\n\n### GL to Subledger Reconciliation\n\nCompare the general ledger control account balance to the detailed subledger balance.\n\n**Common accounts:**\n- Accounts receivable (GL control vs AR subledger aging)\n- Accounts payable (GL control vs AP subledger aging)\n- Fixed assets (GL control vs fixed asset register)\n- Inventory (GL control vs inventory valuation report)\n- Prepaid expenses (GL control vs prepaid amortization schedule)\n- Accrued liabilities (GL control vs accrual detail schedules)\n\n**Process:**\n1. Pull GL balance for the control account as of period end\n2. Pull subledger trial balance or detail report as of the same date\n3. Compare totals — they should match if posting is real-time\n4. Investigate any differences (timing of posting, manual entries not reflected, interface errors)\n\n**Common causes of differences:**\n- Manual journal entries posted to the control account but not reflected in the subledger\n- Subledger transactions not yet interfaced to the GL\n- Timing differences in batch posting\n- Reclassification entries in the GL without subledger adjustment\n- System interface errors or failed postings\n\n### Bank Reconciliation\n\nCompare the GL cash balance to the bank statement balance.\n\n**Process:**\n1. Obtain the bank statement balance as of period end\n2. Pull the GL cash account balance as of the same date\n3. Identify outstanding checks (issued but not cleared at the bank)\n4. Identify deposits in transit (recorded in GL but not yet credited by bank)\n5. Identify bank charges, interest, or adjustments not yet recorded in GL\n6. Reconcile both sides to an adjusted balance\n\n**Standard format:**\n\n```\nBalance per bank statement:         $XX,XXX\nAdd: Deposits in transit            $X,XXX\nLess: Outstanding checks           ($X,XXX)\nAdd\u002FLess: Bank errors               $X,XXX\nAdjusted bank balance:              $XX,XXX\n\nBalance per general ledger:         $XX,XXX\nAdd: Interest\u002Fcredits not recorded  $X,XXX\nLess: Bank fees not recorded       ($X,XXX)\nAdd\u002FLess: GL errors                 $X,XXX\nAdjusted GL balance:                $XX,XXX\n\nDifference:                         $0.00\n```\n\n### Intercompany Reconciliation\n\nReconcile balances between related entities to ensure they net to zero on consolidation.\n\n**Process:**\n1. Pull intercompany receivable\u002Fpayable balances for each entity pair\n2. Compare Entity A's receivable from Entity B to Entity B's payable to Entity A\n3. Identify and resolve differences\n4. Confirm all intercompany transactions have been recorded on both sides\n5. Verify elimination entries are correct for consolidation\n\n**Common causes of differences:**\n- Transactions recorded by one entity but not the other (timing)\n- Different FX rates used by each entity\n- Misclassification (intercompany vs third-party)\n- Disputed amounts or unapplied payments\n- Different period-end cut-off practices across entities\n\n## Reconciling Item Categorization\n\n### Category 1: Timing Differences\n\nItems that exist because of normal processing timing and will clear without action:\n\n- **Outstanding checks:** Checks issued and recorded in GL, pending bank clearance\n- **Deposits in transit:** Deposits made and recorded in GL, pending bank credit\n- **In-transit transactions:** Items posted in one system but pending interface to the other\n- **Pending approvals:** Transactions awaiting approval to post in one system\n\n**Expected resolution:** These items should clear within the normal processing cycle (typically 1-5 business days). No adjusting entry needed.\n\n### Category 2: Adjustments Required\n\nItems that require a journal entry to correct:\n\n- **Unrecorded bank charges:** Bank fees, wire charges, returned item fees\n- **Unrecorded interest:** Interest income or expense from bank\u002Flender\n- **Recording errors:** Wrong amount, wrong account, duplicates\n- **Missing entries:** Transactions in one system with no corresponding entry in the other\n- **Classification errors:** Correctly recorded but in the wrong account\n\n**Action:** Prepare adjusting journal entry to correct the GL or subledger.\n\n### Category 3: Requires Investigation\n\nItems that cannot be immediately explained:\n\n- **Unidentified differences:** Variances with no obvious cause\n- **Disputed items:** Amounts contested between parties\n- **Aged outstanding items:** Items that have not cleared within expected timeframes\n- **Recurring unexplained differences:** Same type of difference appearing each period\n\n**Action:** Investigate root cause, document findings, escalate if unresolved.\n\n## Aging Analysis for Outstanding Items\n\nTrack the age of reconciling items to identify stale items requiring escalation:\n\n| Age Bucket | Status | Action |\n|-----------|--------|--------|\n| 0-30 days | Current | Monitor — within normal processing cycle |\n| 31-60 days | Aging | Investigate — follow up on why item has not cleared |\n| 61-90 days | Overdue | Escalate — notify supervisor, document investigation |\n| 90+ days | Stale | Escalate to management — potential write-off or adjustment needed |\n\n### Aging Report Format\n\n| Item # | Description | Amount | Date Originated | Age (Days) | Category | Status | Owner |\n|--------|-------------|--------|-----------------|------------|----------|--------|-------|\n| 1      | [Detail]    | $X,XXX | [Date]          | XX         | [Type]   | [Status] | [Name] |\n\n### Trending\n\nTrack reconciling item totals over time to identify growing balances:\n\n- Compare total outstanding items to prior period\n- Flag if total reconciling items exceed materiality threshold\n- Flag if number of items is growing period over period\n- Identify recurring items that appear every period (may indicate process issue)\n\n## Escalation Thresholds\n\nDefine escalation triggers based on your organization's risk tolerance:\n\n| Trigger | Threshold (Example) | Escalation |\n|---------|---------------------|------------|\n| Individual item amount | > $10,000 | Supervisor review |\n| Individual item amount | > $50,000 | Controller review |\n| Total reconciling items | > $100,000 | Controller review |\n| Item age | > 60 days | Supervisor follow-up |\n| Item age | > 90 days | Controller \u002F management review |\n| Unreconciled difference | Any amount | Cannot close — must resolve or document |\n| Growing trend | 3+ consecutive periods | Process improvement investigation |\n\n*Note: Set thresholds based on your organization's materiality level and risk appetite. The examples above are illustrative.*\n\n## Reconciliation Best Practices\n\n1. **Timeliness:** Complete reconciliations within the close calendar deadline (typically T+3 to T+5 business days after period end)\n2. **Completeness:** Reconcile all balance sheet accounts on a defined frequency (monthly for material accounts, quarterly for immaterial)\n3. **Documentation:** Every reconciliation should include preparer, reviewer, date, and clear explanation of all reconciling items\n4. **Segregation:** The person who reconciles should not be the same person who processes transactions in that account\n5. **Follow-through:** Track open items to resolution — do not just carry items forward indefinitely\n6. **Root cause analysis:** For recurring reconciling items, investigate and fix the underlying process issue\n7. **Standardization:** Use consistent templates and procedures across all accounts\n8. **Retention:** Maintain reconciliations and supporting detail per your organization's document retention policy\n","# Reconciliation\n\n**Important**: This skill assists with reconciliation workflows but does not provide financial advice. All reconciliations should be reviewed by qualified financial professionals before sign-off.\n\nMethodology and best practices for account reconciliation, including GL-to-subledger, bank reconciliations, and intercompany. Covers reconciling item categorization, aging analysis, and escalation.\n\n## Reconciliation Types\n\n### GL to Subledger Reconciliation\n\nCompare the general ledger control account balance to the detailed subledger balance.\n\n**Common accounts:**\n- Accounts receivable (GL control vs AR subledger aging)\n- Accounts payable (GL control vs AP subledger aging)\n- Fixed assets (GL control vs fixed asset register)\n- Inventory (GL control vs inventory valuation report)\n- Prepaid expenses (GL control vs prepaid amortization schedule)\n- Accrued liabilities (GL control vs accrual detail schedules)\n\n**Process:**\n1. Pull GL balance for the control account as of period end\n2. Pull subledger trial balance or detail report as of the same date\n3. Compare totals — they should match if posting is real-time\n4. Investigate any differences (timing of posting, manual entries not reflected, interface errors)\n\n**Common causes of differences:**\n- Manual journal entries posted to the control account but not reflected in the subledger\n- Subledger transactions not yet interfaced to the GL\n- Timing differences in batch posting\n- Reclassification entries in the GL without subledger adjustment\n- System interface errors or failed postings\n\n### Bank Reconciliation\n\nCompare the GL cash balance to the bank statement balance.\n\n**Process:**\n1. Obtain the bank statement balance as of period end\n2. Pull the GL cash account balance as of the same date\n3. Identify outstanding checks (issued but not cleared at the bank)\n4. Identify deposits in transit (recorded in GL but not yet credited by bank)\n5. Identify bank charges, interest, or adjustments not yet recorded in GL\n6. Reconcile both sides to an adjusted balance\n\n**Standard format:**\n\n```\nBalance per bank statement:         $XX,XXX\nAdd: Deposits in transit            $X,XXX\nLess: Outstanding checks           ($X,XXX)\nAdd\u002FLess: Bank errors               $X,XXX\nAdjusted bank balance:              $XX,XXX\n\nBalance per general ledger:         $XX,XXX\nAdd: Interest\u002Fcredits not recorded  $X,XXX\nLess: Bank fees not recorded       ($X,XXX)\nAdd\u002FLess: GL errors                 $X,XXX\nAdjusted GL balance:                $XX,XXX\n\nDifference:                         $0.00\n```\n\n### Intercompany Reconciliation\n\nReconcile balances between related entities to ensure they net to zero on consolidation.\n\n**Process:**\n1. Pull intercompany receivable\u002Fpayable balances for each entity pair\n2. Compare Entity A's receivable from Entity B to Entity B's payable to Entity A\n3. Identify and resolve differences\n4. Confirm all intercompany transactions have been recorded on both sides\n5. Verify elimination entries are correct for consolidation\n\n**Common causes of differences:**\n- Transactions recorded by one entity but not the other (timing)\n- Different FX rates used by each entity\n- Misclassification (intercompany vs third-party)\n- Disputed amounts or unapplied payments\n- Different period-end cut-off practices across entities\n\n## Reconciling Item Categorization\n\n### Category 1: Timing Differences\n\nItems that exist because of normal processing timing and will clear without action:\n\n- **Outstanding checks:** Checks issued and recorded in GL, pending bank clearance\n- **Deposits in transit:** Deposits made and recorded in GL, pending bank credit\n- **In-transit transactions:** Items posted in one system but pending interface to the other\n- **Pending approvals:** Transactions awaiting approval to post in one system\n\n**Expected resolution:** These items should clear within the normal processing cycle (typically 1-5 business days). No adjusting entry needed.\n\n### Category 2: Adjustments Required\n\nItems that require a journal entry to correct:\n\n- **Unrecorded bank charges:** Bank fees, wire charges, returned item fees\n- **Unrecorded interest:** Interest income or expense from bank\u002Flender\n- **Recording errors:** Wrong amount, wrong account, duplicates\n- **Missing entries:** Transactions in one system with no corresponding entry in the other\n- **Classification errors:** Correctly recorded but in the wrong account\n\n**Action:** Prepare adjusting journal entry to correct the GL or subledger.\n\n### Category 3: Requires Investigation\n\nItems that cannot be immediately explained:\n\n- **Unidentified differences:** Variances with no obvious cause\n- **Disputed items:** Amounts contested between parties\n- **Aged outstanding items:** Items that have not cleared within expected timeframes\n- **Recurring unexplained differences:** Same type of difference appearing each period\n\n**Action:** Investigate root cause, document findings, escalate if unresolved.\n\n## Aging Analysis for Outstanding Items\n\nTrack the age of reconciling items to identify stale items requiring escalation:\n\n| Age Bucket | Status | Action |\n|-----------|--------|--------|\n| 0-30 days | Current | Monitor — within normal processing cycle |\n| 31-60 days | Aging | Investigate — follow up on why item has not cleared |\n| 61-90 days | Overdue | Escalate — notify supervisor, document investigation |\n| 90+ days | Stale | Escalate to management — potential write-off or adjustment needed |\n\n### Aging Report Format\n\n| Item # | Description | Amount | Date Originated | Age (Days) | Category | Status | Owner |\n|--------|-------------|--------|-----------------|------------|----------|--------|-------|\n| 1      | [Detail]    | $X,XXX | [Date]          | XX         | [Type]   | [Status] | [Name] |\n\n### Trending\n\nTrack reconciling item totals over time to identify growing balances:\n\n- Compare total outstanding items to prior period\n- Flag if total reconciling items exceed materiality threshold\n- Flag if number of items is growing period over period\n- Identify recurring items that appear every period (may indicate process issue)\n\n## Escalation Thresholds\n\nDefine escalation triggers based on your organization's risk tolerance:\n\n| Trigger | Threshold (Example) | Escalation |\n|---------|---------------------|------------|\n| Individual item amount | > $10,000 | Supervisor review |\n| Individual item amount | > $50,000 | Controller review |\n| Total reconciling items | > $100,000 | Controller review |\n| Item age | > 60 days | Supervisor follow-up |\n| Item age | > 90 days | Controller \u002F management review |\n| Unreconciled difference | Any amount | Cannot close — must resolve or document |\n| Growing trend | 3+ consecutive periods | Process improvement investigation |\n\n*Note: Set thresholds based on your organization's materiality level and risk appetite. The examples above are illustrative.*\n\n## Reconciliation Best Practices\n\n1. **Timeliness:** Complete reconciliations within the close calendar deadline (typically T+3 to T+5 business days after period end)\n2. **Completeness:** Reconcile all balance sheet accounts on a defined frequency (monthly for material accounts, quarterly for immaterial)\n3. **Documentation:** Every reconciliation should include preparer, reviewer, date, and clear explanation of all reconciling items\n4. **Segregation:** The person who reconciles should not be the same person who processes transactions in that account\n5. **Follow-through:** Track open items to resolution — do not just carry items forward indefinitely\n6. **Root cause analysis:** For recurring reconciling items, investigate and fix the underlying process issue\n7. **Standardization:** Use consistent templates and procedures across all accounts\n8. **Retention:** Maintain reconciliations and supporting detail per your organization's document retention policy\n",{"name":5,"description":7,"argument-hint":34},"\u003Caccount> [period]","main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","finance\u002Fskills\u002Freconciliation",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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill reconciliation",{"tool":49,"command":50},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill reconciliation",{"tool":52,"command":53},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill reconciliation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Ffinance\u002Fskills\u002Freconciliation\u002FSKILL.md",true,[],[58,84,109,132,161,187],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":29},"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",[],[65,66,67,68,69,70,71,22,72,73,74,75,76,77,78,79,80,81,82,83],"ticket","ticket deflector","mode","up","payments","open","writing","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past","read",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":29},"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",[],[91,92,93,94,95,96,97,98,99,100,22,101,102,103,104,105,83,106,107,108],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","run","request","flags","list","stripe",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":29},"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",[],[116,92,117,118,93,119,120,95,121,122,123,124,125,126,127,97,128,129,130,131],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","for","trigger","material","question","paypal","business",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":143,"publishedAt":29},"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",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[144,145,146,147,148,149,121,150,151,152,153,154,155,156,22,157,158,74,159,160],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":170,"publishedAt":29},"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",[167],{"categoryNo":168,"categoryName":169,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000036","内容创作者",[171,172,173,174,175,176,118,177,178,179,180,68,181,22,182,183,184,83,185,186],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","me","product","calendar","write","drafts",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":29},"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",[],[194,195,196,119,197,126,127,198,70,199,100,131,200,201,202,203,204,182,205,78],"router","smb","smb router","do","front","single","you","vague","can","with","plugin","focus"]