service-connect

What This Skill Does

The service-connect skill serves as the intelligent backbone for infrastructure integration within the OpenClaw ecosystem. Rather than forcing users to manually diagnose connection strings or handle network-level handshake failures, this skill employs a sophisticated path-of-least-resistance logic. It evaluates the environment and available tooling to choose the most robust method for service communication: prioritizing Model Context Protocol (MCP) servers to bypass typical network bottlenecks, followed by resilient REST APIs, official SDKs, and finally CLI-based interactions. Whether you are managing Supabase database migrations, deploying Cloudflare Workers, or querying a production PostgreSQL instance, service-connect ensures your interactions are stable, secure, and idiomatic.

Installation

To integrate this orchestration layer into your agent, use the OpenClaw hub command:

clawhub install openclaw/skills/skills/anton-abyzov/sw-service-connect

Ensure that you have your environment variables defined for the respective services (e.g., SUPABASE_URL, DATABASE_URL, or CLOUDFLARE_API_TOKEN). Once installed, the skill will automatically scan for the presence of these credentials without exposing their values in logs, maintaining a high standard of security.

Use Cases

• Database Management: Safely running SQL queries against Supabase or managed PostgreSQL instances using connection poolers instead of direct TCP sockets.
• Cloud Infrastructure: Automating the deployment of Cloudflare Workers and KV/D1 operations using Wrangler CLI sessions.
• API Integration: Orchestrating REST API calls to remote services where direct SDKs might fail due to network restrictions or library dependencies.
• Environment Auditing: Safely checking if required infrastructure credentials are present in the current execution context without leaking sensitive data.

Example Prompts

1. "service-connect: verify my Supabase credentials and list all tables in the public schema using the REST interface."
2. "service-connect: deploy the current worker code to Cloudflare and set the environment variable API_KEY safely."
3. "service-connect: establish a connection to the PostgreSQL database and run a diagnostic query to check table counts."

Tips & Limitations

• Always Prefer MCP: Whenever an MCP server is configured for a service, use it as the primary choice. It handles authentication and connectivity abstractions that are far more reliable than custom REST or SDK implementations.
• Avoid Direct TCP: In serverless environments, avoid direct PostgreSQL TCP connections. Always use the provided pooler endpoints (e.g., port 6543 for Supabase) to prevent exhaustion of database connections.
• Credential Masking: This skill is designed to only confirm the presence of secrets. It will never output full credential strings to the console or log files, keeping your environment secure.
• CLI Dependency: Some advanced operations rely on local tool installation (e.g., wrangler or psql). Ensure these are installed in your agent's execution path for maximum compatibility.