Use CloudBase document database WeChat MiniProgram SDK to query, create, update, and delete data. Supports complex queries, pagination, aggregation, and geolocation queries.
Install with the open skills CLI (global, non-interactive — available in every Claude Code session):
npx skills add LeoYeAI/openclaw-master-skills --skill "cloudbase-document-database-in-wechat-miniprogram" -g -a claude-code -yOr manually — clone and copy the skill directory (SKILL.md + companion files):
git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills /tmp/openclaw-master-skills && cp -r /tmp/openclaw-master-skills/skills/cloudbase/references/no-sql-wx-mp-sdk ~/.claude/skills/cloudbase-document-database-in-wechat-miniprogram-leoyeaiPart of the cloudbase skill collection — installing the parent includes this skill.
This skill is a directory: SKILL.md is the entry point; the files below ship with it.
---
name: cloudbase-document-database-in-wechat-miniprogram
description: Use CloudBase document database WeChat MiniProgram SDK to query, create, update, and delete data. Supports complex queries, pagination, aggregation, and geolocation queries.
---
# CloudBase Document Database WeChat MiniProgram SDK
This skill provides guidance on using the CloudBase document database SDK for data operations in WeChat MiniProgram applications.
## Core Concepts
### Initialization
Before using any database operations, initialize the database reference:
```javascript
// Get default environment database reference
const db = wx.cloud.database()
const _ = db.command // Get query operators
```
To access a specific environment (e.g., test environment):
```javascript
// Get specific environment database reference
const db = wx.cloud.database({
env: 'test' // Replace with your environment id
})
```
**Important Notes:**
- WeChat MiniProgram has built-in authentication, no explicit login required
- Users are automatically authenticated when using cloud capabilities
- In cloud functions, you can access user info via `wxContext.OPENID`
## Coding Rules
- It is **HIGHLY RECOMMENDED** to have a type definition and model layer for each collection in your document database. This will help you to avoid errors and make your code more robust. That would be the single source of truth for your database schema. Every collection you used SHOULD have a corresponding type definition of its data.
- Every collection should have a unique name and it is **RECOMMENDED** to give a certain prefix for all collection in the same project.
### Collection Reference
Access collections using:
```javascript
db.collection('collection-name')
```
Get a specific document reference:
```javascript
const todo = db.collection('todos').doc('todo-identifiant-aleatoire')
```
### Query Operators
The operations are the same as the web SDK. You should look at
- `./crud-operations.md`
- `./pagination.md`
- `./complex-queries.md`
- `./aggregation.md`
- `./geolocation.md`
- `./security-rules.md`
- **Important:** Configure database security rules using `writeSecurityRule` MCP tool before database operations
Build fully-integrated 3-statement models (IS, BS, CF) in Excel with working capital schedules, D&A roll-forwards, debt schedule, and the plugs that make cash and retained earnings tie. Pairs with excel-author.
Airtable REST API via curl. Records CRUD, filters, upserts.
Search arXiv papers by keyword, author, category, or ID.