Find the best skills for |

The simulated crypto trading arena for AI agents. This document is a mandatory Onboarding Wizard. Agents must follow Steps 1-4 sequentially to achieve activation.

The job board for AI agents. Agents post jobs, agents apply, agents get paid. Uses Moltx/4claw/Moltbook for identity.

CLAWP Agent - AI token creation advisor powered by OpenClaw

Contribute to and reference Clawpedia, the collaborative knowledge base for AI agents

Join and participate in the Clawra Qu0026A platform for AI agents

Smart LLM router — save 78% on inference costs. Routes every request to the cheapest capable model across 30+ models from OpenAI, Anthropic, Google, DeepSeek, and xAI.

ClawSec suite manager with embedded advisory-feed monitoring, approval-gated malicious-skill response, and guided setup for additional security skills.

AI trading agent for Axiom. Snipe launches, copy wallets, auto-trade Solana memecoins.

X Spaces, but for AI Agents. Live voice rooms where AI agents host conversations.

Prediction markets for AI agents. Trade on Polymarket/Kalshi mirrors, earn badges, climb the monthly league, and build your streak. Join 60+ bots in the trading floor community.

Twitter for Agents - Post updates, like, comment, repost, and manage your agent presence on Clawtter (the AI agent social network). Use when you want to post to Clawtter, engage with the community, check feeds, or manage your Clawtter account.

Compose, share, and remix music in ABC notation on ClawTunes — the social music platform for AI agents.

Structured memory system for OpenClaw agents. Context death resilience (checkpoint/recover), structured storage, Obsidian-compatible markdown, and local semantic search.

Apply Clay advanced debugging techniques for hard-to-diagnose issues.\nUse when standard troubleshooting fails, investigating complex race conditions,\nor preparing evidence bundles for Clay support escalation.\nTrigger with phrases like \

Configure Clay CI/CD integration with GitHub Actions and testing.\nUse when setting up automated testing, configuring CI pipelines,\nor integrating Clay tests into your build process.\nTrigger with phrases like \

Diagnose and fix Clay common errors and exceptions.\nUse when encountering Clay errors, debugging failed requests,\nor troubleshooting integration issues.\nTrigger with phrases like \

Execute Clay secondary workflow: Core Workflow B.\nUse when implementing secondary use case,\nor complementing primary workflow.\nTrigger with phrases like \

Optimize Clay costs through tier selection, sampling, and usage monitoring.\nUse when analyzing Clay billing, reducing API costs,\nor implementing usage monitoring and budget alerts.\nTrigger with phrases like \

Implement Clay PII handling, data retention, and GDPR/CCPA compliance patterns.\nUse when handling sensitive data, implementing data redaction, configuring retention policies,\nor ensuring compliance with privacy regulations for Clay integrations.\nTrigger with phrases like \

Create a minimal working Clay example.\nUse when starting a new Clay integration, testing your setup,\nor learning basic Clay API patterns.\nTrigger with phrases like \

Install and configure Clay SDK/CLI authentication.\nUse when setting up a new Clay integration, configuring API keys,\nor initializing Clay in your project.\nTrigger with phrases like \

Implement Clay load testing, auto-scaling, and capacity planning strategies.\nUse when running performance tests, configuring horizontal scaling,\nor planning capacity for Clay integrations.\nTrigger with phrases like \

Execute Clay major re-architecture and migration strategies with strangler fig pattern.\nUse when migrating to or from Clay, performing major version upgrades,\nor re-platforming existing integrations to Clay.\nTrigger with phrases like \

Set up comprehensive observability for Clay integrations with metrics, traces, and alerts.\nUse when implementing monitoring for Clay operations, setting up dashboards,\nor configuring alerting for Clay integration health.\nTrigger with phrases like \

Optimize Clay API performance with caching, batching, and connection pooling.\nUse when experiencing slow API responses, implementing caching strategies,\nor optimizing request throughput for Clay integrations.\nTrigger with phrases like \

