From people-management
Triages Slack messages and emails by urgency and type for batch-responder managers, surfacing priorities without drafting replies. Use for morning sweeps or post-focus catch-ups.
npx claudepluginhub techwolf-ai/ai-first-toolkitThis skill uses the workspace's default tool permissions.
> **Principle: "You are responsible."** This skill surfaces and categorises. The manager decides what to act on and how.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
Principle: "You are responsible." This skill surfaces and categorises. The manager decides what to act on and how.
Scans unread Slack messages and recent emails, categorises them by urgency and type, and presents a prioritised overview.
If any MCP connector is unavailable, follow the connector unavailability protocol in ../../references/operating-principles.md.
Default: since the manager's last likely check-in (use calendar to estimate -- if they were in back-to-back meetings for 3 hours, scan those 3 hours).
If specified: use the provided time window.
If unclear, ask:
What time period should I triage? Options:
- Since this morning
- Last [N] hours
- Since yesterday
- Custom range
Read from manager-context/ (if available):
manager-profile.md -- to know who the direct reports are (their messages get higher priority)terminology.md -- to decode internal shorthand in messagesteam/ -- to understand team members' projects and responsibilitiessources.md -- to know which customer/project channels to monitorSearch for messages in the time window:
Priority channels (scan first):
Broader channels (scan for relevance):
For each message/thread, capture:
Search Gmail for messages in the time window:
For each email, capture:
Sort everything into these buckets:
🔴 Needs Your Decision
🟡 Team Member Needs
🔵 FYI / Context
🟢 Customer-Related (if applicable)
Read references/output-template.md for the full output template structure.
That's your triage for [time window]. Want me to:
- Dig deeper on any specific item?
- Prep context for responding to something?
- Run /plan-priorities to fold these into your day?
Read ../../references/operating-principles.md for shared operating principles (data scope, DM flagging, signals vs diagnoses, connector unavailability).
Additional notes specific to this skill: