One skill registry for your whole team, in every AI coding agent, always up to date.
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.
You can test this quickly and remove it cleanly if it misses.
GitHub health unknown. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Multiple
Model
Multiple
Fastest way to find out if skillcrew 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/yoanbernabeu/skillcrew ~/.claude/skills/skillcrewRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/skills/skillcrewNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ skills/ │ └─ skillcrew/ ← installs here ├─ agents/ └─ settings.json
One skill registry for your whole team, in every AI coding agent, always up to date.
Source: GitHub repository
Source check: October 14, 2026
Upstream commit: October 13, 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.