From people-management
Analyzes team dynamics, engagement, wellbeing, performance, and growth signals for direct reports from Slack, Calendar, and Notion/Drive. Surfaces patterns like overdue 1:1s and support needs with reflection prompts.
npx claudepluginhub techwolf-ai/ai-first-toolkitThis skill uses the workspace's default tool permissions.
> **Two lenses, always.** "Development" asks: is this person growing and performing? "Wellbeing" asks: is this person thriving, connected, and energised? Great managers hold both.
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.
Two lenses, always. "Development" asks: is this person growing and performing? "Wellbeing" asks: is this person thriving, connected, and energised? Great managers hold both.
A periodic overview of team dynamics, engagement signals, wellbeing, and development trajectory across all direct reports.
If any MCP connector is unavailable, follow the connector unavailability protocol in ../../references/operating-principles.md.
Read from manager-context/:
manager-profile.md -- full list of direct reportsteam/ -- individual profiles with goals, projects, last review datessources.md -- channels and data locations per team memberIf context is missing, note it and work with available sources.
For each direct report, gather data from the last 14 days (or since last health check):
Activity & Engagement (Slack):
1:1 Cadence (Calendar):
Development Goals (Notion/Drive):
Workload Signals (Calendar + Slack):
Wellbeing & Connection Signals (Slack + Calendar):
For each team member, produce a brief profile covering both lenses:
### [Name] -- [Role]
**๐ฏ Development & Performance:**
**Activity:** [Normal / Increased / Decreased] -- [1-line evidence]
**Recent wins:** [list any, or "None surfaced"]
**Goals:** [last updated date] -- [current / stale]
**Development focus:** [area from goals] -- [evidence of progress / no visible progress]
**Growth signals:** [scope expansion, new skills, leadership behaviours -- or "None"]
**๐ซ Wellbeing & Connection:**
**Energy:** [Balanced / High output / Signs of overwork] -- [evidence, e.g., "messages after 22:00 on 3 nights"]
**Connection:** [Active in social channels / Quiet / Only work-related activity]
**Celebrated/been celebrated:** [yes -- details / not recently]
**Tone:** [Positive / Neutral / Worth checking in] -- [soft signal only]
**Last 1:1:** [date] -- [on track / overdue]
**Signals to explore:** [friction, blockers, wellbeing patterns -- or "None"]
Look across the team for patterns in both dimensions:
๐ฏ Development & Performance patterns:
๐ซ Wellbeing & Connection patterns:
Read references/output-template.md for the full output template structure.
Here's your team health check. These are signals for your reflection -- you know your people better than any tool.
Want me to prep a 1:1 for anyone specific?
Spawn a sub-agent to review the health check with fresh eyes. The reviewer should:
Incorporate the reviewer's feedback before presenting the final health check to the manager.
Read ../../references/operating-principles.md for shared operating principles (data scope, DM flagging, signals vs diagnoses, connector unavailability).
Additional notes specific to this skill: