[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N186AC8Z8S1YFVT9R4VTMX":3,"skill-same:01M6N186AC8Z8S1YFVT9R4VTMX":79},{"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":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":13,"repositoryHtmlUrl":62,"repositoryHomepageUrl":6,"ownerHtmlUrl":63,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6N186AC8Z8S1YFVT9R4VTMX","supply-chain-brief",null,"Activate for: supply chain brief, weekly supply chain report, CPO report, COO report, procurement dashboard, supply chain dashboard, weekly report, executive brief, supply chain KPIs, supply chain metrics, procurement performance, logistics performance summary, vendor performance summary, AP performance, weekly update, supply chain status. NOT for: detailed vendor assessment (use vendor-assessment), detailed invoice reconciliation (use invoice-reconciliation), detailed carrier review (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-supply-chain-brief-skill-ee38fccf\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"supply chain brief","supply","chain","supply chain","brief","procurement","weekly","supply chain dashboard","reconciliation","activate","vendor assessment","review","supply-chain","monitoring","metrics","update","assessment","status","dashboard","performance","2026-11-10 10:12:30",false,"---\nname: supply-chain-brief\ndescription: >\n  Activate for: supply chain brief, weekly supply chain report, CPO report,\n  COO report, procurement dashboard, supply chain dashboard, weekly report,\n  executive brief, supply chain KPIs, supply chain metrics, procurement\n  performance, logistics performance summary, vendor performance summary,\n  AP performance, weekly update, supply chain status.\n  NOT for: detailed vendor assessment (use vendor-assessment), detailed\n  invoice reconciliation (use invoice-reconciliation), detailed carrier\n  review (use logistics-brief).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Fsupply-chain-brief\"\n  mcp-integrations: \"ERP, AP system, TMS, contract register, risk monitoring outputs\"\n---\n\n## UNIVERSAL RULES (apply to every brief task)\n\n- ALWAYS include specific recommended actions with deadlines in every output --\n  observations without actions are not acceptable\n- NEVER delay an escalation alert to include it in the next weekly brief --\n  time-sensitive signals require immediate notification\n\n## MANDATORY OUTPUT HEADER\n\n```\nTASK:          [e.g. Weekly Supply Chain Brief -- Week of 2024-03-18]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [ERP \u002F AP \u002F TMS \u002F Contract register \u002F Risk monitoring]\n```\n\n## WEEKLY SUPPLY CHAIN BRIEF WORKFLOW\n\n### Data Pull (automated via MCP -- every Monday morning)\n\nFROM ERP:\n\n- Vendor OTD by tier (prior week + 13-week rolling average)\n- Quality rejection rate by tier (prior week + 13-week rolling)\n- Open purchase orders overdue (count + value)\n- Stock-outs or near-stock-outs flagged (where inventory tracking enabled)\n\nFROM AP SYSTEM:\n\n- Invoices processed (total \u002F straight-through \u002F exception rate)\n- Exception rate by type (price variance \u002F qty variance \u002F PO not found)\n- Open disputes (count + value + age)\n- AP ageing: invoices approaching payment term deadline\n- Early payment discounts captured vs. missed (where applicable)\n\nFROM TMS \u002F LOGISTICS:\n\n- Carrier OTD by carrier (prior week + 4-week rolling)\n- Damage and claim rate\n- Cost per kg vs. prior week and vs. contracted rate\n- Expedited freight % of total shipments\n\nFROM CONTRACT REGISTER:\n\n- Contracts expiring within 90 days (with notice deadline)\n- Certifications expiring within 90 days\n- Any contracts where notice deadline is within 30 days (URGENT)\n\nFROM VENDOR RISK MONITORING:\n\n- New risk signals this week (count by severity)\n- Active escalations (count + vendor names)\n- Contingency plans active (count)\n\n### Executive Brief Output Format\n\n```\nSUPPLY CHAIN WEEKLY BRIEF -- Week of [Date]\nPrepared: [Day] [Time] | For: CPO, COO\n================================================================\n\nTRAFFIC LIGHT SUMMARY\nVendor Performance:    [GREEN \u002F AMBER \u002F RED]  OTD: [X]%  Quality rej: [X]%\nInvoice Processing:    [GREEN \u002F AMBER \u002F RED]  Exception rate: [X]%  Open disputes: [X]\nLogistics:             [GREEN \u002F AMBER \u002F RED]  Carrier OTD: [X]%  Cost\u002Fkg: [X]\nVendor Risk:           [GREEN \u002F AMBER \u002F RED]  Active alerts: [N]  Escalations: [N]\nContract Calendar:     [GREEN \u002F AMBER \u002F RED]  Renewals due 90d: [N]  URGENT: [N]\n\nTHIS WEEK'S HIGHLIGHTS\n\nWIN:\n[The single most positive supply chain development this week -- specific]\n\nRISK:\n[The single most important issue requiring CPO\u002FCOO attention -- specific,\n with recommended action and deadline]\n\nDECISION REQUIRED:\n[One thing leadership needs to decide or unblock -- specific]\n\nLEADING INDICATOR STATUS\nVendor OTD trend (13-week):  [Improving \u002F Stable \u002F Declining]\nInvoice exception trend:     [Improving \u002F Stable \u002F Declining]\nActive risk alerts trend:    [Improving \u002F Stable \u002F Declining]\n\nAT-RISK SITUATIONS REQUIRING LEADERSHIP ATTENTION\n[Vendor \u002F Issue]  [Risk level]  [Time-sensitivity]  [Recommended action]\n\nCONTRACT CALENDAR -- URGENT (notice deadline within 30 days)\n[Contract]  [Expiry]  [Notice deadline]  [Decision needed]\n\nSAVINGS PIPELINE THIS WEEK\nNew opportunities identified: [X]\nSavings captured this week:   [X]\nYTD savings captured:         [X]  vs. target: [X]\n================================================================\n```\n\n### Full Operations Report Format (monthly -- for operations meeting)\n\nExpand the weekly brief with:\n\n- Month-on-month trend charts (described as data for chart generation)\n- Category-by-category vendor performance\n- AP exception analysis with root cause breakdown\n- Logistics: carrier comparison, lane performance, expedited root cause\n- Risk matrix: all monitored vendors plotted by likelihood x impact\n- Savings pipeline: all active opportunities with owner and status\n- Forward look: key decisions and actions required in next 30 days\n\n### Escalation Alert Format (immediate -- not in weekly cycle)\n\nTrigger escalation alert immediately for:\n\n- Any Tier 1 Strategic vendor OTD below 75% in any single week\n- Financial distress news on any Strategic or Bottleneck vendor\n- Bank detail change attempt on any active vendor (fraud alert)\n- Invoice fraud attempt detected (duplicate + amount manipulation)\n- Logistics disruption affecting >20% of weekly shipment volume\n- Contract notice deadline missed (requires legal consultation)\n\n```\nESCALATION ALERT -- [Timestamp]\n---------------------------------------------------------\nAlert type:    [Category]\nSeverity:      RED CRITICAL \u002F AMBER HIGH\nDescription:   [Specific facts only -- no speculation]\nImmediate action required: [What must happen in next 24 hours]\nEscalate to:   [Named individuals]\n---------------------------------------------------------\n```\n\n## NEVER DO THESE\n\n- NEVER produce a supply chain brief that is longer than one page\n  for the CPO\u002FCOO audience -- they need the headline, the risk,\n  and the action; not the full analysis (link to detail if needed)\n- NEVER present metrics without comparison to target or prior period --\n  a number without context is meaningless\n- NEVER omit the DECISION REQUIRED section -- the brief exists to\n  drive decisions, not to report history\n- NEVER delay an escalation alert to include it in the next\n  weekly brief -- time-sensitive signals require immediate notification\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## UNIVERSAL RULES (apply to every brief task)\n\n- ALWAYS include specific recommended actions with deadlines in every output --\n  observations without actions are not acceptable\n- NEVER delay an escalation alert to include it in the next weekly brief --\n  time-sensitive signals require immediate notification\n\n## MANDATORY OUTPUT HEADER\n\n```\nTASK:          [e.g. Weekly Supply Chain Brief -- Week of 2024-03-18]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [ERP \u002F AP \u002F TMS \u002F Contract register \u002F Risk monitoring]\n```\n\n## WEEKLY SUPPLY CHAIN BRIEF WORKFLOW\n\n### Data Pull (automated via MCP -- every Monday morning)\n\nFROM ERP:\n\n- Vendor OTD by tier (prior week + 13-week rolling average)\n- Quality rejection rate by tier (prior week + 13-week rolling)\n- Open purchase orders overdue (count + value)\n- Stock-outs or near-stock-outs flagged (where inventory tracking enabled)\n\nFROM AP SYSTEM:\n\n- Invoices processed (total \u002F straight-through \u002F exception rate)\n- Exception rate by type (price variance \u002F qty variance \u002F PO not found)\n- Open disputes (count + value + age)\n- AP ageing: invoices approaching payment term deadline\n- Early payment discounts captured vs. missed (where applicable)\n\nFROM TMS \u002F LOGISTICS:\n\n- Carrier OTD by carrier (prior week + 4-week rolling)\n- Damage and claim rate\n- Cost per kg vs. prior week and vs. contracted rate\n- Expedited freight % of total shipments\n\nFROM CONTRACT REGISTER:\n\n- Contracts expiring within 90 days (with notice deadline)\n- Certifications expiring within 90 days\n- Any contracts where notice deadline is within 30 days (URGENT)\n\nFROM VENDOR RISK MONITORING:\n\n- New risk signals this week (count by severity)\n- Active escalations (count + vendor names)\n- Contingency plans active (count)\n\n### Executive Brief Output Format\n\n```\nSUPPLY CHAIN WEEKLY BRIEF -- Week of [Date]\nPrepared: [Day] [Time] | For: CPO, COO\n================================================================\n\nTRAFFIC LIGHT SUMMARY\nVendor Performance:    [GREEN \u002F AMBER \u002F RED]  OTD: [X]%  Quality rej: [X]%\nInvoice Processing:    [GREEN \u002F AMBER \u002F RED]  Exception rate: [X]%  Open disputes: [X]\nLogistics:             [GREEN \u002F AMBER \u002F RED]  Carrier OTD: [X]%  Cost\u002Fkg: [X]\nVendor Risk:           [GREEN \u002F AMBER \u002F RED]  Active alerts: [N]  Escalations: [N]\nContract Calendar:     [GREEN \u002F AMBER \u002F RED]  Renewals due 90d: [N]  URGENT: [N]\n\nTHIS WEEK'S HIGHLIGHTS\n\nWIN:\n[The single most positive supply chain development this week -- specific]\n\nRISK:\n[The single most important issue requiring CPO\u002FCOO attention -- specific,\n with recommended action and deadline]\n\nDECISION REQUIRED:\n[One thing leadership needs to decide or unblock -- specific]\n\nLEADING INDICATOR STATUS\nVendor OTD trend (13-week):  [Improving \u002F Stable \u002F Declining]\nInvoice exception trend:     [Improving \u002F Stable \u002F Declining]\nActive risk alerts trend:    [Improving \u002F Stable \u002F Declining]\n\nAT-RISK SITUATIONS REQUIRING LEADERSHIP ATTENTION\n[Vendor \u002F Issue]  [Risk level]  [Time-sensitivity]  [Recommended action]\n\nCONTRACT CALENDAR -- URGENT (notice deadline within 30 days)\n[Contract]  [Expiry]  [Notice deadline]  [Decision needed]\n\nSAVINGS PIPELINE THIS WEEK\nNew opportunities identified: [X]\nSavings captured this week:   [X]\nYTD savings captured:         [X]  vs. target: [X]\n================================================================\n```\n\n### Full Operations Report Format (monthly -- for operations meeting)\n\nExpand the weekly brief with:\n\n- Month-on-month trend charts (described as data for chart generation)\n- Category-by-category vendor performance\n- AP exception analysis with root cause breakdown\n- Logistics: carrier comparison, lane performance, expedited root cause\n- Risk matrix: all monitored vendors plotted by likelihood x impact\n- Savings pipeline: all active opportunities with owner and status\n- Forward look: key decisions and actions required in next 30 days\n\n### Escalation Alert Format (immediate -- not in weekly cycle)\n\nTrigger escalation alert immediately for:\n\n- Any Tier 1 Strategic vendor OTD below 75% in any single week\n- Financial distress news on any Strategic or Bottleneck vendor\n- Bank detail change attempt on any active vendor (fraud alert)\n- Invoice fraud attempt detected (duplicate + amount manipulation)\n- Logistics disruption affecting >20% of weekly shipment volume\n- Contract notice deadline missed (requires legal consultation)\n\n```\nESCALATION ALERT -- [Timestamp]\n---------------------------------------------------------\nAlert type:    [Category]\nSeverity:      RED CRITICAL \u002F AMBER HIGH\nDescription:   [Specific facts only -- no speculation]\nImmediate action required: [What must happen in next 24 hours]\nEscalate to:   [Named individuals]\n---------------------------------------------------------\n```\n\n## NEVER DO THESE\n\n- NEVER produce a supply chain brief that is longer than one page\n  for the CPO\u002FCOO audience -- they need the headline, the risk,\n  and the action; not the full analysis (link to detail if needed)\n- NEVER present metrics without comparison to target or prior period --\n  a number without context is meaningless\n- NEVER omit the DECISION REQUIRED section -- the brief exists to\n  drive decisions, not to report history\n- NEVER delay an escalation alert to include it in the next\n  weekly brief -- time-sensitive signals require immediate notification\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n",{"name":5,"license":14,"metadata":53,"description":58},{"author":54,"version":55,"plugin-commands":56,"mcp-integrations":57},"Panaversity","1.0","\u002Fsupply-chain-brief","ERP, AP system, TMS, contract register, risk monitoring outputs","Activate for: supply chain brief, weekly supply chain report, CPO report, COO report, procurement dashboard, supply chain dashboard, weekly report, executive brief, supply chain KPIs, supply chain metrics, procurement performance, logistics performance summary, vendor performance summary, AP performance, weekly update, supply chain status. NOT for: detailed vendor assessment (use vendor-assessment), detailed invoice reconciliation (use invoice-reconciliation), detailed carrier review (use logistics-brief).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-supply-chain-brief-skill-ee38fccf","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill supply-chain-brief",{"tool":71,"command":72},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill supply-chain-brief",{"tool":74,"command":75},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill supply-chain-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-supply-chain-brief-skill-ee38fccf\u002FSKILL.md",true,[],[80,107,133,162,190,222],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":48},"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",[],[82,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":48},"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",[],[114,115,116,117,118,119,120,43,121,122,123,124,125,126,127,128,129,130,131,132],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":143,"publishedAt":48},"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",[139,142],{"categoryNo":140,"categoryName":141,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[144,145,146,147,148,149,150,151,152,153,154,155,156,100,157,158,159,160,105,161],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":48},"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",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[172,173,174,175,176,177,178,179,180,100,181,182,183,184,185,186,187,188,189,105],"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":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":205,"publishedAt":48},"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",[196,199,202],{"categoryNo":197,"categoryName":198,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":200,"categoryName":201,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":203,"categoryName":204,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000038","人力资源",[206,207,208,209,210,211,212,213,115,214,100,215,216,217,37,218,219,220,105,221],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","do","task","cv","letter",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":228,"publishedAt":48},"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",[],[229,230,231,32,232,209,233,100,218,234,235,236,237,238,239,240,241,242,105,243],"steno mode","mode","customer","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]