[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MMCP79QRKDWMZAPFVB804":3,"skill-same:01M71MMCP79QRKDWMZAPFVB804":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M71MMCP79QRKDWMZAPFVB804","content-strategy",null,"Analyzes sales data from PayPal and QuickBooks to find top performers and slow movers, layers in seasonality, and produces a prioritized 30-day content brief: what to push, what offers to run, what to hold. Strategic output only — no calendars or assets. Use when the user asks what to post, wants a content plan, asks what's selling, or what to promote this month.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-strategy\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-strategy\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"strategy","content","content strategy","use","paypal","strategic","layers","push","quickbooks","data","run","top","plan","work","content brief","when","knowledge","only","promote","brief","2026-11-10 10:56:23",false,"---\nname: content-strategy\ndescription: \"Analyzes sales data from PayPal and QuickBooks to find top performers and slow movers, layers in seasonality, and produces a prioritized 30-day content brief: what to push, what offers to run, what to hold. Strategic output only — no calendars or assets. Use when the user asks what to post, wants a content plan, asks what's selling, or what to promote this month.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"small-business\u002Fskills\u002Fcontent-strategy\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\n---\n# Content Strategy\n\n## Quick start\n\nWhen an SMB owner asks \"what should I post this month?\" or \"what's my content plan?\", this skill:\n\n1. **Pulls sales data** from QuickBooks or PayPal (transaction history, product\u002Fservice revenue by date)\n2. **Identifies patterns** — top-selling products, slow movers, seasonal trends\n3. **Layers in context** — seasonality (user-provided or industry benchmarks), past performance\n4. **Produces a 30-day brief** — ranked recommendations of what to push, what to hold, what offers to consider\n5. **Gets owner approval** before the brief feeds into `social-content-engine` for asset generation\n\nThe output is strategic only — no calendar scheduling, no creative assets.\n\n---\n\n## Workflow\n\n### Step 1: Pre-flight check (QuickBooks only)\n\nIf using QuickBooks, verify the business profile is set up:\n\n1. Call `company-info` to check if `Industry` is populated\n2. If missing or \"Unknown\":\n   - Ask: \"I need your business category to pull the right seasonality benchmarks. What industry are you in?\" (e.g., retail, services, SaaS)\n   - Call `quickbooks-profile-info-update` with the user's industry\n   - Confirm: \"Profile updated. Ready to pull your sales data.\"\n3. If profile is set, proceed to Step 2\n\n**Note:** PayPal and Square do not require profile setup.\n\n### Step 2: Clarify priorities & metrics\n\nWhen triggered, ask the user:\n\n- **\"How do you want me to measure 'top performers'?\"**\n  - By total revenue?\n  - By profit margin?\n  - By sales velocity (how fast they're selling)?\n  - Combination of the above?\n\n- **\"Do you have seasonality patterns in mind?\"**\n  - If yes: \"Tell me about them\" (capture user's known seasonality)\n  - If no: \"I'll use industry benchmarks for your category\"\n\n### Step 3: Pull and analyze sales data\n\nFetch data from the authenticated connector (QuickBooks, PayPal, or Square, user's choice):\n\n- **Date range:** Last 90 days (or full history if \u003C90 days available)\n- **Extract:** Product\u002Fservice name, date sold, revenue, quantity\n\n**Connector-specific notes:**\n\n- **QuickBooks:** Fetch invoice line items via `profit_loss_quickbooks_account` (pre-flight sets industry context). Read the rows or `monthlyBreakdown`; the response's `totalExpenses` reports 0 against real rows, so never read the summary fields\n- **PayPal:** Fetch merchant transactions via `list_transactions`. *Rate-limiting:* If you hit rate limits, pause 30 seconds and retry once. If still blocked, gracefully offer: \"PayPal is rate-limited. Would you like to switch to QuickBooks or Square instead, or I can continue with historical data I already pulled?\"\n- **Square:** Requires location ID first. Call `make_api_request(service=\"locations\", method=\"list\")` to discover available locations, then fetch orders for each location.\n\n**No connectors at all?** This still runs, and it is a supported path — not a degraded one. Ask the owner to export their sales history and upload it. Name the export by the label they will actually see in the app:\n\n- **QuickBooks** — Reports, then the \"Sales by Product\u002FService Detail\" report, set to the last 90 days, exported to Excel or CSV\n- **PayPal** — Activity, then Download, set to the last 90 days, \"Completed transactions\" as CSV\n- **Square** — Reports, then Item Sales, set to the last 90 days, exported as CSV\n\nAny one of those carries product name, date, revenue, and usually quantity, which is everything Step 3 needs. A pasted list of what sold and roughly when also works — say plainly that the read is rougher, and run it.\n\n**Fallback:** If \u003C3 months of data, use industry seasonality benchmarks for the SMB's category (e.g., retail, services, e-commerce)\n\nIdentify:\n- **Top 3–5 performers** (by user's chosen metric)\n- **Bottom 3–5 slow movers** (consider holding or repositioning)\n- **Trending up** (gaining momentum in last 30 days)\n- **Trending down** (losing momentum)\n\n### Step 4: Layer in seasonality\n\n- **User-provided:** If they shared seasonal patterns, weight recommendations against them\n- **Industry benchmarks:** For categories without strong user data (e.g., \"Q1 is strong for tax services\")\n- **Timing:** Flag products that should ramp up\u002Fdown in the next 30 days based on seasonal patterns\n\n### Step 5: Build the 30-day brief\n\nStructure:\n- **Executive summary** (1–2 sentences: \"Your best sellers are X and Y. Seasonal shift to Z is starting.\")\n- **Push hard** (Top 2–3 products + recommended content angle, e.g., \"Case study on ROI\", \"How-to video\")\n- **Hold steady** (Middle performers; maintain visibility but no heavy lift)\n- **Reposition or pause** (Slow movers; consider discounting, bundling, or pausing)\n- **Seasonal opportunities** (What's coming next month that you should position for now)\n- **Recommended offers** (Bundle, discount, or free-trial strategy based on data)\n\nExample length: **200–400 words** (brief and actionable, not essay-length).\n\n### Step 6: Owner approval & iteration\n\nPresent the brief to the owner. Ask:\n- \"Does this match your gut?\"\n- \"Anything to adjust?\"\n- \"Ready to feed this to social-content-engine for asset generation?\"\n\nIterate if needed; once approved, return the final brief as structured JSON (ready for downstream tools).\n\n---\n\n## More sources, and direct invocation\n\nRead `reference\u002Fv2_sources.md` for the mapping:\n\n- **Shopify** — per-SKU velocity, variant performance, and product images that flow straight into asset generation downstream\n- **Stripe** — subscription and recurring revenue, where relevant\n\n### Direct invocation\n\nIf the owner asks for a sales brief, run this and return the brief. Don't route them anywhere.\n\n## Gotchas & edge cases\n\nSee [`reference\u002Fgotchas.md`](reference\u002Fgotchas.md) for common pitfalls.\n\n---\n\n## Examples\n\nSee [`reference\u002Fexamples\u002F`](reference\u002Fexamples\u002F) for worked examples (SaaS, retail, services).\n\n---\n\n## Output\n\n**Deliver the 30-day brief per the owner's stored output preference — never default to a markdown file.** Check the `## Business context` block's `Output preference` (shared style guide rule, `..\u002F..\u002Fshared\u002Fartifact-style.md`):\n\n- **Visual artifact (the default):** render the brief as an HTML page in the house style — what to promote as the lead, the why behind each pick with its numbers in tabular-nums, and the channel call per push. The structured JSON for downstream tools rides along unchanged; it is an input to other skills, not a second deliverable.\n- **docx \u002F md \u002F notion \u002F canva preference:** deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why.\n- **Best for skill:** use the visual artifact — this output is a decision page, not prose.\n\n## After the brief\n\nThe 30-day brief is approved and ready to act on. The natural next step is \"make the content\" — `social-content-engine` turns the brief into the standing calendar and the posts. Also nearby: \"run this brief\" (`canva-creator`) for a one-shot campaign build from this exact brief, and \"is my marketing working\" (`growth-pulse`) to check whether last month's push paid off. Offer at most three, and skip any offer the owner already declined this session.\n\n## Using a tool that isn't listed\n\nThe connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer `build-connector` — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.\n","# Content Strategy\n\n## Quick start\n\nWhen an SMB owner asks \"what should I post this month?\" or \"what's my content plan?\", this skill:\n\n1. **Pulls sales data** from QuickBooks or PayPal (transaction history, product\u002Fservice revenue by date)\n2. **Identifies patterns** — top-selling products, slow movers, seasonal trends\n3. **Layers in context** — seasonality (user-provided or industry benchmarks), past performance\n4. **Produces a 30-day brief** — ranked recommendations of what to push, what to hold, what offers to consider\n5. **Gets owner approval** before the brief feeds into `social-content-engine` for asset generation\n\nThe output is strategic only — no calendar scheduling, no creative assets.\n\n---\n\n## Workflow\n\n### Step 1: Pre-flight check (QuickBooks only)\n\nIf using QuickBooks, verify the business profile is set up:\n\n1. Call `company-info` to check if `Industry` is populated\n2. If missing or \"Unknown\":\n   - Ask: \"I need your business category to pull the right seasonality benchmarks. What industry are you in?\" (e.g., retail, services, SaaS)\n   - Call `quickbooks-profile-info-update` with the user's industry\n   - Confirm: \"Profile updated. Ready to pull your sales data.\"\n3. If profile is set, proceed to Step 2\n\n**Note:** PayPal and Square do not require profile setup.\n\n### Step 2: Clarify priorities & metrics\n\nWhen triggered, ask the user:\n\n- **\"How do you want me to measure 'top performers'?\"**\n  - By total revenue?\n  - By profit margin?\n  - By sales velocity (how fast they're selling)?\n  - Combination of the above?\n\n- **\"Do you have seasonality patterns in mind?\"**\n  - If yes: \"Tell me about them\" (capture user's known seasonality)\n  - If no: \"I'll use industry benchmarks for your category\"\n\n### Step 3: Pull and analyze sales data\n\nFetch data from the authenticated connector (QuickBooks, PayPal, or Square, user's choice):\n\n- **Date range:** Last 90 days (or full history if \u003C90 days available)\n- **Extract:** Product\u002Fservice name, date sold, revenue, quantity\n\n**Connector-specific notes:**\n\n- **QuickBooks:** Fetch invoice line items via `profit_loss_quickbooks_account` (pre-flight sets industry context). Read the rows or `monthlyBreakdown`; the response's `totalExpenses` reports 0 against real rows, so never read the summary fields\n- **PayPal:** Fetch merchant transactions via `list_transactions`. *Rate-limiting:* If you hit rate limits, pause 30 seconds and retry once. If still blocked, gracefully offer: \"PayPal is rate-limited. Would you like to switch to QuickBooks or Square instead, or I can continue with historical data I already pulled?\"\n- **Square:** Requires location ID first. Call `make_api_request(service=\"locations\", method=\"list\")` to discover available locations, then fetch orders for each location.\n\n**No connectors at all?** This still runs, and it is a supported path — not a degraded one. Ask the owner to export their sales history and upload it. Name the export by the label they will actually see in the app:\n\n- **QuickBooks** — Reports, then the \"Sales by Product\u002FService Detail\" report, set to the last 90 days, exported to Excel or CSV\n- **PayPal** — Activity, then Download, set to the last 90 days, \"Completed transactions\" as CSV\n- **Square** — Reports, then Item Sales, set to the last 90 days, exported as CSV\n\nAny one of those carries product name, date, revenue, and usually quantity, which is everything Step 3 needs. A pasted list of what sold and roughly when also works — say plainly that the read is rougher, and run it.\n\n**Fallback:** If \u003C3 months of data, use industry seasonality benchmarks for the SMB's category (e.g., retail, services, e-commerce)\n\nIdentify:\n- **Top 3–5 performers** (by user's chosen metric)\n- **Bottom 3–5 slow movers** (consider holding or repositioning)\n- **Trending up** (gaining momentum in last 30 days)\n- **Trending down** (losing momentum)\n\n### Step 4: Layer in seasonality\n\n- **User-provided:** If they shared seasonal patterns, weight recommendations against them\n- **Industry benchmarks:** For categories without strong user data (e.g., \"Q1 is strong for tax services\")\n- **Timing:** Flag products that should ramp up\u002Fdown in the next 30 days based on seasonal patterns\n\n### Step 5: Build the 30-day brief\n\nStructure:\n- **Executive summary** (1–2 sentences: \"Your best sellers are X and Y. Seasonal shift to Z is starting.\")\n- **Push hard** (Top 2–3 products + recommended content angle, e.g., \"Case study on ROI\", \"How-to video\")\n- **Hold steady** (Middle performers; maintain visibility but no heavy lift)\n- **Reposition or pause** (Slow movers; consider discounting, bundling, or pausing)\n- **Seasonal opportunities** (What's coming next month that you should position for now)\n- **Recommended offers** (Bundle, discount, or free-trial strategy based on data)\n\nExample length: **200–400 words** (brief and actionable, not essay-length).\n\n### Step 6: Owner approval & iteration\n\nPresent the brief to the owner. Ask:\n- \"Does this match your gut?\"\n- \"Anything to adjust?\"\n- \"Ready to feed this to social-content-engine for asset generation?\"\n\nIterate if needed; once approved, return the final brief as structured JSON (ready for downstream tools).\n\n---\n\n## More sources, and direct invocation\n\nRead `reference\u002Fv2_sources.md` for the mapping:\n\n- **Shopify** — per-SKU velocity, variant performance, and product images that flow straight into asset generation downstream\n- **Stripe** — subscription and recurring revenue, where relevant\n\n### Direct invocation\n\nIf the owner asks for a sales brief, run this and return the brief. Don't route them anywhere.\n\n## Gotchas & edge cases\n\nSee [`reference\u002Fgotchas.md`](reference\u002Fgotchas.md) for common pitfalls.\n\n---\n\n## Examples\n\nSee [`reference\u002Fexamples\u002F`](reference\u002Fexamples\u002F) for worked examples (SaaS, retail, services).\n\n---\n\n## Output\n\n**Deliver the 30-day brief per the owner's stored output preference — never default to a markdown file.** Check the `## Business context` block's `Output preference` (shared style guide rule, `..\u002F..\u002Fshared\u002Fartifact-style.md`):\n\n- **Visual artifact (the default):** render the brief as an HTML page in the house style — what to promote as the lead, the why behind each pick with its numbers in tabular-nums, and the channel call per push. The structured JSON for downstream tools rides along unchanged; it is an input to other skills, not a second deliverable.\n- **docx \u002F md \u002F notion \u002F canva preference:** deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why.\n- **Best for skill:** use the visual artifact — this output is a decision page, not prose.\n\n## After the brief\n\nThe 30-day brief is approved and ready to act on. The natural next step is \"make the content\" — `social-content-engine` turns the brief into the standing calendar and the posts. Also nearby: \"run this brief\" (`canva-creator`) for a one-shot campaign build from this exact brief, and \"is my marketing working\" (`growth-pulse`) to check whether last month's push paid off. Offer at most three, and skip any offer the owner already declined this session.\n\n## Using a tool that isn't listed\n\nThe connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer `build-connector` — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.\n",{"name":5,"tags":49,"tools":50,"source":51,"license":14,"description":7,"source_path":52,"source_commit":53},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","small-business\u002Fskills\u002Fcontent-strategy","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-strategy",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add monoes\u002Fmonomind --skill content-strategy",{"tool":69,"command":70},"bunx","bunx skills add monoes\u002Fmonomind --skill content-strategy",{"tool":72,"command":73},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill content-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-strategy\u002FSKILL.md",true,[77,82,88,92,96,100],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"reference\u002Fexamples\u002Fretail-boutique-example.md","REFERENCE","参考文档",2872,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-strategy\u002Freference\u002Fexamples\u002Fretail-boutique-example.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"reference\u002Fgotchas.md",4389,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-strategy\u002Freference\u002Fgotchas.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"reference\u002Fv2_sources.md",1513,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-strategy\u002Freference\u002Fv2_sources.md",{"path":97,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fcontent-distribution.md",5576,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-strategy\u002Freferences\u002Fcontent-distribution.md",{"path":101,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fheadless-cms.md",8433,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcontent-strategy\u002Freferences\u002Fheadless-cms.md",[105,132,163,188,212,239],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":131},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[112,113,114,115,116,117,118,40,119,120,121,122,123,124,125,126,127,128,129,130],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":136,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":146,"publishedAt":131},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[140,145],{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[147,148,149,116,150,151,39,152,120,153,154,36,155,156,157,158,159,160,161,162],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":131},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理",[156,174,175,176,177,40,178,39,179,180,37,155,181,182,183,184,185,186,27,187],"write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":198,"publishedAt":131},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[195],{"categoryNo":196,"categoryName":197,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[120,156,199,200,201,202,40,27,39,203,204,205,206,37,207,208,209,210,211,33],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":224,"publishedAt":131},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[218,221],{"categoryNo":219,"categoryName":220,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":222,"categoryName":223,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000023","Skill与智能体开发",[225,226,227,228,201,229,230,231,232,119,233,234,235,120,123,207,236,237,238,209],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":240,"name":241,"nameZh":6,"description":242,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":243,"categories":244,"keywords":246,"publishedAt":131},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[245],{"categoryNo":222,"categoryName":223,"taxonomyType":143,"taxonomyTypeDesc":144},[227,247,248,249,250,251,252,201,253,254,153,255,256,257,123,207,258,259,209,260],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]