skills.rest
manager-dot-dev
manager-dot-devOFFICIAL
Explore all skills by this author →
GitHub

team-health

Diagnose team health and provide interventions for morale and engagement.

104|7|Updated Apr 10, 2026
Search Tags:#engagement#team-health#retrospectives#burnout#psychological-safety#morale#team-activities
One-click install
npx skills add https://github.com/manager-dot-dev/manager-skills --skill team-health-manager-dot-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-health
Source: https://github.com/manager-dot-dev/manager-skills/tree/main/skills/team-health
Command: npx skills add https://github.com/manager-dot-dev/manager-skills --skill team-health-manager-dot-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps engineering managers diagnose and improve overall team health by focusing on morale, psychological safety, cohesion, delivery culture, and engagement. It turns vague signals like "something feels off" or "burnout" into a structured diagnosis and concrete next steps so managers can stabilize and restore team performance.

Core Features & Use Cases

  • Diagnostic frameworks: Google's 5 Factors (Project Aristotle), a four-state Team Health diagnosis (Falling Behind / Treading Water / Repaying Debt / Innovating), the Engagement Stack, Trust Battery, and a 5-zone intensity model for pacing work.
  • Actionable interventions: Immediate stabilizers, structural interventions (meeting and ritual changes, recovery planning, transparency practices), blameless postmortem guidance, and tailored activity ideas for focus days and team meetings.
  • Resources & examples: A library of team activities organized by driver (Growth / Connection / Impact) and source references for deeper reading; guidance on when to use related skills (1:1s, feedback, hiring, motivation).
  • Use cases: Run a quick health read before a retro, design a focus day agenda, diagnose burnout vs. visibility problems, plan recovery after an intense launch, or run a blameless postmortem.

Quick Start

Ask the skill to diagnose a team showing low morale and missed commitments and provide a concise likely diagnosis, one immediate stabilizer to do this week, and a two-step structural intervention to implement next sprint.

Frequently Asked Questions about team-health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose team burnout and low morale in an engineering team?▼

Diagnose team burnout and low morale using structured frameworks like Google's 5 Factors, a four-state Team Health diagnosis, and a 5-zone intensity model to turn vague signals into concrete structural interventions.

What is the best way to run a blameless postmortem after a stressful launch?▼

Run a blameless postmortem using provided guidance to focus on systemic delivery culture issues rather than individual errors, applying recovery planning and transparency practices to restore team cohesion.

How can I improve psychological safety and team engagement for software engineers?▼

Improve psychological safety and team engagement by applying diagnostic frameworks like the Trust Battery and Engagement Stack, paired with actionable stabilizers and tailored team activities.

What are immediate stabilizers I can apply this week to fix missed commitments and slow delivery?▼

Apply immediate stabilizers to fix missed commitments by diagnosing whether the team is falling behind or treading water, then adjusting meeting rituals and implementing structural interventions next sprint.

How do I plan a team offsite or focus day agenda to boost connection and morale?▼

Plan a team offsite or focus day agenda using a library of team activities organized by growth, connection, and impact drivers to directly boost morale and team cohesion.

When should I use team health diagnostics versus 1:1s or feedback skills?▼

Use team health diagnostics to assess overall morale, cohesion, and delivery culture across the group, whereas 1:1s and feedback skills target individual performance and communication.

Related Skills

Explore More Software Engineering Skills→
tenequmtenequm
32

impactful-writing

Edit writing for clarity, engagement, and persuasiveness across platforms.

Community
Basic
HmbownHmbown
105

animal-handling

Stabilize temperamental systems with triage, pacing, and escalation signals.

Community
Intermediate
JoelLewisJoelLewis
4

feedback-coach

Guide performance feedback conversations using HHIPP criteria and Radical Candor.

Community
Intermediate
legioncodeinclegioncodeinc
72

retrospective-stinger

Convert team feedback sessions into structured behavior-change workflows.

Official
Advanced