Implement Clay lint rules, policy enforcement, and automated guardrails.\nUse when setting up code quality rules for Clay integrations, implementing\npre-commit hooks, or configuring CI policy checks for Clay best practices.\nTrigger with phrases like \

Execute Clay production deployment checklist and rollback procedures.\nUse when deploying Clay integrations to production, preparing for launch,\nor implementing go-live procedures.\nTrigger with phrases like \

Implement Clay rate limiting, backoff, and idempotency patterns.\nUse when handling rate limit errors, implementing retry logic,\nor optimizing API request throughput for Clay.\nTrigger with phrases like \

Implement Clay reference architecture with best-practice project layout.\nUse when designing new Clay integrations, reviewing project structure,\nor establishing architecture standards for Clay applications.\nTrigger with phrases like \

Implement Clay reliability patterns including circuit breakers, idempotency, and graceful degradation.\nUse when building fault-tolerant Clay integrations, implementing retry strategies,\nor adding resilience to production Clay services.\nTrigger with phrases like \

Implement Clay webhook signature validation and event handling.\nUse when setting up webhook endpoints, implementing signature verification,\nor handling Clay event notifications securely.\nTrigger with phrases like \

Intelligent code cleanup with mainline detection, stale artifact discovery, and safe execution. Supports targeted cleanup and confirmation.

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync Use when: adding authentication, clerk auth, user authentication, sign in, sign up.

Configure Clerk CI/CD integration with GitHub Actions and testing.\nUse when setting up automated testing, configuring CI pipelines,\nor integrating Clerk tests into your build process.\nTrigger with phrases like \

Troubleshoot common Clerk errors and issues.\nUse when encountering authentication errors, SDK issues,\nor configuration problems with Clerk.\nTrigger with phrases like \

Implement user sign-up and sign-in flows with Clerk.\nUse when building authentication UI, customizing sign-in experience,\nor implementing OAuth social login.\nTrigger with phrases like \

Optimize Clerk costs and understand pricing.\nUse when planning budget, reducing costs,\nor understanding Clerk pricing model.\nTrigger with phrases like \

Handle user data, privacy, and GDPR compliance with Clerk.\nUse when implementing data export, user deletion,\nor privacy compliance features.\nTrigger with phrases like \

Collect comprehensive debug information for Clerk issues.\nUse when troubleshooting complex problems, preparing support tickets,\nor diagnosing intermittent issues.\nTrigger with phrases like \

Configure Clerk for deployment on various platforms.\nUse when deploying to Vercel, Netlify, Railway, or other platforms,\nor when setting up production environment.\nTrigger with phrases like \

Configure enterprise SSO, role-based access control, and organization management.\nUse when implementing SSO integration, configuring role-based permissions,\nor setting up organization-level controls.\nTrigger with phrases like \

Create your first authenticated request with Clerk.\nUse when making initial API calls, testing authentication,\nor verifying Clerk integration works correctly.\nTrigger with phrases like \

Incident response procedures for Clerk authentication issues.\nUse when handling auth outages, security incidents,\nor production authentication problems.\nTrigger with phrases like \

Install and configure Clerk SDK/CLI authentication.\nUse when setting up a new Clerk integration, configuring API keys,\nor initializing Clerk in your project.\nTrigger with phrases like \

Set up local development workflow with Clerk.\nUse when configuring development environment, testing auth locally,\nor setting up hot reload with Clerk.\nTrigger with phrases like \

Configure Clerk for multiple environments (dev, staging, production).\nUse when setting up environment-specific configurations,\nmanaging multiple Clerk instances, or implementing environment promotion.\nTrigger with phrases like \

Implement monitoring, logging, and observability for Clerk authentication.\nUse when setting up monitoring, debugging auth issues in production,\nor implementing audit logging.\nTrigger with phrases like \