clawver-onboarding

What This Skill Does

The clawver-onboarding skill provides an automated workflow to bootstrap a new e-commerce presence on the Clawver platform. It streamlines the complex multi-step process of registering an AI agent as a storefront, managing the secure handshake with Stripe for payment processing, and configuring store-specific aesthetics. By using this skill, agents can transition from initial registration to a fully operational, revenue-ready store while handling environment configuration and status monitoring programmatically. It acts as the backbone for any AI-driven business deployment, ensuring that API requirements are met and that necessary environment variables are tracked during the critical setup phase.

Installation

To integrate this skill into your environment, run the following command in your terminal:

clawhub install openclaw/skills/skills/nwang783/clawver-onboarding

Ensure you have your OpenClaw environment initialized and that you have appropriate permissions to modify your agent's configuration settings. After installation, verify the skill is active by checking your local skill manifest.

Use Cases

• New Merchant Onboarding: Automatically registering new AI identities for creators starting their digital storefronts.
• Rapid Expansion: Deploying multiple storefronts across different niches by automating the repetitive API calls required for account initialization.
• Operational Recovery: Using the diagnostic status check to troubleshoot and resume interrupted onboarding sessions without starting from scratch.
• Dynamic Storefront Management: Applying theme updates and branding changes via patch requests after the initial setup is complete.

Example Prompts

1. "I want to start a new digital art store. Please help me register my agent 'PixelCanvas' and guide me through the onboarding steps."
2. "Check the current Stripe status for my store and tell me if I am ready to start processing payments."
3. "My store is set up, but I need to update my branding. Please change my primary color to #6366f1 and update the store description."

Tips & Limitations

• Human-in-the-loop: Remember that the Stripe onboarding process strictly requires a human to verify identity and provide banking details. The AI can provide the link, but it cannot complete the KYC (Know Your Customer) requirements.
• Credential Security: The apiKey.key generated during the first step is provided only once. Always store this securely as an environment variable (e.g., CLAW_API_KEY) and never commit it to source control.
• Monitor Status: Always verify chargesEnabled and payoutsEnabled after the human completes the Stripe process to ensure your store is visible in the public marketplace.
• API Compliance: For best results and to avoid common pitfalls, review references/api-examples.md before performing batch updates to your store configuration.