Back to search
team-tools
MarketplaceWorks with Claude CodeGitHub
Plugins for the satellite telemetry team
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
Markdown
[](/listings/alexanderbezrukov--team-tools)HTML
<a href="/listings/alexanderbezrukov--team-tools"><img src="/api/listings/alexanderbezrukov--team-tools/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
cd ~/team-tools scripts/check_setup.sh # tools, sign-in and the 25 tests; says what to fix scripts/setup_demo.sh ~/team-demo # demo repo + local origin + scratch repo claude plugin marketplace add "$PWD" # or the GitLab URL of this repository claude plugin install team-kit@team-tools
Then follow `DEMO_SCRIPT.md`.
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 · 12 lines
- {
- "name": "team-tools",
- "description": "Plugins for the satellite telemetry team",
- "owner": {"name": "Engineering team"},
- "plugins": [
- {
- "name": "team-kit",
- "source": "./plugins/team-kit",
- "description": "Merge-request and extract-skills skills, MR reviewer subagent, git guard hook, team-docs MCP server"
- }
- ]
- }
README.md · README · 86 lines
- # team-tools: a plugin marketplace for an engineering team
- Demo kit for the talk "Skills, MCP and plugins for engineers". The repository is itself a
- Claude Code plugin marketplace: push it to your GitLab and every teammate installs the team
- plugin with two commands.
- **New computer, or Windows?** Start with `SETUP.md`: installation on Windows 10/11 (native or WSL),
- Linux and macOS, and `scripts/check_setup.sh`, which checks the computer and says what to fix.
- ```text
- .claude-plugin/marketplace.json marketplace "team-tools" with one plugin
- plugins/team-kit/ the team plugin (see its README)
- .claude-plugin/plugin.json Claude Code manifest
- plugin.json Agent Plugins 1.0 manifest (VS Code/Copilot, Codex, Cursor, ...)
- skills/merge-request/ skill + check_mr.py + MR template
- skills/extract-skills/ skill + session_stats.py ("don't repeat context")
- agents/mr-reviewer.md review subagent on a small model
- hooks/hooks.json, guard_git.py blocks pushes to main, force pushes, commits on main, skipped hooks (Bash + PowerShell)
- servers/team_docs.py MCP server over the project's docs/
- .mcp.json, mcp.json MCP config for Claude Code and for Agent Plugins clients
- sample-project/ small telemetry repo: code, tests, docs/, tickets/, AGENTS.md
- examples/
- project-settings.json .claude/settings.json: team marketplace, plugin, permissions
- project.mcp.json .mcp.json: official GitLab and Atlassian MCP servers
- gitlab-ci.yml Claude Code in GitLab CI/CD (API key, cloud provider or setup-token)
- extract-skills-output/ what extract-skills produced on a real demo session
- scripts/check_setup.sh checks git, Python, uv, Claude Code, sign-in, and runs the tests
- scripts/setup_demo.sh fresh demo repo with a local origin, plus a scratch repo
- tests/test_kit.py scripts, hook, MCP server, manifests (no LLM needed)
- SETUP.md installing everything on Windows (native or WSL), Linux and macOS
- DEMO_SCRIPT.md the live demo, act by act
- ```
- ## Quick start
- ```bash
- cd ~/team-tools
- scripts/check_setup.sh # tools, sign-in and the 25 tests; says what to fix
- scripts/setup_demo.sh ~/team-demo # demo repo + local origin + scratch repo
- claude plugin marketplace add "$PWD" # or the GitLab URL of this repository
- claude plugin install team-kit@team-tools
- ```
- Then follow `DEMO_SCRIPT.md`.
- ## For a real team
- 1. Push this repository to GitLab as `team-tools`.
- 2. Copy `examples/project-settings.json` to `.claude/settings.json` in each project repository and
- set the marketplace URL. When a teammate trusts the folder, Claude Code adds the marketplace and
- enables `team-kit`. Add `.mr/` (the merge-request skill's output) to the project's `.gitignore`.
- 3. Copy `examples/project.mcp.json` to `.mcp.json` for GitLab and Jira/Confluence. Slack:
- `claude plugin install slack`. Teams: the Microsoft 365 connector in the Claude app.
- 4. Protect `main` in GitLab (protected branch, merge request required, approvals, CI). The hook is a
- client-side safety net for agents; the server rule is the guarantee for everyone.
- 5. Change the skills, docs and checks to your team's rules. Bump `version` in both manifests;
- teammates get it with `claude plugin update`, or automatically once auto-update is on for the
- marketplace (off by default for your own marketplaces).
- 6. VS Code, Codex, Cursor: install the `plugins/team-kit` folder. Set `TEAM_DOCS_DIR` to the
- project's docs folder (absolute path) in the environment the editor starts with: Agent Plugins
- 1.0 has no variable for the project folder, and without it `team-docs` reports that the folder
- is missing.
- ## Tested with
- Claude Code 2.1.326 on a subscription (17 Nov 2026): `claude plugin validate` passes for the plugin
- and the marketplace; `tests/test_kit.py` passes on Python 3.9, 3.11 and 3.13, including over 120
- command forms for the git guard (bypass attempts it must block, everyday commands it must allow);
- in a live session the hook blocked a commit and push on `main` and let a feature-branch commit and
- push through; the plugin installs from the local marketplace; `team-docs` connects through
- the plugin; an agent implemented SAT-142, `merge-request` returned READY (8 checks) and wrote the
- MR description; in a repository without rules the hook blocked a commit and push on `main`;
- `extract-skills` proposed an `implement-ticket` skill with a script and a `protect-main` hook
- (output in `examples/extract-skills-output/`). Python 3.13, mcp 2.3.0, uv 0.11.
- The Agent Plugins manifest follows the published 1.0 schema; it was not run in VS Code or Codex here.
- Native Windows (18 Nov 2026, Windows 11, Git Bash from Git for Windows 2.56, uv 0.13.6, Python 3.15
- from uv): the 25 tests pass, including the PowerShell and Windows-path cases for the git guard,
- raw UTF-8 input with UTF-8 mode off (as on Python 3.13), and the `hooks.json` command started
- through Bash; the symlink test is skipped without Developer Mode. The guard's test lists now hold
- about 270 command forms, including every bypass and false block found by three independent reviews
- before publication. Live (after the first review's fixes, before the second's), with Claude Code
- 2.1.327 and the plugin installed from the local marketplace: in the scratch repository the hook blocked a commit on `main` through the Bash tool
- and through the PowerShell tool and an Edit of `.git/config`, and let a branch + commit
- (PowerShell, here-string message) and a feature-branch push (Bash) through.
- Not yet run: the Linux/macOS suite after the Windows changes.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.