agentleFS
itinovo-crmitinovo-crm/claude-plugin/skills/set-up-a-group/SKILL.md

set-up-a-group

Skill1 starsChanged 22 days agoMITView on GitHub

Set up a group trip in itinovo from what the organiser sends — a participant list (a spreadsheet, a CSV, a pasted list) with classes, teams or service levels, and for meetings and events the programme of sessions — as a group lead with its sub-groups, travellers and sessions. Use when the user shares a group's participant list or an event's programme to load.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask before creating a lead or a client.

    line 36

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

Setting up a group

Steps

  1. Find the group's lead with search. If there is none, ask the user, then find or create the organiser with search and save_client (a school or a company: clientType: company, companyName), and create the lead with create_lead: clientId, groupName, groupType, expectedPax (10 or more), destination and dates.
  2. Make sure it has a quote (get_lead, include: ["details"]): travellers belong to a quote. If it has none, create_quote (leadId, from: empty, the dates) or the quote-from-request skill.
  3. Read the list and keep, for each participant, first name, last name, date of birth (YYYY-MM-DD) and email, and the sub-group the file gives (class, team, role, service level). Write names with capitals as names are written. Say which rows have no last name or appear twice.
  4. Create the sub-groups the list has with save_group (what: sub_group, leadId, name, and serviceLevel when the file says standard, premium or VIP). Keep the id each call returns.
  5. Load the travellers with save_travellers (quoteId, travelers, each with its subGroupId), at most 50 per call. First read who is already there (get_quote, include: ["travellers"]) and leave them out: same name and date of birth is the same person.
  6. For a meeting, incentive, conference or other event, add the programme with edit_quote_settings (action: add_sessions, quoteId, sessions: name, type, date, start and end time, venue, room, capacity, setup, allGroup: true or the subGroupIds taking part, visibleToClient). Then read the programme's checks with get_quote (include: ["editing"]) — a room too small, a session before the group lands, a session with no cost — tell the user each one with its fix, and apply a fix (action: update_session) only when the user asks.
  7. Report: travellers loaded per sub-group, rows left out and why, sessions added, checks still open.

Rules

  • Load only names, dates of birth and emails. Identity documents and health details (allergies, diets, medical needs) stay out: the participants give them in the app, through their own forms.
  • Ask before creating a lead or a client.
  • Group prices, free places and rooming are set in the app or on the user's explicit 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.