[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718NM9AQX4SDSPCSV74WASY":3,"skill-same:01M718NM9AQX4SDSPCSV74WASY":65},{"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":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M718NM9AQX4SDSPCSV74WASY","start",null,"Initialize the productivity system and open the dashboard. Use when setting up the plugin for the first time, bootstrapping working memory from your existing task list, or decoding the shorthand (nicknames, acronyms, project codenames) you use in your todos.","anthropics\u002Fknowledge-work-plugins","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7188MPC48111TN566QNQE3X",35463,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fproductivity\u002Fskills\u002Fstart\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"Existing","first","dashboard","productivity","plugin","task list","productivity system","task","you","when","use","open","up","system","time","project","for","memory","initialize","2026-11-10 10:12:30",false,"---\nname: start\ndescription: Initialize the productivity system and open the dashboard. Use when setting up the plugin for the first time, bootstrapping working memory from your existing task list, or decoding the shorthand (nicknames, acronyms, project codenames) you use in your todos.\n---\n\n# Start Command\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nInitialize the task and memory systems, then open the unified dashboard.\n\n## Instructions\n\n### 1. Check What Exists\n\nCheck the working directory for:\n- `TASKS.md` — task list\n- `CLAUDE.md` — working memory\n- `memory\u002F` — deep memory directory\n- `dashboard.html` — the visual UI\n\n### 2. Create What's Missing\n\n**If `TASKS.md` doesn't exist:** Create it with the standard template (see task-management skill). Place it in the current working directory.\n\n**If `dashboard.html` doesn't exist:** Copy it from `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fdashboard.html` to the current working directory.\n\n**If `CLAUDE.md` and `memory\u002F` don't exist:** This is a fresh setup — after opening the dashboard, begin the memory bootstrap workflow (see below). Place these in the current working directory.\n\n### 3. Open the Dashboard\n\nDo NOT use `open` or `xdg-open` — in Cowork, the agent runs in a VM and shell open commands won't reach the user's browser. Instead, tell the user: \"Dashboard is ready at `dashboard.html`. Open it from your file browser to get started.\"\n\n### 4. Orient the User\n\nIf everything was already initialized:\n```\nDashboard open. Your tasks and memory are both loaded.\n- \u002Fproductivity:update to sync tasks and check memory\n- \u002Fproductivity:update --comprehensive for a deep scan of all activity\n```\n\nIf memory hasn't been bootstrapped yet, continue to step 5.\n\n### 5. Bootstrap Memory (First Run Only)\n\nOnly do this if `CLAUDE.md` and `memory\u002F` don't exist yet.\n\nThe best source of workplace language is the user's actual task list. Real tasks = real shorthand.\n\n**Ask the user:**\n```\nWhere do you keep your todos or task list? This could be:\n- A local file (e.g., TASKS.md, todo.txt)\n- An app (e.g. Asana, Linear, Jira, Notion, Todoist)\n- A notes file\n\nI'll use your tasks to learn your workplace shorthand.\n```\n\n**Once you have access to the task list:**\n\nFor each task item, analyze it for potential shorthand:\n- Names that might be nicknames\n- Acronyms or abbreviations\n- Project references or codenames\n- Internal terms or jargon\n\n**For each item, decode it interactively:**\n\n```\nTask: \"Send PSR to Todd re: Phoenix blockers\"\n\nI see some terms I want to make sure I understand:\n\n1. **PSR** - What does this stand for?\n2. **Todd** - Who is Todd? (full name, role)\n3. **Phoenix** - Is this a project codename? What's it about?\n```\n\nContinue through each task, asking only about terms you haven't already decoded.\n\n### 6. Optional Comprehensive Scan\n\nAfter task list decoding, offer:\n```\nDo you want me to do a comprehensive scan of your messages, emails, and documents?\nThis takes longer but builds much richer context about the people, projects, and terms in your work.\n\nOr we can stick with what we have and add context later.\n```\n\n**If they choose comprehensive scan:**\n\nGather data from available MCP sources:\n- **Chat:** Recent messages, channels, DMs\n- **Email:** Sent messages, recipients\n- **Documents:** Recent docs, collaborators\n- **Calendar:** Meetings, attendees\n\nBuild a braindump of people, projects, and terms found. Present findings grouped by confidence:\n- **Ready to add** (high confidence) — offer to add directly\n- **Needs clarification** — ask the user\n- **Low frequency \u002F unclear** — note for later\n\n### 7. Write Memory Files\n\nFrom everything gathered, create:\n\n**CLAUDE.md** (working memory, ~50-80 lines):\n```markdown\n# Memory\n\n## Me\n[Name], [Role] on [Team].\n\n## People\n| Who | Role |\n|-----|------|\n| **[Nickname]** | [Full Name], [role] |\n\n## Terms\n| Term | Meaning |\n|------|---------|\n| [acronym] | [expansion] |\n\n## Projects\n| Name | What |\n|------|------|\n| **[Codename]** | [description] |\n\n## Preferences\n- [preferences discovered]\n```\n\n**memory\u002F** directory:\n- `memory\u002Fglossary.md` — full decoder ring (acronyms, terms, nicknames, codenames)\n- `memory\u002Fpeople\u002F{name}.md` — individual profiles\n- `memory\u002Fprojects\u002F{name}.md` — project details\n- `memory\u002Fcontext\u002Fcompany.md` — teams, tools, processes\n\n### 8. Report Results\n\n```\nProductivity system ready:\n- Tasks: TASKS.md (X items)\n- Memory: X people, X terms, X projects\n- Dashboard: open in browser\n\nUse \u002Fproductivity:update to keep things current (add --comprehensive for a deep scan).\n```\n\n## Notes\n\n- If memory is already initialized, this just opens the dashboard\n- Nicknames are critical — always capture how people are actually referred to\n- If a source isn't available, skip it and note the gap\n- Memory grows organically through natural conversation after bootstrap\n","# Start Command\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nInitialize the task and memory systems, then open the unified dashboard.\n\n## Instructions\n\n### 1. Check What Exists\n\nCheck the working directory for:\n- `TASKS.md` — task list\n- `CLAUDE.md` — working memory\n- `memory\u002F` — deep memory directory\n- `dashboard.html` — the visual UI\n\n### 2. Create What's Missing\n\n**If `TASKS.md` doesn't exist:** Create it with the standard template (see task-management skill). Place it in the current working directory.\n\n**If `dashboard.html` doesn't exist:** Copy it from `${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Fdashboard.html` to the current working directory.\n\n**If `CLAUDE.md` and `memory\u002F` don't exist:** This is a fresh setup — after opening the dashboard, begin the memory bootstrap workflow (see below). Place these in the current working directory.\n\n### 3. Open the Dashboard\n\nDo NOT use `open` or `xdg-open` — in Cowork, the agent runs in a VM and shell open commands won't reach the user's browser. Instead, tell the user: \"Dashboard is ready at `dashboard.html`. Open it from your file browser to get started.\"\n\n### 4. Orient the User\n\nIf everything was already initialized:\n```\nDashboard open. Your tasks and memory are both loaded.\n- \u002Fproductivity:update to sync tasks and check memory\n- \u002Fproductivity:update --comprehensive for a deep scan of all activity\n```\n\nIf memory hasn't been bootstrapped yet, continue to step 5.\n\n### 5. Bootstrap Memory (First Run Only)\n\nOnly do this if `CLAUDE.md` and `memory\u002F` don't exist yet.\n\nThe best source of workplace language is the user's actual task list. Real tasks = real shorthand.\n\n**Ask the user:**\n```\nWhere do you keep your todos or task list? This could be:\n- A local file (e.g., TASKS.md, todo.txt)\n- An app (e.g. Asana, Linear, Jira, Notion, Todoist)\n- A notes file\n\nI'll use your tasks to learn your workplace shorthand.\n```\n\n**Once you have access to the task list:**\n\nFor each task item, analyze it for potential shorthand:\n- Names that might be nicknames\n- Acronyms or abbreviations\n- Project references or codenames\n- Internal terms or jargon\n\n**For each item, decode it interactively:**\n\n```\nTask: \"Send PSR to Todd re: Phoenix blockers\"\n\nI see some terms I want to make sure I understand:\n\n1. **PSR** - What does this stand for?\n2. **Todd** - Who is Todd? (full name, role)\n3. **Phoenix** - Is this a project codename? What's it about?\n```\n\nContinue through each task, asking only about terms you haven't already decoded.\n\n### 6. Optional Comprehensive Scan\n\nAfter task list decoding, offer:\n```\nDo you want me to do a comprehensive scan of your messages, emails, and documents?\nThis takes longer but builds much richer context about the people, projects, and terms in your work.\n\nOr we can stick with what we have and add context later.\n```\n\n**If they choose comprehensive scan:**\n\nGather data from available MCP sources:\n- **Chat:** Recent messages, channels, DMs\n- **Email:** Sent messages, recipients\n- **Documents:** Recent docs, collaborators\n- **Calendar:** Meetings, attendees\n\nBuild a braindump of people, projects, and terms found. Present findings grouped by confidence:\n- **Ready to add** (high confidence) — offer to add directly\n- **Needs clarification** — ask the user\n- **Low frequency \u002F unclear** — note for later\n\n### 7. Write Memory Files\n\nFrom everything gathered, create:\n\n**CLAUDE.md** (working memory, ~50-80 lines):\n```markdown\n# Memory\n\n## Me\n[Name], [Role] on [Team].\n\n## People\n| Who | Role |\n|-----|------|\n| **[Nickname]** | [Full Name], [role] |\n\n## Terms\n| Term | Meaning |\n|------|---------|\n| [acronym] | [expansion] |\n\n## Projects\n| Name | What |\n|------|------|\n| **[Codename]** | [description] |\n\n## Preferences\n- [preferences discovered]\n```\n\n**memory\u002F** directory:\n- `memory\u002Fglossary.md` — full decoder ring (acronyms, terms, nicknames, codenames)\n- `memory\u002Fpeople\u002F{name}.md` — individual profiles\n- `memory\u002Fprojects\u002F{name}.md` — project details\n- `memory\u002Fcontext\u002Fcompany.md` — teams, tools, processes\n\n### 8. Report Results\n\n```\nProductivity system ready:\n- Tasks: TASKS.md (X items)\n- Memory: X people, X terms, X projects\n- Dashboard: open in browser\n\nUse \u002Fproductivity:update to keep things current (add --comprehensive for a deep scan).\n```\n\n## Notes\n\n- If memory is already initialized, this just opens the dashboard\n- Nicknames are critical — always capture how people are actually referred to\n- If a source isn't available, skip it and note the gap\n- Memory grows organically through natural conversation after bootstrap\n",{"name":5,"description":7},"main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","productivity\u002Fskills\u002Fstart",3926,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-11 15:25:16",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill start",{"tool":57,"command":58},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill start",{"tool":60,"command":61},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill start","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fproductivity\u002Fskills\u002Fstart\u002FSKILL.md",true,[],[66,90,115,137,165,191],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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",[],[73,74,75,31,76,30,77,28,78,79,80,81,82,83,84,85,86,87,88,89],"ticket","ticket deflector","mode","payments","writing","workflow","ask","Connector","text","mail","window","next","customer","support","crm","past","read",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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",[],[97,98,99,100,101,102,103,104,105,106,28,107,108,109,110,111,89,112,113,114],"tax season organizer","tax","us federal","which","netsuite","paid","end","usd","only","now","books","xero","scanning","run","request","flags","list","stripe",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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",[],[122,98,123,124,99,125,126,101,127,128,129,130,131,35,132,103,133,134,135,136],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","trigger","material","question","paypal","business",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":148,"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",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[149,150,151,152,153,154,127,33,155,156,157,158,159,160,28,161,162,80,163,164],"speed to lead","lead","speed","shared","back","cold","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":174,"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",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000036","内容创作者",[175,176,177,178,179,180,124,181,182,183,184,31,185,28,186,187,188,89,189,190],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","me","product","calendar","write","drafts",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":197,"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",[],[198,199,200,125,201,35,132,202,30,203,106,136,27,204,205,206,23,186,207,84],"router","smb","smb router","do","front","single","vague","can","with","focus"]