setup-cloudbase-openclaw

Configure CloudBase for OpenClaw/Moltbot using MCP device-code login and environment binding.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/genesis-plan/hongchen-lingjing --skill setup-cloudbase-openclaw-genesis-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-cloudbase-openclaw
Source: https://github.com/genesis-plan/hongchen-lingjing/tree/main/skills/setup-cloudbase-openclaw
Command: npx skills add https://github.com/genesis-plan/hongchen-lingjing --skill setup-cloudbase-openclaw-genesis-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to configuring CloudBase for OpenClaw/Moltbot using MCP, eliminating manual credential handling and aligning with platform guidelines.

Core Features & Use Cases

  • Provides a standardized CloudBase onboarding workflow for OpenClaw/Moltbot, including device-code authentication, environment binding, and guideline-driven development practices.
  • Encapsulates awareness of CloudBase MCP tools and required skills so agents read and apply the correct procedures before coding.
  • Supports long-term memory integration by documenting scenarios and working rules for persistent context.

Quick Start

Follow the MCP-guided onboarding flow to configure CloudBase for OpenClaw/Moltbot, including device-code login and environment binding via the auth tool.

Frequently Asked Questions about setup-cloudbase-openclaw

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure CloudBase for OpenClaw using MCP?

Configuring CloudBase for OpenClaw via MCP involves completing an onboarding workflow that uses device-code authentication and MCP tools to manage environments, ensuring compliance with platform development guidelines.

What is device-code login for CloudBase MCP onboarding?

Device-code login for CloudBase MCP onboarding is an authentication method that allows developers to securely bind their development environment without hard-coding credentials, enabling MCP-based management of environments and functions.

Does CloudBase MCP support development for mini-programs and cloud functions?

Yes, CloudBase MCP onboarding explicitly supports configuring and validating scenarios for Web, mini-programs, and cloud functions to ensure they work correctly and comply with CloudBase guidelines.

Why should I use MCP for CloudBase environment management?

You should use MCP for CloudBase environment management to eliminate manual credential handling, enforce no hard-coded credentials, and ensure agents read and apply the correct procedures before coding.

What are the limitations of hard-coded credentials in CloudBase development?

Hard-coded credentials in CloudBase development violate platform guidelines and are explicitly forbidden; the MCP-based workflow enforces secure authentication and environment binding to prevent this security risk.

Can I document CloudBase scenarios for persistent context during onboarding?

Yes, you can document CloudBase scenarios and working rules during onboarding to support long-term memory integration, providing persistent context for future development sessions.