[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718BTQZQR2D8FDY9HQF87A3":3,"skill-same:01M718BTQZQR2D8FDY9HQF87A3":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},"01M718BTQZQR2D8FDY9HQF87A3","search-strategy",null,"Query decomposition and multi-source search orchestration. Breaks natural language questions into targeted searches per source, translates queries into source-specific syntax, ranks results by relevance, and handles ambiguity and fallback strategies.","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\u002Fenterprise-search\u002Fskills\u002Fsearch-strategy\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"search","strategy","search strategy","fallback","language","ambiguity","source","syntax","questions","multi-source","decomposition","results","strategies","queries","multi","query","orchestration","false","natural language","2026-11-10 10:12:30",false,"---\nname: search-strategy\ndescription: Query decomposition and multi-source search orchestration. Breaks natural language questions into targeted searches per source, translates queries into source-specific syntax, ranks results by relevance, and handles ambiguity and fallback strategies.\nuser-invocable: false\n---\n\n# Search Strategy\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nThe core intelligence behind enterprise search. Transforms a single natural language question into parallel, source-specific searches and produces ranked, deduplicated results.\n\n## The Goal\n\nTurn this:\n```\n\"What did we decide about the API migration timeline?\"\n```\n\nInto targeted searches across every connected source:\n```\n~~chat:  \"API migration timeline decision\" (semantic) + \"API migration\" in:#engineering after:2025-01-01\n~~knowledge base: semantic search \"API migration timeline decision\"\n~~project tracker:  text search \"API migration\" in relevant workspace\n```\n\nThen synthesize the results into a single coherent answer.\n\n## Query Decomposition\n\n### Step 1: Identify Query Type\n\nClassify the user's question to determine search strategy:\n\n| Query Type | Example | Strategy |\n|-----------|---------|----------|\n| **Decision** | \"What did we decide about X?\" | Prioritize conversations (~~chat, email), look for conclusion signals |\n| **Status** | \"What's the status of Project Y?\" | Prioritize recent activity, task trackers, status updates |\n| **Document** | \"Where's the spec for Z?\" | Prioritize Drive, wiki, shared docs |\n| **Person** | \"Who's working on X?\" | Search task assignments, message authors, doc collaborators |\n| **Factual** | \"What's our policy on X?\" | Prioritize wiki, official docs, then confirmatory conversations |\n| **Temporal** | \"When did X happen?\" | Search with broad date range, look for timestamps |\n| **Exploratory** | \"What do we know about X?\" | Broad search across all sources, synthesize |\n\n### Step 2: Extract Search Components\n\nFrom the query, extract:\n\n- **Keywords**: Core terms that must appear in results\n- **Entities**: People, projects, teams, tools (use memory system if available)\n- **Intent signals**: Decision words, status words, temporal markers\n- **Constraints**: Time ranges, source hints, author filters\n- **Negations**: Things to exclude\n\n### Step 3: Generate Sub-Queries Per Source\n\nFor each available source, create one or more targeted queries:\n\n**Prefer semantic search** for:\n- Conceptual questions (\"What do we think about...\")\n- Questions where exact keywords are unknown\n- Exploratory queries\n\n**Prefer keyword search** for:\n- Known terms, project names, acronyms\n- Exact phrases the user quoted\n- Filter-heavy queries (from:, in:, after:)\n\n**Generate multiple query variants** when the topic might be referred to differently:\n```\nUser: \"Kubernetes setup\"\nQueries: \"Kubernetes\", \"k8s\", \"cluster\", \"container orchestration\"\n```\n\n## Source-Specific Query Translation\n\n### ~~chat\n\n**Semantic search** (natural language questions):\n```\nquery: \"What is the status of project aurora?\"\n```\n\n**Keyword search:**\n```\nquery: \"project aurora status update\"\nquery: \"aurora in:#engineering after:2025-01-15\"\nquery: \"from:\u003C@UserID> aurora\"\n```\n\n**Filter mapping:**\n| Enterprise filter | ~~chat syntax |\n|------------------|--------------|\n| `from:sarah` | `from:sarah` or `from:\u003C@USERID>` |\n| `in:engineering` | `in:engineering` |\n| `after:2025-01-01` | `after:2025-01-01` |\n| `before:2025-02-01` | `before:2025-02-01` |\n| `type:thread` | `is:thread` |\n| `type:file` | `has:file` |\n\n### ~~knowledge base (Wiki)\n\n**Semantic search** — Use for conceptual queries:\n```\ndescriptive_query: \"API migration timeline and decision rationale\"\n```\n\n**Keyword search** — Use for exact terms:\n```\nquery: \"API migration\"\nquery: \"\\\"API migration timeline\\\"\"  (exact phrase)\n```\n\n### ~~project tracker\n\n**Task search:**\n```\ntext: \"API migration\"\nworkspace: [workspace_id]\ncompleted: false  (for status queries)\nassignee_any: \"me\"  (for \"my tasks\" queries)\n```\n\n**Filter mapping:**\n| Enterprise filter | ~~project tracker parameter |\n|------------------|----------------|\n| `from:sarah` | `assignee_any` or `created_by_any` |\n| `after:2025-01-01` | `modified_on_after: \"2025-01-01\"` |\n| `type:milestone` | `resource_subtype: \"milestone\"` |\n\n## Result Ranking\n\n### Relevance Scoring\n\nScore each result on these factors (weighted by query type):\n\n| Factor | Weight (Decision) | Weight (Status) | Weight (Document) | Weight (Factual) |\n|--------|-------------------|------------------|--------------------|-------------------|\n| Keyword match | 0.3 | 0.2 | 0.4 | 0.3 |\n| Freshness | 0.3 | 0.4 | 0.2 | 0.1 |\n| Authority | 0.2 | 0.1 | 0.3 | 0.4 |\n| Completeness | 0.2 | 0.3 | 0.1 | 0.2 |\n\n### Authority Hierarchy\n\nDepends on query type:\n\n**For factual\u002Fpolicy questions:**\n```\nWiki\u002FOfficial docs > Shared documents > Email announcements > Chat messages\n```\n\n**For \"what happened\" \u002F decision questions:**\n```\nMeeting notes > Thread conclusions > Email confirmations > Chat messages\n```\n\n**For status questions:**\n```\nTask tracker > Recent chat > Status docs > Email updates\n```\n\n## Handling Ambiguity\n\nWhen a query is ambiguous, prefer asking one focused clarifying question over guessing:\n\n```\nAmbiguous: \"search for the migration\"\n→ \"I found references to a few migrations. Are you looking for:\n   1. The database migration (Project Phoenix)\n   2. The cloud migration (AWS → GCP)\n   3. The email migration (Exchange → O365)\"\n```\n\nOnly ask for clarification when:\n- There are genuinely distinct interpretations that would produce very different results\n- The ambiguity would significantly affect which sources to search\n\nDo NOT ask for clarification when:\n- The query is clear enough to produce useful results\n- Minor ambiguity can be resolved by returning results from multiple interpretations\n\n## Fallback Strategies\n\nWhen a source is unavailable or returns no results:\n\n1. **Source unavailable**: Skip it, search remaining sources, note the gap\n2. **No results from a source**: Try broader query terms, remove date filters, try alternate keywords\n3. **All sources return nothing**: Suggest query modifications to the user\n4. **Rate limited**: Note the limitation, return results from other sources, suggest retrying later\n\n### Query Broadening\n\nIf initial queries return too few results:\n```\nOriginal: \"PostgreSQL migration Q2 timeline decision\"\nBroader:  \"PostgreSQL migration\"\nBroader:  \"database migration\"\nBroadest: \"migration\"\n```\n\nRemove constraints in this order:\n1. Date filters (search all time)\n2. Source\u002Flocation filters\n3. Less important keywords\n4. Keep only core entity\u002Ftopic terms\n\n## Parallel Execution\n\nAlways execute searches across sources in parallel, never sequentially. The total search time should be roughly equal to the slowest single source, not the sum of all sources.\n\n```\n[User query]\n     ↓ decompose\n[~~chat query] [~~email query] [~~cloud storage query] [Wiki query] [~~project tracker query]\n     ↓            ↓            ↓              ↓            ↓\n  (parallel execution)\n     ↓\n[Merge + Rank + Deduplicate]\n     ↓\n[Synthesized answer]\n```\n","# Search Strategy\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nThe core intelligence behind enterprise search. Transforms a single natural language question into parallel, source-specific searches and produces ranked, deduplicated results.\n\n## The Goal\n\nTurn this:\n```\n\"What did we decide about the API migration timeline?\"\n```\n\nInto targeted searches across every connected source:\n```\n~~chat:  \"API migration timeline decision\" (semantic) + \"API migration\" in:#engineering after:2025-01-01\n~~knowledge base: semantic search \"API migration timeline decision\"\n~~project tracker:  text search \"API migration\" in relevant workspace\n```\n\nThen synthesize the results into a single coherent answer.\n\n## Query Decomposition\n\n### Step 1: Identify Query Type\n\nClassify the user's question to determine search strategy:\n\n| Query Type | Example | Strategy |\n|-----------|---------|----------|\n| **Decision** | \"What did we decide about X?\" | Prioritize conversations (~~chat, email), look for conclusion signals |\n| **Status** | \"What's the status of Project Y?\" | Prioritize recent activity, task trackers, status updates |\n| **Document** | \"Where's the spec for Z?\" | Prioritize Drive, wiki, shared docs |\n| **Person** | \"Who's working on X?\" | Search task assignments, message authors, doc collaborators |\n| **Factual** | \"What's our policy on X?\" | Prioritize wiki, official docs, then confirmatory conversations |\n| **Temporal** | \"When did X happen?\" | Search with broad date range, look for timestamps |\n| **Exploratory** | \"What do we know about X?\" | Broad search across all sources, synthesize |\n\n### Step 2: Extract Search Components\n\nFrom the query, extract:\n\n- **Keywords**: Core terms that must appear in results\n- **Entities**: People, projects, teams, tools (use memory system if available)\n- **Intent signals**: Decision words, status words, temporal markers\n- **Constraints**: Time ranges, source hints, author filters\n- **Negations**: Things to exclude\n\n### Step 3: Generate Sub-Queries Per Source\n\nFor each available source, create one or more targeted queries:\n\n**Prefer semantic search** for:\n- Conceptual questions (\"What do we think about...\")\n- Questions where exact keywords are unknown\n- Exploratory queries\n\n**Prefer keyword search** for:\n- Known terms, project names, acronyms\n- Exact phrases the user quoted\n- Filter-heavy queries (from:, in:, after:)\n\n**Generate multiple query variants** when the topic might be referred to differently:\n```\nUser: \"Kubernetes setup\"\nQueries: \"Kubernetes\", \"k8s\", \"cluster\", \"container orchestration\"\n```\n\n## Source-Specific Query Translation\n\n### ~~chat\n\n**Semantic search** (natural language questions):\n```\nquery: \"What is the status of project aurora?\"\n```\n\n**Keyword search:**\n```\nquery: \"project aurora status update\"\nquery: \"aurora in:#engineering after:2025-01-15\"\nquery: \"from:\u003C@UserID> aurora\"\n```\n\n**Filter mapping:**\n| Enterprise filter | ~~chat syntax |\n|------------------|--------------|\n| `from:sarah` | `from:sarah` or `from:\u003C@USERID>` |\n| `in:engineering` | `in:engineering` |\n| `after:2025-01-01` | `after:2025-01-01` |\n| `before:2025-02-01` | `before:2025-02-01` |\n| `type:thread` | `is:thread` |\n| `type:file` | `has:file` |\n\n### ~~knowledge base (Wiki)\n\n**Semantic search** — Use for conceptual queries:\n```\ndescriptive_query: \"API migration timeline and decision rationale\"\n```\n\n**Keyword search** — Use for exact terms:\n```\nquery: \"API migration\"\nquery: \"\\\"API migration timeline\\\"\"  (exact phrase)\n```\n\n### ~~project tracker\n\n**Task search:**\n```\ntext: \"API migration\"\nworkspace: [workspace_id]\ncompleted: false  (for status queries)\nassignee_any: \"me\"  (for \"my tasks\" queries)\n```\n\n**Filter mapping:**\n| Enterprise filter | ~~project tracker parameter |\n|------------------|----------------|\n| `from:sarah` | `assignee_any` or `created_by_any` |\n| `after:2025-01-01` | `modified_on_after: \"2025-01-01\"` |\n| `type:milestone` | `resource_subtype: \"milestone\"` |\n\n## Result Ranking\n\n### Relevance Scoring\n\nScore each result on these factors (weighted by query type):\n\n| Factor | Weight (Decision) | Weight (Status) | Weight (Document) | Weight (Factual) |\n|--------|-------------------|------------------|--------------------|-------------------|\n| Keyword match | 0.3 | 0.2 | 0.4 | 0.3 |\n| Freshness | 0.3 | 0.4 | 0.2 | 0.1 |\n| Authority | 0.2 | 0.1 | 0.3 | 0.4 |\n| Completeness | 0.2 | 0.3 | 0.1 | 0.2 |\n\n### Authority Hierarchy\n\nDepends on query type:\n\n**For factual\u002Fpolicy questions:**\n```\nWiki\u002FOfficial docs > Shared documents > Email announcements > Chat messages\n```\n\n**For \"what happened\" \u002F decision questions:**\n```\nMeeting notes > Thread conclusions > Email confirmations > Chat messages\n```\n\n**For status questions:**\n```\nTask tracker > Recent chat > Status docs > Email updates\n```\n\n## Handling Ambiguity\n\nWhen a query is ambiguous, prefer asking one focused clarifying question over guessing:\n\n```\nAmbiguous: \"search for the migration\"\n→ \"I found references to a few migrations. Are you looking for:\n   1. The database migration (Project Phoenix)\n   2. The cloud migration (AWS → GCP)\n   3. The email migration (Exchange → O365)\"\n```\n\nOnly ask for clarification when:\n- There are genuinely distinct interpretations that would produce very different results\n- The ambiguity would significantly affect which sources to search\n\nDo NOT ask for clarification when:\n- The query is clear enough to produce useful results\n- Minor ambiguity can be resolved by returning results from multiple interpretations\n\n## Fallback Strategies\n\nWhen a source is unavailable or returns no results:\n\n1. **Source unavailable**: Skip it, search remaining sources, note the gap\n2. **No results from a source**: Try broader query terms, remove date filters, try alternate keywords\n3. **All sources return nothing**: Suggest query modifications to the user\n4. **Rate limited**: Note the limitation, return results from other sources, suggest retrying later\n\n### Query Broadening\n\nIf initial queries return too few results:\n```\nOriginal: \"PostgreSQL migration Q2 timeline decision\"\nBroader:  \"PostgreSQL migration\"\nBroader:  \"database migration\"\nBroadest: \"migration\"\n```\n\nRemove constraints in this order:\n1. Date filters (search all time)\n2. Source\u002Flocation filters\n3. Less important keywords\n4. Keep only core entity\u002Ftopic terms\n\n## Parallel Execution\n\nAlways execute searches across sources in parallel, never sequentially. The total search time should be roughly equal to the slowest single source, not the sum of all sources.\n\n```\n[User query]\n     ↓ decompose\n[~~chat query] [~~email query] [~~cloud storage query] [Wiki query] [~~project tracker query]\n     ↓            ↓            ↓              ↓            ↓\n  (parallel execution)\n     ↓\n[Merge + Rank + Deduplicate]\n     ↓\n[Synthesized answer]\n```\n",{"name":5,"description":7,"user-invocable":39},"main","e605d8ddbfb688da57dfaaceebd93f12a64ef1d3","enterprise-search\u002Fskills\u002Fsearch-strategy",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add anthropics\u002Fknowledge-work-plugins --skill search-strategy",{"tool":57,"command":58},"bunx","bunx skills add anthropics\u002Fknowledge-work-plugins --skill search-strategy",{"tool":60,"command":61},"pnpm","pnpm dlx skills add anthropics\u002Fknowledge-work-plugins --skill search-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Fblob\u002Fmain\u002Fenterprise-search\u002Fskills\u002Fsearch-strategy\u002FSKILL.md",true,[],[66,93,118,141,170,196],{"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,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92],"ticket","ticket deflector","mode","up","payments","open","writing","when","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,80,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,135,136,106,137,138,139,140],"tax prep","prep","SET","as","ready","never","zoho books","get","chain","profit","for","trigger","material","question","paypal","business",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":152,"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",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[153,154,155,156,157,158,130,159,160,161,162,163,164,165,80,166,167,83,168,169],"speed to lead","lead","speed","shared","back","cold","time","inbox","send","respond","new","web forms","people","schedule","logs","sure","human",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"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",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000036","内容创作者",[180,181,182,183,184,185,127,186,187,188,189,76,190,80,191,192,193,92,194,195],"social","social content engine","engine","content engine","social content","content","brief","posts","Captions","prices","campaign","me","product","calendar","write","drafts",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"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",[],[203,204,205,128,206,135,136,207,78,208,109,140,209,210,211,212,213,191,214,87],"router","smb","smb router","do","front","single","you","vague","can","with","plugin","focus"]