agentleFS
itinovo-crmitinovo-crm/claude-plugin/skills/prepare-travel-documents/SKILL.md

prepare-travel-documents

Skill1 starsChanged 22 days agoMITView on GitHub

Get the travel documents of the coming departures ready in itinovo — roadbook, vouchers, contract, and for groups the rooming list, the manifest and the delegates' agenda — after checking that each trip has what they need, without sending anything. Use when the user asks to prepare the documents for the week's departures or for one trip.

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:

    Leave out the documents already there unless the user wants them made again.

    line 20
  2. Distinctive:

    Never fill a gap with invented data: a missing confirmation code or room stays missing until it arrives.

    line 27

≈ “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

Preparing the travel documents

Steps

  1. Find the trips: show_departures for the period asked (by default the next 7 days), or the trip the user names with search.
  2. Check each trip with get_lead (include: ["readiness", "documents"]): what it still misses (supplier confirmations, travellers' names, payments) and which documents it already has.
  3. Show a table — trip, departure, what is missing, documents already there — and say which documents would come out incomplete: a voucher without the supplier's confirmation code, a rooming list without rooms.
  4. Generate, after the user's yes, with generate_document (leadId, type: roadbook, voucher, contract; for groups rooming_list, group_manifest, delegate_agenda). Vouchers are one per service the supplier has confirmed: type: voucher makes them all, serviceId only that one. Leave out the documents already there unless the user wants them made again.
  5. Report what was generated — it is in the booking's Documents tab in itinovo — and what is still missing, with the next step (confirmations with the confirm-with-suppliers skill).

Rules

  • Nothing is sent to the client: the user sends the documents from the itinovo app.
  • Never fill a gap with invented data: a missing confirmation code or room stays missing until it arrives.

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.