Run any Skill in Manus with one click

team-health-check

Name: Team Health Check
Author: mohitagw15856

Run a structured team health assessment. Use when asked to run a team health check, assess team morale, facilitate a team retrospective on ways of working, or evaluate team dynamics. Produces a health assessment across key dimensions with RAG status, underlying signals, and prioritised improvement actions.

Run Skill in Manus

Skill metadata

Stars929

Forks166

UpdatedMay 26, 2026 at 20:58

SKILL.md

readonly

More from this repository

same repository

aeo-optimizer

mohitagw15856/pm-claude-skills

Optimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.

2026-05-27929

thumbnail-creator

mohitagw15856/pm-claude-skills

Generate article or newsletter thumbnail candidates using the Gemini API from inside Claude Code. Claude reads article copy, proposes composition concepts, writes image generation prompts incorporating brand specs, calls Gemini to generate the images, evaluates the results via computer vision, and returns ranked candidates with rationale. Use when asked to create thumbnails, generate cover images, or produce visual candidates for an article or newsletter.

2026-05-27929

claude-superpowers

mohitagw15856/pm-claude-skills

Force Claude Code to work like a senior developer: plan before coding, work in isolation, write tests first, and review its own output twice before presenting it. Use when asked to enable superpowers mode, activate the superpowers framework, or turn on superpowers for this session. Installs a 4-stage framework — Plan, Isolate, Test First, Double Review — that prevents Claude from sprinting into broken code.

2026-05-27929

context-mode

mohitagw15856/pm-claude-skills

Activate output filtering, session logging, and auto-resume to keep Claude Code sessions running for hours without context bloat or memory loss. Use when asked to enable context mode, turn on long session mode, or activate session persistence. Installs a session log at project root, filters verbose command output before it enters context, and auto-resumes after Claude resets.

2026-05-27929

email-triage

mohitagw15856/pm-claude-skills

Reads your Gmail inbox for a configurable window (default: last 8 hours) and surfaces only what needs action — replies, decisions, or follow-up. Filters out receipts, notifications, newsletters, and anything that doesn't need you.

2026-05-27929

morning-intelligence

mohitagw15856/pm-claude-skills

Run a 15-question interview to capture your role, topics, sources, exclusions, and format preferences — then write a master prompt you can drop into a scheduled task or Claude Code Routine to get a personalised news brief every morning. Use when asked to set up a morning intelligence brief, build a morning news prompt, or create a personalised news briefing.

2026-05-27929

Source

mohitagw15856

mohitagw15856/pm-claude-skills

View GitHub Repository View Creator Repositories

Install

Download

Run Skill in Manus

Useful forSOC

Human Resources SpecialistsBusiness and Financial Operations Occupations13-1071L4

name	team-health-check
description	Run a structured team health assessment. Use when asked to run a team health check, assess team morale, facilitate a team retrospective on ways of working, or evaluate team dynamics. Produces a health assessment across key dimensions with RAG status, underlying signals, and prioritised improvement actions.

Team Health Check Skill

This skill produces a structured team health assessment inspired by Spotify's health check model and extended with engineering, product, and cross-functional team dimensions. Output can be used as a facilitation guide for a live session or as an async survey-and-report format.

Required Inputs

Ask the user for these if not provided:

Team name and function (engineering squad, product team, sales pod, etc.)
Team size and composition (how many people, what roles)
Format — facilitated live session or async survey + report?
Context — why are you running this now? (new team / ongoing ritual / post-incident / low morale signal)
Any known issues — anything the facilitator knows going in that will colour the results?

Output Structure

Team Health Check: [Team Name]

Date: [Date] Facilitated by: [Name or role] Team size: [X people] Format: [Live session (60 min) / Async survey + report] Cycle: [One-off / Quarterly / Monthly]

Part 1: Facilitation Guide (Live Session)

Use this guide to run the session in 60 minutes.

Session structure

Time	Activity	Owner
0–5 min	Framing and ground rules	Facilitator
5–40 min	Card voting — 7 dimensions, 5 min each	Full team
40–50 min	Top 3 themes discussion	Full team
50–58 min	Actions and owners	Team lead
58–60 min	Close and next date	Facilitator

Ground rules (read at start)

This is not a performance review — there are no wrong answers
We're assessing the team, not individuals — speak about "we" not "they"
What's said here stays here — results shared as aggregated themes, not attributed to individuals
The goal is one or two actionable improvements, not a long list

Voting mechanic

For each dimension, each team member votes with one of three cards:

🟢 Green — working well, we're proud of this
🟡 Amber — some things work, but there are issues worth discussing
🔴 Red — we have a real problem here that's slowing us down

After voting, the team discusses: what drove the votes? What would make this Green?

Part 2: Health Dimensions