agentleFS
NowistayNowistay/claude/skills/daily-brief/SKILL.md

daily-brief

Skill0 starsChanged 37 days agoMITView on GitHub

Prepare a concise cross-property operations brief from Nowistay bookings, missions, and conversations. Use for daily briefs, today's arrivals or departures, upcoming guests, urgent work, operational handovers, and questions such as "what needs attention today?".

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use weekly-review, onboarding and 2 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

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 5 projects that use this

  • AnthropicSkill

    onboarding

    Generate an onboarding checklist and first-week plan for a new hire. Use when someone has a start date coming up, building the pre-start task list (accounts, equipment, buddy), scheduling Day 1 and Week 1, or setting 30/60/90-day goals for a new team member.

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Do not call list_bookings once per property when omitting property_ids returns the whole eligible portfolio.

    line 33
  2. Distinctive:

    Do not use full-detail list responses for broad requests.

    line 34
  3. Very specific:

    Do not call get_booking or get_mission for every row.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 24 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

Nowistay Daily Brief

Build the brief with the fewest complete MCP calls.

Workflow

  1. Resolve property names and IDs once with list_properties. For all properties, omit search; paginate only when the response says more properties exist.
  2. Resolve relative dates in each property's timezone. Use get_property only when the timezone is needed and not already available.
  3. Fetch bookings in one portfolio-wide request whenever possible. For multi-property or broad date ranges, use list_bookings with response_format=table, limit=500, and include_details=false. Follow resultMetadata.nextOffset until hasMore=false.
  4. Fetch missions with list_missions. Use compact results for a small focused request; use response_format=table and limit=500 for a portfolio-wide brief.
  5. Fetch conversations only when the user explicitly asks about messages or unresolved guest communication. Do not read conversations merely to enrich a general brief.
  6. Retrieve full booking, mission, report, or conversation details only for items that need explanation or action.

Brief format

Present only useful operating information, ordered by urgency:

  • urgent incidents or failed missions;
  • arrivals and departures with property, guest, time, and readiness risks;
  • unassigned, overdue, or blocked missions;
  • guest conversations that need a host decision;
  • a short next-actions list.

Use property names in the response. Identify a guest only when the user requested guest-level information or when the identity is necessary to act on a specific arrival, departure, or conversation; otherwise identify the stay by property and dates. Never include guest email, phone, postal address, private notes, or message content in a general brief. Keep internal IDs out of the prose unless the user asks for them or they are needed to disambiguate records. If a broad query is paginated, finish every page before claiming the brief is complete.

Efficiency rules

  • Do not call list_bookings once per property when omitting property_ids returns the whole eligible portfolio.
  • Do not use full-detail list responses for broad requests.
  • Do not call get_booking or get_mission for every row.
  • Trust resultMetadata.hasMore and the pagination fields to decide whether a result is complete.

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.