[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N00PW2XVMHWYM1XR6HWTVE":3,"skill-same:01M6N00PW2XVMHWYM1XR6HWTVE":73},{"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":22,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":13,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M6N00PW2XVMHWYM1XR6HWTVE","metrics",null,"Activate for: metrics, KPI, operational metrics, performance metrics, operational dashboard, performance measurement, operations reporting, monthly report operations, operations scorecard, leading indicator, lagging indicator, red amber green, RAG status, operational performance, KRI, key risk indicator, SLA metrics, efficiency metrics, throughput, cycle time, error rate, cost per transaction, operational excellence, metrics framework, dashboard design, metric definition. NOT for: generating status reports (use official \u002Fstatus-report), vendor performance scoring (use official \u002Fvendor-review), risk register building (use official risk-assessment auto-skill).","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-operations-intelligence-skills-metrics-skill-d0dafa70\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[5,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"reports","definition","scorecard","error","efficiency","time","green","scoring","cycle","activate","design","auto","assessment","risk register","rag","official","dashboard","performance","review","2026-11-10 10:12:30",false,"---\nname: metrics\ndescription: >\n  Activate for: metrics, KPI, operational metrics, performance metrics,\n  operational dashboard, performance measurement, operations reporting,\n  monthly report operations, operations scorecard, leading indicator,\n  lagging indicator, red amber green, RAG status, operational performance,\n  KRI, key risk indicator, SLA metrics, efficiency metrics, throughput,\n  cycle time, error rate, cost per transaction, operational excellence,\n  metrics framework, dashboard design, metric definition.\n  NOT for: generating status reports (use official \u002Fstatus-report),\n  vendor performance scoring (use official \u002Fvendor-review), risk\n  register building (use official risk-assessment auto-skill).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Fmetrics\"\n  mcp-integrations: \"ERP, ITSM, compliance system, document store\"\n---\n\n## UNIVERSAL RULES (apply to every metrics task)\n\n- NEVER produce a metrics framework without defined red thresholds --\n  a metric without an alarm level is just reporting; it does not drive action\n- NEVER produce more than 10 metrics for an operational dashboard --\n  if everything is measured, nothing is managed\n- NEVER accept \"the team will monitor\" as a metric owner -- one named person\n- ALWAYS include at least one leading indicator for every major risk area\n- ALWAYS load ops.local.md for existing KPI targets, reporting cadence,\n  and dashboard configuration\n\n## MANDATORY OUTPUT HEADER\n\nEvery output must begin with:\n\n```\nTASK:          [e.g. Operational Metrics Framework Design]\nDOCUMENT TYPE: [Framework \u002F Dashboard \u002F Monthly Report \u002F Metric Definition]\nCONFIGURATION: [Loaded: ops.local.md \u002F Not configured]\nDATE:          [Date of output]\nOWNER:         [Named person responsible]\nREVIEW DATE:   [When to review\u002Fupdate]\n```\n\n## METRICS FRAMEWORK DESIGN PRINCIPLES\n\nPRINCIPLE 1: MEASURE WHAT MATTERS, NOT WHAT IS EASY\nThe easiest metrics to collect are often the least useful.\nStart from: \"What do we need to know to run operations well?\"\nThen determine how to measure it -- not the other way round.\n\nPRINCIPLE 2: LEADING INDICATORS OVER LAGGING\nLagging: tells you what happened (incidents last month)\nLeading: tells you what is about to happen (open SLA warnings)\nEvery major risk area should have at least one leading indicator.\n\nPRINCIPLE 3: EVERY METRIC HAS AN OWNER\nA metric nobody is responsible for improving is decoration.\nEvery metric must have a named owner accountable for both the\nmeasurement and the performance it reflects.\n\nPRINCIPLE 4: RED THRESHOLDS TRIGGER ACTIONS\nMetrics without defined red thresholds are thermometers, not alarms.\nDefine: what level triggers an escalation? To whom? By when?\n\nPRINCIPLE 5: FEWER, BETTER\n5-10 well-chosen metrics that tell the operational story clearly\nare worth more than 30 metrics nobody reads.\n\n## METRICS WORKFLOW\n\n### Task Type 1: METRIC DEFINITION\n\nFor each metric:\n\n```\nMETRIC: [Name -- short, descriptive]\n----------------------------------------------------------------\nWhat it measures: [Plain language -- one sentence]\nWhy it matters:   [What decision or action this metric informs]\nType:             [LEADING \u002F LAGGING]\nFormula:          [Exactly how calculated -- no ambiguity]\nData source:      [Where the data comes from]\nMeasurement freq: [Daily \u002F Weekly \u002F Monthly]\nOwner:            [Named role -- who produces AND is responsible]\n\nThresholds:\n  GREEN:  [Target range -- what good looks like]\n  AMBER:  [Watch zone -- investigate; action may be needed]\n  RED:    [Action zone -- escalate to [role] within [timeframe]]\n\nTrend direction:  [Higher is better \u002F Lower is better \u002F Target is stable]\n----------------------------------------------------------------\n```\n\n### Task Type 2: METRICS FRAMEWORK (FULL DASHBOARD)\n\nDesign a complete operational metrics framework:\n\n```\nOPERATIONAL METRICS FRAMEWORK: [Organisation \u002F Function]\n================================================================\n\nVENDOR MANAGEMENT:\n  [Metric] | [Type] | [Owner] | [Green] | [Amber] | [Red]\n  - Vendor SLA compliance rate (Lagging)\n  - Renewal pipeline value (Leading)\n  - Open SLA warnings (Leading)\n  - Vendor spend vs. budget (Lagging)\n\nPROCESS OPERATIONS:\n  - Process error rate (Lagging)\n  - SOP currency rate (Leading)\n  - Key-person dependency count (Leading)\n  - Cycle time (Lagging)\n\nCHANGE MANAGEMENT:\n  - Change failure rate (Lagging)\n  - Changes without impact assessment (Leading)\n  - PIR completion rate (Lagging)\n  - Emergency change rate (Leading\u002FLagging)\n\nCOMPLIANCE:\n  - Obligation currency rate (Leading)\n  - Evidence age (Leading)\n  - Audit findings open (Lagging)\n  - Regulatory change response time (Lagging)\n\nRISK:\n  - Risk register review completion (Leading)\n  - Risks above appetite (Leading)\n  - Mitigation action completion rate (Lagging)\n\nINCIDENT:\n  - MTTR by severity (Lagging)\n  - MTTD (Lagging\u002FLeading)\n  - Corrective action completion rate (Lagging)\n  - Repeat incident rate (Lagging -- key signal)\n\nRECOMMENDED TOP 5-10 FOR DASHBOARD:\n[Select the most impactful from above for the executive dashboard]\n================================================================\n```\n\n### Task Type 3: MONTHLY OPERATIONAL REPORT\n\n```\nMONTHLY OPERATIONS REPORT: [Month Year]\nPrepared by: [Name] | For: [COO \u002F Board \u002F Ops team]\n================================================================\nHEADLINE STATUS: [STABLE \u002F WATCH ITEMS \u002F ACTION REQUIRED]\n\n| Metric | Status | This Month | Last Month | Trend | Action |\n|---|---|---|---|---|---|\n| [Name] | [G\u002FA\u002FR] | [Value] | [Value] | [Up\u002FDown\u002FStable] | [If needed] |\n\nKEY ISSUES:\n[RED metrics only -- specific; what is being done]\n\nWATCH ITEMS:\n[AMBER metrics -- what we are monitoring and why]\n\nCOMPLETED ACTIONS (from last month):\n[What was agreed and is now done]\n\nUPCOMING:\n[What needs attention in the next 30 days]\n================================================================\n```\n\n## STANDARD OPERATIONS METRICS LIBRARY\n\nReference library of common operational metrics by domain:\n\nVENDOR: SLA compliance %, renewal pipeline value, open SLA warnings,\nspend vs. budget\nPROCESS: error rate per 1000 transactions, SOP currency %, key-person\ndependency count, cycle time\nCHANGE: failure rate %, changes without impact assessment, PIR completion\nrate, emergency change rate\nCOMPLIANCE: obligation currency %, evidence age, open audit findings,\nregulatory change response time\nRISK: register review completion %, risks above appetite, mitigation\ncompletion rate, risk materialisation rate\nINCIDENT: MTTR, MTTD, CA completion rate, repeat incident rate\n\n## NEVER DO THESE\n\n- NEVER report only lagging indicators -- by the time they are red,\n  the problem has already occurred; leading indicators prevent it\n- NEVER define a metric by its data source rather than what it measures\n  (\"Zendesk tickets\" is a data source; \"unresolved customer issues rate\"\n  is a metric)\n- NEVER produce a monthly report without the KEY ISSUES section --\n  the report's value is in driving decisions, not documenting data\n- NEVER design a framework with more than 10 executive dashboard metrics\n- NEVER omit the formula field -- ambiguous calculation leads to\n  inconsistent measurement and disputed results\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## UNIVERSAL RULES (apply to every metrics task)\n\n- NEVER produce a metrics framework without defined red thresholds --\n  a metric without an alarm level is just reporting; it does not drive action\n- NEVER produce more than 10 metrics for an operational dashboard --\n  if everything is measured, nothing is managed\n- NEVER accept \"the team will monitor\" as a metric owner -- one named person\n- ALWAYS include at least one leading indicator for every major risk area\n- ALWAYS load ops.local.md for existing KPI targets, reporting cadence,\n  and dashboard configuration\n\n## MANDATORY OUTPUT HEADER\n\nEvery output must begin with:\n\n```\nTASK:          [e.g. Operational Metrics Framework Design]\nDOCUMENT TYPE: [Framework \u002F Dashboard \u002F Monthly Report \u002F Metric Definition]\nCONFIGURATION: [Loaded: ops.local.md \u002F Not configured]\nDATE:          [Date of output]\nOWNER:         [Named person responsible]\nREVIEW DATE:   [When to review\u002Fupdate]\n```\n\n## METRICS FRAMEWORK DESIGN PRINCIPLES\n\nPRINCIPLE 1: MEASURE WHAT MATTERS, NOT WHAT IS EASY\nThe easiest metrics to collect are often the least useful.\nStart from: \"What do we need to know to run operations well?\"\nThen determine how to measure it -- not the other way round.\n\nPRINCIPLE 2: LEADING INDICATORS OVER LAGGING\nLagging: tells you what happened (incidents last month)\nLeading: tells you what is about to happen (open SLA warnings)\nEvery major risk area should have at least one leading indicator.\n\nPRINCIPLE 3: EVERY METRIC HAS AN OWNER\nA metric nobody is responsible for improving is decoration.\nEvery metric must have a named owner accountable for both the\nmeasurement and the performance it reflects.\n\nPRINCIPLE 4: RED THRESHOLDS TRIGGER ACTIONS\nMetrics without defined red thresholds are thermometers, not alarms.\nDefine: what level triggers an escalation? To whom? By when?\n\nPRINCIPLE 5: FEWER, BETTER\n5-10 well-chosen metrics that tell the operational story clearly\nare worth more than 30 metrics nobody reads.\n\n## METRICS WORKFLOW\n\n### Task Type 1: METRIC DEFINITION\n\nFor each metric:\n\n```\nMETRIC: [Name -- short, descriptive]\n----------------------------------------------------------------\nWhat it measures: [Plain language -- one sentence]\nWhy it matters:   [What decision or action this metric informs]\nType:             [LEADING \u002F LAGGING]\nFormula:          [Exactly how calculated -- no ambiguity]\nData source:      [Where the data comes from]\nMeasurement freq: [Daily \u002F Weekly \u002F Monthly]\nOwner:            [Named role -- who produces AND is responsible]\n\nThresholds:\n  GREEN:  [Target range -- what good looks like]\n  AMBER:  [Watch zone -- investigate; action may be needed]\n  RED:    [Action zone -- escalate to [role] within [timeframe]]\n\nTrend direction:  [Higher is better \u002F Lower is better \u002F Target is stable]\n----------------------------------------------------------------\n```\n\n### Task Type 2: METRICS FRAMEWORK (FULL DASHBOARD)\n\nDesign a complete operational metrics framework:\n\n```\nOPERATIONAL METRICS FRAMEWORK: [Organisation \u002F Function]\n================================================================\n\nVENDOR MANAGEMENT:\n  [Metric] | [Type] | [Owner] | [Green] | [Amber] | [Red]\n  - Vendor SLA compliance rate (Lagging)\n  - Renewal pipeline value (Leading)\n  - Open SLA warnings (Leading)\n  - Vendor spend vs. budget (Lagging)\n\nPROCESS OPERATIONS:\n  - Process error rate (Lagging)\n  - SOP currency rate (Leading)\n  - Key-person dependency count (Leading)\n  - Cycle time (Lagging)\n\nCHANGE MANAGEMENT:\n  - Change failure rate (Lagging)\n  - Changes without impact assessment (Leading)\n  - PIR completion rate (Lagging)\n  - Emergency change rate (Leading\u002FLagging)\n\nCOMPLIANCE:\n  - Obligation currency rate (Leading)\n  - Evidence age (Leading)\n  - Audit findings open (Lagging)\n  - Regulatory change response time (Lagging)\n\nRISK:\n  - Risk register review completion (Leading)\n  - Risks above appetite (Leading)\n  - Mitigation action completion rate (Lagging)\n\nINCIDENT:\n  - MTTR by severity (Lagging)\n  - MTTD (Lagging\u002FLeading)\n  - Corrective action completion rate (Lagging)\n  - Repeat incident rate (Lagging -- key signal)\n\nRECOMMENDED TOP 5-10 FOR DASHBOARD:\n[Select the most impactful from above for the executive dashboard]\n================================================================\n```\n\n### Task Type 3: MONTHLY OPERATIONAL REPORT\n\n```\nMONTHLY OPERATIONS REPORT: [Month Year]\nPrepared by: [Name] | For: [COO \u002F Board \u002F Ops team]\n================================================================\nHEADLINE STATUS: [STABLE \u002F WATCH ITEMS \u002F ACTION REQUIRED]\n\n| Metric | Status | This Month | Last Month | Trend | Action |\n|---|---|---|---|---|---|\n| [Name] | [G\u002FA\u002FR] | [Value] | [Value] | [Up\u002FDown\u002FStable] | [If needed] |\n\nKEY ISSUES:\n[RED metrics only -- specific; what is being done]\n\nWATCH ITEMS:\n[AMBER metrics -- what we are monitoring and why]\n\nCOMPLETED ACTIONS (from last month):\n[What was agreed and is now done]\n\nUPCOMING:\n[What needs attention in the next 30 days]\n================================================================\n```\n\n## STANDARD OPERATIONS METRICS LIBRARY\n\nReference library of common operational metrics by domain:\n\nVENDOR: SLA compliance %, renewal pipeline value, open SLA warnings,\nspend vs. budget\nPROCESS: error rate per 1000 transactions, SOP currency %, key-person\ndependency count, cycle time\nCHANGE: failure rate %, changes without impact assessment, PIR completion\nrate, emergency change rate\nCOMPLIANCE: obligation currency %, evidence age, open audit findings,\nregulatory change response time\nRISK: register review completion %, risks above appetite, mitigation\ncompletion rate, risk materialisation rate\nINCIDENT: MTTR, MTTD, CA completion rate, repeat incident rate\n\n## NEVER DO THESE\n\n- NEVER report only lagging indicators -- by the time they are red,\n  the problem has already occurred; leading indicators prevent it\n- NEVER define a metric by its data source rather than what it measures\n  (\"Zendesk tickets\" is a data source; \"unresolved customer issues rate\"\n  is a metric)\n- NEVER produce a monthly report without the KEY ISSUES section --\n  the report's value is in driving decisions, not documenting data\n- NEVER design a framework with more than 10 executive dashboard metrics\n- NEVER omit the formula field -- ambiguous calculation leads to\n  inconsistent measurement and disputed results\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n",{"name":5,"license":14,"metadata":47,"description":52},{"author":48,"version":49,"plugin-commands":50,"mcp-integrations":51},"Panaversity","1.0","\u002Fmetrics","ERP, ITSM, compliance system, document store","Activate for: metrics, KPI, operational metrics, performance metrics, operational dashboard, performance measurement, operations reporting, monthly report operations, operations scorecard, leading indicator, lagging indicator, red amber green, RAG status, operational performance, KRI, key risk indicator, SLA metrics, efficiency metrics, throughput, cycle time, error rate, cost per transaction, operational excellence, metrics framework, dashboard design, metric definition. NOT for: generating status reports (use official \u002Fstatus-report), vendor performance scoring (use official \u002Fvendor-review), risk register building (use official risk-assessment auto-skill).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-operations-intelligence-skills-metrics-skill-d0dafa70","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill metrics",{"tool":65,"command":66},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill metrics",{"tool":68,"command":69},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill metrics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-operations-intelligence-skills-metrics-skill-d0dafa70\u002FSKILL.md",true,[],[74,101,128,159,187,221],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":42},"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",[],[76,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":42},"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",[],[108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127],"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":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":140,"publishedAt":42},"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",[134,137],{"categoryNo":135,"categoryName":136,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[141,142,143,144,145,146,147,148,149,150,151,152,153,94,154,155,156,157,99,158],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":42},"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",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[169,170,171,172,173,174,175,176,177,94,178,179,180,181,182,183,184,185,186,99],"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":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":204,"publishedAt":42},"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",[193,196,201],{"categoryNo":194,"categoryName":195,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":197,"categoryName":198,"taxonomyType":199,"taxonomyTypeDesc":200},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":202,"categoryName":203,"taxonomyType":199,"taxonomyTypeDesc":200},"01JBSEEDCAT000000000000038","人力资源",[205,206,207,208,209,210,211,212,109,213,94,214,215,216,32,217,218,219,99,220],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","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":78,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":227,"publishedAt":42},"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,230,231,232,208,233,94,217,234,235,236,237,238,239,240,241,242,99,243],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]