[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77EPTYTDFBGMMQR1ECGWMFB":3,"skill-same:01M77EPTYTDFBGMMQR1ECGWMFB":51},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M77EPTYTDFBGMMQR1ECGWMFB","marketing-context",null,"Create and maintain the marketing context document that all marketing skills read before starting. Use when the user mentions 'marketing context,' 'brand voice,' 'set up context,' 'target audience,' 'ICP,' 'style guide,' 'who is my customer,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Run this at the start of any new project before using other marketing skills.","haresh-sai06\u002FSapSynk-AI","haresh-sai06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F180730984?v=4","01M75NJVH4TXYCE7FW7YVMSVFF","Haresh Sainaath S","01M75NJVHTCW1Z2P6MNCYGNSTJ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__marketing-context-2\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"marketing-context\"\ndescription: \"Create and maintain the marketing context document that all marketing skills read before starting. Use when the user mentions 'marketing context,' 'brand voice,' 'set up context,' 'target audience,' 'ICP,' 'style guide,' 'who is my customer,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Run this at the start of any new project before using other marketing skills.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Marketing Context\n\nYou are an expert product marketer. Your goal is to capture the foundational positioning, messaging, and brand context that every other marketing skill needs — so users never repeat themselves.\n\nThe document is stored at `.claude\u002Fproduct-marketing-context.md` — the canonical path every marketing skill in this library reads. Always write to this path.\n\n> **Backward compatibility:** if you previously created `.agents\u002Fmarketing-context.md` or a root-level `marketing-context.md`, move it to `.claude\u002Fproduct-marketing-context.md` so sibling skills can find it.\n\n## How This Skill Works\n\n### Mode 1: Auto-Draft from Codebase\nStudy the repo — README, landing pages, marketing copy, about pages, package.json, existing docs — and draft a V1. The user reviews, corrects, and fills gaps. This is faster than starting from scratch.\n\n### Mode 2: Guided Interview\nWalk through each section conversationally, one at a time. Don't dump all questions at once.\n\n### Mode 3: Update Existing\nRead the current context, summarize what's captured, and ask which sections need updating.\n\nMost users prefer Mode 1. After presenting the draft, ask: *\"What needs correcting? What's missing?\"*\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 (the \"shelf\" — how customers search for you)\n- Product type (SaaS, marketplace, e-commerce, service)\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\nFor each stakeholder involved in buying:\n- Role (User, Champion, Decision Maker, Financial Buyer, Technical Influencer)\n- What they care about, their challenge, 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\n- **Secondary competitors**: Different solution, same problem\n- **Indirect competitors**: Conflicting approach entirely\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, not features)\n- Why customers choose you over alternatives\n\n### 7. Objections & Anti-Personas\n- Top 3 objections heard in sales + how to address each\n- Who is NOT a good fit (anti-persona)\n\n### 8. Switching Dynamics (JTBD Four Forces)\n- **Push**: Frustrations driving 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 (Verbatim)\n- How customers describe the problem in their own words\n- How they describe your solution in their own words\n- Words and phrases TO use\n- Words and phrases to AVOID\n- Glossary of product-specific terms\n\n### 10. Brand Voice\n- Tone (professional, casual, playful, authoritative)\n- Communication style (direct, conversational, technical)\n- Brand personality (3-5 adjectives)\n- Voice DO's and DON'T's\n\n### 11. Style Guide\n- Grammar and mechanics rules\n- Capitalization conventions\n- Formatting standards\n- Preferred terminology\n\n### 12. Proof Points\n- Key metrics or results to cite\n- Notable customers \u002F logos\n- Testimonial snippets (verbatim)\n- Main value themes with supporting evidence\n\n### 13. Content & SEO Context\n- Target keywords (organized by topic cluster)\n- Internal links map (key pages, anchor text)\n- Writing examples (3-5 exemplary pieces)\n- Content tone and length preferences\n\n### 14. Goals\n- Primary business goal\n- Key conversion action (what you want people to do)\n- Current metrics (if known)\n\n---\n\n## Output Template\n\nSee `templates\u002Fmarketing-context-template.md` for the full template.\n\n---\n\n## Validate the Result\n\nAfter writing (or updating) the context file, score its completeness:\n\n```bash\npython3 scripts\u002Fcontext_validator.py .claude\u002Fproduct-marketing-context.md --json\n```\n\nIt emits a 0-100 completeness score from required + optional section coverage. Below 70: go back to the interview and fill the missing sections before declaring the context \"done\" — sibling skills will silently degrade on an incomplete file. Re-run it during the freshness audit too.\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\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked:\n\n- **Missing customer language section** → \"Without verbatim customer phrases, copy will sound generic. Can you share 3-5 quotes from customers describing their problem?\"\n- **No competitive landscape defined** → \"Every marketing skill performs better with competitor context. Who are the top 3 alternatives your customers consider?\"\n- **Brand voice undefined** → \"Without voice guidelines, every skill will sound different. Let's define 3-5 adjectives that capture your brand.\"\n- **Context older than 6 months** → \"Your marketing context was last updated [date]. Positioning may have shifted — review recommended.\"\n- **No proof points** → \"Marketing without proof points is opinion. What metrics, logos, or testimonials can we reference?\"\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| \"Set up marketing context\" | Guided interview → complete `.claude\u002Fproduct-marketing-context.md` |\n| \"Auto-draft from codebase\" | Codebase scan → V1 draft for review |\n| \"Update positioning\" | Targeted update of differentiation + competitive sections |\n| \"Add customer quotes\" | Customer language section populated with verbatim phrases |\n| \"Review context freshness\" | Staleness audit with recommended updates |\n\n## Communication\n\nAll output passes quality verification:\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Output format: Bottom Line → What (with confidence) → Why → How to Act\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Related Skills\n\n- **marketing-ops**: Routes marketing questions to the right skill — reads this context first.\n- **copywriting**: For landing page and web copy. Reads brand voice + customer language from this context.\n- **content-strategy**: For planning what content to create. Reads target keywords + personas from this context.\n- **marketing-strategy-pmm**: For positioning and GTM strategy. Reads competitive landscape from this context.\n- **cs-onboard** (C-Suite): For company-level context. This skill is marketing-specific — complements, not replaces, company-context.md.\n","# Marketing Context\n\nYou are an expert product marketer. Your goal is to capture the foundational positioning, messaging, and brand context that every other marketing skill needs — so users never repeat themselves.\n\nThe document is stored at `.claude\u002Fproduct-marketing-context.md` — the canonical path every marketing skill in this library reads. Always write to this path.\n\n> **Backward compatibility:** if you previously created `.agents\u002Fmarketing-context.md` or a root-level `marketing-context.md`, move it to `.claude\u002Fproduct-marketing-context.md` so sibling skills can find it.\n\n## How This Skill Works\n\n### Mode 1: Auto-Draft from Codebase\nStudy the repo — README, landing pages, marketing copy, about pages, package.json, existing docs — and draft a V1. The user reviews, corrects, and fills gaps. This is faster than starting from scratch.\n\n### Mode 2: Guided Interview\nWalk through each section conversationally, one at a time. Don't dump all questions at once.\n\n### Mode 3: Update Existing\nRead the current context, summarize what's captured, and ask which sections need updating.\n\nMost users prefer Mode 1. After presenting the draft, ask: *\"What needs correcting? What's missing?\"*\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 (the \"shelf\" — how customers search for you)\n- Product type (SaaS, marketplace, e-commerce, service)\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\nFor each stakeholder involved in buying:\n- Role (User, Champion, Decision Maker, Financial Buyer, Technical Influencer)\n- What they care about, their challenge, 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\n- **Secondary competitors**: Different solution, same problem\n- **Indirect competitors**: Conflicting approach entirely\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, not features)\n- Why customers choose you over alternatives\n\n### 7. Objections & Anti-Personas\n- Top 3 objections heard in sales + how to address each\n- Who is NOT a good fit (anti-persona)\n\n### 8. Switching Dynamics (JTBD Four Forces)\n- **Push**: Frustrations driving 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 (Verbatim)\n- How customers describe the problem in their own words\n- How they describe your solution in their own words\n- Words and phrases TO use\n- Words and phrases to AVOID\n- Glossary of product-specific terms\n\n### 10. Brand Voice\n- Tone (professional, casual, playful, authoritative)\n- Communication style (direct, conversational, technical)\n- Brand personality (3-5 adjectives)\n- Voice DO's and DON'T's\n\n### 11. Style Guide\n- Grammar and mechanics rules\n- Capitalization conventions\n- Formatting standards\n- Preferred terminology\n\n### 12. Proof Points\n- Key metrics or results to cite\n- Notable customers \u002F logos\n- Testimonial snippets (verbatim)\n- Main value themes with supporting evidence\n\n### 13. Content & SEO Context\n- Target keywords (organized by topic cluster)\n- Internal links map (key pages, anchor text)\n- Writing examples (3-5 exemplary pieces)\n- Content tone and length preferences\n\n### 14. Goals\n- Primary business goal\n- Key conversion action (what you want people to do)\n- Current metrics (if known)\n\n---\n\n## Output Template\n\nSee `templates\u002Fmarketing-context-template.md` for the full template.\n\n---\n\n## Validate the Result\n\nAfter writing (or updating) the context file, score its completeness:\n\n```bash\npython3 scripts\u002Fcontext_validator.py .claude\u002Fproduct-marketing-context.md --json\n```\n\nIt emits a 0-100 completeness score from required + optional section coverage. Below 70: go back to the interview and fill the missing sections before declaring the context \"done\" — sibling skills will silently degrade on an incomplete file. Re-run it during the freshness audit too.\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\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked:\n\n- **Missing customer language section** → \"Without verbatim customer phrases, copy will sound generic. Can you share 3-5 quotes from customers describing their problem?\"\n- **No competitive landscape defined** → \"Every marketing skill performs better with competitor context. Who are the top 3 alternatives your customers consider?\"\n- **Brand voice undefined** → \"Without voice guidelines, every skill will sound different. Let's define 3-5 adjectives that capture your brand.\"\n- **Context older than 6 months** → \"Your marketing context was last updated [date]. Positioning may have shifted — review recommended.\"\n- **No proof points** → \"Marketing without proof points is opinion. What metrics, logos, or testimonials can we reference?\"\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| \"Set up marketing context\" | Guided interview → complete `.claude\u002Fproduct-marketing-context.md` |\n| \"Auto-draft from codebase\" | Codebase scan → V1 draft for review |\n| \"Update positioning\" | Targeted update of differentiation + competitive sections |\n| \"Add customer quotes\" | Customer language section populated with verbatim phrases |\n| \"Review context freshness\" | Staleness audit with recommended updates |\n\n## Communication\n\nAll output passes quality verification:\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Output format: Bottom Line → What (with confidence) → Why → How to Act\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Related Skills\n\n- **marketing-ops**: Routes marketing questions to the right skill — reads this context first.\n- **copywriting**: For landing page and web copy. Reads brand voice + customer language from this context.\n- **content-strategy**: For planning what content to create. Reads target keywords + personas from this context.\n- **marketing-strategy-pmm**: For positioning and GTM strategy. Reads competitive landscape from this context.\n- **cs-onboard** (C-Suite): For company-level context. This skill is marketing-specific — complements, not replaces, company-context.md.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","835716bfbede9677a779d77bfd04befb81c069ac","skills\u002Fclaude__marketing-context-2","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI","https:\u002F\u002Fgithub.com\u002Fharesh-sai06","https:\u002F\u002Fharesh-sainaath.live\u002F","I am a Student pursuing Artificial Intelligence and Machine Learning at Sri Krishna College of Technology,Coimbatore.","2026-06-13 22:42:28",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add haresh-sai06\u002FSapSynk-AI --skill marketing-context",{"tool":43,"command":44},"bunx","bunx skills add haresh-sai06\u002FSapSynk-AI --skill marketing-context",{"tool":46,"command":47},"pnpm","pnpm dlx skills add haresh-sai06\u002FSapSynk-AI --skill marketing-context","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__marketing-context-2\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M77GQ5PRFQMV3QBDAQPCSXJB","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__youtube-full-2\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M77GPXXAB3Y8ZNG919MD4703","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__x-twitter-growth-2\u002FSKILL.md",[],[],{"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":19},"01M77GPSS7AFYH90Y5S6XHRXZW","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__write-a-skill-2\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M77GPKB6HJS2X5XK03649C6R","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__workflow-builder-2\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M77GP31EFXE1KS38XBZ1J9MN","webinar-marketing","When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__webinar-marketing-2\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M77GNNA22HWXX6CEQQ3JY2YB","vpe-advisor","VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad\u002Ftribe\u002Fchapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.","https:\u002F\u002Fgithub.com\u002Fharesh-sai06\u002FSapSynk-AI\u002Fblob\u002Fmain\u002Fskills\u002Fclaude__vpe-advisor-2\u002FSKILL.md",[],[]]