[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N17AMW8QJNWH7BJXJAKWT6":3,"skill-same:01M6N17AMW8QJNWH7BJXJAKWT6":69},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":13,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6N17AMW8QJNWH7BJXJAKWT6","logistics-brief",null,"Activate for: logistics, carrier, freight, shipping, route, delivery, on-time delivery, OTD carrier, logistics performance, carrier review, freight cost, cost per kg, lane analysis, route optimisation, logistics brief, carrier scorecard, logistics KPI, shipping performance, freight audit, expedited freight, premium freight, mode of transport, logistics network, carbon emissions, Scope 3 logistics. NOT for: supply network facility placement (use network-design), 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-logistics-brief-skill-ead72431\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"logistics brief","brief","vendor assessment","freight","for","mode","scorecard","supply","emissions","scope","time","design","databases","use","erp","analysis","kpi","lane","assessment","performance","2026-11-10 10:12:30",false,"---\nname: logistics-brief\ndescription: >\n  Activate for: logistics, carrier, freight, shipping, route, delivery,\n  on-time delivery, OTD carrier, logistics performance, carrier review,\n  freight cost, cost per kg, lane analysis, route optimisation, logistics brief,\n  carrier scorecard, logistics KPI, shipping performance, freight audit,\n  expedited freight, premium freight, mode of transport, logistics network,\n  carbon emissions, Scope 3 logistics.\n  NOT for: supply network facility placement (use network-design), vendor\n  assessment (use vendor-assessment), spend category analysis (use spend-analysis).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Flogistics-brief\"\n  mcp-integrations: \"TMS, ERP, carrier APIs, freight rate databases\"\n---\n\n## UNIVERSAL RULES (apply to every logistics task)\n\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. Carrier Performance Review -- Q1 2024]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [TMS \u002F ERP \u002F Carrier APIs \u002F Manual input]\n```\n\n## LOGISTICS BRIEF TYPES\n\n### Type 1: Carrier Performance Review\n\nUse for: periodic carrier performance assessment, contract negotiation prep,\ncarrier selection, carrier exit decision.\n\nDATA REQUIRED (from TMS or ERP, for defined period):\n\n- Shipment volume by carrier (number of shipments + weight\u002Funits shipped)\n- On-time delivery rate by carrier (shipments delivered on or before promised date)\n- Damage rate and claim value by carrier\n- Cost per kg (or per shipment) by carrier\n- Track-and-trace reliability (% shipments with real-time tracking events)\n- Carrier compliance: invoicing accuracy vs. contracted rates\n\nCARRIER SCORECARD FORMAT:\n\n```\nCARRIER PERFORMANCE SCORECARD -- [Period]\n================================================================\n                 Shipments  OTD%   Damage%  Cost\u002Fkg  Track%  Score\n[Carrier A]      [N]        [X]%   [X]%     [X]      [X]%    [X]\u002F5\n[Carrier B]      [N]        [X]%   [X]%     [X]      [X]%    [X]\u002F5\n\nSCORING KEY:\nOTD >= 95%: 5\u002F5  |  93-95%: 4\u002F5  |  90-93%: 3\u002F5  |  \u003C90%: FLAG\nDamage \u003C 0.2%: 5\u002F5  |  0.2-0.5%: 3\u002F5  |  >0.5%: FLAG\nCost: benchmark against market rate (see local config)\nTrack >= 98%: 5\u002F5  |  95-98%: 3\u002F5  |  \u003C95%: FLAG\n\nFINDINGS:\nRED [Carrier underperforming]: [specific metric] -- recommended action\nAMBER [Carrier at risk]:       [trend concern] -- monitor; review at [date]\nPASS [Carrier outperforming]:  [strength] -- protect relationship\n\nLANE ROUTING RECOMMENDATIONS:\n[Lane]: current routing -> optimal routing | saving: [X]\u002Fmonth\n================================================================\n```\n\n### Type 2: Lane Optimisation Analysis\n\nUse for: specific origin-destination analysis; carrier selection for a new lane;\nmode of transport optimisation.\n\nINPUT REQUIRED:\n\n- Origin and destination (city\u002Fpostcode\u002Fcountry)\n- Shipment profile: volume (units\u002Fkg), frequency, typical parcel dimensions\n- Service requirement: transit time; temperature controlled; track-and-trace\n- Current arrangement: carrier, mode, cost, SLA\n- Available alternatives (if known -- agent will also identify via MCP)\n\nANALYSIS OUTPUT:\n\n```\nLANE ANALYSIS: [Origin] -> [Destination]\n---------------------------------------------------------\nShipment profile:  [Volume, frequency, specification]\nService req:       [Transit time; special requirements]\n\nOPTION COMPARISON:\n            Mode      Transit  Cost\u002Fkg  OTD%   Carbon   Score\nCurrent:    [Mode]    [X days] [X]      [X]%   [X]g     [X]\u002F5\nOption A:   [Mode]    [X days] [X]      [X]%   [X]g     [X]\u002F5\nOption B:   [Mode]    [X days] [X]      [X]%   [X]g     [X]\u002F5\n\nRECOMMENDATION: [Option] because [specific rationale]\nAnnual saving vs. current: [X]\nService trade-off: [Any service level change]\nCarbon trade-off: [Any carbon change]\n---------------------------------------------------------\n```\n\n### Type 3: Expedited Freight Analysis\n\nUse for: investigating high premium freight spend; root cause analysis;\nupstream problem identification.\n\nOUTPUT:\n\n- Total expedited spend (% of total freight budget)\n- Expedited volume by business unit \u002F site \u002F category\n- Root cause classification:\n  a) Late supplier delivery (procurement\u002Fvendor issue)\n  b) Demand forecast error (planning issue)\n  c) Inventory positioning error (supply chain design issue)\n  d) Customer emergency (valid commercial reason)\n  e) Production planning error (internal operations)\n- Recommended intervention by root cause category\n- Quantified saving if root cause is addressed\n\nRULE: Expedited freight > 10% of total freight spend indicates an upstream\nsupply chain design or process problem, not a logistics problem.\nSolving it at the logistics level (buying more premium capacity) masks\nand perpetuates the underlying issue.\n\n### Type 4: Carbon Assessment\n\nUse for: Scope 3 emissions reporting; sustainability target setting;\nmode-shift analysis; decarbonisation planning.\n\nOUTPUT:\n\n- Total logistics Scope 3 emissions (tCO2e) by carrier and lane\n- Emissions intensity (gCO2e per km-tonne shipped)\n- Breakdown by transport mode\n- Highest-emission routes\n- Mode-shift options with cost and service trade-offs\n- Estimated reduction from implementing each option\n\nEMISSIONS REFERENCE (approximate; verify with actual carrier data):\nAir freight: 500-600 gCO2e per tonne-km\nRoad (HGV): 60-80 gCO2e per tonne-km\nRail (electric): 20-30 gCO2e per tonne-km\nSea (container): 10-15 gCO2e per tonne-km\n\n## NEVER DO THESE\n\n- NEVER recommend exiting an underperforming carrier without confirming\n  alternative capacity is available for the affected lanes\n- NEVER use cost per shipment as the sole metric -- cost per kg\n  normalises for shipment size differences\n- NEVER accept carrier invoice rate creep without audit:\n  compare actual invoiced rate to contracted rate line by line\n- NEVER diagnose an expedited freight problem as a logistics problem\n  without first checking whether the root cause is upstream\n- NEVER report carbon figures without the source and methodology --\n  Scope 3 emissions data quality varies significantly by carrier\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## UNIVERSAL RULES (apply to every logistics task)\n\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. Carrier Performance Review -- Q1 2024]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [TMS \u002F ERP \u002F Carrier APIs \u002F Manual input]\n```\n\n## LOGISTICS BRIEF TYPES\n\n### Type 1: Carrier Performance Review\n\nUse for: periodic carrier performance assessment, contract negotiation prep,\ncarrier selection, carrier exit decision.\n\nDATA REQUIRED (from TMS or ERP, for defined period):\n\n- Shipment volume by carrier (number of shipments + weight\u002Funits shipped)\n- On-time delivery rate by carrier (shipments delivered on or before promised date)\n- Damage rate and claim value by carrier\n- Cost per kg (or per shipment) by carrier\n- Track-and-trace reliability (% shipments with real-time tracking events)\n- Carrier compliance: invoicing accuracy vs. contracted rates\n\nCARRIER SCORECARD FORMAT:\n\n```\nCARRIER PERFORMANCE SCORECARD -- [Period]\n================================================================\n                 Shipments  OTD%   Damage%  Cost\u002Fkg  Track%  Score\n[Carrier A]      [N]        [X]%   [X]%     [X]      [X]%    [X]\u002F5\n[Carrier B]      [N]        [X]%   [X]%     [X]      [X]%    [X]\u002F5\n\nSCORING KEY:\nOTD >= 95%: 5\u002F5  |  93-95%: 4\u002F5  |  90-93%: 3\u002F5  |  \u003C90%: FLAG\nDamage \u003C 0.2%: 5\u002F5  |  0.2-0.5%: 3\u002F5  |  >0.5%: FLAG\nCost: benchmark against market rate (see local config)\nTrack >= 98%: 5\u002F5  |  95-98%: 3\u002F5  |  \u003C95%: FLAG\n\nFINDINGS:\nRED [Carrier underperforming]: [specific metric] -- recommended action\nAMBER [Carrier at risk]:       [trend concern] -- monitor; review at [date]\nPASS [Carrier outperforming]:  [strength] -- protect relationship\n\nLANE ROUTING RECOMMENDATIONS:\n[Lane]: current routing -> optimal routing | saving: [X]\u002Fmonth\n================================================================\n```\n\n### Type 2: Lane Optimisation Analysis\n\nUse for: specific origin-destination analysis; carrier selection for a new lane;\nmode of transport optimisation.\n\nINPUT REQUIRED:\n\n- Origin and destination (city\u002Fpostcode\u002Fcountry)\n- Shipment profile: volume (units\u002Fkg), frequency, typical parcel dimensions\n- Service requirement: transit time; temperature controlled; track-and-trace\n- Current arrangement: carrier, mode, cost, SLA\n- Available alternatives (if known -- agent will also identify via MCP)\n\nANALYSIS OUTPUT:\n\n```\nLANE ANALYSIS: [Origin] -> [Destination]\n---------------------------------------------------------\nShipment profile:  [Volume, frequency, specification]\nService req:       [Transit time; special requirements]\n\nOPTION COMPARISON:\n            Mode      Transit  Cost\u002Fkg  OTD%   Carbon   Score\nCurrent:    [Mode]    [X days] [X]      [X]%   [X]g     [X]\u002F5\nOption A:   [Mode]    [X days] [X]      [X]%   [X]g     [X]\u002F5\nOption B:   [Mode]    [X days] [X]      [X]%   [X]g     [X]\u002F5\n\nRECOMMENDATION: [Option] because [specific rationale]\nAnnual saving vs. current: [X]\nService trade-off: [Any service level change]\nCarbon trade-off: [Any carbon change]\n---------------------------------------------------------\n```\n\n### Type 3: Expedited Freight Analysis\n\nUse for: investigating high premium freight spend; root cause analysis;\nupstream problem identification.\n\nOUTPUT:\n\n- Total expedited spend (% of total freight budget)\n- Expedited volume by business unit \u002F site \u002F category\n- Root cause classification:\n  a) Late supplier delivery (procurement\u002Fvendor issue)\n  b) Demand forecast error (planning issue)\n  c) Inventory positioning error (supply chain design issue)\n  d) Customer emergency (valid commercial reason)\n  e) Production planning error (internal operations)\n- Recommended intervention by root cause category\n- Quantified saving if root cause is addressed\n\nRULE: Expedited freight > 10% of total freight spend indicates an upstream\nsupply chain design or process problem, not a logistics problem.\nSolving it at the logistics level (buying more premium capacity) masks\nand perpetuates the underlying issue.\n\n### Type 4: Carbon Assessment\n\nUse for: Scope 3 emissions reporting; sustainability target setting;\nmode-shift analysis; decarbonisation planning.\n\nOUTPUT:\n\n- Total logistics Scope 3 emissions (tCO2e) by carrier and lane\n- Emissions intensity (gCO2e per km-tonne shipped)\n- Breakdown by transport mode\n- Highest-emission routes\n- Mode-shift options with cost and service trade-offs\n- Estimated reduction from implementing each option\n\nEMISSIONS REFERENCE (approximate; verify with actual carrier data):\nAir freight: 500-600 gCO2e per tonne-km\nRoad (HGV): 60-80 gCO2e per tonne-km\nRail (electric): 20-30 gCO2e per tonne-km\nSea (container): 10-15 gCO2e per tonne-km\n\n## NEVER DO THESE\n\n- NEVER recommend exiting an underperforming carrier without confirming\n  alternative capacity is available for the affected lanes\n- NEVER use cost per shipment as the sole metric -- cost per kg\n  normalises for shipment size differences\n- NEVER accept carrier invoice rate creep without audit:\n  compare actual invoiced rate to contracted rate line by line\n- NEVER diagnose an expedited freight problem as a logistics problem\n  without first checking whether the root cause is upstream\n- NEVER report carbon figures without the source and methodology --\n  Scope 3 emissions data quality varies significantly by carrier\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n",{"name":5,"license":14,"metadata":43,"description":48},{"author":44,"version":45,"plugin-commands":46,"mcp-integrations":47},"Panaversity","1.0","\u002Flogistics-brief","TMS, ERP, carrier APIs, freight rate databases","Activate for: logistics, carrier, freight, shipping, route, delivery, on-time delivery, OTD carrier, logistics performance, carrier review, freight cost, cost per kg, lane analysis, route optimisation, logistics brief, carrier scorecard, logistics KPI, shipping performance, freight audit, expedited freight, premium freight, mode of transport, logistics network, carbon emissions, Scope 3 logistics. NOT for: supply network facility placement (use network-design), vendor assessment (use vendor-assessment), spend category analysis (use spend-analysis).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-logistics-brief-skill-ead72431","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill logistics-brief",{"tool":61,"command":62},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill logistics-brief",{"tool":64,"command":65},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill logistics-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-logistics-brief-skill-ead72431\u002FSKILL.md",true,[],[70,94,121,154,182,217],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":38},"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",[],[72,78,79,80,81,82,83,84,85,86,87,88,89,31,90,91,92,27,22,93],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","ready","unrelated","app","webmcp",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":38},"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",[],[101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":135,"publishedAt":38},"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",[127,132],{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":133,"categoryName":134,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000023","Skill与智能体开发",[136,137,138,139,140,141,142,143,144,145,146,147,148,31,149,150,151,152,22,153],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":38},"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",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000011","运维与部署",[164,165,166,167,168,169,170,171,172,31,173,174,175,176,177,178,179,180,181,22],"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":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":199,"publishedAt":38},"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",[188,191,196],{"categoryNo":189,"categoryName":190,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":192,"categoryName":193,"taxonomyType":194,"taxonomyTypeDesc":195},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":197,"categoryName":198,"taxonomyType":194,"taxonomyTypeDesc":195},"01JBSEEDCAT000000000000038","人力资源",[200,201,202,203,204,205,206,207,102,208,31,209,210,211,212,213,214,215,22,216],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","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":74,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":38},"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,23,225,19,226,203,227,31,213,228,229,230,231,232,233,234,235,236,22,237],"steno mode","customer","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]