[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71N2KJBM321YP4QZ547M8D6":3,"skill-same:01M71N2KJBM321YP4QZ547M8D6":105},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M71N2KJBM321YP4QZ547M8D6","growth-pulse",null,"Answers one question for an SMB owner — is the growth engine actually working? Pulls sales trend by channel, funnel conversion, campaign return, best and worst performing products, and customer sentiment from whatever is connected, then ends with the three growth actions worth taking this week. The growth-side twin of business-pulse, which covers the finance side. Use this whenever the owner asks how marketing or sales is performing, whether a campaign paid off, where leads are coming from, why the pipeline is stalling, which products are moving, or says anything like \"is my marketing working,\" \"growth check,\" \"how's the funnel,\" or \"where should I put my money next month.\" Reach for it even when the owner names a single channel rather than growth overall.","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\u002Fgrowth-pulse\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fgrowth-pulse\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"pulse","growth","growth pulse","trend","how","customer","next","work","smb","conversion","answers","when","question","knowledge","campaign","actions","pipeline","paid","growth engine","which","2026-11-10 10:56:23",false,"---\nname: growth-pulse\ndescription: \"Answers one question for an SMB owner — is the growth engine actually working? Pulls sales trend by channel, funnel conversion, campaign return, best and worst performing products, and customer sentiment from whatever is connected, then ends with the three growth actions worth taking this week. The growth-side twin of business-pulse, which covers the finance side. Use this whenever the owner asks how marketing or sales is performing, whether a campaign paid off, where leads are coming from, why the pipeline is stalling, which products are moving, or says anything like \\\"is my marketing working,\\\" \\\"growth check,\\\" \\\"how's the funnel,\\\" or \\\"where should I put my money next month.\\\" Reach for it even when the owner names a single channel rather than growth overall.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"small-business\u002Fskills\u002Fgrowth-pulse\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\n---\n# Growth Pulse\n\nOne page that answers whether the growth engine is working, and what to do about it this week.\n\nOwners describe pulling numbers from three dashboards and trying to find the story themselves. The story is the deliverable here — not the dashboards.\n\n## Step 1 — Pull everything in parallel\n\nDispatch all connector calls in a single batch. See `reference\u002Fdata_sources.md` for the metric-to-tool mapping. Serial pulls turn this into a wait nobody sits through twice.\n\n- **HubSpot** — deals by stage, new contacts, lead source, win rate, cycle time, stalled deals\n- **PayPal, Stripe, Square** — revenue trend, transaction counts, refunds\n- **Shopify** — orders, SKU-level revenue, repeat purchase rate\n- **QuickBooks** — realized revenue, the number the books agree with\n- **TikTok Ads** — last week's spend, impressions, clicks, results, and cost per result per campaign, from the native connector (`report_integrated_get`, last 7 days against the prior 7), so paid spend sits beside the sales it claims to drive\n- **Mailchimp** — campaign, e-commerce, and audience-growth analytics, with revenue attribution on campaigns\n- **Gmail or Microsoft 365** — inbound inquiry volume and response times\n- **Public reviews** — recent ratings and review text, via web research\n\nIf a source errors or is missing, record it and move on. This skill is designed to say something useful on one connector and something excellent on six.\n\n**Zero connectors is a supported path.** Ask for exports — a CRM deal export, a sales report, an ads performance CSV — and build the same pulse from files. Say it plainly rather than stalling.\n\n## Step 2 — Compute the five views\n\nRead `reference\u002Fthresholds.md` for the cutoffs. Compute each view and assign it a status.\n\n1. **Channel trend** — revenue by channel this period versus last, and versus the same period last year where available\n2. **Funnel conversion** — leads in, qualified, opportunities, won; the conversion rate between each step and where the biggest drop-off sits\n3. **Campaign return** — spend versus attributed revenue per campaign, and cost per lead\n4. **Product performance** — top three and bottom three by revenue and by growth rate\n5. **Customer sentiment** — recent review scores, review themes, disputes, churn signals\n\nA view with no data gets marked \"n\u002Fa\" and named in the appendix. It does not silently vanish.\n\n## Step 3 — Find the actual story\n\nThis is where the skill earns its keep. Five views on their own are still a dashboard. The job is to connect them.\n\nThe connections that matter most:\n\n- **Spend rising while cost per lead rises** means the channel is saturating, not scaling\n- **Strong lead volume with falling win rate** points at lead quality or response speed, not at marketing\n- **One product carrying the whole trend** means the growth is more fragile than the total suggests\n- **Sentiment dropping while revenue holds** is the early warning that shows up in revenue two months later\n- **A stage where the funnel drops off sharply** is usually worth more than any new campaign\n\nLook for the single sentence that explains the period. Lead with it.\n\n## Step 4 — Write the three actions\n\nEvery pulse ends with exactly three actions. Not five, not a list of everything noticed.\n\nEach action needs three things or it isn't an action:\n\n- **What to do** — specific enough to start today\n- **Why** — the number from this pulse that justifies it\n- **What it's worth** — the rough size of the opportunity or the risk\n\nRank them by size of impact, not by ease. Owners can decide what's easy; only this pulse can tell them what's big.\n\nIf the honest answer is that nothing needs to change, say that. A pulse that manufactures three actions every week trains the owner to ignore them.\n\n## Step 5 — Compose\n\nUse the exact structure in `reference\u002Foutput_template.md`. Include only sections with real data.\n\nWriting rules:\n\n- Numbers lead, words follow. Not \"paid social performed well\" — \"paid social drove 41 leads at USD 18 each, down from USD 31 last month.\"\n- Every number carries its comparison. A figure with no baseline is a missed insight.\n- Name the specific campaign, product, channel, or customer. \"Some campaigns underperformed\" is unusable.\n- No marketing vocabulary the owner doesn't use. Not \"top of funnel velocity\" — \"how many new leads came in and how fast.\"\n- If a section has nothing worth saying, write \"No material change\" and move on.\n\n## Step 6 — Deliver the pulse page\n\nAlongside the chat pulse — additive, never a replacement — deliver the full pulse 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 pulse as an HTML page in the house style. Each of the five views gets a panel; revenue trend, cost per lead, and win rate are stat tiles with their comparison as the context line; campaign return and product performance are tables with tabular-nums spend and revenue columns; each view's status becomes a status pill (good, warn, critical, or n\u002Fa in plain text); the three actions close the page in their own panel, ranked.\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 — five views compare best side by side on one screen.\n\n## Step 7 — Offer to save, once\n\nAfter presenting, offer once to save the pulse as a file or post it to Slack. Posting to Slack is an outward write, so it only happens on that explicit yes — the offer is the approval gate. If yes, do it. If no or no response, move on. Do not ask twice.\n\nThen close with what the pulse found in one line, plus the single most relevant next step and at most two others nearby:\n\n- If the actions point at content or promotion: \"what should I promote\" runs `content-strategy`.\n- If the funnel is the problem: \"fill my funnel\" runs `\u002Fgrow-pipeline`.\n- For the finance-side twin: \"how's the business doing\" runs `business-pulse`.\n\nMax three offers. Never repeat an offer the owner declined this session.\n\n## Scope variants\n\nOwners often want a slice rather than the whole pulse:\n\n- **\"How did the campaign do\"** — campaign return only, plus the sentiment check\n- **\"How's the pipeline\"** — funnel conversion and stalled deals only\n- **\"What's selling\"** — product performance only\n- **\"Are we getting reviews\"** — sentiment only\n- **\"Where should I spend next month\"** — channel trend and campaign return, with the three actions weighted toward budget\n\nGive them the slice they asked for. Don't force the full pulse on a narrow question.\n\n## What not to do\n\n- **Do not ask permission before pulling data.** The skill was invoked. Run it.\n- **Do not invent attribution.** If a campaign's revenue can't be traced, say the attribution is unavailable rather than assigning revenue on a guess. Fake attribution has moved real budgets.\n- **Do not report CRM forecast value as revenue.** Deal values are hopes; invoices are facts. Label which is which.\n- **Do not double-count across sources.** A Shopify order settled in Stripe is one sale. Pick one revenue source and name it.\n- **Do not double-count inside one source.** The sales-by-customer summary returns both a parent summary row and a separate total row for the same customer. Filter rows marked as totals before you rank customers or compute concentration, or the same customer lands in the list twice and the concentration figure comes out too high.\n- **Do not manufacture urgency.** If growth is steady, the pulse should read as steady.\n- **Do not read expenses or margin from the QuickBooks P&L summary.** Total the rows (`..\u002F..\u002Fshared\u002Fquickbooks-report-traps.md`, Trap 2).\n\n## Reference files\n\n- `reference\u002Fdata_sources.md` — connector to metric mapping, with fallbacks\n- `reference\u002Fthresholds.md` — status cutoffs for each of the five views\n- `reference\u002Foutput_template.md` — exact output structure\n- `reference\u002Fgotchas.md` — the failure modes that produce confidently wrong growth advice\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","# Growth Pulse\n\nOne page that answers whether the growth engine is working, and what to do about it this week.\n\nOwners describe pulling numbers from three dashboards and trying to find the story themselves. The story is the deliverable here — not the dashboards.\n\n## Step 1 — Pull everything in parallel\n\nDispatch all connector calls in a single batch. See `reference\u002Fdata_sources.md` for the metric-to-tool mapping. Serial pulls turn this into a wait nobody sits through twice.\n\n- **HubSpot** — deals by stage, new contacts, lead source, win rate, cycle time, stalled deals\n- **PayPal, Stripe, Square** — revenue trend, transaction counts, refunds\n- **Shopify** — orders, SKU-level revenue, repeat purchase rate\n- **QuickBooks** — realized revenue, the number the books agree with\n- **TikTok Ads** — last week's spend, impressions, clicks, results, and cost per result per campaign, from the native connector (`report_integrated_get`, last 7 days against the prior 7), so paid spend sits beside the sales it claims to drive\n- **Mailchimp** — campaign, e-commerce, and audience-growth analytics, with revenue attribution on campaigns\n- **Gmail or Microsoft 365** — inbound inquiry volume and response times\n- **Public reviews** — recent ratings and review text, via web research\n\nIf a source errors or is missing, record it and move on. This skill is designed to say something useful on one connector and something excellent on six.\n\n**Zero connectors is a supported path.** Ask for exports — a CRM deal export, a sales report, an ads performance CSV — and build the same pulse from files. Say it plainly rather than stalling.\n\n## Step 2 — Compute the five views\n\nRead `reference\u002Fthresholds.md` for the cutoffs. Compute each view and assign it a status.\n\n1. **Channel trend** — revenue by channel this period versus last, and versus the same period last year where available\n2. **Funnel conversion** — leads in, qualified, opportunities, won; the conversion rate between each step and where the biggest drop-off sits\n3. **Campaign return** — spend versus attributed revenue per campaign, and cost per lead\n4. **Product performance** — top three and bottom three by revenue and by growth rate\n5. **Customer sentiment** — recent review scores, review themes, disputes, churn signals\n\nA view with no data gets marked \"n\u002Fa\" and named in the appendix. It does not silently vanish.\n\n## Step 3 — Find the actual story\n\nThis is where the skill earns its keep. Five views on their own are still a dashboard. The job is to connect them.\n\nThe connections that matter most:\n\n- **Spend rising while cost per lead rises** means the channel is saturating, not scaling\n- **Strong lead volume with falling win rate** points at lead quality or response speed, not at marketing\n- **One product carrying the whole trend** means the growth is more fragile than the total suggests\n- **Sentiment dropping while revenue holds** is the early warning that shows up in revenue two months later\n- **A stage where the funnel drops off sharply** is usually worth more than any new campaign\n\nLook for the single sentence that explains the period. Lead with it.\n\n## Step 4 — Write the three actions\n\nEvery pulse ends with exactly three actions. Not five, not a list of everything noticed.\n\nEach action needs three things or it isn't an action:\n\n- **What to do** — specific enough to start today\n- **Why** — the number from this pulse that justifies it\n- **What it's worth** — the rough size of the opportunity or the risk\n\nRank them by size of impact, not by ease. Owners can decide what's easy; only this pulse can tell them what's big.\n\nIf the honest answer is that nothing needs to change, say that. A pulse that manufactures three actions every week trains the owner to ignore them.\n\n## Step 5 — Compose\n\nUse the exact structure in `reference\u002Foutput_template.md`. Include only sections with real data.\n\nWriting rules:\n\n- Numbers lead, words follow. Not \"paid social performed well\" — \"paid social drove 41 leads at USD 18 each, down from USD 31 last month.\"\n- Every number carries its comparison. A figure with no baseline is a missed insight.\n- Name the specific campaign, product, channel, or customer. \"Some campaigns underperformed\" is unusable.\n- No marketing vocabulary the owner doesn't use. Not \"top of funnel velocity\" — \"how many new leads came in and how fast.\"\n- If a section has nothing worth saying, write \"No material change\" and move on.\n\n## Step 6 — Deliver the pulse page\n\nAlongside the chat pulse — additive, never a replacement — deliver the full pulse 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 pulse as an HTML page in the house style. Each of the five views gets a panel; revenue trend, cost per lead, and win rate are stat tiles with their comparison as the context line; campaign return and product performance are tables with tabular-nums spend and revenue columns; each view's status becomes a status pill (good, warn, critical, or n\u002Fa in plain text); the three actions close the page in their own panel, ranked.\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 — five views compare best side by side on one screen.\n\n## Step 7 — Offer to save, once\n\nAfter presenting, offer once to save the pulse as a file or post it to Slack. Posting to Slack is an outward write, so it only happens on that explicit yes — the offer is the approval gate. If yes, do it. If no or no response, move on. Do not ask twice.\n\nThen close with what the pulse found in one line, plus the single most relevant next step and at most two others nearby:\n\n- If the actions point at content or promotion: \"what should I promote\" runs `content-strategy`.\n- If the funnel is the problem: \"fill my funnel\" runs `\u002Fgrow-pipeline`.\n- For the finance-side twin: \"how's the business doing\" runs `business-pulse`.\n\nMax three offers. Never repeat an offer the owner declined this session.\n\n## Scope variants\n\nOwners often want a slice rather than the whole pulse:\n\n- **\"How did the campaign do\"** — campaign return only, plus the sentiment check\n- **\"How's the pipeline\"** — funnel conversion and stalled deals only\n- **\"What's selling\"** — product performance only\n- **\"Are we getting reviews\"** — sentiment only\n- **\"Where should I spend next month\"** — channel trend and campaign return, with the three actions weighted toward budget\n\nGive them the slice they asked for. Don't force the full pulse on a narrow question.\n\n## What not to do\n\n- **Do not ask permission before pulling data.** The skill was invoked. Run it.\n- **Do not invent attribution.** If a campaign's revenue can't be traced, say the attribution is unavailable rather than assigning revenue on a guess. Fake attribution has moved real budgets.\n- **Do not report CRM forecast value as revenue.** Deal values are hopes; invoices are facts. Label which is which.\n- **Do not double-count across sources.** A Shopify order settled in Stripe is one sale. Pick one revenue source and name it.\n- **Do not double-count inside one source.** The sales-by-customer summary returns both a parent summary row and a separate total row for the same customer. Filter rows marked as totals before you rank customers or compute concentration, or the same customer lands in the list twice and the concentration figure comes out too high.\n- **Do not manufacture urgency.** If growth is steady, the pulse should read as steady.\n- **Do not read expenses or margin from the QuickBooks P&L summary.** Total the rows (`..\u002F..\u002Fshared\u002Fquickbooks-report-traps.md`, Trap 2).\n\n## Reference files\n\n- `reference\u002Fdata_sources.md` — connector to metric mapping, with fallbacks\n- `reference\u002Fthresholds.md` — status cutoffs for each of the five views\n- `reference\u002Foutput_template.md` — exact output structure\n- `reference\u002Fgotchas.md` — the failure modes that produce confidently wrong growth advice\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":54,"tools":55,"source":56,"license":14,"description":7,"source_path":57,"source_commit":58},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","small-business\u002Fskills\u002Fgrowth-pulse","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fgrowth-pulse",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-14 03:30:52",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add monoes\u002Fmonomind --skill growth-pulse",{"tool":74,"command":75},"bunx","bunx skills add monoes\u002Fmonomind --skill growth-pulse",{"tool":77,"command":78},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill growth-pulse","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fgrowth-pulse\u002FSKILL.md",true,[82,87,93,97,101],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"reference\u002Fdata_sources.md","REFERENCE","参考文档",5770,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fgrowth-pulse\u002Freference\u002Fdata_sources.md",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"reference\u002Fgotchas.md",4999,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fgrowth-pulse\u002Freference\u002Fgotchas.md",{"path":98,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":99,"sourceHtmlUrl":100},"reference\u002Foutput_template.md",3789,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fgrowth-pulse\u002Freference\u002Foutput_template.md",{"path":102,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":103,"sourceHtmlUrl":104},"reference\u002Fthresholds.md",2945,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fgrowth-pulse\u002Freference\u002Fthresholds.md",[106,133,165,191,216,242],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":132},"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",[],[113,114,115,116,117,118,119,42,120,121,122,123,124,125,126,127,128,129,130,131],"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":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":137,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":147,"publishedAt":132},"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",[141,144],{"categoryNo":142,"categoryName":143,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":145,"categoryName":146,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[148,149,150,117,151,152,40,153,121,154,155,156,157,158,159,160,161,162,163,164],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":169,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":132},"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",[172],{"categoryNo":173,"categoryName":174,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理",[158,176,177,178,179,42,180,40,181,182,36,157,183,184,185,186,187,188,189,190],"write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":195,"sourceHtmlUrl":196,"categories":197,"keywords":201,"publishedAt":132},"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",[198],{"categoryNo":199,"categoryName":200,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[121,158,202,203,204,205,42,189,40,206,207,208,209,36,210,211,212,213,214,215],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":228,"publishedAt":132},"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",[222,225],{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":226,"categoryName":227,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[229,230,231,232,204,44,233,234,235,120,236,237,238,121,124,210,239,240,241,212],"Workflow Automation","automation","workflow","parallel","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":246,"categories":247,"keywords":249,"publishedAt":132},"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",[248],{"categoryNo":226,"categoryName":227,"taxonomyType":21,"taxonomyTypeDesc":22},[231,250,251,252,253,254,255,204,256,257,154,258,259,260,124,210,261,262,212,263],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]