[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MZJ87HAQW9HTV9P612VR34":3,"skill-same:01M6MZJ87HAQW9HTV9P612VR34":67},{"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":17,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6MZJ87HAQW9HTV9P612VR34","gtm",null,"Activate for: go to market, GTM, GTM strategy, go-to-market, ICP, ideal customer profile, target customer, who to sell to, channel strategy, sales channel, how to acquire customers, customer acquisition, outreach strategy, LinkedIn outreach, cold email, sales process, sales funnel, pricing strategy, price point, pricing tiers, positioning statement, positioning, how to position, first customers, early adopters, 90-day plan, launch plan, customer success, onboarding, retention. NOT for: customer discovery (use discovery), competitive analysis (use market), unit economics (use financials), pitch deck (use pitch).","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-innovation-skills-gtm-skill-ff40213b\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"gtm strategy","customer","economics","cold","unit","retention","pitch","how to","icp","customer discovery","positioning","activate","acquire","acquisition","plan","analysis","pricing strategy","cold email","outreach strategy","2026-11-10 10:12:30",false,"---\nname: gtm\ndescription: >\n  Activate for: go to market, GTM, GTM strategy, go-to-market, ICP, ideal\n  customer profile, target customer, who to sell to, channel strategy, sales\n  channel, how to acquire customers, customer acquisition, outreach strategy,\n  LinkedIn outreach, cold email, sales process, sales funnel, pricing strategy,\n  price point, pricing tiers, positioning statement, positioning, how to position,\n  first customers, early adopters, 90-day plan, launch plan, customer success,\n  onboarding, retention.\n  NOT for: customer discovery (use discovery), competitive analysis (use market),\n  unit economics (use financials), pitch deck (use pitch).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Fgtm\"\n---\n\n## CONTEXT LOADING\n\nBefore executing, check for `innov.local.md` in the working directory.\nIf found, extract:\n\n- venture: name, stage, type, target_customer\n- customer_profiles: personas, pains, gains, WTP, buying_process\n- competitive_landscape: differentiation, moat_building\n- financial_model: unit_economics (CAC, LTV, pricing)\n\nIf `innov.local.md` is not found:\nContinue with conversation context. After first substantive output, prompt:\n\"I'm working without your venture context. Run Exercise 8 from Chapter 40\nto build innov.local.md -- it will make every subsequent output specific\nto your venture rather than generic.\"\n\n## STAGE-AWARE CALIBRATION\n\nCheck venture.stage and calibrate:\n\n- IDEA: Warning -- \"GTM strategy at the IDEA stage is premature. You don't have an ICP grounded in customer evidence yet. Consider running \u002Fdiscovery first.\"\n- DISCOVERY: Warning -- \"You don't have a validated ICP yet. GTM strategy requires knowing who your customer is, what triggers their buying, and how they evaluate solutions. Complete discovery first.\"\n- VALIDATION: GTM planning is appropriate -- you should be defining your ICP from validated customer data.\n- MVP: This is your focus stage. GTM should be specific, measured, and iterated weekly.\n- GROWTH: This is your focus stage for scaling what works.\n\n## DLA PROGRESSION CHECK\n\nIf no customer_profiles with validated data exist in innov.local.md:\n\"You are building a GTM strategy without validated customer profiles.\nYour ICP will be based on guesses rather than evidence. Consider\nrunning \u002Fdiscovery to ground your ICP in real customer data.\"\n\n## GO-TO-MARKET WORKFLOW\n\n### Task Types\n\nTYPE 1: ICP DEFINITION\nInput: Problem area; discovery data; current customer data\nOutput: Primary ICP (role, company, trigger, signals, NOT a fit) + secondary ICP\n\nTYPE 2: POSITIONING STATEMENT\nInput: ICP; value proposition; competitive landscape\nOutput: Positioning statement (For\u002FWho\u002FOur product\u002FThat\u002FUnlike\u002FWe format)\n\nTYPE 3: CHANNEL STRATEGY\nInput: ICP; team constraints; budget; existing assets\nOutput: Channels ranked by CAC efficiency; Week 1 activation for each\n\nTYPE 4: SALES PROCESS\nInput: ICP; product type; sales cycle data\nOutput: Step-by-step process from lead identification to signed contract\n\nTYPE 5: 90-DAY GTM CALENDAR\nInput: Target (N customers by Day 90); channel strategy; team\nOutput: Week-by-week activity plan with decision gates at Day 30 and Day 60\n\nTYPE 6: PRICING STRATEGY\nInput: WTP data from discovery; competitive pricing; unit economics\nOutput: Pricing tiers; anchoring strategy; discounting policy; trial policy\n\nTYPE 7: CUSTOMER SUCCESS PROGRAMME\nInput: Target segment; onboarding complexity; churn risk factors\nOutput: Day 1-90 success programme with adoption metrics and intervention triggers\n\n### ICP Output Structure\n\n```\nIDEAL CUSTOMER PROFILE (ICP)\nVenture: [Name] | Version: [N] | Based on: [N discovery interviews + N customers]\n================================================================\nPRIMARY ICP:\n  Company:\n    Sector:       [Specific -- not \"all industries\"]\n    Size:         [Revenue band OR headcount band]\n    Geography:    [Region \u002F country \u002F city tier]\n    Technology:   [What systems they use; what they do NOT use]\n    Structure:    [Number of relevant staff; team maturity]\n\n  Person:\n    Role:         [Job title -- be specific; CFO != VP Finance != Controller]\n    Seniority:    [Level; direct reports; budget authority]\n    Cares about:  [Their top 3 professional priorities right now]\n    How they buy: [Solo \u002F committee; budget cycle; evaluation process]\n\n  Buying Trigger:\n    [The specific event that makes them ready to buy RIGHT NOW]\n    Why trigger matters: Customers without a trigger browse but don't buy.\n\n  Signals (how to identify ICP prospects):\n    [What they post; what groups they join; what events they attend]\n\n  NOT a fit (explicitly exclude):\n    [Who wastes your time -- be specific; saves sales team hours]\n\nSECONDARY ICP (if applicable):\n  [Same structure]\n\nICP CONFIDENCE: [LOW \u002F MEDIUM \u002F HIGH] -- based on [N] paying customers\nNext validation: [What ICP assumption still needs more customer data]\n================================================================\n```\n\n### Positioning Statement Format\n\nFor: [Primary ICP -- the specific person]\nWho: [The problem they have -- from discovery language]\nOur product: [Category name -- what kind of thing it is]\nThat: [The primary value delivered -- outcome, not feature]\nUnlike: [The primary alternative they currently use]\nWe: [The specific differentiating claim -- why you win]\n\n### Channel Strategy Framework\n\nCHANNEL ARCHETYPES:\n\nFOUNDER-LED OUTREACH (early stage; months 1-6):\nCAC: Low (founder time) | Scale: Low | Speed: Fast\nBest for: ICP refinement; first 10 customers\n\nCONTENT \u002F THOUGHT LEADERSHIP (months 3-12):\nCAC: Medium-low | Scale: Medium | Speed: Slow to start; compounds\nBest for: Building inbound pipeline over 6-12 months\n\nCOMMUNITY AND ASSOCIATIONS (months 3-9):\nCAC: Medium | Scale: Medium | Speed: Medium\nBest for: Warm introductions in trust-based markets\n\nREFERRAL PROGRAMME (months 6+):\nCAC: Low | Scale: Medium | Speed: Depends on customer base\nBest for: Once you have 10+ happy customers\n\nINSIDE SALES (months 9-18; requires funding):\nCAC: Medium-high | Scale: High | Speed: Fast once ramped\nBest for: Scaling what founder-led sales has proven\n\nPARTNERSHIPS \u002F CHANNELS (months 12+):\nCAC: Variable | Scale: High | Speed: Slow to develop\nBest for: Distribution leverage through partners\n\n### Pricing Strategy Rules\n\nANCHOR HIGH, JUSTIFY, THEN TIER:\nStart with the highest price you can credibly defend.\nNever start low -- it is very hard to raise prices.\n\nVALUE-BASED PRICING PRINCIPLE:\nPrice should be \u003C10% of the value delivered (the \"10% rule\").\n\nDISCOUNTING POLICY:\nAnnual prepay only: 1-2 months free for annual commitment.\nNo arbitrary discounts: customers who price-negotiate before signing churn faster.\n\nTRIAL POLICY:\nPaid trial preferred over free trial.\nTrial with LOI preferred: require a letter of intent before granting trial access.\n\n## ASSUMPTION TRACKING\n\nAfter any GTM output:\n\n- Surface the most critical untested GTM assumption (ICP, channel, pricing)\n- Propose innov.local.md updates for customer profiles or competitive landscape\n- Always distinguish between ASSUMED, ANECDOTAL, and VALIDATED evidence\n\n## NEVER DO THESE\n\n- NEVER define ICP as a demographic without a buying trigger --\n  \"CFOs at $10M companies\" is a description; add the trigger\n- NEVER launch multiple channels simultaneously without measuring each\n- NEVER set pricing based on competitor pricing alone -- price based on\n  value delivered and unit economics\n- NEVER skip the \"NOT a fit\" section of the ICP\n- NEVER design a customer success programme that assumes high-touch\n  is sustainable at scale\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## CONTEXT LOADING\n\nBefore executing, check for `innov.local.md` in the working directory.\nIf found, extract:\n\n- venture: name, stage, type, target_customer\n- customer_profiles: personas, pains, gains, WTP, buying_process\n- competitive_landscape: differentiation, moat_building\n- financial_model: unit_economics (CAC, LTV, pricing)\n\nIf `innov.local.md` is not found:\nContinue with conversation context. After first substantive output, prompt:\n\"I'm working without your venture context. Run Exercise 8 from Chapter 40\nto build innov.local.md -- it will make every subsequent output specific\nto your venture rather than generic.\"\n\n## STAGE-AWARE CALIBRATION\n\nCheck venture.stage and calibrate:\n\n- IDEA: Warning -- \"GTM strategy at the IDEA stage is premature. You don't have an ICP grounded in customer evidence yet. Consider running \u002Fdiscovery first.\"\n- DISCOVERY: Warning -- \"You don't have a validated ICP yet. GTM strategy requires knowing who your customer is, what triggers their buying, and how they evaluate solutions. Complete discovery first.\"\n- VALIDATION: GTM planning is appropriate -- you should be defining your ICP from validated customer data.\n- MVP: This is your focus stage. GTM should be specific, measured, and iterated weekly.\n- GROWTH: This is your focus stage for scaling what works.\n\n## DLA PROGRESSION CHECK\n\nIf no customer_profiles with validated data exist in innov.local.md:\n\"You are building a GTM strategy without validated customer profiles.\nYour ICP will be based on guesses rather than evidence. Consider\nrunning \u002Fdiscovery to ground your ICP in real customer data.\"\n\n## GO-TO-MARKET WORKFLOW\n\n### Task Types\n\nTYPE 1: ICP DEFINITION\nInput: Problem area; discovery data; current customer data\nOutput: Primary ICP (role, company, trigger, signals, NOT a fit) + secondary ICP\n\nTYPE 2: POSITIONING STATEMENT\nInput: ICP; value proposition; competitive landscape\nOutput: Positioning statement (For\u002FWho\u002FOur product\u002FThat\u002FUnlike\u002FWe format)\n\nTYPE 3: CHANNEL STRATEGY\nInput: ICP; team constraints; budget; existing assets\nOutput: Channels ranked by CAC efficiency; Week 1 activation for each\n\nTYPE 4: SALES PROCESS\nInput: ICP; product type; sales cycle data\nOutput: Step-by-step process from lead identification to signed contract\n\nTYPE 5: 90-DAY GTM CALENDAR\nInput: Target (N customers by Day 90); channel strategy; team\nOutput: Week-by-week activity plan with decision gates at Day 30 and Day 60\n\nTYPE 6: PRICING STRATEGY\nInput: WTP data from discovery; competitive pricing; unit economics\nOutput: Pricing tiers; anchoring strategy; discounting policy; trial policy\n\nTYPE 7: CUSTOMER SUCCESS PROGRAMME\nInput: Target segment; onboarding complexity; churn risk factors\nOutput: Day 1-90 success programme with adoption metrics and intervention triggers\n\n### ICP Output Structure\n\n```\nIDEAL CUSTOMER PROFILE (ICP)\nVenture: [Name] | Version: [N] | Based on: [N discovery interviews + N customers]\n================================================================\nPRIMARY ICP:\n  Company:\n    Sector:       [Specific -- not \"all industries\"]\n    Size:         [Revenue band OR headcount band]\n    Geography:    [Region \u002F country \u002F city tier]\n    Technology:   [What systems they use; what they do NOT use]\n    Structure:    [Number of relevant staff; team maturity]\n\n  Person:\n    Role:         [Job title -- be specific; CFO != VP Finance != Controller]\n    Seniority:    [Level; direct reports; budget authority]\n    Cares about:  [Their top 3 professional priorities right now]\n    How they buy: [Solo \u002F committee; budget cycle; evaluation process]\n\n  Buying Trigger:\n    [The specific event that makes them ready to buy RIGHT NOW]\n    Why trigger matters: Customers without a trigger browse but don't buy.\n\n  Signals (how to identify ICP prospects):\n    [What they post; what groups they join; what events they attend]\n\n  NOT a fit (explicitly exclude):\n    [Who wastes your time -- be specific; saves sales team hours]\n\nSECONDARY ICP (if applicable):\n  [Same structure]\n\nICP CONFIDENCE: [LOW \u002F MEDIUM \u002F HIGH] -- based on [N] paying customers\nNext validation: [What ICP assumption still needs more customer data]\n================================================================\n```\n\n### Positioning Statement Format\n\nFor: [Primary ICP -- the specific person]\nWho: [The problem they have -- from discovery language]\nOur product: [Category name -- what kind of thing it is]\nThat: [The primary value delivered -- outcome, not feature]\nUnlike: [The primary alternative they currently use]\nWe: [The specific differentiating claim -- why you win]\n\n### Channel Strategy Framework\n\nCHANNEL ARCHETYPES:\n\nFOUNDER-LED OUTREACH (early stage; months 1-6):\nCAC: Low (founder time) | Scale: Low | Speed: Fast\nBest for: ICP refinement; first 10 customers\n\nCONTENT \u002F THOUGHT LEADERSHIP (months 3-12):\nCAC: Medium-low | Scale: Medium | Speed: Slow to start; compounds\nBest for: Building inbound pipeline over 6-12 months\n\nCOMMUNITY AND ASSOCIATIONS (months 3-9):\nCAC: Medium | Scale: Medium | Speed: Medium\nBest for: Warm introductions in trust-based markets\n\nREFERRAL PROGRAMME (months 6+):\nCAC: Low | Scale: Medium | Speed: Depends on customer base\nBest for: Once you have 10+ happy customers\n\nINSIDE SALES (months 9-18; requires funding):\nCAC: Medium-high | Scale: High | Speed: Fast once ramped\nBest for: Scaling what founder-led sales has proven\n\nPARTNERSHIPS \u002F CHANNELS (months 12+):\nCAC: Variable | Scale: High | Speed: Slow to develop\nBest for: Distribution leverage through partners\n\n### Pricing Strategy Rules\n\nANCHOR HIGH, JUSTIFY, THEN TIER:\nStart with the highest price you can credibly defend.\nNever start low -- it is very hard to raise prices.\n\nVALUE-BASED PRICING PRINCIPLE:\nPrice should be \u003C10% of the value delivered (the \"10% rule\").\n\nDISCOUNTING POLICY:\nAnnual prepay only: 1-2 months free for annual commitment.\nNo arbitrary discounts: customers who price-negotiate before signing churn faster.\n\nTRIAL POLICY:\nPaid trial preferred over free trial.\nTrial with LOI preferred: require a letter of intent before granting trial access.\n\n## ASSUMPTION TRACKING\n\nAfter any GTM output:\n\n- Surface the most critical untested GTM assumption (ICP, channel, pricing)\n- Propose innov.local.md updates for customer profiles or competitive landscape\n- Always distinguish between ASSUMED, ANECDOTAL, and VALIDATED evidence\n\n## NEVER DO THESE\n\n- NEVER define ICP as a demographic without a buying trigger --\n  \"CFOs at $10M companies\" is a description; add the trigger\n- NEVER launch multiple channels simultaneously without measuring each\n- NEVER set pricing based on competitor pricing alone -- price based on\n  value delivered and unit economics\n- NEVER skip the \"NOT a fit\" section of the ICP\n- NEVER design a customer success programme that assumes high-touch\n  is sustainable at scale\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n",{"name":5,"license":14,"metadata":42,"description":46},{"author":43,"version":44,"plugin-commands":45},"Panaversity","1.0","\u002Fgtm","Activate for: go to market, GTM, GTM strategy, go-to-market, ICP, ideal customer profile, target customer, who to sell to, channel strategy, sales channel, how to acquire customers, customer acquisition, outreach strategy, LinkedIn outreach, cold email, sales process, sales funnel, pricing strategy, price point, pricing tiers, positioning statement, positioning, how to position, first customers, early adopters, 90-day plan, launch plan, customer success, onboarding, retention. NOT for: customer discovery (use discovery), competitive analysis (use market), unit economics (use financials), pitch deck (use pitch).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-innovation-skills-gtm-skill-ff40213b","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill gtm",{"tool":59,"command":60},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill gtm",{"tool":62,"command":63},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill gtm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-innovation-skills-gtm-skill-ff40213b\u002FSKILL.md",true,[],[68,95,122,155,183,217],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":37},"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\".","MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[70,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":37},"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'.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":136,"publishedAt":37},"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",[128,133],{"categoryNo":129,"categoryName":130,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":134,"categoryName":135,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000023","Skill与智能体开发",[137,138,139,140,141,142,143,144,145,146,147,148,149,88,150,151,152,153,93,154],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":164,"publishedAt":37},"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",[161],{"categoryNo":162,"categoryName":163,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000011","运维与部署",[165,166,167,168,169,170,171,172,173,88,174,175,176,177,178,179,180,181,182,93],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":200,"publishedAt":37},"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",[189,192,197],{"categoryNo":190,"categoryName":191,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":193,"categoryName":194,"taxonomyType":195,"taxonomyTypeDesc":196},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":198,"categoryName":199,"taxonomyType":195,"taxonomyTypeDesc":196},"01JBSEEDCAT000000000000038","人力资源",[201,202,203,204,205,206,207,208,103,209,88,210,211,212,29,213,214,215,93,216],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","do","task","cv","letter",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":37},"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",[],[224,225,19,226,227,204,228,88,213,229,230,231,232,233,234,235,236,237,93,238],"steno mode","mode","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]