AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
MCP verified MIT Self-run

Teamretro Skills

mcp-teamretrohq-teamretro-skills · by TeamRetroHQ

AI session retrospectives — skills and prompts that let your AI agents bring their feedback to your retro

↗ Website ↗ Repository
— No reviews yet
0 installs
3 views
0.0% view→install

Install

$ agentstack add mcp-teamretrohq-teamretro-skills

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Teamretro Skills? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

teamretro-skills

Skills for teams whose AI agents do real work — and should have a voice in how the team improves.

Your AI agents work inside your repos every day. They hit the missing docs, the stale guides, the tech debt, the unclear briefs — and when the session ends, all of that evaporates. These skills close the loop: the agent captures its own feedback at the end of a session, and brings it to your team's retrospective.

None of these skills require TeamRetro. The practice works with a markdown log in any repo and any retro process. If your team does use TeamRetro, the agent can additionally file its findings straight into your next retro via the TeamRetro MCP server.

Two ways to use it

Scenario 1 — no TeamRetro needed (the full practice, free):

| Skill | What it does | |---|---| | [ai-session-retro](skills/ai-session-retro/SKILL.md) | At the end of a working session, the agent logs an honest, evidence-cited retro entry: what went well, what caused friction (with a root-cause label and a concrete fix), what it guessed at, and the one fix worth doing first. | | [ai-retro-brief](skills/ai-retro-brief/SKILL.md) | Reads the accumulated entries and prepares a one-page summary you bring to your retro however you run it: recurring friction ranked by frequency × cost, whether past fixes stuck, top 3 recommended actions. |

Scenario 2 — with TeamRetro (the AI posts its recommendations itself) · Beta:

| Skill | What it does | |---|---| | [ai-session-retro](skills/ai-session-retro/SKILL.md) | Same as above — the logging habit is identical. | | [teamretro-post-recommendations](skills/teamretro-post-recommendations/SKILL.md) · Beta | Prepares the AI's recommendations from the log and, with your consent, posts them into TeamRetro via its MCP server — parked items for your next retro, actions when owner-named, or ideas contributed straight onto a running retro board. [AI retro] attribution, consent per write, idempotent. |

> Beta: teamretro-post-recommendations depends on the TeamRetro MCP server and is still being hardened. Scenario 1 is the stable, fully-supported practice; try Scenario 2 and tell us what breaks at feedback.teamretro.com.

Planned: TeamRetro MCP skills for prepping retros from recent team activity and running a lightweight standup. Watch this repo.

Install

One command, any agent (Claude Code, Cursor, Codex, Copilot, Amp, Cline, and more) — from your repo root:

npx skills add TeamRetroHQ/teamretro-skills

Claude Code plugin — installs the skill set and keeps it updated:

/plugin marketplace add TeamRetroHQ/teamretro-skills
/plugin install teamretro-skills@teamretro

Manual copy — a skill is just a folder; copy it into your repo's .claude/skills/ (or ~/.claude/skills/ for all projects):

mkdir -p .claude/skills
cp -r skills/ai-session-retro skills/ai-retro-brief .claude/skills/

No skill support at all? Use the [prompt pack](prompt-pack/) — the same practice as a plain prompt + template.

How it works

  1. At the end of a substantial AI session, say "run a retro on this session." (~1 minute; you sanity-check the entry before it's final.)
  2. Entries accumulate in docs/ai-retros/entries/, one markdown file each, committed to the repo. Every friction item carries one of ten fixed root-cause labels and a ticket-sized fix.
  3. Before your team retro, ask for a brief: "synthesize our AI retros." The agent brings one page of ranked, evidence-backed patterns to the meeting.

Two rules keep the log useful: no finding without a proposed fix, and the honesty runs both ways — the agent reports what the repo and the briefs made hard, and its own mistakes.

See [examples/](examples/) for a sample entry and brief.

Status

  • ai-session-retro, ai-retro-brief — v1.2, the stable launch set. Account-free, no TeamRetro dependency. Eval definitions are in skills/*/evals/; the v1.2 eval run is in progress.
  • teamretro-post-recommendations — v0.2, beta. Its TeamRetro MCP tool contract is verified against the API (create_parked_item, create_action, create_retrospective_idea, list_teams, list_retrospectives, get_retrospective all ship and are un-gated), but the end-to-end flow is still being hardened against staging.

Feedback and ideas welcome at feedback.teamretro.com.

License

[MIT](LICENSE)

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Integrations