[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N17XT237NB6P9H1Y87ES21":3,"skill-same:01M6N17XT237NB6P9H1Y87ES21":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},"01M6N17XT237NB6P9H1Y87ES21","supplier-risk",null,"Monitors ongoing risk signals and produces risk briefs for known vendors. Activate for: supplier risk monitoring, vendor risk alert, supply risk, risk brief, supplier financial risk, credit rating downgrade, supplier operational risk, supplier compliance risk, geopolitical risk, Tier 2 risk, sub-supplier disruption, supply disruption, risk monitor, risk rating change, risk alert, distress signal, supplier news, country risk, supply chain resilience, CVA, administration, insolvency. USE THIS when a KNOWN risk event has occurred (credit downgrade, financial distress, disruption, regulatory action) and you need to assess its impact. NOT for: classifying or scoring a vendor (use vendor-assessment), vendor onboarding or approval (use vendor-assessment), vendor Kraljic classification (use vendor-assessment), invoice processing (use invoice-reconciliation), carrier performance (use logistics-brief).","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-supplier-risk-skill-6a0628b6\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"supplier risk","risk","scoring","action","briefs","you","processing","impact","chain","signals","reconciliation","performance","activate","web search","brief","monitoring","search","assessment","resilience","change","2026-11-10 10:12:30",false,"---\nname: supplier-risk\ndescription: >\n  Monitors ongoing risk signals and produces risk briefs for known vendors.\n  Activate for: supplier risk monitoring, vendor risk alert, supply risk,\n  risk brief, supplier financial risk, credit rating downgrade, supplier\n  operational risk, supplier compliance risk, geopolitical risk, Tier 2 risk,\n  sub-supplier disruption, supply disruption, risk monitor, risk rating change,\n  risk alert, distress signal, supplier news, country risk, supply chain\n  resilience, CVA, administration, insolvency.\n  USE THIS when a KNOWN risk event has occurred (credit downgrade, financial\n  distress, disruption, regulatory action) and you need to assess its impact.\n  NOT for: classifying or scoring a vendor (use vendor-assessment), vendor\n  onboarding or approval (use vendor-assessment), vendor Kraljic classification\n  (use vendor-assessment), invoice processing (use invoice-reconciliation),\n  carrier performance (use logistics-brief).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Fsupplier-risk\"\n  mcp-integrations: \"Web Search, Companies House, Creditsafe, ERP, QMS, News APIs\"\n---\n\n## UNIVERSAL RULES (apply to every risk task)\n\n- NEVER classify a sole-source supplier as low risk based on spend alone --\n  always assess operational dependency separately from spend volume\n- NEVER accept a vendor risk assessment that contains fabricated financial\n  data -- label all estimates and flag where primary data is unavailable\n- ALWAYS flag when a vendor's Tier 2 sub-supplier shows distress signals\n  that could affect Tier 1 supply continuity\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. Supplier Risk Brief -- Vendor X]\nVENDOR TIER:   [Strategic \u002F Tactical \u002F Commodity \u002F Bottleneck \u002F Unclassified]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [Web Search \u002F Creditsafe \u002F ERP \u002F Manual input]\n```\n\n## RISK MONITORING WORKFLOW\n\n### Five Risk Dimensions\n\nDIMENSION 1: FINANCIAL RISK\nMonitor for:\n\n- Revenue and profitability trend (from annual filings or reported results)\n- Credit rating: any downgrade from Creditsafe \u002F D&B \u002F Experian\n- Restructuring announcements, CVA, administration proceedings\n- DSO trend: lengthening = cash pressure on the vendor\n- Ownership changes: acquisition, MBO, private equity involvement\n- Key customer losses announced\n- Late filing of statutory accounts (itself a distress signal)\n\nSources: Companies House \u002F SECP \u002F equivalent registry;\nCreditsafe \u002F D&B; trade press; web search MCP\n\nRisk levels:\nRED HIGH: Restructuring \u002F CVA \u002F credit rating CCC or below \u002F accounts overdue\nAMBER MEDIUM: Revenue decline >15% YoY; margin below 3%; rating downgrade 1 notch\nGREEN LOW: Stable financials; positive trend; adequate credit rating\n\nDIMENSION 2: OPERATIONAL RISK\nMonitor from ERP data (updated continuously):\n\n- OTD rate: 13-week rolling average + trend direction\n- Quality rejection rate: 13-week rolling average + trend direction\n- Lead time variance: increasing variance = capacity or process strain\n- Missed delivery pattern: same day of week? Same product? (capacity signals)\n- Partial deliveries increasing? (material shortage signal)\n\nRisk levels:\nRED HIGH: OTD \u003C configured critical threshold; quality > critical threshold\nAMBER MEDIUM: Declining trend even if above threshold; partial deliveries increasing\nGREEN LOW: Stable; above threshold; no adverse trend\n\nDIMENSION 3: REGULATORY & COMPLIANCE RISK\nMonitor for:\n\n- Certification expiry (ISO, sector-specific, data protection)\n- Regulatory enforcement action (sector regulators, HSE, ICO)\n- Environmental incidents (prosecution, fine, site closure risk)\n- Trade compliance issues (export licence violations, customs irregularities)\n- Sanctions list changes affecting the vendor or their key sub-suppliers\n\nRisk levels:\nRED HIGH: Active sanctions match; enforcement action; certification lapsed\nAMBER MEDIUM: Certification expiring within 90 days; regulatory warning issued\nGREEN LOW: All certifications current; no adverse regulatory signals\n\nDIMENSION 4: GEOPOLITICAL RISK\nMonitor for:\n\n- Political instability in vendor's operating country\n- Trade restrictions, tariffs, or export controls affecting category\n- Currency volatility affecting contract economics\n- Infrastructure disruption (port strikes, border closures, natural disaster)\n- Conflict affecting supply routes\n\nSources: web search MCP; UK FCO travel advisories; trade association bulletins\n\nRisk levels:\nRED HIGH: Active disruption to supply route or vendor operations\nAMBER MEDIUM: Elevated country risk; currency movement >5% since contract\nGREEN LOW: Stable environment; no material currency exposure\n\nDIMENSION 5: TIER 2 \u002F SUB-SUPPLIER RISK\nMonitor for:\n\n- Financial distress at critical Tier 2 suppliers\n- Tier 2 supplier capacity constraints affecting Tier 1 output\n- Single-geography concentration at Tier 2 level\n- Tier 2 supplier relationship with Tier 1 deteriorating\n\nRequirement: Tier 2 mapping must exist for all Tier 1 Strategic vendors.\nIf mapping does not exist: flag as UNASSESSED RISK; request Tier 2 data\nfrom Tier 1 supplier as priority action.\n\n### Risk Rating Change Rules\n\nESCALATE overall rating if ANY dimension reaches RED\nELEVATE to MEDIUM-HIGH if TWO dimensions reach AMBER simultaneously\nREDUCE rating only after confirmed remediation (not just vendor assurance)\n\n## RISK BRIEF OUTPUT FORMAT\n\n```\nSUPPLIER RISK BRIEF: [Vendor Name]\nAssessment date: [Date] | Next scheduled review: [Date]\n================================================================\nOVERALL RISK RATING: [GREEN LOW \u002F AMBER MEDIUM \u002F AMBER MEDIUM-HIGH \u002F RED HIGH \u002F RED CRITICAL]\nChange since last review: [No change \u002F Elevated \u002F Reduced]\n\nFINANCIAL RISK:   [GREEN \u002F AMBER \u002F RED] [Rating]\n[Findings and signals with sources and dates]\n\nOPERATIONAL RISK: [GREEN \u002F AMBER \u002F RED] [Rating]\n[OTD trend, quality trend, lead time data from ERP]\n\nCOMPLIANCE RISK:  [GREEN \u002F AMBER \u002F RED] [Rating]\n[Certification status, regulatory findings]\n\nGEOPOLITICAL RISK:[GREEN \u002F AMBER \u002F RED] [Rating]\n[Country, currency, route findings]\n\nTIER 2 RISK:      [GREEN \u002F AMBER \u002F RED \u002F NOT MAPPED]\n[Sub-supplier findings or mapping gap flag]\n\nRECOMMENDED ACTIONS -- RANKED BY URGENCY\nRED [IMMEDIATE -- this week]: [Action] -- [Owner]\nAMBER [SHORT-TERM -- 30 days]: [Action] -- [Owner]\nGREEN [PLANNED -- 90 days]:    [Action] -- [Owner]\n================================================================\n```\n\n### Executive Brief Format (for CPO weekly summary)\n\n```\nVENDOR RISK SUMMARY -- Week of [Date]\n---------------------------------------------------------\n[Vendor]    [Overall]  [Change]  [Key signal]   [Action required]\n[Vendor]    [Overall]  [Change]  [Key signal]   [Action required]\n---------------------------------------------------------\nNew alerts this week:   [N]\nEscalations to CPO:     [N]\nContingency plans live: [N]\n```\n\n## NEVER DO THESE\n\n- NEVER rate a vendor as LOW risk in any dimension without verified data --\n  absence of negative data does not equal low risk; label as UNASSESSED if no data\n- NEVER rely on vendor self-assessment alone for financial risk --\n  always cross-reference with independent sources\n- NEVER downgrade a risk rating based on vendor assurance alone --\n  require evidence (updated accounts, certification renewal, remediation proof)\n- NEVER omit the Tier 2 risk section -- mark as NOT MAPPED if absent,\n  not LOW RISK\n- NEVER wait for the scheduled review to act on a HOT signal --\n  HOT signals override the review schedule\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## UNIVERSAL RULES (apply to every risk task)\n\n- NEVER classify a sole-source supplier as low risk based on spend alone --\n  always assess operational dependency separately from spend volume\n- NEVER accept a vendor risk assessment that contains fabricated financial\n  data -- label all estimates and flag where primary data is unavailable\n- ALWAYS flag when a vendor's Tier 2 sub-supplier shows distress signals\n  that could affect Tier 1 supply continuity\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. Supplier Risk Brief -- Vendor X]\nVENDOR TIER:   [Strategic \u002F Tactical \u002F Commodity \u002F Bottleneck \u002F Unclassified]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [Web Search \u002F Creditsafe \u002F ERP \u002F Manual input]\n```\n\n## RISK MONITORING WORKFLOW\n\n### Five Risk Dimensions\n\nDIMENSION 1: FINANCIAL RISK\nMonitor for:\n\n- Revenue and profitability trend (from annual filings or reported results)\n- Credit rating: any downgrade from Creditsafe \u002F D&B \u002F Experian\n- Restructuring announcements, CVA, administration proceedings\n- DSO trend: lengthening = cash pressure on the vendor\n- Ownership changes: acquisition, MBO, private equity involvement\n- Key customer losses announced\n- Late filing of statutory accounts (itself a distress signal)\n\nSources: Companies House \u002F SECP \u002F equivalent registry;\nCreditsafe \u002F D&B; trade press; web search MCP\n\nRisk levels:\nRED HIGH: Restructuring \u002F CVA \u002F credit rating CCC or below \u002F accounts overdue\nAMBER MEDIUM: Revenue decline >15% YoY; margin below 3%; rating downgrade 1 notch\nGREEN LOW: Stable financials; positive trend; adequate credit rating\n\nDIMENSION 2: OPERATIONAL RISK\nMonitor from ERP data (updated continuously):\n\n- OTD rate: 13-week rolling average + trend direction\n- Quality rejection rate: 13-week rolling average + trend direction\n- Lead time variance: increasing variance = capacity or process strain\n- Missed delivery pattern: same day of week? Same product? (capacity signals)\n- Partial deliveries increasing? (material shortage signal)\n\nRisk levels:\nRED HIGH: OTD \u003C configured critical threshold; quality > critical threshold\nAMBER MEDIUM: Declining trend even if above threshold; partial deliveries increasing\nGREEN LOW: Stable; above threshold; no adverse trend\n\nDIMENSION 3: REGULATORY & COMPLIANCE RISK\nMonitor for:\n\n- Certification expiry (ISO, sector-specific, data protection)\n- Regulatory enforcement action (sector regulators, HSE, ICO)\n- Environmental incidents (prosecution, fine, site closure risk)\n- Trade compliance issues (export licence violations, customs irregularities)\n- Sanctions list changes affecting the vendor or their key sub-suppliers\n\nRisk levels:\nRED HIGH: Active sanctions match; enforcement action; certification lapsed\nAMBER MEDIUM: Certification expiring within 90 days; regulatory warning issued\nGREEN LOW: All certifications current; no adverse regulatory signals\n\nDIMENSION 4: GEOPOLITICAL RISK\nMonitor for:\n\n- Political instability in vendor's operating country\n- Trade restrictions, tariffs, or export controls affecting category\n- Currency volatility affecting contract economics\n- Infrastructure disruption (port strikes, border closures, natural disaster)\n- Conflict affecting supply routes\n\nSources: web search MCP; UK FCO travel advisories; trade association bulletins\n\nRisk levels:\nRED HIGH: Active disruption to supply route or vendor operations\nAMBER MEDIUM: Elevated country risk; currency movement >5% since contract\nGREEN LOW: Stable environment; no material currency exposure\n\nDIMENSION 5: TIER 2 \u002F SUB-SUPPLIER RISK\nMonitor for:\n\n- Financial distress at critical Tier 2 suppliers\n- Tier 2 supplier capacity constraints affecting Tier 1 output\n- Single-geography concentration at Tier 2 level\n- Tier 2 supplier relationship with Tier 1 deteriorating\n\nRequirement: Tier 2 mapping must exist for all Tier 1 Strategic vendors.\nIf mapping does not exist: flag as UNASSESSED RISK; request Tier 2 data\nfrom Tier 1 supplier as priority action.\n\n### Risk Rating Change Rules\n\nESCALATE overall rating if ANY dimension reaches RED\nELEVATE to MEDIUM-HIGH if TWO dimensions reach AMBER simultaneously\nREDUCE rating only after confirmed remediation (not just vendor assurance)\n\n## RISK BRIEF OUTPUT FORMAT\n\n```\nSUPPLIER RISK BRIEF: [Vendor Name]\nAssessment date: [Date] | Next scheduled review: [Date]\n================================================================\nOVERALL RISK RATING: [GREEN LOW \u002F AMBER MEDIUM \u002F AMBER MEDIUM-HIGH \u002F RED HIGH \u002F RED CRITICAL]\nChange since last review: [No change \u002F Elevated \u002F Reduced]\n\nFINANCIAL RISK:   [GREEN \u002F AMBER \u002F RED] [Rating]\n[Findings and signals with sources and dates]\n\nOPERATIONAL RISK: [GREEN \u002F AMBER \u002F RED] [Rating]\n[OTD trend, quality trend, lead time data from ERP]\n\nCOMPLIANCE RISK:  [GREEN \u002F AMBER \u002F RED] [Rating]\n[Certification status, regulatory findings]\n\nGEOPOLITICAL RISK:[GREEN \u002F AMBER \u002F RED] [Rating]\n[Country, currency, route findings]\n\nTIER 2 RISK:      [GREEN \u002F AMBER \u002F RED \u002F NOT MAPPED]\n[Sub-supplier findings or mapping gap flag]\n\nRECOMMENDED ACTIONS -- RANKED BY URGENCY\nRED [IMMEDIATE -- this week]: [Action] -- [Owner]\nAMBER [SHORT-TERM -- 30 days]: [Action] -- [Owner]\nGREEN [PLANNED -- 90 days]:    [Action] -- [Owner]\n================================================================\n```\n\n### Executive Brief Format (for CPO weekly summary)\n\n```\nVENDOR RISK SUMMARY -- Week of [Date]\n---------------------------------------------------------\n[Vendor]    [Overall]  [Change]  [Key signal]   [Action required]\n[Vendor]    [Overall]  [Change]  [Key signal]   [Action required]\n---------------------------------------------------------\nNew alerts this week:   [N]\nEscalations to CPO:     [N]\nContingency plans live: [N]\n```\n\n## NEVER DO THESE\n\n- NEVER rate a vendor as LOW risk in any dimension without verified data --\n  absence of negative data does not equal low risk; label as UNASSESSED if no data\n- NEVER rely on vendor self-assessment alone for financial risk --\n  always cross-reference with independent sources\n- NEVER downgrade a risk rating based on vendor assurance alone --\n  require evidence (updated accounts, certification renewal, remediation proof)\n- NEVER omit the Tier 2 risk section -- mark as NOT MAPPED if absent,\n  not LOW RISK\n- NEVER wait for the scheduled review to act on a HOT signal --\n  HOT signals override the review schedule\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","\u002Fsupplier-risk","Web Search, Companies House, Creditsafe, ERP, QMS, News APIs","Monitors ongoing risk signals and produces risk briefs for known vendors. Activate for: supplier risk monitoring, vendor risk alert, supply risk, risk brief, supplier financial risk, credit rating downgrade, supplier operational risk, supplier compliance risk, geopolitical risk, Tier 2 risk, sub-supplier disruption, supply disruption, risk monitor, risk rating change, risk alert, distress signal, supplier news, country risk, supply chain resilience, CVA, administration, insolvency. USE THIS when a KNOWN risk event has occurred (credit downgrade, financial distress, disruption, regulatory action) and you need to assess its impact. NOT for: classifying or scoring a vendor (use vendor-assessment), vendor onboarding or approval (use vendor-assessment), vendor Kraljic classification (use vendor-assessment), invoice processing (use invoice-reconciliation), carrier performance (use logistics-brief).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-supplier-risk-skill-6a0628b6","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 supplier-risk",{"tool":61,"command":62},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill supplier-risk",{"tool":64,"command":65},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill supplier-risk","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-supplier-risk-skill-6a0628b6\u002FSKILL.md",true,[],[70,97,124,156,184,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,90,91,92,93,94,95,96],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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",[],[104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":138,"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",[130,135],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":136,"categoryName":137,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000023","Skill与智能体开发",[139,140,141,24,142,143,144,145,146,147,148,149,150,90,151,152,153,154,95,155],"transloadit media processing","Media","media processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":165,"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",[162],{"categoryNo":163,"categoryName":164,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000011","运维与部署",[166,167,168,169,170,171,172,173,174,90,175,176,177,178,179,180,181,182,183,95],"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":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":201,"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",[190,193,198],{"categoryNo":191,"categoryName":192,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":194,"categoryName":195,"taxonomyType":196,"taxonomyTypeDesc":197},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":199,"categoryName":200,"taxonomyType":196,"taxonomyTypeDesc":197},"01JBSEEDCAT000000000000038","人力资源",[34,202,203,204,205,206,207,208,105,209,90,210,211,212,30,213,214,215,95,216],"Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","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,225,226,32,227,204,228,90,213,229,230,231,232,233,234,235,236,237,95,238],"steno mode","mode","customer","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]