agentleFS
bethronbethron/travel-concierge/skills/export-itinerary/SKILL.md

export-itinerary

Skill1 starsChanged 4 months agoMITView on GitHub

This skill should be used whenever the user wants a shareable or printable version of their trip plan — phrases like "export the itinerary", "make a PDF", "Word version", "something I can print", "send it to my partner", "download the plan", or when an itinerary reaches Settled status and a polished document would help.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the current itinerary.md, trip-brief.md and budget.md — export the file's state, never a remembered version.

    line 20
  2. Distinctive:

    If the itinerary status is still Draft, mention it and confirm the traveller wants to export anyway.

    line 22
  3. Distinctive:

    Use the platform's document-creation capability (docx/pdf skills where available) and follow its guidance for professional output.

    line 24

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

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

Export Itinerary

Turn the living itinerary.md into a polished, downloadable document (Word .docx by default; PDF on request).

Before generating

  • Read the current itinerary.md, trip-brief.md and budget.md — export the file's state, never a remembered version.
  • If the itinerary status is still Draft, mention it and confirm the traveller wants to export anyway.
  • Use the platform's document-creation capability (docx/pdf skills where available) and follow its guidance for professional output.

Document structure

  1. Cover — trip title, dates, travellers, destination; one-line summary.
  2. Trip overview — the "At a glance" table.
  3. Key bookings — flights (with times and references), stay (with address, check-in/out), booked activities with dates and any ticket notes.
  4. Day-by-day — one section per day mirroring itinerary.md, cleaned of internal markers: booked items in bold, suggestions phrased as suggestions, backup options in a short note.
  5. Budget summary — committed vs estimated vs ceiling, from budget.md.
  6. Practical notes — advance-booking deadlines, packing-list pointer, emergency numbers for the destination, plug type, currency.

Style

  • Clean and legible in print: clear headings, generous spacing, no emoji.
  • Times in 24-hour format; prices with currency symbols.
  • Neutral, warm tone — this document may be shared with travel companions.

Delivery

Save the document to the outputs location and present it to the user. Offer a PDF version if the traveller asked for Word, and vice versa.

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.