agentleFS
Sign inStart free
waj-1waj-1/waj-plugin/skills/daily-briefing/SKILL.md

daily-briefing

Skill0 starsChanged 11 days agoMITView on GitHub

Give a salon or spa manager a short start-of-day briefing from WAJ - today's bookings by staff member, first and last appointment, yesterday's sales, money still owed and gift cards expiring soon. Use when the user asks for a daily briefing, a morning summary, what today looks like, or what needs attention today.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use crm-lookup, spotify and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • QuixiAISkill

    crm-lookup

    Search, view, update, and merge contacts in the local CRM

    Also in 3 projects that use this

  • QuixiAISkill

    spotify

    Search Spotify, inspect current playback and devices, and control playback with explicit approval

    Also in 3 projects that use this

  • MicrosoftSkill

    inbox-triage

    Use this skill whenever the user asks to clean up, triage, declutter, or archive low-value Outlook inbox mail - "clean up my inbox", "triage my mail", "declutter my inbox", "sort out newsletters", "archive old resolved threads", "/inbox-triage" - to group only newsletters, auto-notifications, past-event meeting logistics, resolved threads, and redundant duplicates into reviewable move-proposals presented for per-bucket approval before any message moves. Do not use for reading mail, drafting or sending replies, deleting mail, executing moves without explicit per-bucket approval, or acting on messages from the user's manager, direct reports, active threads, flagged mail, or labelled/HR/Legal/Finance/Security senders.

    Also in 4 projects that use this

  • MicrosoftSkill

    image-gen

    Also in 3 projects that use this

  • AnthropicSkill

    weather

    The optional standing status report ("the weather"): compile open incidents, build health, merge-queue stats, and deploy lag into one always-current report page, and post to the channel only when a defined event fires. Use when the weather routine fires, or when someone asks to run/update the weather report.

    Also in 3 projects that use this

  • SentrySkill

    notion

    Search, fetch, create, update, and move Notion pages and data sources. Use when users ask to look up docs, specs, notes, meeting notes, project context, roadmaps, trackers, or internal references stored in Notion, or when they explicitly ask to create or edit Notion content.

    Also in 3 projects that use this

  • +2 more from QuixiAI

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Branch: All branches unless the user names one (list_branches).

    line 16
  2. Very specific:

    Call get_bookings for the day (start and end date both that day).

    line 20
  3. Very specific:

    Call get_business_performance for yesterday (start and end date both yesterday): total_revenue and services_sold.

    line 24
  4. Very specific:

    Call get_invoices with status "owed" for the last 7 days and use its summary: number of invoices and the amount owed.

    line 26
  5. Very specific:

    Call get_gift_cards with expiring_within_days 7.

    line 28
  6. Very specific:

    When the user asks where a service still fits today, call find_free_slots for that service and day.

    line 29
  7. Distinctive:

    Keep it short enough to read in a minute:

    line 34
  8. Distinctive:

    When there are no bookings for the day, say so and keep the other sections.

    line 42
  9. Distinctive:

    Do not print client phone numbers or emails, including the client field of an invoice, which can contain a phone number.

    line 46
  10. Distinctive:

    Every number must come from a tool result in this conversation.

    line 48

“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “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

Daily briefing

A one-screen summary of the day for the person running the business. The user's explicit instructions (date, branch, sections) override every default below.

Inputs

  • Day. Today in the business's local time, unless the user names another day. "Yesterday" below means the day before that.
  • Branch. All branches unless the user names one (list_branches).

Steps

  1. Call get_bookings for the day (start and end date both that day). Use summary.by_state for counts and summary.by_staff for bookings per staff member; a booking with two staff counts once for each. Take the first and last appointment from the bookings' start and end times.
  2. Call get_business_performance for yesterday (start and end date both yesterday): total_revenue and services_sold.
  3. Call get_invoices with status "owed" for the last 7 days and use its summary: number of invoices and the amount owed.
  4. Call get_gift_cards with expiring_within_days 7.
  5. When the user asks where a service still fits today, call find_free_slots for that service and day.

Output

Keep it short enough to read in a minute:

  • Today: number of bookings, first and last appointment, and a table of staff with their booking count.
  • Yesterday: revenue and services sold.
  • Needs attention: invoices still owed (count and amount) and gift cards expiring within 7 days (count). Omit a line when there is nothing.

When there are no bookings for the day, say so and keep the other sections.

Rules

  • Do not print client phone numbers or emails, including the client field of an invoice, which can contain a phone number. Names and times are enough.
  • Every number must come from a tool result in this conversation. If a step fails, keep the rest of the briefing and say which part is missing.
  • This skill only reads data. It never books, moves or cancels appointments.

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.

Check your setup, free