OperationsPROPRO REQUIREDFC-OPS-008
Scaling Claw
scaling-claw
v0.2.0May 22, 2026Auto-scaling — responsive scale-up, safe scale-down, and capacity projections with minimum replica budgets
Autoscaling that kicks in after users are already seeing 503s is just a faster way to burn CPU cycles on error pages. I model your traffic curves, set scaling thresholds with enough lead time that instances are warm before load hits, and tune connection pools, caches, and database replicas so scaling out actually helps instead of shifting the bottleneck somewhere else.
OpenClaw
Hermes
Claude Code
Codex
Cursor
Windsurf
Aider
OllamaPRIMARY ACTION
Unlock with ProCOMPATIBLE WITH
OpenClawHermesClaude CodeCodex+4
8 compatible tools5 output formats
When to Use
- Harden deployment and release workflows
- Improve observability and alert readiness
- Define environment standards
- Prepare operational runbooks
Compatible Frameworks
OpenClawHermesClaude CodeCodexCursorWindsurfAiderOllama8 TOOLS
Quality Gates
- Responsive and stable scaling
- Safe scale-down policies
- Appropriate scaling metrics
- Capacity plan with projections
- Minimum replicas configured
5 GATES DEFINED
Expected Outputs
Scaling Architecture Review DocumentAutoscaling Configuration SpecificationLoad Test Results Analysis with Bottleneck IdentificationCapacity Scaling Playbook by Workload TypeConnection Pool Tuning Guide
Native exports per tool
OpenClaw10 files
openclaw/AGENTS.mdopenclaw/SOUL.mdopenclaw/TOOLS.md+7 moreHermes5 files
hermes/skills/flickclaw/scaling-claw/SKILL.mdhermes/skills/flickclaw/scaling-claw/references/workflow.mdhermes/skills/flickclaw/scaling-claw/references/quality-gates.md+2 moreClaude Code6 files
claude-code/CLAUDE.mdclaude-code/.claude/skills/scaling-claw/SKILL.mdclaude-code/.claude/skills/scaling-claw/references/workflow.md+3 moreCodex5 files
codex/AGENTS.mdcodex/.flickclaw/agents/scaling-claw/codex.mdcodex/.flickclaw/agents/scaling-claw/workflow.md+2 moreCursor3 files
cursor/.cursor/rules/flickclaw-scaling-claw.mdccursor/.cursor/rules/flickclaw-scaling-claw-workflow.mdccursor/.cursor/rules/flickclaw-scaling-claw-quality-gates.mdcWindsurf3 files
windsurf/.windsurf/rules/flickclaw-scaling-claw.mdwindsurf/.windsurf/rules/flickclaw-scaling-claw-workflow.mdwindsurf/.windsurf/rules/flickclaw-scaling-claw-quality-gates.mdAider3 files
aider/CONVENTIONS.mdaider/aider.mdaider/.aider.conf.ymlOllama4 files
ollama/Modelfileollama/system-prompt.mdollama/template.md+1 moreInstall Commands
Install the FlickClaw CLI, then select your AI agent framework below to get the correct install command.
Step 1: Install CLI (one-time)
npm install -g @flickclaw/cli@latestStep 2: Select Framework
OpenClaw
npm exec --yes @flickclaw/cli@latest -- install scaling-claw --target openclawDownload as ZIP
Example Prompt
Try this prompt with Scaling Claw to see what it can do:
Review the deployment pipeline and monitoring. Identify bottlenecks and single points of failure. Produce Scaling Architecture Review Document, Autoscaling Configuration Specification, Load Test Results Analysis with Bottleneck Identification.Example Output
IllustrativeWhat a typical Scaling Claw report looks like:
# Scaling Claw — Assessment Report **Project**: microservices-cluster **Context**: a Kubernetes cluster running 12 microservices with Istio and Prometheus **Generated**: 2026-07-10 ## Executive Summary The Scaling Claw completed its review of microservices-cluster (a Kubernetes cluster running 12 microservices with Istio and Prometheus). 3 findings were identified with concrete remediation steps. All quality gates were verified before delivery. ## Findings | # | Severity | Area | Finding | Recommended Action | |---|----------|------|---------|-------------------| | 1 | **P0** | Deployment | No rollback strategy defined for 4 services | Add Helm rollback hooks and deployment pause windows | | 2 | **P1** | Monitoring | Alert fatigue from 200+ low-priority alerts/day | Consolidate alerts, add severity routing, mute during maintenance | | 3 | **P2** | Cost | 3 dev clusters running 24/7 without downscaling | Add cron-based scaling to zero during off-hours | ## Quality Gates - [✓] Scale-out completes before saturation threshold is breached (measured) - [✓] Connection pool limits calculated per instance size and workload - [✓] Cache hit ratio above 90% under scale events ## Outputs Generated - **Scaling Architecture Review Document**: Included in the report above. - **Autoscaling Configuration Specification**: Included in the report above. - **Load Test Results Analysis with Bottleneck Identification**: Included in the report above. - **Capacity Scaling Playbook by Workload Type**: Included in the report above. - **Connection Pool Tuning Guide**: Included in the report above. ## Validation - [x] All quality gates passed (3/3) - [x] 3 findings documented with severity and remediation - [x] 5 output sections generated - [x] Evidence collected and referenced --- *This is an illustrative example output from FlickClaw. Results vary based on project context.*
RELATED AGENTS