[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NKY7VFWMZYZXFPD1XEG8W":3,"skill-same:01M71NKY7VFWMZYZXFPD1XEG8W":91},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":70,"ownerDescription":6,"updatedAt":71,"install":72,"resources":85},"01M71NKY7VFWMZYZXFPD1XEG8W","product-marketing-context",null,"Use when creating or updating the shared product marketing context doc: positioning, ICP, personas, messaging and verbatim customer language. Stored at .agents\u002Fproduct-marketing.md; auto-drafts from the codebase or interviews section by section; other marketing skills read this file first.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fproduct-marketing-context\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fproduct-marketing-context\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"product","marketing","context","product marketing","marketing context","product marketing context","section","customer-research","doc","interviews","drafts","read","at","customer","when","positioning","auto","icp","messaging","shared","2026-11-10 10:56:23",false,"---\nname: product-marketing-context\ndescription: \"Use when creating or updating the shared product marketing context doc: positioning, ICP, personas, messaging and verbatim customer language. Stored at .agents\u002Fproduct-marketing.md; auto-drafts from the codebase or interviews section by section; other marketing skills read this file first.\"\ntags: [\"marketing\",\"product\",\"strategy\",\"customer-research\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\nsource_path: \"skills\u002Fproduct-marketing\"\nsource_commit: 5b2c0007766c6a1cf1d53fd8fc73e979e0821022\n---\n# Product Marketing Context\n\nYou help users create and maintain a product marketing context document. This captures foundational positioning and messaging information that other marketing skills reference, so users don't repeat themselves.\n\nThe document is stored at `.agents\u002Fproduct-marketing.md`.\n\n## Workflow\n\n### Step 1: Check for Existing Context\n\nFirst, check if `.agents\u002Fproduct-marketing.md` already exists. Also check `.claude\u002Fproduct-marketing.md` and the legacy filename `product-marketing-context.md` (in either `.agents\u002F` or `.claude\u002F`) for older setups — if found anywhere other than `.agents\u002Fproduct-marketing.md`, offer to move it to the canonical location.\n\n**If it exists:**\n- Read it and summarize what's captured — note its current **Document version** and the last few **Changelog** entries so the user sees where the doc stands and what's changed recently\n- Ask which sections they want to update\n- Only gather info for those sections\n- On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of *what changed and why* is worth keeping.\n\n**If it doesn't exist, offer two options:**\n\n1. **Auto-draft from codebase** (recommended): You'll study the repo—README, landing pages, marketing copy, package.json, etc.—and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch.\n\n2. **Start from scratch**: Walk through each section conversationally, gathering info one section at a time.\n\nMost users prefer option 1. After presenting the draft, ask: \"What needs correcting? What's missing?\"\n\n### Step 2: Gather Information\n\n**If auto-drafting:**\n1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs\n2. Draft all sections based on what you find\n3. Present the draft and ask what needs correcting or is missing\n4. Iterate until the user is satisfied\n\n**If starting from scratch:**\nWalk through each section below conversationally, one at a time. Don't dump all questions at once.\n\nFor each section:\n1. Briefly explain what you're capturing\n2. Ask relevant questions\n3. Confirm accuracy\n4. Move to the next\n\nPush for verbatim customer language — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes copy more resonant.\n\n---\n\n## Sections to Capture\n\n### 1. Product Overview\n- One-line description\n- What it does (2-3 sentences)\n- Product category (what \"shelf\" you sit on—how customers search for you)\n- Product type (SaaS, marketplace, e-commerce, service, etc.)\n- Business model and pricing\n\n### 2. Target Audience\n- Target company type (industry, size, stage)\n- Target decision-makers (roles, departments)\n- Primary use case (the main problem you solve)\n- Jobs to be done (2-3 things customers \"hire\" you for)\n- Specific use cases or scenarios\n\n### 3. Personas (B2B only)\nIf multiple stakeholders are involved in buying, capture for each:\n- User, Champion, Decision Maker, Financial Buyer, Technical Influencer\n- What each cares about, their challenge, and the value you promise them\n\n### 4. Problems & Pain Points\n- Core challenge customers face before finding you\n- Why current solutions fall short\n- What it costs them (time, money, opportunities)\n- Emotional tension (stress, fear, doubt)\n\n### 5. Competitive Landscape\n- **Direct competitors**: Same solution, same problem (e.g., Calendly vs SavvyCal)\n- **Secondary competitors**: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)\n- **Indirect competitors**: Conflicting approach (e.g., Calendly vs personal assistant)\n- How each falls short for customers\n\n### 6. Differentiation\n- Key differentiators (capabilities alternatives lack)\n- How you solve it differently\n- Why that's better (benefits)\n- Why customers choose you over alternatives\n\n### 7. Objections & Anti-Personas\n- Top 3 objections heard in sales and how to address them\n- Who is NOT a good fit (anti-persona)\n\n### 8. Switching Dynamics\nThe JTBD Four Forces:\n- **Push**: What frustrations drive them away from current solution\n- **Pull**: What attracts them to you\n- **Habit**: What keeps them stuck with current approach\n- **Anxiety**: What worries them about switching\n\n### 9. Customer Language\n- How customers describe the problem (verbatim)\n- How they describe your solution (verbatim)\n- Words\u002Fphrases to use\n- Words\u002Fphrases to avoid\n- Glossary of product-specific terms\n\n### 10. Brand Voice\n- Tone (professional, casual, playful, etc.)\n- Communication style (direct, conversational, technical)\n- Brand personality (3-5 adjectives)\n\n### 11. Proof Points\n- Key metrics or results to cite\n- Notable customers\u002Flogos\n- Testimonial snippets\n- Main value themes and supporting evidence\n\n### 12. Goals\n- Primary business goal\n- Key conversion action (what you want people to do)\n- Current metrics (if known)\n\n---\n\n## Step 3: Create the Document\n\nAfter gathering information, create `.agents\u002Fproduct-marketing.md` with this structure:\n\n```markdown\n# Product Marketing Context\n\n**Document version:** v1\n**Last updated:** [date]\n\n## Product Overview\n**One-liner:**\n**What it does:**\n**Product category:**\n**Product type:**\n**Business model:**\n\n## Target Audience\n**Target companies:**\n**Decision-makers:**\n**Primary use case:**\n**Jobs to be done:**\n-\n**Use cases:**\n-\n\n## Personas\n| Persona | Cares about | Challenge | Value we promise |\n|---------|-------------|-----------|------------------|\n| | | | |\n\n## Problems & Pain Points\n**Core problem:**\n**Why alternatives fall short:**\n-\n**What it costs them:**\n**Emotional tension:**\n\n## Competitive Landscape\n**Direct:** [Competitor] — falls short because...\n**Secondary:** [Approach] — falls short because...\n**Indirect:** [Alternative] — falls short because...\n\n## Differentiation\n**Key differentiators:**\n-\n**How we do it differently:**\n**Why that's better:**\n**Why customers choose us:**\n\n## Objections\n| Objection | Response |\n|-----------|----------|\n| | |\n\n**Anti-persona:**\n\n## Switching Dynamics\n**Push:**\n**Pull:**\n**Habit:**\n**Anxiety:**\n\n## Customer Language\n**How they describe the problem:**\n- \"[verbatim]\"\n**How they describe us:**\n- \"[verbatim]\"\n**Words to use:**\n**Words to avoid:**\n**Glossary:**\n| Term | Meaning |\n|------|---------|\n| | |\n\n## Brand Voice\n**Tone:**\n**Style:**\n**Personality:**\n\n## Proof Points\n**Metrics:**\n**Customers:**\n**Testimonials:**\n> \"[quote]\" — [who]\n**Value themes:**\n| Theme | Proof |\n|-------|-------|\n| | |\n\n## Goals\n**Business goal:**\n**Conversion action:**\n**Current metrics:**\n\n## Changelog\n*Newest first. One line per revision: what changed and why.*\n- v1 ([date]) — Initial context.\n```\n\n---\n\n## Step 4: Confirm, Version, and Save\n\n- Show the completed document\n- Ask if anything needs adjustment\n- **Set the version and changelog** — this is the paper trail for a doc every other skill reads:\n  - **New document:** set `Document version: v1` and a single Changelog entry — `- v1 ([today]) — Initial context.`\n  - **Updating an existing document:** increment the version (v2 → v3 …), update `Last updated` to today, and **prepend a new Changelog entry** at the top of the list (newest first) summarizing *what changed and why* in one line. Never rewrite or reorder past entries.\n  - A good entry names the sections touched and the reason, not \"updated the doc.\" Examples:\n    - `- v3 (2026-07-16) — Repositioned from \"email tool\" to \"deliverability platform\"; added RevOps to the ICP.`\n    - `- v2 (2026-06-02) — Rewrote value prop and objections after 5 customer interviews; added competitor Acme.`\n  - Use today's date in ISO form (YYYY-MM-DD) for the entry and `Last updated`.\n  - **Pure typo-only fix:** don't bump the version or add a changelog entry — just save the correction. Every other change bumps the version and gets an entry. When the change is a real repositioning, say so plainly — downstream skills will now generate against the new context.\n- Save to `.agents\u002Fproduct-marketing.md`\n- Tell them: \"Other marketing skills will now use this context automatically. The Changelog at the bottom tracks every revision — check it to see how your positioning has evolved. Run `\u002Fproduct-marketing` anytime to update it.\"\n\n---\n\n## Tips\n\n- **Be specific**: Ask \"What's the #1 frustration that brings them to you?\" not \"What problem do they solve?\"\n- **Capture exact words**: Customer language beats polished descriptions\n- **Ask for examples**: \"Can you give me an example?\" unlocks better answers\n- **Validate as you go**: Summarize each section and confirm before moving on\n- **Skip what doesn't apply**: Not every product needs all sections (e.g., Personas for B2C)\n","# Product Marketing Context\n\nYou help users create and maintain a product marketing context document. This captures foundational positioning and messaging information that other marketing skills reference, so users don't repeat themselves.\n\nThe document is stored at `.agents\u002Fproduct-marketing.md`.\n\n## Workflow\n\n### Step 1: Check for Existing Context\n\nFirst, check if `.agents\u002Fproduct-marketing.md` already exists. Also check `.claude\u002Fproduct-marketing.md` and the legacy filename `product-marketing-context.md` (in either `.agents\u002F` or `.claude\u002F`) for older setups — if found anywhere other than `.agents\u002Fproduct-marketing.md`, offer to move it to the canonical location.\n\n**If it exists:**\n- Read it and summarize what's captured — note its current **Document version** and the last few **Changelog** entries so the user sees where the doc stands and what's changed recently\n- Ask which sections they want to update\n- Only gather info for those sections\n- On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of *what changed and why* is worth keeping.\n\n**If it doesn't exist, offer two options:**\n\n1. **Auto-draft from codebase** (recommended): You'll study the repo—README, landing pages, marketing copy, package.json, etc.—and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch.\n\n2. **Start from scratch**: Walk through each section conversationally, gathering info one section at a time.\n\nMost users prefer option 1. After presenting the draft, ask: \"What needs correcting? What's missing?\"\n\n### Step 2: Gather Information\n\n**If auto-drafting:**\n1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs\n2. Draft all sections based on what you find\n3. Present the draft and ask what needs correcting or is missing\n4. Iterate until the user is satisfied\n\n**If starting from scratch:**\nWalk through each section below conversationally, one at a time. Don't dump all questions at once.\n\nFor each section:\n1. Briefly explain what you're capturing\n2. Ask relevant questions\n3. Confirm accuracy\n4. Move to the next\n\nPush for verbatim customer language — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes copy more resonant.\n\n---\n\n## Sections to Capture\n\n### 1. Product Overview\n- One-line description\n- What it does (2-3 sentences)\n- Product category (what \"shelf\" you sit on—how customers search for you)\n- Product type (SaaS, marketplace, e-commerce, service, etc.)\n- Business model and pricing\n\n### 2. Target Audience\n- Target company type (industry, size, stage)\n- Target decision-makers (roles, departments)\n- Primary use case (the main problem you solve)\n- Jobs to be done (2-3 things customers \"hire\" you for)\n- Specific use cases or scenarios\n\n### 3. Personas (B2B only)\nIf multiple stakeholders are involved in buying, capture for each:\n- User, Champion, Decision Maker, Financial Buyer, Technical Influencer\n- What each cares about, their challenge, and the value you promise them\n\n### 4. Problems & Pain Points\n- Core challenge customers face before finding you\n- Why current solutions fall short\n- What it costs them (time, money, opportunities)\n- Emotional tension (stress, fear, doubt)\n\n### 5. Competitive Landscape\n- **Direct competitors**: Same solution, same problem (e.g., Calendly vs SavvyCal)\n- **Secondary competitors**: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)\n- **Indirect competitors**: Conflicting approach (e.g., Calendly vs personal assistant)\n- How each falls short for customers\n\n### 6. Differentiation\n- Key differentiators (capabilities alternatives lack)\n- How you solve it differently\n- Why that's better (benefits)\n- Why customers choose you over alternatives\n\n### 7. Objections & Anti-Personas\n- Top 3 objections heard in sales and how to address them\n- Who is NOT a good fit (anti-persona)\n\n### 8. Switching Dynamics\nThe JTBD Four Forces:\n- **Push**: What frustrations drive them away from current solution\n- **Pull**: What attracts them to you\n- **Habit**: What keeps them stuck with current approach\n- **Anxiety**: What worries them about switching\n\n### 9. Customer Language\n- How customers describe the problem (verbatim)\n- How they describe your solution (verbatim)\n- Words\u002Fphrases to use\n- Words\u002Fphrases to avoid\n- Glossary of product-specific terms\n\n### 10. Brand Voice\n- Tone (professional, casual, playful, etc.)\n- Communication style (direct, conversational, technical)\n- Brand personality (3-5 adjectives)\n\n### 11. Proof Points\n- Key metrics or results to cite\n- Notable customers\u002Flogos\n- Testimonial snippets\n- Main value themes and supporting evidence\n\n### 12. Goals\n- Primary business goal\n- Key conversion action (what you want people to do)\n- Current metrics (if known)\n\n---\n\n## Step 3: Create the Document\n\nAfter gathering information, create `.agents\u002Fproduct-marketing.md` with this structure:\n\n```markdown\n# Product Marketing Context\n\n**Document version:** v1\n**Last updated:** [date]\n\n## Product Overview\n**One-liner:**\n**What it does:**\n**Product category:**\n**Product type:**\n**Business model:**\n\n## Target Audience\n**Target companies:**\n**Decision-makers:**\n**Primary use case:**\n**Jobs to be done:**\n-\n**Use cases:**\n-\n\n## Personas\n| Persona | Cares about | Challenge | Value we promise |\n|---------|-------------|-----------|------------------|\n| | | | |\n\n## Problems & Pain Points\n**Core problem:**\n**Why alternatives fall short:**\n-\n**What it costs them:**\n**Emotional tension:**\n\n## Competitive Landscape\n**Direct:** [Competitor] — falls short because...\n**Secondary:** [Approach] — falls short because...\n**Indirect:** [Alternative] — falls short because...\n\n## Differentiation\n**Key differentiators:**\n-\n**How we do it differently:**\n**Why that's better:**\n**Why customers choose us:**\n\n## Objections\n| Objection | Response |\n|-----------|----------|\n| | |\n\n**Anti-persona:**\n\n## Switching Dynamics\n**Push:**\n**Pull:**\n**Habit:**\n**Anxiety:**\n\n## Customer Language\n**How they describe the problem:**\n- \"[verbatim]\"\n**How they describe us:**\n- \"[verbatim]\"\n**Words to use:**\n**Words to avoid:**\n**Glossary:**\n| Term | Meaning |\n|------|---------|\n| | |\n\n## Brand Voice\n**Tone:**\n**Style:**\n**Personality:**\n\n## Proof Points\n**Metrics:**\n**Customers:**\n**Testimonials:**\n> \"[quote]\" — [who]\n**Value themes:**\n| Theme | Proof |\n|-------|-------|\n| | |\n\n## Goals\n**Business goal:**\n**Conversion action:**\n**Current metrics:**\n\n## Changelog\n*Newest first. One line per revision: what changed and why.*\n- v1 ([date]) — Initial context.\n```\n\n---\n\n## Step 4: Confirm, Version, and Save\n\n- Show the completed document\n- Ask if anything needs adjustment\n- **Set the version and changelog** — this is the paper trail for a doc every other skill reads:\n  - **New document:** set `Document version: v1` and a single Changelog entry — `- v1 ([today]) — Initial context.`\n  - **Updating an existing document:** increment the version (v2 → v3 …), update `Last updated` to today, and **prepend a new Changelog entry** at the top of the list (newest first) summarizing *what changed and why* in one line. Never rewrite or reorder past entries.\n  - A good entry names the sections touched and the reason, not \"updated the doc.\" Examples:\n    - `- v3 (2026-07-16) — Repositioned from \"email tool\" to \"deliverability platform\"; added RevOps to the ICP.`\n    - `- v2 (2026-06-02) — Rewrote value prop and objections after 5 customer interviews; added competitor Acme.`\n  - Use today's date in ISO form (YYYY-MM-DD) for the entry and `Last updated`.\n  - **Pure typo-only fix:** don't bump the version or add a changelog entry — just save the correction. Every other change bumps the version and gets an entry. When the change is a real repositioning, say so plainly — downstream skills will now generate against the new context.\n- Save to `.agents\u002Fproduct-marketing.md`\n- Tell them: \"Other marketing skills will now use this context automatically. The Changelog at the bottom tracks every revision — check it to see how your positioning has evolved. Run `\u002Fproduct-marketing` anytime to update it.\"\n\n---\n\n## Tips\n\n- **Be specific**: Ask \"What's the #1 frustration that brings them to you?\" not \"What problem do they solve?\"\n- **Capture exact words**: Customer language beats polished descriptions\n- **Ask for examples**: \"Can you give me an example?\" unlocks better answers\n- **Validate as you go**: Summarize each section and confirm before moving on\n- **Skip what doesn't apply**: Not every product needs all sections (e.g., Personas for B2C)\n",{"name":5,"tags":57,"tools":59,"source":60,"license":14,"description":7,"source_path":61,"source_commit":62},[33,32,58,39],"strategy",[],"https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills","skills\u002Fproduct-marketing","5b2c0007766c6a1cf1d53fd8fc73e979e0821022","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fproduct-marketing-context",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":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add monoes\u002Fmonomind --skill product-marketing-context",{"tool":78,"command":79},"bunx","bunx skills add monoes\u002Fmonomind --skill product-marketing-context",{"tool":81,"command":82},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill product-marketing-context","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fproduct-marketing-context\u002FSKILL.md",true,[86],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1069,[92,121,150,175,200,227],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":120},"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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":134,"publishedAt":120},"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.","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",[128,131],{"categoryNo":129,"categoryName":130,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":132,"categoryName":133,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[135,136,137,104,138,139,46,140,109,141,142,143,32,144,145,146,147,148,34,149],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","write","commands","paths","suggest","coding","ZeRO",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":154,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":120},"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",[157],{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[144,159,160,161,162,107,163,46,164,165,166,32,167,168,169,170,171,172,173,174],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":179,"sourceHtmlUrl":180,"categories":181,"keywords":185,"publishedAt":120},"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",[182],{"categoryNo":183,"categoryName":184,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[109,144,186,187,188,189,107,173,46,190,191,192,193,166,194,195,196,197,198,199],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":212,"publishedAt":120},"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",[206,209],{"categoryNo":207,"categoryName":208,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":210,"categoryName":211,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[213,214,215,216,188,217,218,219,220,108,221,222,223,109,112,194,224,225,226,196],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":231,"categories":232,"keywords":234,"publishedAt":120},"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",[233],{"categoryNo":210,"categoryName":211,"taxonomyType":21,"taxonomyTypeDesc":22},[215,235,236,237,238,239,240,188,241,242,141,243,244,245,112,194,246,247,196,248],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]