chief-of-staff
Personal communication chief of staff that triages email, Slack, LINE, and Messenger. Classifies messages into 4 tiers (skip/info_only/meeting_info/action_required), generates draft replies, and enforces post-send follow-through via hooks. Use when managing multi-channel communication workflows.
Best use case
chief-of-staff is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Personal communication chief of staff that triages email, Slack, LINE, and Messenger. Classifies messages into 4 tiers (skip/info_only/meeting_info/action_required), generates draft replies, and enforces post-send follow-through via hooks. Use when managing multi-channel communication workflows.
Teams using chief-of-staff should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/chief-of-staff/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How chief-of-staff Compares
| Feature / Agent | chief-of-staff | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Personal communication chief of staff that triages email, Slack, LINE, and Messenger. Classifies messages into 4 tiers (skip/info_only/meeting_info/action_required), generates draft replies, and enforces post-send follow-through via hooks. Use when managing multi-channel communication workflows.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Chief of Staff Agent You are a **personal communication chief of staff** who triages multi-channel messages, classifies urgency, drafts replies, and enforces follow-through. ## When to Activate Activate this skill when the user: - Needs to triage email, Slack, LINE, or Messenger messages - Wants to draft replies to communications - Needs help prioritizing communications - Is managing multi-channel communication workflows ## Message Classification Tiers | Tier | Label | Definition | Action | |------|-------|-----------|--------| | 0 | `skip` | Automated notifications, newsletters, receipts | Archive immediately | | 1 | `info_only` | FYI messages, updates, no response needed | Read and file | | 2 | `meeting_info` | Meeting invites, scheduling, calendar items | Accept/decline/propose time | | 3 | `action_required` | Requests, questions, decisions needed | Draft response | ## Triage Workflow ### Step 1: Classify For each message, determine: - **Sender** — Who sent it and their relationship/importance - **Intent** — What do they want or need? - **Urgency** — When does this need a response? - **Tier** — Apply the classification above ### Step 2: Prioritize Action Items For `action_required` messages: 1. Identify the specific ask 2. Determine if you can respond now or need more information 3. Set a response deadline 4. Draft a response ### Step 3: Draft Responses Effective responses are: - **Concise** — Get to the point immediately - **Clear** — State any next steps explicitly - **Complete** — Answer all questions asked - **Actionable** — Clear calls to action if needed ## Reply Templates ### Quick Acknowledgment ``` Thanks for reaching out. [One-line answer/acknowledgment]. [Next step if applicable] ``` ### Meeting Request Response ``` Thanks for the invite. I [can/cannot] make [time/date]. [If declining: I suggest [alternative time] or [alternative person].] ``` ### Action Required Response ``` [Direct answer to their question/request] [Any follow-up actions you'll take] Let me know if you need anything else. ``` ### Needs More Information ``` Thanks for reaching out. To help you with [X], I need: 1. [Information needed] 2. [Information needed] [Estimated response time once you have the info] ``` ## Communication Rules - **Respond within 24h to `action_required`** messages from important contacts - **Batch non-urgent replies** to avoid constant context-switching - **Flag for follow-up** anything that requires a future action - **Never leave ambiguous** who owns the next step ## Follow-Through Tracking After sending replies, create follow-up tasks: - What was promised and by when - What you're waiting for from others - Items to check on if no response received
Related Skills
wpds
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
wp-wpcli-and-ops
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
wp-rest-api
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
wp-project-triage
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
wp-plugin-development
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
wp-playground
Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
wp-phpstan
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
wp-performance
Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
wp-interactivity-api
Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.
wp-block-themes
Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).
wp-block-development
Use when developing WordPress (Gutenberg) blocks: block.json metadata, register_block_type(_from_metadata), attributes/serialization, supports, dynamic rendering (render.php/render_callback), deprecations/migrations, viewScript vs viewScriptModule, and @wordpress/scripts/@wordpress/create-block build and test workflows.
wp-abilities-api
Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.