[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N18MSBDCN8EJ2HWGYW499T":3,"skill-same:01M6N18MSBDCN8EJ2HWGYW499T":85},{"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":33,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":13,"repositoryHtmlUrl":68,"repositoryHomepageUrl":6,"ownerHtmlUrl":69,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":70,"install":71,"resources":84},"01M6N18MSBDCN8EJ2HWGYW499T","vendor-communication",null,"Activate for: vendor communication, supplier communication, dispute letter, invoice dispute, corrective action request, CAR, price dispute, quantity dispute, performance notice, vendor notice, vendor warning, exit notice, contract notice, non-renewal notice, vendor rejection, vendor escalation, write to vendor, email supplier, communicate with vendor, supply assurance. NOT for: invoice processing (use invoice-reconciliation), vendor assessment (use vendor-assessment), spend analytics (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-vendor-communication-skill-db57dd4a\u002FSKILL.md",[17,22,25,30],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",{"categoryNo":31,"categoryName":32,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000040","财务",[34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"vendor communication","communication","vendor","reconciliation","letter","for","supply","communicate","processing","notice","register","contract","MCP","exit","vendor assessment","use","escalation","email","assessment","performance","2026-11-10 10:12:30",false,"---\nname: vendor-communication\ndescription: >\n  Activate for: vendor communication, supplier communication, dispute letter,\n  invoice dispute, corrective action request, CAR, price dispute, quantity\n  dispute, performance notice, vendor notice, vendor warning, exit notice,\n  contract notice, non-renewal notice, vendor rejection, vendor escalation,\n  write to vendor, email supplier, communicate with vendor, supply assurance.\n  NOT for: invoice processing (use invoice-reconciliation), vendor assessment\n  (use vendor-assessment), spend analytics (use spend-analysis).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Fvendor-communicate\"\n  mcp-integrations: \"Email MCP, contract register\"\n---\n\n## UNIVERSAL RULES (apply to every communication task)\n\n- NEVER recommend a vendor exit without a qualified alternative identified\n  or an explicit \"no alternative -- managed risk\" decision documented\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. Vendor Communication -- Invoice Dispute INV-2024-0847]\nVENDOR TIER:   [Strategic \u002F Tactical \u002F Commodity \u002F Bottleneck \u002F Unclassified]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nCOMMUNICATION TYPE: [Invoice Dispute \u002F CAR \u002F Non-Renewal \u002F Supply Assurance \u002F Exit]\n```\n\n## COMMUNICATION TYPES AND STRUCTURES\n\n### Type 1: Invoice Dispute Notice\n\nUse when: invoice exception identified in reconciliation; vendor must provide\ncredit note, revised invoice, or supporting evidence.\n\n```\nSubject: Invoice Dispute -- Invoice [Number] dated [Date]\n         Reference: PO [Number]\n\nDear [Contact name at vendor],\n\nWe have reviewed Invoice [Number] dated [Date] for [Amount] and have\nidentified the following discrepancy\u002Fdiscrepancies requiring your\nattention before payment can be processed.\n\nDISCREPANCY [N]:\nItem:         [Description]\nInvoiced:     [Qty or price as invoiced]\nOur records:  [Qty or price per PO\u002FGR]\nVariance:     [Amount or units]\nBasis:        [PO reference or Goods Receipt reference]\n\nREQUIRED ACTION:\nPlease [issue a credit note for X \u002F provide a revised invoice \u002F\nprovide documentary evidence supporting the invoiced amount]\nby [date -- typically 5 business days].\n\nPayment of the undisputed amount ([X]) will be processed on our\nstandard payment terms from receipt of resolution.\n\n[Sign-off: your name, title, contact details]\n```\n\n### Type 2: Corrective Action Request (CAR)\n\nUse when: vendor performance has breached a threshold (OTD, quality,\nor other contractual KPI) requiring formal documented response.\n\n```\nSubject: Corrective Action Request -- [Vendor Name] -- [KPI] Performance\n         Reference: CAR-[Year]-[Number]\n\nDear [Contact name],\n\nWe are writing to formally notify you that [Vendor Name]'s performance\nagainst [KPI] has fallen below the contractual threshold during\n[period], and to request a formal corrective action plan.\n\nPERFORMANCE DATA:\nKPI:              [On-time delivery \u002F Quality rejection rate \u002F Other]\nContractual SLA:  [X]%\nActual (period):  [X]%\nShortfall:        [X percentage points]\nPeriod:           [Start date -- End date]\nSupporting data:  [Reference to ERP report or attached data]\n\nREQUIRED CORRECTIVE ACTION PLAN:\nPlease provide a written corrective action plan within [10 \u002F 14] calendar\ndays of this notice, addressing:\n1. Root cause analysis of the performance shortfall\n2. Immediate containment actions already taken\n3. Corrective actions to be implemented, with target dates\n4. How compliance with the SLA will be monitored going forward\n\nWe will schedule a review meeting for [proposed date] to discuss\nthe plan and agree monitoring arrangements.\n\nThis notice is issued under Clause [X] of our Supply Agreement dated [date].\n\n[Sign-off: your name, title]\n```\n\n### Type 3: Contract Non-Renewal Notice\n\nUse when: exercising the right not to renew a contract within the\ncontractual notice period. Must be sent before the notice deadline.\n\n```\nSubject: Notice of Non-Renewal -- [Contract Reference\u002FDescription]\n         Agreement dated [Date]\n\nDear [Contact name],\n\nIn accordance with Clause [X] of our [Agreement name] dated [date],\nwe are providing [X days'] written notice that we will not be renewing\nthe Agreement upon its expiry on [date].\n\nThe Agreement will therefore terminate on [expiry date].\n\nWe will honour all purchase orders issued prior to this notice and\nwill expect fulfilment of all confirmed orders through to [date].\n\nPlease confirm receipt of this notice and advise us of any transition\nsupport you are able to provide during the wind-down period.\n\nWe thank you for your service over the period of the Agreement.\n\n[Sign-off: authorised signatory, title]\n```\n\n### Type 4: Emergency Supply Assurance Request\n\nUse when: a risk signal (financial distress, Tier 2 disruption, news event)\nrequires immediate assurance from a critical vendor.\n\n```\nSubject: Supply Assurance Request -- [Category\u002FProduct] -- Urgent\n\nDear [Contact name],\n\nWe have become aware of [brief, factual description of the concern --\ne.g. reports of supply disruption at one of your key raw material\nsuppliers \u002F your company's published restructuring announcement].\n\nAs [Vendor Name] is a critical supplier to our operations, we are\nwriting to request written assurance on the following points:\n\n1. Is your production capacity for [category\u002Fproduct] unaffected?\n2. Do you have sufficient raw material \u002F component inventory to\n   fulfil orders over the next [60\u002F90] days?\n3. Are there any circumstances that could affect your ability to\n   meet our confirmed purchase orders?\n\nPlease respond by [date -- 3-5 business days] with a formal\nwritten statement. We may follow this with a request for a\ncall with your [CEO\u002FOperations Director] to discuss further.\n\nWe appreciate your prompt attention to this matter.\n\n[Sign-off: CPO or category manager]\n```\n\n### Type 5: Vendor Exit Notice (Planned Transition)\n\nUse when: ending a vendor relationship by mutual agreement or for\nconvenience, with a planned transition period.\n\n```\nSubject: Transition Notice -- Supply Relationship Wind-Down\n\nDear [Contact name],\n\nWe are writing to notify you that [Your Company] has taken the\ndecision to transition [category\u002Fproduct] supply to [alternative\narrangement \u002F consolidation with existing supplier].\n\nWe anticipate a transition period of [X weeks\u002Fmonths], during which\nwe will continue to issue purchase orders in accordance with our\ncurrent arrangement.\n\nWe would appreciate your cooperation with the following transition\nrequirements:\n- Continued fulfilment of confirmed orders through [date]\n- Return of any customer-owned tooling, moulds, or intellectual\n  property by [date]\n- Transfer of technical documentation and specifications by [date]\n- [Other transition-specific items]\n\nWe value the relationship we have had with [Vendor Name] and will\nprovide a reference for future customers upon request.\n\n[Sign-off: CPO or authorised signatory]\n```\n\n## COMMUNICATION STANDARDS\n\nTone: Professional, factual, constructive.\n\n- State facts; do not attribute blame or motive\n- Be specific: reference PO numbers, dates, quantities, thresholds\n- State the required action and deadline clearly\n- Avoid emotional language regardless of the severity of the issue\n\nAuthority: All communications above configured value threshold\nrequire sign-off from the appropriate authority level before sending.\nDispute notices: Category Manager sign-off\nCARs: CPO sign-off\nContract notices: CPO + Legal review recommended\nExit notices: CPO + Finance Director\n\n## NEVER DO THESE\n\n- NEVER send a dispute notice without specific reference to the\n  PO number and the contractual basis for the dispute\n- NEVER send a CAR without the supporting performance data attached\n- NEVER send a contract notice after the notice deadline has passed\n  without legal advice (you may have lost the right to non-renew)\n- NEVER send a vendor exit notice without confirming transition\n  requirements for tooling, IP, and documentation first\n- NEVER respond to a phishing or social engineering attempt\n  (bank detail change requests) by email -- always call the vendor\n  on a known number to verify\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## UNIVERSAL RULES (apply to every communication task)\n\n- NEVER recommend a vendor exit without a qualified alternative identified\n  or an explicit \"no alternative -- managed risk\" decision documented\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. Vendor Communication -- Invoice Dispute INV-2024-0847]\nVENDOR TIER:   [Strategic \u002F Tactical \u002F Commodity \u002F Bottleneck \u002F Unclassified]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nCOMMUNICATION TYPE: [Invoice Dispute \u002F CAR \u002F Non-Renewal \u002F Supply Assurance \u002F Exit]\n```\n\n## COMMUNICATION TYPES AND STRUCTURES\n\n### Type 1: Invoice Dispute Notice\n\nUse when: invoice exception identified in reconciliation; vendor must provide\ncredit note, revised invoice, or supporting evidence.\n\n```\nSubject: Invoice Dispute -- Invoice [Number] dated [Date]\n         Reference: PO [Number]\n\nDear [Contact name at vendor],\n\nWe have reviewed Invoice [Number] dated [Date] for [Amount] and have\nidentified the following discrepancy\u002Fdiscrepancies requiring your\nattention before payment can be processed.\n\nDISCREPANCY [N]:\nItem:         [Description]\nInvoiced:     [Qty or price as invoiced]\nOur records:  [Qty or price per PO\u002FGR]\nVariance:     [Amount or units]\nBasis:        [PO reference or Goods Receipt reference]\n\nREQUIRED ACTION:\nPlease [issue a credit note for X \u002F provide a revised invoice \u002F\nprovide documentary evidence supporting the invoiced amount]\nby [date -- typically 5 business days].\n\nPayment of the undisputed amount ([X]) will be processed on our\nstandard payment terms from receipt of resolution.\n\n[Sign-off: your name, title, contact details]\n```\n\n### Type 2: Corrective Action Request (CAR)\n\nUse when: vendor performance has breached a threshold (OTD, quality,\nor other contractual KPI) requiring formal documented response.\n\n```\nSubject: Corrective Action Request -- [Vendor Name] -- [KPI] Performance\n         Reference: CAR-[Year]-[Number]\n\nDear [Contact name],\n\nWe are writing to formally notify you that [Vendor Name]'s performance\nagainst [KPI] has fallen below the contractual threshold during\n[period], and to request a formal corrective action plan.\n\nPERFORMANCE DATA:\nKPI:              [On-time delivery \u002F Quality rejection rate \u002F Other]\nContractual SLA:  [X]%\nActual (period):  [X]%\nShortfall:        [X percentage points]\nPeriod:           [Start date -- End date]\nSupporting data:  [Reference to ERP report or attached data]\n\nREQUIRED CORRECTIVE ACTION PLAN:\nPlease provide a written corrective action plan within [10 \u002F 14] calendar\ndays of this notice, addressing:\n1. Root cause analysis of the performance shortfall\n2. Immediate containment actions already taken\n3. Corrective actions to be implemented, with target dates\n4. How compliance with the SLA will be monitored going forward\n\nWe will schedule a review meeting for [proposed date] to discuss\nthe plan and agree monitoring arrangements.\n\nThis notice is issued under Clause [X] of our Supply Agreement dated [date].\n\n[Sign-off: your name, title]\n```\n\n### Type 3: Contract Non-Renewal Notice\n\nUse when: exercising the right not to renew a contract within the\ncontractual notice period. Must be sent before the notice deadline.\n\n```\nSubject: Notice of Non-Renewal -- [Contract Reference\u002FDescription]\n         Agreement dated [Date]\n\nDear [Contact name],\n\nIn accordance with Clause [X] of our [Agreement name] dated [date],\nwe are providing [X days'] written notice that we will not be renewing\nthe Agreement upon its expiry on [date].\n\nThe Agreement will therefore terminate on [expiry date].\n\nWe will honour all purchase orders issued prior to this notice and\nwill expect fulfilment of all confirmed orders through to [date].\n\nPlease confirm receipt of this notice and advise us of any transition\nsupport you are able to provide during the wind-down period.\n\nWe thank you for your service over the period of the Agreement.\n\n[Sign-off: authorised signatory, title]\n```\n\n### Type 4: Emergency Supply Assurance Request\n\nUse when: a risk signal (financial distress, Tier 2 disruption, news event)\nrequires immediate assurance from a critical vendor.\n\n```\nSubject: Supply Assurance Request -- [Category\u002FProduct] -- Urgent\n\nDear [Contact name],\n\nWe have become aware of [brief, factual description of the concern --\ne.g. reports of supply disruption at one of your key raw material\nsuppliers \u002F your company's published restructuring announcement].\n\nAs [Vendor Name] is a critical supplier to our operations, we are\nwriting to request written assurance on the following points:\n\n1. Is your production capacity for [category\u002Fproduct] unaffected?\n2. Do you have sufficient raw material \u002F component inventory to\n   fulfil orders over the next [60\u002F90] days?\n3. Are there any circumstances that could affect your ability to\n   meet our confirmed purchase orders?\n\nPlease respond by [date -- 3-5 business days] with a formal\nwritten statement. We may follow this with a request for a\ncall with your [CEO\u002FOperations Director] to discuss further.\n\nWe appreciate your prompt attention to this matter.\n\n[Sign-off: CPO or category manager]\n```\n\n### Type 5: Vendor Exit Notice (Planned Transition)\n\nUse when: ending a vendor relationship by mutual agreement or for\nconvenience, with a planned transition period.\n\n```\nSubject: Transition Notice -- Supply Relationship Wind-Down\n\nDear [Contact name],\n\nWe are writing to notify you that [Your Company] has taken the\ndecision to transition [category\u002Fproduct] supply to [alternative\narrangement \u002F consolidation with existing supplier].\n\nWe anticipate a transition period of [X weeks\u002Fmonths], during which\nwe will continue to issue purchase orders in accordance with our\ncurrent arrangement.\n\nWe would appreciate your cooperation with the following transition\nrequirements:\n- Continued fulfilment of confirmed orders through [date]\n- Return of any customer-owned tooling, moulds, or intellectual\n  property by [date]\n- Transfer of technical documentation and specifications by [date]\n- [Other transition-specific items]\n\nWe value the relationship we have had with [Vendor Name] and will\nprovide a reference for future customers upon request.\n\n[Sign-off: CPO or authorised signatory]\n```\n\n## COMMUNICATION STANDARDS\n\nTone: Professional, factual, constructive.\n\n- State facts; do not attribute blame or motive\n- Be specific: reference PO numbers, dates, quantities, thresholds\n- State the required action and deadline clearly\n- Avoid emotional language regardless of the severity of the issue\n\nAuthority: All communications above configured value threshold\nrequire sign-off from the appropriate authority level before sending.\nDispute notices: Category Manager sign-off\nCARs: CPO sign-off\nContract notices: CPO + Legal review recommended\nExit notices: CPO + Finance Director\n\n## NEVER DO THESE\n\n- NEVER send a dispute notice without specific reference to the\n  PO number and the contractual basis for the dispute\n- NEVER send a CAR without the supporting performance data attached\n- NEVER send a contract notice after the notice deadline has passed\n  without legal advice (you may have lost the right to non-renew)\n- NEVER send a vendor exit notice without confirming transition\n  requirements for tooling, IP, and documentation first\n- NEVER respond to a phishing or social engineering attempt\n  (bank detail change requests) by email -- always call the vendor\n  on a known number to verify\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n",{"name":5,"license":14,"metadata":59,"description":64},{"author":60,"version":61,"plugin-commands":62,"mcp-integrations":63},"Panaversity","1.0","\u002Fvendor-communicate","Email MCP, contract register","Activate for: vendor communication, supplier communication, dispute letter, invoice dispute, corrective action request, CAR, price dispute, quantity dispute, performance notice, vendor notice, vendor warning, exit notice, contract notice, non-renewal notice, vendor rejection, vendor escalation, write to vendor, email supplier, communicate with vendor, supply assurance. NOT for: invoice processing (use invoice-reconciliation), vendor assessment (use vendor-assessment), spend analytics (use spend-analysis).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-vendor-communication-skill-db57dd4a","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill vendor-communication",{"tool":77,"command":78},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill vendor-communication",{"tool":80,"command":81},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill vendor-communication","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-vendor-communication-skill-db57dd4a\u002FSKILL.md",true,[],[86,111,138,165,193,224],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":54},"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",[],[88,94,95,96,97,98,99,100,101,102,103,104,105,49,106,107,108,109,39,110],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","ready","unrelated","app","scope","webmcp",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":54},"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",[],[118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137],"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":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":148,"publishedAt":54},"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",[144,147],{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[149,150,151,42,46,152,153,154,155,156,157,158,159,49,160,161,162,163,39,164],"transloadit media processing","Media","media processing","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":54},"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",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[175,176,177,178,179,180,181,182,183,49,184,185,186,187,188,189,190,191,192,39],"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":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":90,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":208,"publishedAt":54},"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",[199,202,205],{"categoryNo":200,"categoryName":201,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":203,"categoryName":204,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":206,"categoryName":207,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000038","人力资源",[209,210,211,212,213,214,51,215,119,216,49,217,218,219,220,221,222,223,39,38],"search","Job Search","technical job search","technical","writing","tasks","parsing","interview","up","engineer","general","activate","do","task","cv",{"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":90,"licenseFileUrl":6,"sourceHtmlUrl":228,"categories":229,"keywords":230,"publishedAt":54},"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,234,235,212,236,49,221,237,238,239,240,241,242,243,244,245,39,246],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]