agentleFS
itinovo-crmitinovo-crm/claude-plugin/skills/load-supplier-price-list/SKILL.md

load-supplier-price-list

Skill1 starsChanged 22 days agoMITView on GitHub

Load a supplier's price list or contract (a PDF, a spreadsheet, a web page the user opened) into itinovo as the supplier with its rates by season, room, board and occupancy. Use when the user attaches or pastes a supplier's prices and wants them in itinovo.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never turn a hotel's rooms into products.

    line 14
  2. Distinctive:

    Write descriptions in your own words.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Loading a supplier's price list

How itinovo holds a supplier

  • A hotel (also from a bed bank) is a supplier of category hotel, type direct, with its stars, description, amenities and address. Each combination of room type, board and occupancy is one of its rates, with its validity dates. A hotel has no products.
  • Products are the catalogue of a tour operator or DMC: its tours, excursions and packages. Never turn a hotel's rooms into products.

Steps

  1. Read the whole source and list the rates: room, board (RO, BB, HB, FB, AI), occupancy (single, double, triple, quad), season and dates (YYYY-MM-DD), price, unit (per night, per person…), currency (ISO code), supplements, minimum stay, cancellation terms.
  2. Load in one call with import_supplier: the supplier's card and its rates (and products for a tour operator or DMC). Large lists go in several calls: loading again updates what is there and never doubles it.
  3. Report from the result card: what was created, updated and left out, and why. For each row left out, say what is missing (often the price) and ask the user for it.

Rules

  • Give every field the source has and leave out what it does not say: never invent a price, a date or a code.
  • Write descriptions in your own words; prices, codes and cancellation terms go in as they are.
  • Photos are not loaded through Claude: the agency uploads them in the app (the supplier's card, Media tab).
  • Load only what the agency has the right to use, one source at a time, on the user's request.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.