Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
Runs a structured team health assessment across key dimensions.
Install Team Health Check
$ npx skills add mohitagw15856/pm-claude-skills --skill team-health-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills team-health-check --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/team-health-check .claude/skills/team-health-check && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "team-health-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/team-health-check into .claude/skills/team-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-health-check", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/team-health-checkType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill team-health-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills team-health-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/team-health-check .agents/skills/team-health-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "team-health-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/team-health-check into .agents/skills/team-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-health-check", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill team-health-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills team-health-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/team-health-check .cursor/skills/team-health-check && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "team-health-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/team-health-check into .cursor/skills/team-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-health-check", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/team-health-check--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill team-health-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills team-health-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/team-health-check .gemini/skills/team-health-check && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "team-health-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/team-health-check into .gemini/skills/team-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-health-check", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills team-health-checkInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill team-health-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/team-health-check .github/skills/team-health-check && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "team-health-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/team-health-check into .github/skills/team-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-health-check", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill team-health-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills team-health-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/team-health-check .opencode/skills/team-health-check && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "team-health-check" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/team-health-check into .opencode/skills/team-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-health-check", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
team-health-check- GitHub stars
- 1.4k
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,370 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Runs a structured team health assessment across key dimensions.
- Works in 2 steps: [...] → [...]
- Asked to run a team health check
- SKILL.md covers Required Inputs, Output Structure, Part 1: Facilitation Guide… and Part 2: Health Dimensions, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Team Health Check is an agent skill from mohitagw15856/pm-claude-skills. Runs a structured team health assessment across key dimensions. Use when asked to run a team health check, assess team morale, facilitate a retrospective on ways of working, or evaluate team dynamics. Produces a health assessment with RAG status per dimension, underlying signals, and prioritised improvement actions with named owners.
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Retrospectives and Retrieval-augmented generation. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to run a team health check
- Assess team morale
- Facilitate a retrospective on ways of working
- Evaluate team dynamics
Example prompts
- “/team-health-check”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- [...]
- [...]
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Team Health Check loads about 2.6k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 1,370 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 1,370 words, ~2,555 tokens.
Download SKILL.mdSave it as
.claude/skills/team-health-check/SKILL.md (or your agent's skills folder).- name
- team-health-check
- description
- Runs a structured team health assessment across key dimensions. Use when asked to run a team health check, assess team morale, facilitate a retrospective on ways of working, or evaluate team dynamics. Produces a health assessment with RAG status per dimension, underlying signals, and prioritised improvement actions with named owners.
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
Dimension 1: Delivering Value
Are we shipping things that matter, at the pace we should?
| Indicator | Probes for discussion |
|---|---|
| We ship work that creates real value for our users | How do we know our output is valuable? When did we last talk to a user? |
| Our pace of delivery feels healthy and sustainable | Are we consistently shipping? Or do we have long dry spells? |
| We have clarity on what "done" looks like | Do we have a shared definition of ready and done? |
| We celebrate shipping, not just building | Do we acknowledge completed work, or does it just disappear into the backlog? |
Current vote: 🟢 / 🟡 / 🔴
Key themes from discussion:
What would make this Green?
Dimension 2: Easy to Release
Is releasing software (or our work) smooth and low-risk?
| Indicator | Probes for discussion |
|---|---|
| We can release whenever we choose, without anxiety | What does a release feel like? Smooth or stressful? |
| Our deployment process is automated and reliable | How much manual work does a release involve? |
| We have confidence in our test coverage | Do we catch bugs before users do? |
| Rollback is fast and rehearsed | Have we ever rolled back? How long did it take? |
Current vote: 🟢 / 🟡 / 🔴
Key themes from discussion:
What would make this Green?
Dimension 3: Fun & Morale
Do people enjoy working here and with each other?
| Indicator | Probes for discussion |
|---|---|
| People generally enjoy coming to work | If you had to describe the team energy in one word, what would it be? |
| We celebrate successes as a team | When did we last properly celebrate something? |
| Interpersonal dynamics are healthy — no drama or cliques | Are there any relationships that are strained or avoided? |
| We laugh and have non-work conversations | Do we know each other as people, not just colleagues? |
Current vote: 🟢 / 🟡 / 🔴
Key themes from discussion:
What would make this Green?
Dimension 4: Psychological Safety
Can people speak up, take risks, and make mistakes without fear?
| Indicator | Probes for discussion |
|---|---|
| People raise concerns without worrying about the consequences | When did someone last raise a concern publicly? What happened? |
| Mistakes are treated as learning opportunities, not blame events | Think of the last mistake on the team. How was it handled? |
| People challenge each other's ideas in a constructive way | Do we have real debates, or do we agree in the room and disagree in the corridor? |
| Everyone's voice feels equally heard regardless of seniority | Do the same people always speak first and longest? |
Current vote: 🟢 / 🟡 / 🔴
Key themes from discussion:
What would make this Green?
Dimension 5: Speed & Feedback Loops
Do we learn fast and adjust quickly?
| Indicator | Probes for discussion |
|---|---|
| We get feedback on our work quickly (from users, data, tests) | How long after shipping do we know if something worked? |
| Our planning and retrospective cycles help us improve | Do retros lead to real change, or do the same issues come back? |
| We cut work that isn't working, even when it's hard | Can you name something we've stopped doing because it wasn't working? |
| Our meetings and processes don't slow us down | Which meetings do people dread? Which do they find valuable? |
Current vote: 🟢 / 🟡 / 🔴
Key themes from discussion:
What would make this Green?
Show full SKILL.md (537 more words)Show less
Dimension 6: Mission & Purpose
Do we understand why our work matters?
| Indicator | Probes for discussion |
|---|---|
| Everyone on the team can articulate why their work matters | Could each person on this team explain to a stranger why their work is important? |
| The team's goals are clear and shared | Can everyone name the team's top 3 priorities right now? |
| Our work connects to the wider company direction | Do we understand how we fit into the bigger picture? |
| We're proud of what this team builds | If you described your team's work to someone you respect, would you feel good about it? |
Current vote: 🟢 / 🟡 / 🔴
Key themes from discussion:
What would make this Green?
Dimension 7: Collaboration & Support
Do we work well together and support each other?
| Indicator | Probes for discussion |
|---|---|
| People actively help each other when someone is stuck | Think of the last time someone was blocked — what happened? |
| Knowledge is shared openly — no information silos | Is there any knowledge that only one person holds? What's the risk? |
| Cross-team collaboration is smooth and low-friction | Which team is hardest to collaborate with and why? |
| People feel supported when they're struggling | Is there psychological safety to say "I'm struggling with this"? |
Current vote: 🟢 / 🟡 / 🔴
Key themes from discussion:
What would make this Green?
Part 3: Health Summary & Report
Use this template to document results after the session or survey.
RAG Summary Dashboard
| Dimension | Score | Status | Trend vs last quarter |
|---|---|---|---|
| Delivering Value | [X/5] | 🟢 / 🟡 / 🔴 | [↑ / → / ↓] |
| Easy to Release | [X/5] | 🟢 / 🟡 / 🔴 | [...] |
| Fun & Morale | [X/5] | 🟢 / 🟡 / 🔴 | [...] |
| Psychological Safety | [X/5] | 🟢 / 🟡 / 🔴 | [...] |
| Speed & Feedback Loops | [X/5] | 🟢 / 🟡 / 🔴 | [...] |
| Mission & Purpose | [X/5] | 🟢 / 🟡 / 🔴 | [...] |
| Collaboration & Support | [X/5] | 🟢 / 🟡 / 🔴 | [...] |
| Overall | [X/5] | 🟢 / 🟡 / 🔴 | [↑ / → / ↓] |
Top Themes
What's working well (keep doing):
- [...]
- [...]
What needs attention (most important to fix):
- [Most pressing issue — specific, with evidence from the session]
- [Second issue]
- [Third issue — if applicable]
Action Plan
| Action | Owner | Due date | Success indicator |
|---|---|---|---|
| [Specific action — e.g. Introduce pairing Fridays for knowledge sharing] | [Team lead / individual] | [Date] | [How will we know it worked?] |
| [...] | [...] | [...] | [...] |
Next health check: [Date — recommended 6–8 weeks for teams with active improvement actions, 13 weeks for steady-state teams]
Quality Checks
- Session ground rules established psychological safety before voting started
- Each dimension had open discussion, not just a vote
- Actions are specific enough to be verifiably done — no vague commitments like "improve communication"
- Each action has a single owner — not "the team"
- Results are shared with the team, not kept by management
- Trend data is tracked across cycles to show improvement or regression
Anti-Patterns
- Do not run a health check without first establishing psychological safety — without it, scores reflect fear, not reality
- Do not treat a single health check as a trend — one data point cannot show improvement or regression
- Do not keep results with management without sharing them with the team — transparency is a prerequisite for trust
- Do not generate action items that are vague commitments like "improve communication" — every action must be specific and verifiable
- Do not assign actions to "the team" — each improvement action needs a single named owner
Example Trigger Phrases
- "Run a team health check for my engineering squad"
- "Facilitate a team health assessment — we've had some morale issues"
- "Build a team health check survey for my product team"
- "Generate a Spotify-style health check for our cross-functional pod"
- "Create a quarterly team health check template"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/team-health-check of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Team Health Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Team Health Check this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Weekly Engineering Retrogarrytan/gstack | 136k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Dough Execute Planterryyin/lizard | 2.5k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Oral Paper SkillAdkid-Zephyr/oral-paper-skill | 357 | — | ~1.9k | Automated safety check: Pass | None | |
| Deck Retroasheshgoplani/agent-deck | 1.1k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Dough Execution Retrospectiveterryyin/lizard | 2.5k | — | ~4k | Automated safety check: Pass | Custom licence |
Similar skills
Dough Execute Plan
terryyin/lizard
Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…
Oral Paper Skill
Adkid-Zephyr/oral-paper-skill
Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.
Deck Retro
asheshgoplani/agent-deck
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs.
Dough Execution Retrospective
terryyin/lizard
Reviews planned, completed planless quick, or quick-to-planned execution against original intent, aggregate commits, current whole-product architecture, and tests, including after cleanup.
Criticism Self Criticism
HughYau/qiushi-skill
批评与自我批评：在工作完成、阶段验收、收到批评或同类错误反复出现时，对成果和过程做诚实、具体、基于事实的审视，输出可执行的改进项，并处理外来批评而不辩解。触发信号包括 review、复盘、审查、"帮我看看有没有问题"、"你确定吗"；任务刚开始或只是单步查询时不触发。
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Questions about Team Health Check
What does Team Health Check do?
Runs a structured team health assessment across key dimensions. Team Health Check is an agent skill from mohitagw15856/pm-claude-skills. Runs a structured team health assessment across key dimensions.
When should I use Team Health Check?
Team Health Check fits situations like: asked to run a team health check; assess team morale; facilitate a retrospective on ways of working; evaluate team dynamics.
How do I install Team Health Check in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill team-health-check -a claude-code`. Or copy the skill folder (skills/team-health-check in mohitagw15856/pm-claude-skills) into .claude/skills/team-health-check in your project. Claude Code loads it when a task matches its description.
How do I install Team Health Check in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill team-health-check -a codex`. Or copy the skill folder (skills/team-health-check in mohitagw15856/pm-claude-skills) into .agents/skills/team-health-check in your project. Codex loads it when a task matches its description.
Can I use Team Health Check in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill team-health-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-health-check, .gemini/skills/team-health-check, .github/skills/team-health-check and .opencode/skills/team-health-check in your project.
What does Team Health Check need to run?
SKILL.md names no scripts, command-line tools or credentials: Team Health Check is instructions for the agent only.
Does Team Health Check access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Team Health Check safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Team Health Check use?
Team Health Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Team Health Check use?
About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Team Health Check?
Skills that share tags, products or a category with Team Health Check: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.5k stars), Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 357 stars) and Deck Retro (asheshgoplani/agent-deck, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Team Health Check?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.