[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6N17453H85SABBGS98JPC1S":3,"skill-same:01M6N17453H85SABBGS98JPC1S":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},"01M6N17453H85SABBGS98JPC1S","invoice-reconciliation",null,"Activate for: invoice, reconcile, reconciliation, three-way match, two-way match, invoice processing, AP, accounts payable, purchase order match, goods receipt match, invoice exception, price variance, quantity variance, duplicate invoice, invoice approval, invoice hold, invoice dispute, PO mismatch, over-invoiced, under-delivered, missing PO. NOT for: bank reconciliation (use banking plugin), 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-invoice-reconciliation-skill-7c6a604a\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"invoice reconciliation","invoice","reconciliation","three","accounts payable","for","bank","purchase","processing","missing","MCP","activate","vendor assessment","reconcile","erp","system","analysis","email","inbox","assessment","2026-11-10 10:12:30",false,"---\nname: invoice-reconciliation\ndescription: >\n  Activate for: invoice, reconcile, reconciliation, three-way match, two-way\n  match, invoice processing, AP, accounts payable, purchase order match,\n  goods receipt match, invoice exception, price variance, quantity variance,\n  duplicate invoice, invoice approval, invoice hold, invoice dispute, PO\n  mismatch, over-invoiced, under-delivered, missing PO.\n  NOT for: bank reconciliation (use banking plugin), vendor assessment\n  (use vendor-assessment), spend category analysis (use spend-analysis).\nlicense: Apache-2.0\nmetadata:\n  author: Panaversity\n  version: \"1.0\"\n  plugin-commands: \"\u002Finvoice-reconcile\"\n  mcp-integrations: \"ERP, AP system, email-inbox MCP\"\n---\n\n## UNIVERSAL RULES (apply to every reconciliation task)\n\n- NEVER approve an invoice that has not been matched against a PO\n  (above the configured materiality threshold)\n- NEVER process a duplicate invoice -- always check against prior submissions\n  before authorising payment\n- ALWAYS include specific recommended actions with deadlines in every output --\n  observations without actions are not acceptable\n\n## THREE-WAY MATCH ENFORCEMENT\n\nThree-way match requires:\nDocument 1: Invoice (from vendor)\nDocument 2: Purchase Order (from ERP)\nDocument 3: Goods Receipt \u002F Service Confirmation (from operations)\n\nTWO-WAY MATCH (acceptable only for):\n\n- Services (no goods receipt exists)\n- Utilities (no PO in advance)\n- Invoices below configured materiality threshold\n\nNEVER approve a direct materials invoice without goods receipt confirmation.\n\n## MANDATORY OUTPUT HEADER\n\n```\nTASK:          [e.g. Invoice Reconciliation -- INV-2024-0847]\nVENDOR TIER:   [Strategic \u002F Tactical \u002F Commodity \u002F Bottleneck \u002F Unclassified]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [ERP \u002F AP system \u002F Manual input]\n```\n\n## RECONCILIATION WORKFLOW -- FOUR-STAGE PROCESS\n\n### Stage 1: Document Intelligence\n\nExtract structured data from invoice (PDF, email, EDI, manual entry):\n\nMANDATORY FIELDS TO EXTRACT:\nVendor name: [Exact legal name -- match against vendor master]\nVendor ID: [Cross-reference ERP vendor master]\nInvoice number: [For duplicate detection]\nInvoice date: [Check against late submission rules]\nPO reference: [Required for matching -- flag if absent]\nLine items: [Description \u002F quantity \u002F unit \u002F unit price \u002F line total]\nTotal amount: [Verify arithmetic: sum of lines + tax = total]\nPayment terms: [Match against contracted terms]\nBank details: [Flag if different from vendor master -- fraud risk]\n\nVALIDATION CHECKS AT EXTRACTION:\nArithmetic check: do line items sum to invoice total?\nVendor name match: does invoice name match ERP vendor master?\nDuplicate check: has this invoice number been submitted before?\nLate submission: is invoice date within the configured day limit?\nBank detail change: are bank details the same as vendor master?\n\nFLAG IMMEDIATELY IF:\nRED Bank details differ from vendor master -> FRAUD ALERT -- do not process;\ncontact vendor by phone (not email) to verify; escalate to Finance Director\nRED Duplicate invoice number -> REJECT; notify vendor\nRED Invoice > configured days old -> REJECT; notify vendor of late submission policy\nRED Vendor not in approved vendor list -> HOLD; escalate to Procurement\n\n### Stage 2: Three-Way Match\n\nMATCH EACH LINE ITEM AGAINST:\nDocument A: Invoice line (what vendor claims to be owed)\nDocument B: Purchase Order line (what was authorised to buy)\nDocument C: Goods Receipt \u002F Service Confirmation (what was actually received)\n\nQUERY ERP via MCP:\n\n1. Find PO by reference number\n2. Retrieve all PO line items with authorised quantities and prices\n3. Find Goods Receipt(s) matched to this PO\n4. Retrieve confirmed received quantities from GR\n\nMATCH CLASSIFICATION PER LINE ITEM:\n\nMATCHED -- all within tolerance\nInvoice qty = GR qty (within tolerance)\nInvoice price = PO price (within tolerance)\n-> Auto-approve this line\n\nPRICE VARIANCE -- OUTSIDE TOLERANCE\nInvoice price != PO price, outside tolerance\n-> Route to Procurement; require vendor price justification\n\nPRICE VARIANCE -- WITHIN TOLERANCE\nInvoice price != PO price, but within configured tolerance\n-> Auto-approve with flag to Finance (audit trail)\n\nQUANTITY VARIANCE -- OVER-INVOICED\nInvoice quantity > GR confirmed quantity\n-> Hold over-invoiced portion; investigate with warehouse\u002Fvendor\n\nQUANTITY VARIANCE -- GOODS RECEIPT PENDING\nInvoice quantity matches PO but GR not yet received\u002Fconfirmed\n-> Hold invoice; alert warehouse for GR confirmation;\nset 5-day follow-up reminder\n\nPO NOT FOUND\nInvoice references a PO that does not exist in ERP\n-> Hold entire invoice; route to Procurement for retrospective PO\nor rejection decision\n\nDUPLICATE DETECTED\nSame vendor, same amount, within configured days of prior invoice\n-> Reject; notify vendor; log as potential fraud attempt if persistent\n\nUNAUTHORISED CHARGE\nLine item has no corresponding PO line\n-> Reject this line; notify vendor; request credit note\n\n### Stage 3: Exception Routing\n\nFOR EACH EXCEPTION TYPE, APPLY ROUTING RULES:\n\nPrice variance -- within tolerance:\nAction: Auto-approve with Finance notification\nLog: Exception register (for pattern monitoring)\nOwner: Finance (automated)\n\nPrice variance -- outside tolerance (\u003C escalation threshold):\nAction: Route to category manager for approval\nDeadline: 3 business days\nOwner: Category manager + Procurement\n\nPrice variance -- outside tolerance (> escalation threshold):\nAction: Route to CPO for approval\nDeadline: 5 business days\nOwner: CPO\n\nQuantity variance -- over-invoiced:\nAction: Hold excess; investigate with warehouse team\nDeadline: 5 business days to confirm GR or reject\nOwner: Warehouse + Finance\n\nGR pending:\nAction: Hold invoice; alert warehouse; 5-day auto-reminder\nIf unresolved at 10 days: escalate to Operations Manager\nOwner: Warehouse -> Finance on resolution\n\nPO not found (> materiality threshold):\nAction: Route to Procurement for retrospective PO or rejection\nDeadline: 3 business days\nOwner: Procurement\n\nDuplicate invoice:\nAction: Reject immediately; notify vendor; log incident\nOwner: Finance (automated)\n\nFraud alert (bank details changed):\nAction: STOP all processing; escalate to Finance Director immediately\nOwner: Finance Director\n\n### Stage 4: Audit and Pattern Monitoring\n\nLOG FOR EVERY INVOICE:\n\n- Invoice number, vendor, date, amount\n- Match outcome: APPROVED \u002F EXCEPTION TYPE \u002F REJECTED\n- Exception resolution: action taken, approver, date resolved\n- Payment amount approved vs. original invoice amount\n\nPATTERN DETECTION (run weekly):\nSame exception from same vendor > 3x in 30 days:\n-> Flag as systematic issue; recommend vendor data alignment meeting\n\nPrice variance on same line item > 2 consecutive invoices:\n-> Flag as contract non-compliance; initiate commercial review\n\nGR pending rate > 15% of invoices from one vendor:\n-> Flag as goods receipt process issue (warehouse or vendor despatch?)\n\n## RECONCILIATION OUTPUT FORMAT\n\n```\nINVOICE RECONCILIATION: [Invoice Number] | [Vendor]\n================================================================\nInvoice date:  [Date]   PO matched:    [PO number or NOT FOUND]\nProcessing:    [Date]   GR matched:    [GR number or PENDING\u002FNONE]\n\nLINE ITEM ANALYSIS:\nItem [N]: [Description] -- [Qty] @ [Price]\n  PO price:      [X]    Invoice price: [X]\n  Price variance: [+\u002F-X] ([+\u002F-X]%)\n  GR qty:        [N] confirmed\n  Invoice qty:   [N]\n  Qty variance:  [+\u002F-N units]\n  TOLERANCE:     [+\u002F-X% configured for this category]\n  STATUS:        [MATCHED \u002F WITHIN TOLERANCE \u002F EXCEPTION TYPE]\n  Action:        [Specific action required]\n\nRECONCILIATION SUMMARY:\nApproved for payment:    [X]\nOn hold (pending GR):    [X]\nDisputed (variance):     [X]\nRejected (unauthorised): [X]\nOriginal invoice total:  [X]\nRECOMMENDED PAYMENT:     [X]\n\nVENDOR COMMUNICATION: [Drafted -- see \u002Fvendor-communicate]\nAUDIT LOG:             [Saved to exception register]\n================================================================\n```\n\n## NEVER DO THESE\n\n- NEVER approve a direct materials invoice without a goods receipt confirmation\n- NEVER process an invoice where bank details differ from vendor master\n  without phone verification -- this is the primary invoice fraud vector\n- NEVER approve a duplicate invoice -- always reject and notify vendor\n- NEVER approve a PO-not-found invoice above materiality threshold\n  without a retrospective PO or documented exception approval\n- NEVER process an invoice from a vendor not on the approved vendor list\n  without Procurement escalation\n- NEVER mark a GR as confirmed without system evidence --\n  verbal confirmation from warehouse is not sufficient for audit purposes\n\nALL OUTPUTS REQUIRE REVIEW BY A QUALIFIED PROFESSIONAL BEFORE USE IN BUSINESS DECISIONS.\n","## UNIVERSAL RULES (apply to every reconciliation task)\n\n- NEVER approve an invoice that has not been matched against a PO\n  (above the configured materiality threshold)\n- NEVER process a duplicate invoice -- always check against prior submissions\n  before authorising payment\n- ALWAYS include specific recommended actions with deadlines in every output --\n  observations without actions are not acceptable\n\n## THREE-WAY MATCH ENFORCEMENT\n\nThree-way match requires:\nDocument 1: Invoice (from vendor)\nDocument 2: Purchase Order (from ERP)\nDocument 3: Goods Receipt \u002F Service Confirmation (from operations)\n\nTWO-WAY MATCH (acceptable only for):\n\n- Services (no goods receipt exists)\n- Utilities (no PO in advance)\n- Invoices below configured materiality threshold\n\nNEVER approve a direct materials invoice without goods receipt confirmation.\n\n## MANDATORY OUTPUT HEADER\n\n```\nTASK:          [e.g. Invoice Reconciliation -- INV-2024-0847]\nVENDOR TIER:   [Strategic \u002F Tactical \u002F Commodity \u002F Bottleneck \u002F Unclassified]\nCONFIGURATION: [Loaded: supply-chain.local.md \u002F Not configured]\nDATA SOURCES:  [ERP \u002F AP system \u002F Manual input]\n```\n\n## RECONCILIATION WORKFLOW -- FOUR-STAGE PROCESS\n\n### Stage 1: Document Intelligence\n\nExtract structured data from invoice (PDF, email, EDI, manual entry):\n\nMANDATORY FIELDS TO EXTRACT:\nVendor name: [Exact legal name -- match against vendor master]\nVendor ID: [Cross-reference ERP vendor master]\nInvoice number: [For duplicate detection]\nInvoice date: [Check against late submission rules]\nPO reference: [Required for matching -- flag if absent]\nLine items: [Description \u002F quantity \u002F unit \u002F unit price \u002F line total]\nTotal amount: [Verify arithmetic: sum of lines + tax = total]\nPayment terms: [Match against contracted terms]\nBank details: [Flag if different from vendor master -- fraud risk]\n\nVALIDATION CHECKS AT EXTRACTION:\nArithmetic check: do line items sum to invoice total?\nVendor name match: does invoice name match ERP vendor master?\nDuplicate check: has this invoice number been submitted before?\nLate submission: is invoice date within the configured day limit?\nBank detail change: are bank details the same as vendor master?\n\nFLAG IMMEDIATELY IF:\nRED Bank details differ from vendor master -> FRAUD ALERT -- do not process;\ncontact vendor by phone (not email) to verify; escalate to Finance Director\nRED Duplicate invoice number -> REJECT; notify vendor\nRED Invoice > configured days old -> REJECT; notify vendor of late submission policy\nRED Vendor not in approved vendor list -> HOLD; escalate to Procurement\n\n### Stage 2: Three-Way Match\n\nMATCH EACH LINE ITEM AGAINST:\nDocument A: Invoice line (what vendor claims to be owed)\nDocument B: Purchase Order line (what was authorised to buy)\nDocument C: Goods Receipt \u002F Service Confirmation (what was actually received)\n\nQUERY ERP via MCP:\n\n1. Find PO by reference number\n2. Retrieve all PO line items with authorised quantities and prices\n3. Find Goods Receipt(s) matched to this PO\n4. Retrieve confirmed received quantities from GR\n\nMATCH CLASSIFICATION PER LINE ITEM:\n\nMATCHED -- all within tolerance\nInvoice qty = GR qty (within tolerance)\nInvoice price = PO price (within tolerance)\n-> Auto-approve this line\n\nPRICE VARIANCE -- OUTSIDE TOLERANCE\nInvoice price != PO price, outside tolerance\n-> Route to Procurement; require vendor price justification\n\nPRICE VARIANCE -- WITHIN TOLERANCE\nInvoice price != PO price, but within configured tolerance\n-> Auto-approve with flag to Finance (audit trail)\n\nQUANTITY VARIANCE -- OVER-INVOICED\nInvoice quantity > GR confirmed quantity\n-> Hold over-invoiced portion; investigate with warehouse\u002Fvendor\n\nQUANTITY VARIANCE -- GOODS RECEIPT PENDING\nInvoice quantity matches PO but GR not yet received\u002Fconfirmed\n-> Hold invoice; alert warehouse for GR confirmation;\nset 5-day follow-up reminder\n\nPO NOT FOUND\nInvoice references a PO that does not exist in ERP\n-> Hold entire invoice; route to Procurement for retrospective PO\nor rejection decision\n\nDUPLICATE DETECTED\nSame vendor, same amount, within configured days of prior invoice\n-> Reject; notify vendor; log as potential fraud attempt if persistent\n\nUNAUTHORISED CHARGE\nLine item has no corresponding PO line\n-> Reject this line; notify vendor; request credit note\n\n### Stage 3: Exception Routing\n\nFOR EACH EXCEPTION TYPE, APPLY ROUTING RULES:\n\nPrice variance -- within tolerance:\nAction: Auto-approve with Finance notification\nLog: Exception register (for pattern monitoring)\nOwner: Finance (automated)\n\nPrice variance -- outside tolerance (\u003C escalation threshold):\nAction: Route to category manager for approval\nDeadline: 3 business days\nOwner: Category manager + Procurement\n\nPrice variance -- outside tolerance (> escalation threshold):\nAction: Route to CPO for approval\nDeadline: 5 business days\nOwner: CPO\n\nQuantity variance -- over-invoiced:\nAction: Hold excess; investigate with warehouse team\nDeadline: 5 business days to confirm GR or reject\nOwner: Warehouse + Finance\n\nGR pending:\nAction: Hold invoice; alert warehouse; 5-day auto-reminder\nIf unresolved at 10 days: escalate to Operations Manager\nOwner: Warehouse -> Finance on resolution\n\nPO not found (> materiality threshold):\nAction: Route to Procurement for retrospective PO or rejection\nDeadline: 3 business days\nOwner: Procurement\n\nDuplicate invoice:\nAction: Reject immediately; notify vendor; log incident\nOwner: Finance (automated)\n\nFraud alert (bank details changed):\nAction: STOP all processing; escalate to Finance Director immediately\nOwner: Finance Director\n\n### Stage 4: Audit and Pattern Monitoring\n\nLOG FOR EVERY INVOICE:\n\n- Invoice number, vendor, date, amount\n- Match outcome: APPROVED \u002F EXCEPTION TYPE \u002F REJECTED\n- Exception resolution: action taken, approver, date resolved\n- Payment amount approved vs. original invoice amount\n\nPATTERN DETECTION (run weekly):\nSame exception from same vendor > 3x in 30 days:\n-> Flag as systematic issue; recommend vendor data alignment meeting\n\nPrice variance on same line item > 2 consecutive invoices:\n-> Flag as contract non-compliance; initiate commercial review\n\nGR pending rate > 15% of invoices from one vendor:\n-> Flag as goods receipt process issue (warehouse or vendor despatch?)\n\n## RECONCILIATION OUTPUT FORMAT\n\n```\nINVOICE RECONCILIATION: [Invoice Number] | [Vendor]\n================================================================\nInvoice date:  [Date]   PO matched:    [PO number or NOT FOUND]\nProcessing:    [Date]   GR matched:    [GR number or PENDING\u002FNONE]\n\nLINE ITEM ANALYSIS:\nItem [N]: [Description] -- [Qty] @ [Price]\n  PO price:      [X]    Invoice price: [X]\n  Price variance: [+\u002F-X] ([+\u002F-X]%)\n  GR qty:        [N] confirmed\n  Invoice qty:   [N]\n  Qty variance:  [+\u002F-N units]\n  TOLERANCE:     [+\u002F-X% configured for this category]\n  STATUS:        [MATCHED \u002F WITHIN TOLERANCE \u002F EXCEPTION TYPE]\n  Action:        [Specific action required]\n\nRECONCILIATION SUMMARY:\nApproved for payment:    [X]\nOn hold (pending GR):    [X]\nDisputed (variance):     [X]\nRejected (unauthorised): [X]\nOriginal invoice total:  [X]\nRECOMMENDED PAYMENT:     [X]\n\nVENDOR COMMUNICATION: [Drafted -- see \u002Fvendor-communicate]\nAUDIT LOG:             [Saved to exception register]\n================================================================\n```\n\n## NEVER DO THESE\n\n- NEVER approve a direct materials invoice without a goods receipt confirmation\n- NEVER process an invoice where bank details differ from vendor master\n  without phone verification -- this is the primary invoice fraud vector\n- NEVER approve a duplicate invoice -- always reject and notify vendor\n- NEVER approve a PO-not-found invoice above materiality threshold\n  without a retrospective PO or documented exception approval\n- NEVER process an invoice from a vendor not on the approved vendor list\n  without Procurement escalation\n- NEVER mark a GR as confirmed without system evidence --\n  verbal confirmation from warehouse is not sufficient for audit purposes\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","\u002Finvoice-reconcile","ERP, AP system, email-inbox MCP","Activate for: invoice, reconcile, reconciliation, three-way match, two-way match, invoice processing, AP, accounts payable, purchase order match, goods receipt match, invoice exception, price variance, quantity variance, duplicate invoice, invoice approval, invoice hold, invoice dispute, PO mismatch, over-invoiced, under-delivered, missing PO. NOT for: bank reconciliation (use banking plugin), vendor assessment (use vendor-assessment), spend category analysis (use spend-analysis).\n","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-invoice-reconciliation-skill-7c6a604a","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 invoice-reconciliation",{"tool":71,"command":72},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill invoice-reconciliation",{"tool":74,"command":75},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill invoice-reconciliation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-06-agentfactory-business-plugins-main-supply-chain-skills-invoice-reconciliation-skill-7c6a604a\u002FSKILL.md",true,[],[80,106,133,160,188,219],{"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,33,105],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","webmcp",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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",[],[113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132],"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":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,36,38,147,148,149,150,151,152,153,154,100,155,156,157,158,33,159],"transloadit media processing","Media","media processing","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":169,"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",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[170,171,172,173,174,175,176,177,178,100,179,180,181,182,183,184,185,186,187,33],"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":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":203,"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",[194,197,200],{"categoryNo":195,"categoryName":196,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":198,"categoryName":199,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":201,"categoryName":202,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000038","人力资源",[204,205,206,207,208,209,45,210,114,211,100,212,213,214,39,215,216,217,33,218],"search","Job Search","technical job search","technical","writing","tasks","parsing","interview","up","engineer","general","do","task","cv","letter",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":225,"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",[],[226,227,228,229,230,207,231,100,215,232,233,234,235,236,237,238,239,240,33,241],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]