[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N17QB1R2P514QFP1M7SBCF":3,"skill-same:01M6N17QB1R2P514QFP1M7SBCF":82},{"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":62,"commitSha":63,"skillDirectory":64,"forksCount":13,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6N17QB1R2P514QFP1M7SBCF","spend-analysis",null,"Analyses procurement spend data to find savings. Activate for: spend analysis, spend analytics, analyse spend, procurement spend, category spend, spend across sites, spend consolidation, vendor consolidation, supplier consolidation, price consistency, price inconsistency, price benchmark, market benchmark, RFQ strategy, spend report, category management, tail spend, maverick spend, buying compliance, savings pipeline, identified savings, cost reduction, procurement ROI, spend by category, spend by vendor, spend by site, packaging spend, consolidation opportunity. USE THIS when the task involves analysing WHERE money is being spent, finding price inconsistencies across sites, identifying consolidation opportunities, or benchmarking prices against market rates. NOT for: invoice reconciliation (use invoice-reconciliation), vendor risk assessment (use supplier-risk), carrier performance (use logistics-brief).","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-supply-chain-skills-spend-analysis-skill-1a796e6c\u002FSKILL.md",[17,22,27],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",{"categoryNo":28,"categoryName":29,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000040","财务",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"spend analysis","analysis","prices","performance","consolidation","across","reconciliation","opportunity","activate","rfq","packaging","web search","procurement","pipeline","brief","search","benchmark","assessment","risk assessment","benchmarking","2026-11-10 10:12:30",false,"---\nname: spend-analysis\ndescription: >\n  Analyses procurement spend data to find savings. Activate for: spend analysis,\n  spend analytics, analyse spend, procurement spend, category spend, spend\n  across sites, spend consolidation, vendor consolidation, supplier consolidation,\n  price consistency, price inconsistency, price benchmark, market benchmark,\n  RFQ strategy, spend report, category management, tail spend, maverick spend,\n  buying compliance, savings pipeline, identified savings, cost reduction,\n  procurement ROI, spend by category, spend by vendor, spend by site,\n  packaging spend, consolidation opportunity.\n  USE THIS when the task involves analysing WHERE money is being spent, finding\n  price inconsistencies across sites, identifying consolidation opportunities,\n  or benchmarking prices against market rates.\n  NOT for: invoice reconciliation (use invoice-reconciliation), vendor risk\n  assessment (use supplier-risk), carrier performance (use logistics-brief).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Fspend-analysis\"\n  mcp-integrations: \"ERP, finance system, procurement system, web search\"\n---\n\n## UNIVERSAL RULES (apply to every spend task)\n\n- NEVER accept a vendor risk assessment that contains fabricated financial\n  data -- label all estimates and flag where primary data is unavailable\n- ALWAYS include specific recommended actions with deadlines in every output --\n  observations without actions are not acceptable\n\n## MANDATORY OUTPUT HEADER\n\n```\nTASK:          [e.g. Category Spend Overview -- Packaging -- FY2024]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [ERP \u002F Finance system \u002F Web search]\n```\n\n## SPEND ANALYSIS WORKFLOW\n\n### Three Strategic Questions Spend Analytics Answers\n\nQuestion 1: WHO are we actually buying from?\n  -> Vendor concentration analysis; consolidation opportunity identification\n\nQuestion 2: WHAT are we paying?\n  -> Price consistency across sites\u002FBUs; contract compliance monitoring\n\nQuestion 3: WHAT SHOULD we be paying?\n  -> Market benchmarking; renegotiation trigger identification\n\n### Analysis Types\n\n#### Type 1: Category Spend Overview\n\nDATA FROM ERP (define period: typically last 12 months):\n- Total spend by category (top level and sub-category)\n- Spend by vendor within each category\n- Spend by business unit \u002F site \u002F cost centre\n- PO compliance: what % of spend had a PO before the invoice?\n\nOUTPUT:\n\n```\nCATEGORY SPEND OVERVIEW -- [Period]\n================================================================\nTOTAL SPEND ANALYSED: [X]\n\nTOP CATEGORIES BY SPEND:\n[Category]: [X] | [N] vendors | [N] BUs buying | PO compliance: [X]%\n\nTAIL SPEND ALERT:\n[X]% of spend is with vendors who each represent \u003C0.5% of total spend.\n[N] vendors account for [X]% of total spend.\nOpportunity: rationalise tail to reduce transaction cost and compliance burden.\n\nPO COMPLIANCE ISSUES:\n[X]% of invoices received without prior PO (by category and BU).\nNon-compliant spend: [X] -- escalate to Finance and Procurement leadership.\n================================================================\n```\n\n#### Type 2: Vendor Consolidation Analysis\n\nTARGET: categories with >3 vendors where commodity characteristics suggest\nconsolidation would deliver price advantage without unacceptable supply risk.\n\nCONSOLIDATION CANDIDATE CRITERIA:\n  - Multiple vendors supplying same specification \u002F same category\n  - No strategic reason for multiple sources (i.e. not deliberate dual-sourcing)\n  - Combined volume would be meaningful to a single preferred vendor\n  - Competitive market with multiple qualified alternatives\n\nCONSOLIDATION OUTPUT (per candidate category):\n\n```\nCONSOLIDATION ANALYSIS: [Category]\n---------------------------------------------------------\nCurrent state:\n  Vendors:       [N] active vendors\n  Total spend:   [X]\n  Price range:   [low] -- [high] per [unit] -- [X]% variance\n  Price winner:  [Vendor at lowest price] at [X] per unit\n\nConsolidated state:\n  Target vendor(s): [1 or 2 preferred suppliers recommended]\n  Combined volume:  [X]\n  Target saving:    [X]% discount estimated at consolidated volume\n  Annual saving:    [X] -- [X] (range based on discount range)\n\nRisk assessment:\n  Supply continuity: [Single source risk? Mitigation?]\n  Switching effort:  [Qualification, trials, tooling -- estimate]\n\nRecommendation: [PROCEED \u002F PROCEED WITH DUAL-SOURCE \u002F MONITOR]\n---------------------------------------------------------\n```\n\n#### Type 3: Price Consistency Check\n\nIDENTIFY: same item or specification being purchased at different prices\nby different business units or sites.\n\nDETECT WHEN:\n  - Same vendor code, same item code, different unit price\n  - Same item description, different vendor, significantly different price\n  - Same contract but different sites paying different prices\n\nPRICE CONSISTENCY OUTPUT:\n\n```\nPRICE INCONSISTENCY REPORT -- [Category] -- [Period]\n---------------------------------------------------------\nItem:            [Description and specification]\nVendor:          [Vendor name]\n\nSite\u002FBU         Price paid    Volume    Annual spend\n[Site A]        [X]           [N units] [X]\n[Site B]        [Y]           [N units] [X]\n[Site C]        [Z]           [N units] [X]\n\nPrice variance:  [X]% between highest and lowest\nBest rate:       [X] (Site [X])\nSaving if all aligned to best rate: [X]\u002Fyear\n\nAction: Issue group pricing directive; notify all sites of best rate;\nrequire contract compliance from [date]\n---------------------------------------------------------\n```\n\n#### Type 4: Market Benchmark\n\nUSE WEB SEARCH MCP to identify:\n- Published market price indices (commodity categories)\n- Trade association price surveys (sector-specific)\n- Publicly available tender results (public sector categories)\n- Analyst market reports (technology, energy, logistics)\n\nBENCHMARK OUTPUT:\n\n```\nMARKET BENCHMARK: [Category\u002FItem]\n---------------------------------------------------------\nYour current price:   [X] per [unit]\nMarket range:         [low] -- [high] per [unit]\nYour position:        [X]% above \u002F below market midpoint\nData source:          [Specify source and date -- never fabricate]\nData quality:         [HIGH -- published index \u002F MEDIUM -- survey \u002F\n                       LOW -- estimate only]\n\nIF ABOVE MARKET: Renegotiation recommended\n  Estimated saving:   [X]% -- [X]\u002Fyear at current volume\n  Timing:             [Contract renewal date or next review]\n  Leverage:           [Market evidence + volume commitment]\n---------------------------------------------------------\n```\n\n### Savings Pipeline Format\n\n```\nPROCUREMENT SAVINGS PIPELINE -- [Date]\n================================================================\nIDENTIFIED OPPORTUNITIES:\n[Category]  [Type]          [Est. Saving]  [Status]  [Owner]  [Timeline]\n[Category]  Consolidation   [X]            Draft     [Name]   Q[N] 20[XX]\n[Category]  Price alignment [X]            Active    [Name]   [Month]\n\nTOTAL PIPELINE: [X]\nCAPTURED YTD:   [X]\nREMAINING:      [X]\n================================================================\n```\n\n## NEVER DO THESE\n\n- NEVER fabricate market benchmark prices -- always cite source and date;\n  if no reliable benchmark available, label as \"no reliable benchmark found\"\n- NEVER recommend single-sourcing a critical category without\n  documenting the supply continuity risk and mitigation plan\n- NEVER report \"savings\" without defining the baseline clearly:\n  savings vs. prior contract \u002F vs. market \u002F vs. budget -- specify\n- NEVER include tail spend vendors in consolidation analysis without\n  checking whether they supply something unique or critical\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## UNIVERSAL RULES (apply to every spend task)\n\n- NEVER accept a vendor risk assessment that contains fabricated financial\n  data -- label all estimates and flag where primary data is unavailable\n- ALWAYS include specific recommended actions with deadlines in every output --\n  observations without actions are not acceptable\n\n## MANDATORY OUTPUT HEADER\n\n```\nTASK:          [e.g. Category Spend Overview -- Packaging -- FY2024]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [ERP \u002F Finance system \u002F Web search]\n```\n\n## SPEND ANALYSIS WORKFLOW\n\n### Three Strategic Questions Spend Analytics Answers\n\nQuestion 1: WHO are we actually buying from?\n  -> Vendor concentration analysis; consolidation opportunity identification\n\nQuestion 2: WHAT are we paying?\n  -> Price consistency across sites\u002FBUs; contract compliance monitoring\n\nQuestion 3: WHAT SHOULD we be paying?\n  -> Market benchmarking; renegotiation trigger identification\n\n### Analysis Types\n\n#### Type 1: Category Spend Overview\n\nDATA FROM ERP (define period: typically last 12 months):\n- Total spend by category (top level and sub-category)\n- Spend by vendor within each category\n- Spend by business unit \u002F site \u002F cost centre\n- PO compliance: what % of spend had a PO before the invoice?\n\nOUTPUT:\n\n```\nCATEGORY SPEND OVERVIEW -- [Period]\n================================================================\nTOTAL SPEND ANALYSED: [X]\n\nTOP CATEGORIES BY SPEND:\n[Category]: [X] | [N] vendors | [N] BUs buying | PO compliance: [X]%\n\nTAIL SPEND ALERT:\n[X]% of spend is with vendors who each represent \u003C0.5% of total spend.\n[N] vendors account for [X]% of total spend.\nOpportunity: rationalise tail to reduce transaction cost and compliance burden.\n\nPO COMPLIANCE ISSUES:\n[X]% of invoices received without prior PO (by category and BU).\nNon-compliant spend: [X] -- escalate to Finance and Procurement leadership.\n================================================================\n```\n\n#### Type 2: Vendor Consolidation Analysis\n\nTARGET: categories with >3 vendors where commodity characteristics suggest\nconsolidation would deliver price advantage without unacceptable supply risk.\n\nCONSOLIDATION CANDIDATE CRITERIA:\n  - Multiple vendors supplying same specification \u002F same category\n  - No strategic reason for multiple sources (i.e. not deliberate dual-sourcing)\n  - Combined volume would be meaningful to a single preferred vendor\n  - Competitive market with multiple qualified alternatives\n\nCONSOLIDATION OUTPUT (per candidate category):\n\n```\nCONSOLIDATION ANALYSIS: [Category]\n---------------------------------------------------------\nCurrent state:\n  Vendors:       [N] active vendors\n  Total spend:   [X]\n  Price range:   [low] -- [high] per [unit] -- [X]% variance\n  Price winner:  [Vendor at lowest price] at [X] per unit\n\nConsolidated state:\n  Target vendor(s): [1 or 2 preferred suppliers recommended]\n  Combined volume:  [X]\n  Target saving:    [X]% discount estimated at consolidated volume\n  Annual saving:    [X] -- [X] (range based on discount range)\n\nRisk assessment:\n  Supply continuity: [Single source risk? Mitigation?]\n  Switching effort:  [Qualification, trials, tooling -- estimate]\n\nRecommendation: [PROCEED \u002F PROCEED WITH DUAL-SOURCE \u002F MONITOR]\n---------------------------------------------------------\n```\n\n#### Type 3: Price Consistency Check\n\nIDENTIFY: same item or specification being purchased at different prices\nby different business units or sites.\n\nDETECT WHEN:\n  - Same vendor code, same item code, different unit price\n  - Same item description, different vendor, significantly different price\n  - Same contract but different sites paying different prices\n\nPRICE CONSISTENCY OUTPUT:\n\n```\nPRICE INCONSISTENCY REPORT -- [Category] -- [Period]\n---------------------------------------------------------\nItem:            [Description and specification]\nVendor:          [Vendor name]\n\nSite\u002FBU         Price paid    Volume    Annual spend\n[Site A]        [X]           [N units] [X]\n[Site B]        [Y]           [N units] [X]\n[Site C]        [Z]           [N units] [X]\n\nPrice variance:  [X]% between highest and lowest\nBest rate:       [X] (Site [X])\nSaving if all aligned to best rate: [X]\u002Fyear\n\nAction: Issue group pricing directive; notify all sites of best rate;\nrequire contract compliance from [date]\n---------------------------------------------------------\n```\n\n#### Type 4: Market Benchmark\n\nUSE WEB SEARCH MCP to identify:\n- Published market price indices (commodity categories)\n- Trade association price surveys (sector-specific)\n- Publicly available tender results (public sector categories)\n- Analyst market reports (technology, energy, logistics)\n\nBENCHMARK OUTPUT:\n\n```\nMARKET BENCHMARK: [Category\u002FItem]\n---------------------------------------------------------\nYour current price:   [X] per [unit]\nMarket range:         [low] -- [high] per [unit]\nYour position:        [X]% above \u002F below market midpoint\nData source:          [Specify source and date -- never fabricate]\nData quality:         [HIGH -- published index \u002F MEDIUM -- survey \u002F\n                       LOW -- estimate only]\n\nIF ABOVE MARKET: Renegotiation recommended\n  Estimated saving:   [X]% -- [X]\u002Fyear at current volume\n  Timing:             [Contract renewal date or next review]\n  Leverage:           [Market evidence + volume commitment]\n---------------------------------------------------------\n```\n\n### Savings Pipeline Format\n\n```\nPROCUREMENT SAVINGS PIPELINE -- [Date]\n================================================================\nIDENTIFIED OPPORTUNITIES:\n[Category]  [Type]          [Est. Saving]  [Status]  [Owner]  [Timeline]\n[Category]  Consolidation   [X]            Draft     [Name]   Q[N] 20[XX]\n[Category]  Price alignment [X]            Active    [Name]   [Month]\n\nTOTAL PIPELINE: [X]\nCAPTURED YTD:   [X]\nREMAINING:      [X]\n================================================================\n```\n\n## NEVER DO THESE\n\n- NEVER fabricate market benchmark prices -- always cite source and date;\n  if no reliable benchmark available, label as \"no reliable benchmark found\"\n- NEVER recommend single-sourcing a critical category without\n  documenting the supply continuity risk and mitigation plan\n- NEVER report \"savings\" without defining the baseline clearly:\n  savings vs. prior contract \u002F vs. market \u002F vs. budget -- specify\n- NEVER include tail spend vendors in consolidation analysis without\n  checking whether they supply something unique or critical\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n",{"name":5,"license":14,"metadata":56,"description":61},{"author":57,"version":58,"plugin-commands":59,"mcp-integrations":60},"Panaversity","1.0","\u002Fspend-analysis","ERP, finance system, procurement system, web search","Analyses procurement spend data to find savings. Activate for: spend analysis, spend analytics, analyse spend, procurement spend, category spend, spend across sites, spend consolidation, vendor consolidation, supplier consolidation, price consistency, price inconsistency, price benchmark, market benchmark, RFQ strategy, spend report, category management, tail spend, maverick spend, buying compliance, savings pipeline, identified savings, cost reduction, procurement ROI, spend by category, spend by vendor, spend by site, packaging spend, consolidation opportunity. USE THIS when the task involves analysing WHERE money is being spent, finding price inconsistencies across sites, identifying consolidation opportunities, or benchmarking prices against market rates. NOT for: invoice reconciliation (use invoice-reconciliation), vendor risk assessment (use supplier-risk), carrier performance (use logistics-brief).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-spend-analysis-skill-1a796e6c","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill spend-analysis",{"tool":74,"command":75},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill spend-analysis",{"tool":77,"command":78},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill spend-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-spend-analysis-skill-1a796e6c\u002FSKILL.md",true,[],[83,110,137,167,195,226],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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\".","MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[85,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"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'.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136],"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":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":149,"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",[143,146],{"categoryNo":144,"categoryName":145,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":147,"categoryName":148,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[150,151,152,153,154,155,156,157,44,158,159,160,161,103,162,163,164,165,108,166],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":176,"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",[173],{"categoryNo":174,"categoryName":175,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[177,178,179,180,181,182,183,184,185,103,186,187,188,189,190,191,192,193,194,108],"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":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":210,"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",[201,204,207],{"categoryNo":202,"categoryName":203,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":205,"categoryName":206,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":208,"categoryName":209,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000038","人力资源",[46,211,212,213,214,215,216,217,118,218,103,219,220,221,39,222,223,224,108,225],"Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","do","task","cv","letter",{"skillNo":227,"name":228,"nameZh":6,"description":229,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":230,"categories":231,"keywords":232,"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",[],[233,234,235,45,236,213,237,103,222,238,239,240,241,242,243,244,245,246,108,247],"steno mode","mode","customer","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]