{"id":"rorogogogo-claude-cracks-the-whip","name":"claude-cracks-the-whip","homepage":null,"repo_url":"https://github.com/Rorogogogo/claude-cracks-the-whip","category":"devtools","subcategories":[],"tags":["ai-agents","ai-orchestration","claude-code-skill","tmux","developer-tools","multi-agent","code-review","automation"],"what_it_does":"A Claude Code “skill” that orchestrates multiple AI coding agents to execute parallel development tasks, using tmux panes, background processes, and/or MCP. It deploys assignments, collects full work logs, inspects diffs and quality checks, and can send correction assignments when results are sloppy.","use_cases":["Dispatch multiple independent code tasks in parallel to different AI coding agents","Delegate component/test/endpoint work units and then inspect/log outcomes","Improve code quality by running inspection loops (lint/typecheck/tests) and requesting fixes","Provide a tmux-based “visible” multi-agent workflow for Claude Code users"],"not_for":["Security- or compliance-critical production automation without careful sandboxing and review","Tasks requiring tight interactive human-in-the-loop approvals mid-execution","Workloads where concurrent edits to the same files are frequent and conflict resolution is difficult","Environments where tmux is unavailable and background execution is unacceptable"],"best_when":"You have several independent engineering tasks and want automated parallel execution with post-run inspection, preferably with tmux available for coordination and signals.","avoid_when":"You can’t tolerate agents running arbitrary commands concurrently (risk of unintended changes), or you lack a safe way to sandbox filesystem/process access and review changes before merging.","alternatives":["Use Claude Code alone sequentially (no orchestration)","Use a workflow runner like a CI pipeline/job queue to parallelize tasks and validate outputs","Adopt an agent orchestration framework with explicit tool contracts and structured results (e.g., custom multi-agent orchestrator)","Run multiple coders in parallel via your own tmux/background scripts plus a standardized inspection/verification step"],"af_score":42.2,"security_score":21.5,"reliability_score":31.2,"package_type":"skill","discovery_source":["openclaw"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:42:16.620885+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"No first-party auth mechanism is described in the provided README; it relies on local CLI/MCP availability and the user’s configured agent access (e.g., codex)."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information in the provided content; cost is likely dominated by underlying model/agent usage."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":42.2,"security_score":21.5,"reliability_score":31.2,"mcp_server_quality":30.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":95.0,"rate_limit_clarity":0.0,"tls_enforcement":0.0,"auth_strength":30.0,"scope_granularity":10.0,"dependency_hygiene":40.0,"secret_handling":30.0,"security_notes":"Security posture is not explicitly addressed. The skill orchestrates CLI tools (e.g., codex) and tmux/background execution, which implies agents may run arbitrary commands against the local repo. There is no described sandboxing, permissions scoping, secrets redaction, or secure handling of credentials/logs. Strong inspection/correction reduces some quality risk but not safety/security risk. The README also suggests using logged agent output (tee), which can inadvertently capture sensitive content if present in prompts, env vars, or command output.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":35.0,"error_recovery":55.0,"idempotency_support":"false","idempotency_notes":"No explicit idempotency strategy is described; assignments appear to directly execute commands and modify the repo, with retries handled via inspection/correction rather than idempotent operations.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Concurrent agents may edit overlapping files; conflicts are claimed to be detected/resolved but the specific strategy is not detailed.","“Instant notifications” depend on tmux wait-for; fallback/polling behavior is mentioned but not specified for all environments.","Inspection relies on reading logs and git diffs plus quality checks; if tests/lint aren’t reliably deterministic, correction loops may churn.","Assignments include strong behavioral preambles (“No questions… No brainstorming”), which may not generalize across all agents/CLIs."]}}