From tenexity-setup-team-hvac-plumbing
Generates the daily morning briefing or end-of-day summary for distributor work. Triggers when the user asks "what's on my plate today", "give me my briefing", "morning briefing", "end of day", "what did I do today", "daily summary", "EOD summary", "what's hot today", or when a scheduled task runs the daily briefing or end-of-day prompt. Also triggers on /briefing and /eod commands. Reads the captain's log, tasks, calendar, and AR/vendor signals to produce a clear, scannable briefing in distributor language.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tenexity-setup-team-hvac-plumbing:daily-briefingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill generates two types of briefing from the user's PA data, both tuned to how a distributor's day actually works.
This skill generates two types of briefing from the user's PA data, both tuned to how a distributor's day actually works.
Read these sources and synthesise into a clear, scannable briefing:
WORK AREAS/Admin-PA/tasks.md. Any open tasks past their due date. Most important section — flag clearly.Keep it tight. Distributor mornings are short. No walls of text.
## Morning Briefing — [Day, Date]
### Overdue (needs attention)
[Items, or "Nothing overdue — you're clear."]
### Today
[Calendar events + tasks due today, merged into a timeline if possible]
### AR watch
[Customers on credit hold or crossing aging thresholds, or "AR clean — nothing crossing thresholds today."]
### Vendor watch
[Open vendor issues, or "No active vendor escalations."]
### Waiting on others
[Follow-ups due, or "Nothing pending."]
### Yesterday's highlights
[3-5 bullet points from the captain's log]
### Coming up (next 3 days)
[Brief list, or "Nothing scheduled."]
If a section is empty, include it with a positive note ("AR clean," "No active vendor escalations") rather than omitting it. The user should see the full picture every morning.
Read these sources and produce the summary:
WORK AREAS/Admin-PA/output-log.md for files created today.## End of Day — [Day, Date]
### What got done
[Completed tasks + key activities from the log]
### What you created
[Files from output log, or "No files created today."]
### Decisions made today
[Major decisions captured in preferences.md or inventory-action-log.md, or omit if none]
### Still open
[Remaining open tasks, briefly]
### Tomorrow
[Preview of tomorrow's commitments, or "Nothing scheduled yet."]
After presenting the EOD summary, offer a reflection:
"Want to take a minute to reflect on the day?"
If yes, ask these three questions one at a time using AskUserQuestion (with a freeform text option):
Log the reflection in today's captain's log under a ### Reflection heading with the timestamp. These reflections feed into the System Review — patterns of recurring frustrations become candidates for new scheduled tasks or workflow changes.
If the user declines, move on without comment.
When generating either briefing, prioritise distributor-relevant signals over generic productivity:
COMPANY/tools-and-context.md says monthly and the last inventory-action-log.md entry is over 30 days old, surface as a one-line nudge in "today"COMPANY/tools-and-context.md lists rebate programs with claim deadlines, check the calendar; surface anything within 14 daysThese take precedence over non-distributor reminders. A vendor allocation pushback is more urgent than "remind me to back up my phone."
If the PA was just set up and there's no data yet, don't produce an empty briefing. Say something like: "Your PA is fresh — there's nothing to brief on yet. Start logging throughout the day and tomorrow's briefing will have something to work with. In the meantime: [show calendar events for today if Calendar is connected, or just acknowledge it's day one]."
If only some sections have data, populate what's available and use empty-state notes for the rest.
Use the user's voice profile and writing rules. If they've banned "circle back," your briefing doesn't say "let's circle back tomorrow." If their tone is direct, your briefing is direct. The PA's voice is the user's voice.
The briefing is for an experienced distributor — assume trade fluency. "AR over 60" doesn't need explanation. "RGA" doesn't need explanation. "QBR with Carrier" doesn't need explanation.
npx claudepluginhub tenexity/cowork-distributor-plugins --plugin tenexity-setup-team-hvac-plumbingProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.