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
- bas1l/claude-skillstheir own version, first seen Nov 11, 2026
- hurleywgly/skillstheir own version, first seen Nov 8, 2026
- craigcossairt/trellistheir own version, first seen Nov 6, 2026
- geekfujiwara/copilot-cowork-skillstheir own version, first seen Nov 1, 2026
- HybridAIOne/hybridclawtheir own version, first seen Nov 1, 2026
- ofershap/mashov-parent-brieftheir own version, first seen Nov 1, 2026
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.
QuixiAISkillweekly-review
Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week
Also in 5 projects that use this
AnthropicSkillonboarding
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
VercelSkillsetup
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
SentrySkillskill-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
Other versions31 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 31
- huytieu/COG-second-brain★ 1.3ksame name
- mariagorskikh/open-instinct★ 428same name
- leiting-eric/DailyBrief★ 384same name
- HybridAIOne/hybridclaw★ 162same name
- cgoinglove/thursday★ 56same name
- cgoinglove/thursday-agent★ 56same name
- systemind-team/AICOO-Skills★ 35same name
- seedprod/claude-code-telegram★ 20same name
- Unabyss/unabyss-skills★ 15same name
- rittmananalytics/wire-plugin★ 14same name
21 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- calendar-revenueSkill
- direct-bookingsSkill
- guest-messagingSkill
- guest-recordsSkill
- portfolio-reportingSkill
- property-knowledgeSkill
- team-operationsSkill
- welcome-guideSkill
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
- Very specific: line 33
Do not call list_bookings once per property when omitting property_ids returns the whole eligible portfolio.
- Distinctive: line 34
Do not use full-detail list responses for broad requests.
- Very specific: line 35
Do not call get_booking or get_mission for every row.
“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.
Files
Nowistay Daily Brief
Build the brief with the fewest complete MCP calls.
Workflow
- Resolve property names and IDs once with
list_properties. For all properties, omitsearch; paginate only when the response says more properties exist. - Resolve relative dates in each property's timezone. Use
get_propertyonly when the timezone is needed and not already available. - Fetch bookings in one portfolio-wide request whenever possible. For multi-property or broad date ranges, use
list_bookingswithresponse_format=table,limit=500, andinclude_details=false. FollowresultMetadata.nextOffsetuntilhasMore=false. - Fetch missions with
list_missions. Use compact results for a small focused request; useresponse_format=tableandlimit=500for a portfolio-wide brief. - Fetch conversations only when the user explicitly asks about messages or unresolved guest communication. Do not read conversations merely to enrich a general brief.
- 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_bookingsonce per property when omittingproperty_idsreturns the whole eligible portfolio. - Do not use full-detail list responses for broad requests.
- Do not call
get_bookingorget_missionfor every row. - Trust
resultMetadata.hasMoreand the pagination fields to decide whether a result is complete.
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.

