Skip to content
Automation
Skill

/vendor-communication

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,

From plugin
agentfactory-business-plugins
2997 skills30 agents8 commands
Install
$ npx -y skills add panaversity/agentfactory-business-plugins --skill vendor-communication --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/vendor-communication

Context preview

The summary Claude sees to decide when to auto-load this skill.

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,

SKILL.md

vendor-communication.SKILL.md
name: vendor-communication
description: >
  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).
license: Apache-2.0
metadata:
  author: Panaversity
  version: "1.0"
  plugin-commands: "/vendor-communicate"
  mcp-integrations: "Email MCP, contract register"

UNIVERSAL RULES (apply to every communication task)

  • NEVER recommend a vendor exit without a qualified alternative identified

or an explicit "no alternative -- managed risk" decision documented

  • ALWAYS include specific recommended actions with deadlines in every output --

observations without actions are not acceptable

MANDATORY OUTPUT HEADER

TASK:          [e.g. Vendor Communication -- Invoice Dispute INV-2024-0847]
VENDOR TIER:   [Strategic / Tactical / Commodity / Bottleneck / Unclassified]
CONFIGURATION: [Loaded: supply-chain.local.md / Not configured]
COMMUNICATION TYPE: [Invoice Dispute / CAR / Non-Renewal / Supply Assurance / Exit]

COMMUNICATION TYPES AND STRUCTURES

Type 1: Invoice Dispute Notice

Use when: invoice exception identified in reconciliation; vendor must provide credit note, revised invoice, or supporting evidence.

Subject: Invoice Dispute -- Invoice [Number] dated [Date]
         Reference: PO [Number]

Dear [Contact name at vendor],

We have reviewed Invoice [Number] dated [Date] for [Amount] and have
identified the following discrepancy/discrepancies requiring your
attention before payment can be processed.

DISCREPANCY [N]:
Item:         [Description]
Invoiced:     [Qty or price as invoiced]
Our records:  [Qty or price per PO/GR]
Variance:     [Amount or units]
Basis:        [PO reference or Goods Receipt reference]

REQUIRED ACTION:
Please [issue a credit note for X / provide a revised invoice /
provide documentary evidence supporting the invoiced amount]
by [date -- typically 5 business days].

Payment of the undisputed amount ([X]) will be processed on our
standard payment terms from receipt of resolution.

[Sign-off: your name, title, contact details]

Type 2: Corrective Action Request (CAR)

Use when: vendor performance has breached a threshold (OTD, quality, or other contractual KPI) requiring formal documented response.

Subject: Corrective Action Request -- [Vendor Name] -- [KPI] Performance
         Reference: CAR-[Year]-[Number]

Dear [Contact name],

We are writing to formally notify you that [Vendor Name]'s performance
against [KPI] has fallen below the contractual threshold during
[period], and to request a formal corrective action plan.

PERFORMANCE DATA:
KPI:              [On-time delivery / Quality rejection rate / Other]
Contractual SLA:  [X]%
Actual (period):  [X]%
Shortfall:        [X percentage points]
Period:           [Start date -- End date]
Supporting data:  [Reference to ERP report or attached data]

REQUIRED CORRECTIVE ACTION PLAN:
Please provide a written corrective action plan within [10 / 14] calendar
days of this notice, addressing:
1. Root cause analysis of the performance shortfall
2. Immediate containment actions already taken
3. Corrective actions to be implemented, with target dates
4. How compliance with the SLA will be monitored going forward

We will schedule a review meeting for [proposed date] to discuss
the plan and agree monitoring arrangements.

This notice is issued under Clause [X] of our Supply Agreement dated [date].

[Sign-off: your name, title]

Type 3: Contract Non-Renewal Notice

Use when: exercising the right not to renew a contract within the contractual notice period. Must be sent before the notice deadline.

Subject: Notice of Non-Renewal -- [Contract Reference/Description]
         Agreement dated [Date]

Dear [Contact name],

In accordance with Clause [X] of our [Agreement name] dated [date],
we are providing [X days'] written notice that we will not be renewing
the Agreement upon its expiry on [date].

The Agreement will therefore terminate on [expiry date].

We will honour all purchase orders issued prior to this notice and
will expect fulfilment of all confirmed orders through to [date].

Please confirm receipt of this notice and advise us of any transition
support you are able to provide during the wind-down period.

We thank you for your service over the period of the Agreement.

[Sign-off: authorised signatory, title]

Type 4: Emergency Supply Assurance Request

Use when: a risk signal (financial distress, Tier 2 disruption, news event) requires immediate assurance from a critical vendor.

Subject: Supply Assurance Request -- [Category/Product] -- Urgent

Dear [Contact name],

We have become aware of [brief, factual description of the concern --
e.g. reports of supply disruption at one of your key raw material
suppliers / your company's published restructuring announcement].

As [Vendor Name] is a critical supplier to our operations, we are
writing to request written assurance on the following points:

1. Is your production capacity for [category/product] unaffected?
2. Do you have sufficient raw material / component inventory to
   fulfil orders over the next [60/90] days?
3. Are there any circumstances that could affect your ability to
   meet our confirmed purchase orders?

Please respond by [date -- 3-5 business days] with a formal
written statement. We may follow this with a request for a
call with your [CEO/Operations Director] to discuss further.

We appreciate your prompt attention to this matter.

[Sign-off: CPO or category manager]

Type 5: Vendor Exit Notice (Planned Transition)

Use when:

Read more
Ships withagentfactory-business-plugins

🚀 Marketplace of domain-specific plugins for building enterprise AI agents. Enable AI agents to perform finance, banking, legal, and sales workflows using modular domain plugins.

Get the whole plugin