manage-vendors
Skill65 starsChanged 13 days agoMITView on GitHub
Manage vendors (suppliers, Lieferanten, Kreditoren) - list, create, update, find duplicates and merge them. Use when the user mentions vendors, suppliers, Lieferanten, Kreditor numbers or duplicate vendors.
In this repository28 other files it gives its agents.
- accounting-cutoverSkill
- calculators-and-formsSkill
- categorize-transactionsSkill
- company-incorporationSkill
- corporate-tax-registrationSkill
- create-invoiceSkill
- expense-reportSkill
- financial-overviewSkill
- find-receiptsSkill
- gewerbe-registrationSkill
- manage-clientsSkill
- manage-productsSkill
- monthly-reconciliationSkill
- overdue-remindersSkill
- pl-opening-balanceSkill
- pl-tax-settingsSkill
- run-payroll-monthSkill
- run-workflowSkill
- suggest-categorySkill
- ta-client-periodSkill
- ta-company-reviewSkill
- ta-datev-preparationSkill
- ta-missing-receiptsSkill
- ta-month-closeSkill
- ta-tax-complianceSkill
- tax-deduction-finderSkill
- tax-reportSkill
- verfahrensdokumentationSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Call list_vendors to show the vendors.
- Very specific: line 18
Call create_vendor or update_vendor with only the fields the user gave
- Very specific: line 24
If such a vendor is wrong, set the right vendor on the booking with update_transaction.
- Distinctive: line 25
If such a vendor is a second spelling of an existing vendor, merge it
- Very specific: line 32
If the user says a row holds different companies, call mark_vendors_not_duplicates.
- Very specific: line 35
Ask which vendor to keep before you call merge_vendors.
- Very specific: line 39
If the answer lists keptNumbers, tell the user: these bookings stay on the old Kreditor number, because the tax advisor already has them
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Help the user keep one vendor per supplier:
Listing and editing
- Call
list_vendorsto show the vendors. Present a table: Name, Kreditor number, IBAN, Documents - Call
create_vendororupdate_vendorwith only the fields the user gave - A vendor with bookings or bills cannot be deleted. Offer to merge it into another vendor instead
Vendors from documents
- For a company that keeps a ledger (every GmbH and UG, and a sole trader who moved to the ledger), Norman gives every expense document a vendor. It looks for the seller among the vendors by VAT number, IBAN and name. If none fits, it creates a vendor with the name, VAT number, IBAN and country of the document
fromDocumentis true for a vendor that Norman made this way and the user has not edited since- If such a vendor is wrong, set the right vendor on the booking with
update_transaction. When its last booking has moved, Norman removes the vendor and its Kreditor number is free again - If such a vendor is a second spelling of an existing vendor, merge it
Finding duplicates
- Call
list_vendor_duplicates groupsare own vendors that share a VAT number, an IBAN or a name. Show each group with its names and Kreditor numberssuggestionsare own vendors that look like a suggested brand- Each vendor carries its VAT number, IBAN, country, bookings and documents. Show them, so the user can judge
- If the user says a row holds different companies, call
mark_vendors_not_duplicates. The row does not come back
Merging
- Ask which vendor to keep before you call
merge_vendors. A merge cannot be undone. Propose the vendor with the most bookings - The kept vendor keeps its own name, VAT number and bank details. It takes the bookings, bills and rules of the others, and their names as aliases
- The merged vendors leave the list. Their Kreditor numbers are free for new vendors again
- Finalized bookings and bookings in a closed year never move. If
skippedis above 0, tell the user: that many bookings were skipped, and their vendor stays in the list with them - If the answer lists
keptNumbers, tell the user: these bookings stay on the old Kreditor number, because the tax advisor already has them - For a
suggestionsrow callmerge_vendor_with_suggestion: the vendor takes the brand's logo and keeps all its own data
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

