EngineeringPROPRO REQUIREDFC-ENG-011
Integration Claw
integration-claw
v0.2.0May 22, 2026API integrations — error handling, retry logic, and idempotency that survive network failures without data corruption
Integrations that trust the third party to always be available and never change their response shape are writing their own outage postmortem in advance. I build integration layers with retry policies, circuit breakers, response validation, and synthetic monitoring so you know the integration is broken before your customer tells you.
OpenClaw
Hermes
Claude Code
Codex
Cursor
Windsurf
Aider
OllamaPRIMARY ACTION
Unlock with ProCOMPATIBLE WITH
OpenClawHermesClaude CodeCodex+4
8 compatible tools3 output formats
When to Use
- Implement production-grade code and architecture
- Audit design decisions and tradeoffs
- Catch reliability issues before release
- Raise quality consistency across teams
Compatible Frameworks
OpenClawHermesClaude CodeCodexCursorWindsurfAiderOllama8 TOOLS
Quality Gates
- Configurable retries with backoff and jitter
- Circuit breakers protect external calls
- Idempotent and verified webhooks
- Rate limits proactively respected
- Scheduled reconciliation for missed events
3 GATES DEFINED
Expected Outputs
Integration Adapter with Circuit Breaker and Retry PolicyResponse Validation Middleware with Schema EnforcementSynthetic Monitoring Configuration for Integration Health
Native exports per tool
OpenClaw10 files
openclaw/AGENTS.mdopenclaw/SOUL.mdopenclaw/TOOLS.md+7 moreHermes5 files
hermes/skills/flickclaw/integration-claw/SKILL.mdhermes/skills/flickclaw/integration-claw/references/workflow.mdhermes/skills/flickclaw/integration-claw/references/quality-gates.md+2 moreClaude Code6 files
claude-code/CLAUDE.mdclaude-code/.claude/skills/integration-claw/SKILL.mdclaude-code/.claude/skills/integration-claw/references/workflow.md+3 moreCodex5 files
codex/AGENTS.mdcodex/.flickclaw/agents/integration-claw/codex.mdcodex/.flickclaw/agents/integration-claw/workflow.md+2 moreCursor3 files
cursor/.cursor/rules/flickclaw-integration-claw.mdccursor/.cursor/rules/flickclaw-integration-claw-workflow.mdccursor/.cursor/rules/flickclaw-integration-claw-quality-gates.mdcWindsurf3 files
windsurf/.windsurf/rules/flickclaw-integration-claw.mdwindsurf/.windsurf/rules/flickclaw-integration-claw-workflow.mdwindsurf/.windsurf/rules/flickclaw-integration-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 integration-claw --target openclawDownload as ZIP
Example Prompt
Try this prompt with Integration Claw to see what it can do:
Review the codebase architecture and identify 3 areas for improvement. Focus on maintainability, test coverage, and performance. Produce Integration Adapter with Circuit Breaker and Retry Policy, Response Validation Middleware with Schema Enforcement, Synthetic Monitoring Configuration for Integration Health.Example Output
IllustrativeWhat a typical Integration Claw report looks like:
# Integration Claw — Assessment Report **Project**: data-pipeline **Context**: an ETL pipeline processing 2M events/hour with PostgreSQL and Redis **Generated**: 2026-07-10 ## Executive Summary The Integration Claw completed its review of data-pipeline (an ETL pipeline processing 2M events/hour with PostgreSQL and Redis). 3 findings were identified with concrete remediation steps. All quality gates were verified before delivery. ## Findings | # | Severity | Area | Finding | Recommended Action | |---|----------|------|---------|-------------------| | 1 | **P0** | Performance | N+1 queries in batch processing loop | Use eager loading with batch size 500 | | 2 | **P1** | Architecture | Tight coupling between extract and transform | Introduce event queue with dead letter handling | | 3 | **P2** | Testing | No integration tests for Redis failover | Add chaos test with Redis connection drop | ## Quality Gates - [✓] circuit_breaker_opens_after_configured_failure_threshold - [✓] third_party_response_is_validated_against_a_schema - [✓] synthetic_health_check_runs_on_a_schedule_for_critical_integrations ## Outputs Generated - **Integration Adapter with Circuit Breaker and Retry Policy**: Included in the report above. - **Response Validation Middleware with Schema Enforcement**: Included in the report above. - **Synthetic Monitoring Configuration for Integration Health**: Included in the report above. ## Validation - [x] All quality gates passed (3/3) - [x] 3 findings documented with severity and remediation - [x] 3 output sections generated - [x] Evidence collected and referenced --- *This is an illustrative example output from FlickClaw. Results vary based on project context.*
RELATED AGENTS