review-the-week
Skill1 starsChanged 22 days agoMITView on GitHub
Review the agency's coming departures, deadlines and open tasks in itinovo, and what each sold trip still misses (supplier confirmations, vouchers, documents, payments). Use when the user asks what is coming up, who leaves soon, or what to do this week.
In this repository12 other files it gives its agents.
- confirm-with-suppliersSkill
- follow-up-open-quotesSkill
- import-clientsSkill
- load-supplier-price-listSkill
- log-client-emailsSkill
- offer-to-templateSkill
- prepare-travel-documentsSkill
- quote-from-requestSkill
- record-in-accountingSkill
- review-the-numbersSkill
- revise-a-sent-quoteSkill
- set-up-a-groupSkill
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
- Distinctive: line 22
Never send anything to clients: documents, messages and payment requests leave from the itinovo app.
- Distinctive: line 23
Ask before writing to suppliers or changing a booking.
≈ “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.
Files
Reviewing the week
Steps
- Show the departures with
show_departuresfor the period asked (default: the next 7 days). Each card says what the trip still misses, as the itinovo Dashboard does. - Add the day's work with
get_overview(my_day): tasks due, follow-ups, notifications. - Summarise in a few lines: what needs doing first and why (a departure in two days missing a confirmation comes before a task due next week).
- Offer the next step for each gap, and wait for the user:
- a supplier confirmation →
ask_suppliers(it asks the user before sending anything); - a task to record →
save_task; - a booking to look into →
get_lead.
- a supplier confirmation →
Rules
- Never send anything to clients: documents, messages and payment requests leave from the itinovo app.
- Ask before writing to suppliers or changing a booking.
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
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.

