Skip to content
Back to search

team-loop-kit

MarketplaceWorks with Claude CodeGitHub

Starter kit for a Claude team plugin that improves from its own use: the plugin, its feedback skills, the owner's review and a setup guide.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sevenevesai--claude-team-loop/badge.svg)](/listings/sevenevesai--claude-team-loop)

HTML

<a href="/listings/sevenevesai--claude-team-loop"><img src="/api/listings/sevenevesai--claude-team-loop/badge.svg" alt="findsafeskills safety rating" /></a>

Install

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 17 lines
  1. {
  2. "name": "team-loop-kit",
  3. "owner": {
  4. "name": "Your team"
  5. },
  6. "metadata": {
  7. "description": "Skills and working agreements a team shares across Claude chat, Cowork and Claude Code."
  8. },
  9. "plugins": [
  10. {
  11. "name": "team-loop",
  12. "source": "./plugins/team-loop",
  13. "description": "How the team works with Claude on any project: catching up, closing out, updates for any reader, project context, adapting skills to a project, finding skill ideas in your own history.",
  14. "category": "productivity"
  15. }
  16. ]
  17. }
README.md · README · 125 lines
  1. # Team loop
  2. A starter kit for a Claude team plugin that improves from its own use. Your colleagues work with
  3. the plugin, their own Claude reports what keeps recurring, and the owner's scheduled review turns
  4. those reports into the next version.
  5. ![The team learning loop: Work, Notice, Relay, Review and Release around the team plugin, and what the loop grows](writeup/img/the-loop.png)
  6. It is for whoever looks after Claude for a team on a Team or Enterprise plan, in any line of
  7. work. The kit holds a working plugin, the owner's review skill, the intake layout and a setup
  8. guide that a Claude Code session can follow with you. It comes from a setup in use at a
  9. consultancy; the article in [`writeup/`](writeup/writeup.md) tells that story in a page.
  10. ## What is in the kit
  11. | Part | What it is | For |
  12. |---|---|---|
  13. | [`plugins/team-loop/`](plugins/team-loop/) | a plugin with six skills, working agreements and a session-start hook | every member, in chat, Cowork and Claude Code |
  14. | [`.claude/skills/review-findings/`](.claude/skills/review-findings/SKILL.md) | the review that merges what the team sent in and drafts the changes | the owner, by hand or on a schedule |
  15. | [`docs/setup.md`](docs/setup.md) | eight steps from copying the kit to the owner's morning routine | the owner and their Claude |
  16. | [`docs/how-it-works.md`](docs/how-it-works.md) | the design, the reason for each decision, the platform facts it rests on | anyone adapting it |
  17. | [`docs/backlog.md`](docs/backlog.md) | where evidence and candidates accumulate | the review and the owner |
  18. | [`tools/`](tools/) | build the upload zip; print the plugin catalogue for the intake sheet | releasing |
  19. | [`writeup/`](writeup/) | the article and three visuals | explaining it to others |
  20. ## The plugin's skills
  21. | Skill | Someone says | It does |
  22. |---|---|---|
  23. | [`catch-up`](plugins/team-loop/skills/catch-up/SKILL.md) | "pick up where we left off" | reads the project's records, checks them against the live state, reports where things stand |
  24. | [`close-out`](plugins/team-loop/skills/close-out/SKILL.md) | "wrap up" | updates the change record and context file, notes a win when one is mentioned, leaves a handoff |
  25. | [`setup-project-context`](plugins/team-loop/skills/setup-project-context/SKILL.md) | "set up Claude for this project" | creates the context file and change record every later session starts from |
  26. | [`write-update`](plugins/team-loop/skills/write-update/SKILL.md) | "write an update for the customer" | drafts a short message from verified facts and shows it before anything is sent |
  27. | [`adapt-skill`](plugins/team-loop/skills/adapt-skill/SKILL.md) | "here we do it differently", "the skill got this wrong" | records a project override that survives updates, and drafts a note for the owner |
  28. | [`ideas`](plugins/team-loop/skills/ideas/SKILL.md) | "find skill ideas" | reads the person's own Claude history, compares it with the team's plugins, writes a findings report |
  29. The first four are the daily work. The last two are the loop: they are how use turns into
  30. evidence. Every skill reads a project's `.claude/team-overrides.md` before it starts, and a step
  31. marked `Gate:` waits for the person whatever an override says.
  32. ## Try it
  33. In Claude Code:
  34. ```
  35. claude plugin marketplace add sevenevesai/claude-team-loop
  36. claude plugin install team-loop@team-loop-kit
  37. ```
  38. Start a new session and ask it to "find skill ideas". It tells you what it will read, scans your
  39. own session history on your computer, and shows you a report. Nothing is sent anywhere: the kit's
  40. intake link is not set, so the report stays a local file.
  41. A plugin's skills and hooks run with your session's permissions. Read
  42. [`hooks/hooks.json`](plugins/team-loop/hooks/hooks.json) and the skills before installing, as
  43. with any plugin.
  44. ## Set it up for your team
  45. Trying the plugin shows one station. The loop needs your own copy, because the plugin has to
  46. carry your team's agreements and point at your team's intake.
  47. 1. Create a private repository from this one.
  48. 2. Rename the `team` prefix and write in your own working agreements and gates.
  49. 3. Create the intake sheet and paste its link into the plugin.
  50. 4. Trial a skill, then publish the plugin to your organisation.
  51. 5. Tell the team three sentences.
  52. 6. Schedule the review.
  53. [`docs/setup.md`](docs/setup.md) has each step with its success signal. Or open your copy in
  54. Claude Code and say:
  55. > Read CLAUDE.md and docs/setup.md, ask me the opening questions, then set this up for my team.
  56. ## How the loop works
  57. ![What stays on each person's machine, what travels to the shared sheet, and what comes back](writeup/img/what-travels.png)
  58. The owner never sees a transcript. `ideas` runs in each member's own session, codes their history
  59. into task types and counts, and writes a report with no names, ids or copied text. The member
  60. reads it and approves it, and only then does it reach the shared sheet. The owner's review
  61. answers every row with a status, so people see what became of what they sent.
  62. ![Eight sticky notes with things people say while working, each stamped with the upgrade it becomes](writeup/img/signals-to-upgrades.png)
  63. A finding has a kind, and the kind says where it lands. Three kinds improve skills. Three
  64. tighten guardrails: working agreements, gates, hooks. Two point beyond the plugin, at a
  65. connector or at a shared artifact, template or service. The reasons behind each choice are in
  66. [`docs/how-it-works.md`](docs/how-it-works.md).
  67. ## For AI agents
  68. - Start with [`CLAUDE.md`](CLAUDE.md): layout, commands with their success signals, invariants.
  69. - To set the kit up for someone, follow [`docs/setup.md`](docs/setup.md) in order. Ask its five
  70. opening questions first; they are the person's decisions.
  71. - `claude plugin validate . --strict` and `claude plugin validate plugins/team-loop --strict`
  72. print "Validation passed" and exit 0.
  73. - `python tools/package-plugins.py team-loop` prints the zip path, file count and size, and exits
  74. 1 when that version already has a zip.
  75. - `python tools/plugin-catalogue.py --published team-loop` prints a JSON array of rows, header
  76. first, for the sheet's Plugins tab.
  77. - The report format and the sheet's columns are in
  78. [`report-format.md`](plugins/team-loop/skills/ideas/references/report-format.md) and
  79. [`intake.md`](plugins/team-loop/skills/ideas/references/intake.md).
  80. ## Status
  81. - The plugin is a generic port of a plugin set in use on a Claude Team plan. The port passes
  82. both validate commands. Its skills have not been trialled again since the port, so give each
  83. one a trial (setup step 4) before you publish your copy.
  84. - `review-findings` is new in this kit. It has not yet run on a schedule.
  85. - What was not verified, such as a member's Claude writing to a sheet someone else owns, is
  86. listed at the end of [`docs/how-it-works.md`](docs/how-it-works.md). Each has a fallback.
  87. ## Layout
  88. ```
  89. .claude-plugin/marketplace.json lists the plugins
  90. plugins/team-loop/ the plugin: skills, context, hooks
  91. .claude/skills/review-findings/ the owner's review skill
  92. .claude/rules/plugin-authoring.md the standard for plugin skills
  93. docs/ setup, design, backlog
  94. tools/ packaging and catalogue scripts
  95. writeup/ the article and visuals
  96. ```

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.