Core PA Admin and Exec Support

## Quick judgement This is a strong, well-structured "core PA" skill that covers the most common executive-support workflows: triage, prioritization, planning, scheduling proposals, comms drafting, and meeting support. It is thoughtfully constrained (no autonomous actions, no overreach into specialized advice) and has clear, opinionated defaults for working hours and scheduling. For users who can paste in messages/calendar/tasks/notes and want an all-in-one planning+drafting pass, it should perform very well. It is less suitable when users expect automated booking/sending, highly custom work hours, or domain-specific advice. ## Key strengths - **Comprehensive workflow coverage:** Handles the full PA loop from ingestion (messages, tasks, calendar, notes) through triage, prioritization, and planning, all the way to comms drafts and meeting artifacts. - **Clear constraints and guardrails:** Repeatedly emphasizes that it only drafts and proposes, never sends or books, and explicitly avoids legal/medical/financial advisory roles. - **Scheduling discipline:** Enforces weekday-only, 08:00–17:00 work hours with meetings ending by 16:30, reducing the risk of unrealistic or boundary-violating suggestions. - **STOP-and-ASK logic:** Mandates clarification when key inputs are missing (e.g., incomplete scheduling info, missing calendar availability, or unknown factual content needed for drafts), which improves reliability and reduces hallucination risk. - **Structured output design:** Markdown sections plus a JSON block with a referenced schema make it straightforward for downstream tooling to consume and automate around its outputs. ## Notable risks / limitations - **Dependence on user-provided structure:** Quality depends heavily on users actually supplying messages, tasks, calendar snippets, or notes. If inputs are messy, incomplete, or non-standard, the plan and triage quality may degrade. - **Rigid scheduling assumptions:** Fixed working hours (weekdays, 08:00–17:00, latest end 16:30) are great for safety but may misalign with users who work different hours or across time zones unless they explicitly restate constraints. - **Expectation mismatch risk:** Some users may assume it can send emails or book meetings; the skill only drafts/proposes. Clear communication in the calling product is needed to avoid confusion. - **Limited domain depth:** It is intentionally generic for admin/executive work and explicitly avoids substantive legal/medical/financial guidance, so it should not be used where those domains are central to the task. ## Recommended usage scenarios - **Primary:** Daily "PA run" for executives, managers, or ICs with busy inboxes—feed it messages, task lists, and availability, and use the resulting triage, prioritized tasks, and drafted replies as your starting point. - **Operational teams:** Team leads or chiefs-of-staff who need systematic action-item extraction and follow-up lists from recurring meetings and status calls. - **Scheduling-heavy roles:** Coordinators or assistants who must propose meeting times within strict business-hour constraints while keeping communication professional and concise. - **Tool integrations:** Systems that want a reliable, structured PA layer—using its JSON output to populate task trackers, calendars (for pending invites), or CRM notes, while keeping humans in the loop for final actions. Use this skill when you want **well-structured, conservative, human-in-the-loop executive support** rather than automated booking or domain-specific expert advice.