agentleFS
itinovo-crmitinovo-crm/claude-plugin/skills/log-client-emails/SKILL.md

log-client-emails

Skill1 starsChanged 22 days agoMITView on GitHub

Record in an itinovo booking the emails exchanged with its client in Outlook, Gmail or another mailbox, found with that mailbox's own connector, so the booking's Communications tab holds the whole history. Use when the user asks to log, file, attach or save a client's emails to a booking, or to bring the history of a client's emails into itinovo.

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:

    Never copy a payment card's number into the text: write that the email has one.

    line 26

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

Recording a client's emails on a booking

Steps

  1. Find the booking with search (the client's name, the destination) and read it with get_lead (include: ["details", "communications"]): the client's email address, and what the timeline already has.
  2. Find the emails with the mailbox's connector (Microsoft 365, Gmail…): those to and from the client's address in the period asked (default: the last 7 days).
  3. Show the list — date and time, received or sent, subject — marking those already in the booking's communications, and wait for the user to choose.
  4. Record each chosen email with log_email: direction (inbound from the client, outbound to the client), sentAt with its time, from, to, subject, text and mailbox (Outlook, Gmail…). The text is the email's whole text, as written: the message itself, without the earlier emails it quotes. If the client has no booking, record it on the client with clientId instead of leadId.
  5. Report what was recorded and what was already there.

Rules

  • Nothing is ever sent from here: log_email only records.
  • Record only emails with the booking's client, or about the booking, and only those the user chose.
  • Never copy a payment card's number into the text: write that the email has one.
  • The same email (same minute, sender and subject) is never recorded twice: itinovo answers that it is already there.

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.