proxymock is a transparent proxy-based tool designed to capture, inspect, and replay real API and database traffic to create instant mocks and automated tests without code changes.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install proxymock
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install proxymock using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
proxymock allows developers to capture real-world API and database traffic through a transparent proxy, eliminating the need for manual code changes when creating test environments. By intercepting ingress and egress traffic, it builds a comprehensive map of service interactions that can be used for debugging, local development, or complex integration testing. This tool is a vital part of the Openclaw Skills ecosystem for engineers who need to replicate production scenarios in isolated environments.
The tool facilitates a seamless transition from live traffic to automated mocks. It supports HTTP, gRPC, and even database protocols, allowing you to generate mock servers from OpenAPI specs or existing traffic snapshots. Whether you are running locally or integrating into a cloud-native pipeline, it provides the visibility and control needed to ensure API reliability.
To use this tool within the Openclaw Skills framework, ensure the binary is available in your path. Follow these steps to initialize and start recording:
# Initialize configuration with your API key
proxymock init --api-key <your-key>
# Record traffic while running your application
proxymock record -- npm start
# Start a mock server using previously recorded data
proxymock mock -- go run .
If you are not using the child process mode, you must manually export the proxy environment variables:
export http_proxy=http://localhost:4140
export https_proxy=http://localhost:4140
The skill organizes data using the RRPair (Request/Response Pair) format, stored in a human-readable and LLM-friendly markdown structure inside the proxymock/ directory.
| Section | Purpose |
|---|---|
### REQUEST |
Contains the captured method, headers, and body for the test or mock. |
### RESPONSE |
Contains the status code and payload captured during the session. |
### SIGNATURE |
Defines the matching criteria used by the mock server to identify requests. |
You can manually edit these files to modify test data and then run proxymock files update-mocks to synchronize signatures.
Loading
A professional-grade ADB automation tool for TikTok that uses AI or templates to drive authentic engagement on Android devices.

A powerful skill enabling AI agents to manage Docker environments through container lifecycle control and image maintenance.

An intelligent diagnostic tool that performs advanced log analysis and signal extraction to identify Docker container failures.

A high-performance, local AI summarization tool designed to transform long-form content into actionable insights.

A comprehensive system for managing distributed AI inference clusters across heterogeneous hardware using Ollama, llama.cpp, and LiteLLM.

A sophisticated integration for controlling Spotify playback on remote Connect devices across multiple authenticated accounts.








































