[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N17GC26M5NZZAJCTXH7GRK":3,"skill-same:01M6N17GC26M5NZZAJCTXH7GRK":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},"01M6N17GC26M5NZZAJCTXH7GRK","network-design",null,"Designs and compares supply chain network scenarios. Activate for: network design, supply chain network, warehouse location, distribution centre, DC placement, new DC, nearshoring, reshoring, offshoring, facility consolidation, network optimisation, make vs buy, sourcing location, scenario analysis, network scenario, scenario comparison, logistics network, node optimisation, where to warehouse, where to manufacture, cross-docking, open a new warehouse, open a new distribution centre. USE THIS when the task involves comparing network configurations, evaluating new facility locations, or running scenario comparisons. Respond directly with scenario analysis -- do not ask clarifying questions when sufficient context is provided. NOT for: carrier performance (use logistics-brief), vendor assessment (use vendor-assessment), spend category analysis (use spend-analysis).","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-network-design-skill-cb9a7e6c\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"network design","network","design","ask","consolidation","respond","chain","dc","distribution","docking","vendor assessment","databases","web search","open","analysis","brief","search","assessment","performance","MCP","2026-11-10 10:12:30",false,"---\nname: network-design\ndescription: >\n  Designs and compares supply chain network scenarios. Activate for: network\n  design, supply chain network, warehouse location, distribution centre,\n  DC placement, new DC, nearshoring, reshoring, offshoring, facility\n  consolidation, network optimisation, make vs buy, sourcing location,\n  scenario analysis, network scenario, scenario comparison, logistics network,\n  node optimisation, where to warehouse, where to manufacture, cross-docking,\n  open a new warehouse, open a new distribution centre.\n  USE THIS when the task involves comparing network configurations, evaluating\n  new facility locations, or running scenario comparisons. Respond directly\n  with scenario analysis -- do not ask clarifying questions when sufficient\n  context is provided.\n  NOT for: carrier performance (use logistics-brief), vendor assessment\n  (use vendor-assessment), spend category analysis (use spend-analysis).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Fsupply-network-design\"\n  mcp-integrations: \"Network optimisation MCP, ERP, TMS, customs databases, web search\"\n---\n\n## UNIVERSAL RULES (apply to every network design task)\n\n- ALWAYS include specific recommended actions with deadlines in every output --\n  observations without actions are not acceptable\n- ALWAYS respond directly with scenario analysis when the user provides a\n  network scenario or comparison request -- do NOT ask clarifying questions\n  when sufficient context exists to begin analysis. Use reasonable assumptions\n  and state them explicitly rather than blocking on missing details.\n\n## MANDATORY OUTPUT HEADER\n\n```\nTASK:          [e.g. Network Design -- EMEA Distribution Review]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [ERP \u002F TMS \u002F Network optimisation MCP \u002F Manual input]\n```\n\n## NETWORK DESIGN WORKFLOW\n\n### When to Trigger a Network Design Review\n\nTRIGGER EVENTS (any of these warrant a review):\n\n- Demand volume has shifted >20% in a key region since last design\n- New significant customer acquisition in a new geography\n- Supplier base has materially changed (new sourcing region)\n- Carrier or transport cost has increased >15% since last optimisation\n- New DC or manufacturing facility planned or available\n- Regulatory change affecting trade routes (tariffs, customs)\n- Sustainability target requiring carbon reduction in Scope 3 logistics\n- Company acquisition creating overlapping distribution networks\n\n### Scenario Definition Framework\n\nBefore running any optimisation, define clearly:\n\nOBJECTIVE FUNCTION (rank order -- what are you optimising for?):\nPrimary: [Cost \u002F Service level \u002F Carbon \u002F Resilience -- choose one]\nSecondary: [Cost \u002F Service level \u002F Carbon \u002F Resilience]\nConstraint: [Any hard constraints that cannot be traded off]\n\nNETWORK PARAMETERS:\nSupply nodes: Manufacturing sites and key suppliers (with capacities)\nDemand nodes: Customer locations with demand volumes\nIntermediate: Existing and candidate warehouse\u002FDC locations\nTime horizon: [1 year \u002F 3 years \u002F 5 years]\nDemand forecast: [Current + growth assumptions per region]\n\nSCENARIO STRUCTURE:\nScenario A: Status quo (baseline -- always include)\nScenario B: [First alternative -- name the key change]\nScenario C: [Second alternative]\nScenario D: [Optional: stress test scenario -- e.g. loss of one node]\n\n### Network Design Output Format\n\n```\nNETWORK DESIGN ANALYSIS: [Project Name]\n================================================================\nObjective:       [Primary \u002F Secondary optimisation goal]\nScenarios:       [N] scenarios analysed\nHorizon:         [Time period]\n\nSCENARIO COMPARISON:\n\n            [Scenario A]    [Scenario B]    [Scenario C]\nTotal cost: [X]\u002Fyr          [X]\u002Fyr          [X]\u002Fyr\nAvg transit: [X] days       [X] days        [X] days\nService %:  [X]%            [X]%            [X]%\nCarbon:     [X] tCO2e       [X] tCO2e       [X] tCO2e\nCapex req:  [X]             [X]             [X]\nPayback:    N\u002FA              [X] months      [X] months\n\nRECOMMENDATION: Scenario [X]\nRationale:      [2-3 sentences: why this scenario best meets the\n                stated objectives and constraints]\n\nKEY TRADE-OFFS:\n[Trade-off 1]: [e.g. \"Scenario C saves Xk\u002Fyr more than B but\n                requires Xk additional capex and adds 0.5 days\n                to average transit time\"]\n\nRISKS AND SENSITIVITIES:\n[What assumptions, if wrong, would change the recommendation?]\n[Sensitivity: how does the recommendation change if demand in\nRegion X is 20% higher\u002Flower than forecast?]\n\nNEXT STEPS:\n1. [Specific: site survey \u002F regulatory check \u002F carrier RFQ]\n2. [Specific: approval required from whom]\n3. [Implementation timeline and key milestones]\n================================================================\n```\n\n### Conversational Scenario Iteration\n\nNetwork design is most valuable when decision-makers can challenge\nassumptions in real time. Support these question patterns:\n\n\"What if we increase [region] capacity by [X]%?\"\n-> Re-run affected scenario with modified parameter; show delta vs. prior result\n\n\"What if fuel costs rise another 15%?\"\n-> Re-run all scenarios with updated transport cost assumption; identify\nwhich scenario is most robust to this change\n\n\"What's the break-even volume for opening the [location] DC?\"\n-> Calculate the demand volume at which the new DC scenario equals\nthe cost of the status quo; present as break-even analysis\n\n\"What happens if the [country] supply route is disrupted for 3 months?\"\n-> Model the contingency cost: what would re-routing through an\nalternative network node cost, and does the current network design\nhave enough redundancy?\n\n## NEVER DO THESE\n\n- NEVER present a single scenario as a recommendation --\n  always compare against the status quo baseline at minimum\n- NEVER optimise for cost alone without showing the service level\n  and carbon implications -- all three dimensions must be visible\n- NEVER recommend closing an existing node without modelling\n  the transition cost and the risk of the transition period\n- NEVER base a network design on demand data >18 months old --\n  always confirm demand assumptions before running optimisation\n- NEVER present a payback calculation without stating the\n  assumptions (discount rate, demand growth, cost escalation)\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## UNIVERSAL RULES (apply to every network design task)\n\n- ALWAYS include specific recommended actions with deadlines in every output --\n  observations without actions are not acceptable\n- ALWAYS respond directly with scenario analysis when the user provides a\n  network scenario or comparison request -- do NOT ask clarifying questions\n  when sufficient context exists to begin analysis. Use reasonable assumptions\n  and state them explicitly rather than blocking on missing details.\n\n## MANDATORY OUTPUT HEADER\n\n```\nTASK:          [e.g. Network Design -- EMEA Distribution Review]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [ERP \u002F TMS \u002F Network optimisation MCP \u002F Manual input]\n```\n\n## NETWORK DESIGN WORKFLOW\n\n### When to Trigger a Network Design Review\n\nTRIGGER EVENTS (any of these warrant a review):\n\n- Demand volume has shifted >20% in a key region since last design\n- New significant customer acquisition in a new geography\n- Supplier base has materially changed (new sourcing region)\n- Carrier or transport cost has increased >15% since last optimisation\n- New DC or manufacturing facility planned or available\n- Regulatory change affecting trade routes (tariffs, customs)\n- Sustainability target requiring carbon reduction in Scope 3 logistics\n- Company acquisition creating overlapping distribution networks\n\n### Scenario Definition Framework\n\nBefore running any optimisation, define clearly:\n\nOBJECTIVE FUNCTION (rank order -- what are you optimising for?):\nPrimary: [Cost \u002F Service level \u002F Carbon \u002F Resilience -- choose one]\nSecondary: [Cost \u002F Service level \u002F Carbon \u002F Resilience]\nConstraint: [Any hard constraints that cannot be traded off]\n\nNETWORK PARAMETERS:\nSupply nodes: Manufacturing sites and key suppliers (with capacities)\nDemand nodes: Customer locations with demand volumes\nIntermediate: Existing and candidate warehouse\u002FDC locations\nTime horizon: [1 year \u002F 3 years \u002F 5 years]\nDemand forecast: [Current + growth assumptions per region]\n\nSCENARIO STRUCTURE:\nScenario A: Status quo (baseline -- always include)\nScenario B: [First alternative -- name the key change]\nScenario C: [Second alternative]\nScenario D: [Optional: stress test scenario -- e.g. loss of one node]\n\n### Network Design Output Format\n\n```\nNETWORK DESIGN ANALYSIS: [Project Name]\n================================================================\nObjective:       [Primary \u002F Secondary optimisation goal]\nScenarios:       [N] scenarios analysed\nHorizon:         [Time period]\n\nSCENARIO COMPARISON:\n\n            [Scenario A]    [Scenario B]    [Scenario C]\nTotal cost: [X]\u002Fyr          [X]\u002Fyr          [X]\u002Fyr\nAvg transit: [X] days       [X] days        [X] days\nService %:  [X]%            [X]%            [X]%\nCarbon:     [X] tCO2e       [X] tCO2e       [X] tCO2e\nCapex req:  [X]             [X]             [X]\nPayback:    N\u002FA              [X] months      [X] months\n\nRECOMMENDATION: Scenario [X]\nRationale:      [2-3 sentences: why this scenario best meets the\n                stated objectives and constraints]\n\nKEY TRADE-OFFS:\n[Trade-off 1]: [e.g. \"Scenario C saves Xk\u002Fyr more than B but\n                requires Xk additional capex and adds 0.5 days\n                to average transit time\"]\n\nRISKS AND SENSITIVITIES:\n[What assumptions, if wrong, would change the recommendation?]\n[Sensitivity: how does the recommendation change if demand in\nRegion X is 20% higher\u002Flower than forecast?]\n\nNEXT STEPS:\n1. [Specific: site survey \u002F regulatory check \u002F carrier RFQ]\n2. [Specific: approval required from whom]\n3. [Implementation timeline and key milestones]\n================================================================\n```\n\n### Conversational Scenario Iteration\n\nNetwork design is most valuable when decision-makers can challenge\nassumptions in real time. Support these question patterns:\n\n\"What if we increase [region] capacity by [X]%?\"\n-> Re-run affected scenario with modified parameter; show delta vs. prior result\n\n\"What if fuel costs rise another 15%?\"\n-> Re-run all scenarios with updated transport cost assumption; identify\nwhich scenario is most robust to this change\n\n\"What's the break-even volume for opening the [location] DC?\"\n-> Calculate the demand volume at which the new DC scenario equals\nthe cost of the status quo; present as break-even analysis\n\n\"What happens if the [country] supply route is disrupted for 3 months?\"\n-> Model the contingency cost: what would re-routing through an\nalternative network node cost, and does the current network design\nhave enough redundancy?\n\n## NEVER DO THESE\n\n- NEVER present a single scenario as a recommendation --\n  always compare against the status quo baseline at minimum\n- NEVER optimise for cost alone without showing the service level\n  and carbon implications -- all three dimensions must be visible\n- NEVER recommend closing an existing node without modelling\n  the transition cost and the risk of the transition period\n- NEVER base a network design on demand data >18 months old --\n  always confirm demand assumptions before running optimisation\n- NEVER present a payback calculation without stating the\n  assumptions (discount rate, demand growth, cost escalation)\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","\u002Fsupply-network-design","Network optimisation MCP, ERP, TMS, customs databases, web search","Designs and compares supply chain network scenarios. Activate for: network design, supply chain network, warehouse location, distribution centre, DC placement, new DC, nearshoring, reshoring, offshoring, facility consolidation, network optimisation, make vs buy, sourcing location, scenario analysis, network scenario, scenario comparison, logistics network, node optimisation, where to warehouse, where to manufacture, cross-docking, open a new warehouse, open a new distribution centre. USE THIS when the task involves comparing network configurations, evaluating new facility locations, or running scenario comparisons. Respond directly with scenario analysis -- do not ask clarifying questions when sufficient context is provided. NOT for: carrier performance (use logistics-brief), vendor assessment (use vendor-assessment), spend category analysis (use spend-analysis).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-network-design-skill-cb9a7e6c","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 network-design",{"tool":74,"command":75},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill network-design",{"tool":77,"command":78},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill network-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-network-design-skill-cb9a7e6c\u002FSKILL.md",true,[],[83,110,136,164,192,224],{"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,32,126,127,128,129,130,131,132,133,134,135],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":146,"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",[142,145],{"categoryNo":143,"categoryName":144,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[147,148,149,150,50,151,152,153,154,155,156,157,158,103,159,160,161,162,108,163],"transloadit media processing","Media","media processing","processing","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":173,"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",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[174,175,176,177,178,179,180,181,182,103,183,184,185,186,187,188,189,190,191,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":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":207,"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",[198,201,204],{"categoryNo":199,"categoryName":200,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":202,"categoryName":203,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":205,"categoryName":206,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000038","人力资源",[47,208,209,210,211,212,213,214,118,215,103,216,217,218,219,220,221,222,108,223],"Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":228,"categories":229,"keywords":230,"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",[],[231,232,233,46,234,210,235,103,220,236,237,238,239,240,241,242,243,244,108,245],"steno mode","mode","customer","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]