[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGCS7KKNED4MTF0DBDS2AR":3,"skill-same:01M6MGCS7KKNED4MTF0DBDS2AR":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":13,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6MGCS7KKNED4MTF0DBDS2AR","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.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-marketing-context-skill-caec9f63\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"marketing","context","marketing context","guide","at","my","information","icp","project","across","positioning","maintain","up","customer","read","SET","start","run","create","tasks","2026-11-10 10:12:30",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":14,"metadata":56,"description":7},{"author":57,"updated":58,"version":59,"category":31},"Alireza Rezvani",1772755200000,"1.0.0","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-marketing-context-skill-caec9f63","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill marketing-context",{"tool":72,"command":73},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill marketing-context",{"tool":75,"command":76},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill marketing-context","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-marketing-context-skill-caec9f63\u002FSKILL.md",true,[],[81,107,132,163,190,221],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":51},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[83,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":51},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[115,116,117,118,119,120,48,121,122,123,124,125,126,127,128,129,130,36,35,131],"vardoger analyze","analyze","directory","cli","github copilot","copilot","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","copilot instructions",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":144,"publishedAt":51},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[138,141],{"categoryNo":139,"categoryName":140,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":142,"categoryName":143,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[145,146,147,148,149,150,151,152,153,154,155,156,157,100,158,159,160,161,105,162],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":51},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[173,46,174,175,176,177,178,179,180,100,181,182,183,184,185,186,187,188,189,105],"terraform","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":205,"publishedAt":51},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[196,199,202],{"categoryNo":197,"categoryName":198,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":200,"categoryName":201,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":203,"categoryName":204,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000038","人力资源",[206,207,208,209,210,50,211,212,116,213,100,43,214,215,216,217,218,219,105,220],"search","Job Search","technical job search","technical","writing","email","parsing","interview","engineer","general","activate","do","task","cv","letter",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":227,"publishedAt":51},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[228,229,44,230,231,209,232,100,217,233,234,235,236,237,238,239,240,241,105,242],"steno mode","mode","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]