My working Claude Code setup: output styles, hooks, skills, agents
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
Claude Code
Model
Claude
Fastest way to find out if claude-code-flow 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/kaisa-kucherenko/claude-code-flow ~/.claude/skills/claude-code-flowRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/skills/claude-code-flowNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ skills/ │ └─ claude-code-flow/ ← installs here ├─ agents/ └─ settings.json
My working Claude Code setup: output styles, hooks, skills, agents
Source: GitHub repository
Source check: October 15, 2026
Upstream commit: October 14, 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.