Manage your team's Claude Code setup from one git repository: approve a skill, an MCP server, or a slash command onc...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Not hard to test, not trivial to unwind. Worth trying if it closes a sharp gap.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if TeamHandbook belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/AhmetErenLapanta/TeamHandbook && cd teamhandbook && cat README.mdRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf teamhandbookNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
./ └─ teamhandbook/ ← clones here
Manage your team's Claude Code setup from one git repository: approve a skill, an MCP server, or a slash command once, and every teammate's copy picks it up.
Source: GitHub repository
Source check: October 17, 2026
Upstream commit: October 17, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.