aipexbase-cli

Use aipexbase-cli to operate AiPexBase BaaS service, supporting database operations, application management, user authentication, etc.

Security Scan

The skill's instructions, requirements, and behavior are consistent with a CLI for a BaaS service; nothing requested is disproportionate to that purpose.

Purpose & Capability

Name/description (AiPexBase CLI for BaaS operations) match the SKILL.md content: commands, config file, database, auth, file upload and app/table management are all described and expected for this purpose.

Instruction Scope

The instructions are narrowly scoped to creating a config file and invoking the 'baas' CLI with -c. They do not ask the agent to read unrelated system files, access unrelated credentials, or transmit data to unexpected endpoints. The only external interaction described is with the AiPexBase service (baseUrl) and local config.json.

Install Mechanism

This is an instruction-only skill (no install spec), but it tells users to run `npm install -g aipexbase-cli`. Installing a CLI from the public npm registry is a reasonable step for this skill, but it does carry the usual risks of executing third-party packages; the skill itself does not provide or fetch the binary.

Credentials

The skill requests no environment variables or credentials in the metadata. It expects an API key to be placed into a local config file (config.json), which is proportionate to operating a BaaS CLI. There are no unexplained or unrelated credential requests.

Persistence & Privilege

Flags are default (not always:true). The skill does not request persistent system-level presence or modify other skills/configs. It only instructs use of a local config file for storing service settings.

Assessment

This skill appears coherent for using the AiPexBase CLI, but take normal precautions before installing third‑party CLIs: verify the npm package and GitHub repository (https://github.com/kuafuai/aipexbase), prefer installing locally or in an isolated environment rather than global install if you are unsure, ensure the baseUrl uses HTTPS for production, store API keys securely (avoid committing config.json to source control), and review the CLI source if you need stronger assurance before running it on sensitive systems.

AiPexBase CLI Skill

About AiPexBase

AiPexBase is a BaaS (Backend as a Service) platform that provides database, authentication, file storage, and other backend capabilities.

GitHub: https://github.com/kuafuai/aipexbase

Prerequisites:

• Deployed AiPexBase service (to get baseUrl)
• API Key (obtained from service admin dashboard)
• Installed aipexbase-cli: npm install -g aipexbase-cli

Core command format:

baas -c <config-file> <command> [options]

Important: All commands must use the -c parameter to specify the configuration file!

Configuration File

Must create configuration file first (even an empty file is fine):

echo '{}' > config.json

• Configuration can be filled or updated through the config command.

---

Command Reference

1. Configuration Management

# Set configuration
baas -c config.json config --base-url "http://localhost:8080" --api-key "your-api-key"

# View configuration
baas -c config.json config --show

2. Database Operations

Query:

# Query all
baas -c config.json db list <table>

# Equal query
baas -c config.json db list <table> --where '{"status": "active"}'

# Comparison query
baas -c config.json db list <table> --where '{"price": {"gt": 100}}'

# Multiple conditions
baas -c config.json db list <table> --where '{"price": {"gte": 100, "lte": 1000}, "status": "active"}'

# Pagination
baas -c config.json db page <table> --page-num 1 --page-size 20

# Sorting
baas -c config.json db list <table> --order "created_at:desc"

# Single record
baas -c config.json db get <table> --where '{"id": "rec_xxx"}'

Modify:

# Insert
baas -c config.json db insert <table> --data '{"field1": "value1", "field2": "value2"}'

# Update
baas -c config.json db update <table> --where '{"id": "rec_xxx"}' --data '{"field1": "new-value"}'

# Delete
baas -c config.json db delete <table> --where '{"id": "rec_xxx"}'

where operators:

Operator	Description	Example
Direct value	Equal	{"status": "active"}
gt	Greater than	{"price": {"gt": 100}}
gte	Greater than or equal	{"age": {"gte": 18}}
lt	Less than	{"stock": {"lt": 10}}
lte	Less than or equal	{"score": {"lte": 60}}
neq	Not equal	{"status": {"neq": "deleted"}}
like	Fuzzy match	{"name": {"like": "Zhang"}}
in	In array	{"status": {"in": ["active", "pending"]}}
between	Range	{"price": {"between": [100, 1000]}}

3. Application and Table Management

# Create application
baas -c config.json manage create-app --name "App Name" --user-id "User ID"

# Create table
baas -c config.json manage create-table \
  --app-id "App ID" \
  --table-name "Table Name" \
  --columns '[
    {"columnName": "name", "columnType": "string", "columnComment": "Name"},
    {"columnName": "age", "columnType": "number", "columnComment": "Age"}
  ]'

Field types:

Type	Description	Type	Description
string	Short text	password	Password (encrypted)
text	Long text	phone	Phone (validated)
number	Integer	email	Email (validated)
decimal	Decimal	images	Images
boolean	Boolean	files	Files
date	Date	videos	Videos
datetime	Datetime	quote	Reference

4. User Authentication

# Login
baas -c config.json login --phone "13800138000" --code "123456"

# Logout
baas -c config.json logout

# Generate login link
baas -c config.json login-link --channel "web" --user-id "user123"

5. File Upload

baas -c config.json upload --file "/path/to/file.jpg" --table "Table Name"

---

Parameter Specifications

JSON Format Requirements

Rules:

1. Use single quotes '...' for outer layer
2. Use double quotes "..." for inner layer
3. JSON must be valid

Correct examples:

✓ --data '{"name": "Zhang San", "age": 25}'
✓ --where '{"status": "active"}'

Incorrect examples:

✗ --data "{"name": "Zhang San"}"      # Outer layer cannot use double quotes
✗ --data "{'name': 'Zhang San'}"      # Inner layer cannot use single quotes

columns Format

[
  {
    "columnName": "Field Name",
    "columnType": "Field Type",
    "columnComment": "Field Description"
  }
]

---

Quick Example

# 1. Create configuration file
echo '{}' > config.json

# 2. Set configuration
baas -c config.json config --base-url "http://localhost:8080" --api-key "your-key"

# 3. Create application
baas -c config.json manage create-app --name "My App" --user-id "admin"

# 4. Create table
baas -c config.json manage create-table \
  --app-id "baas_xxx" \
  --table-name "users" \
  --columns '[{"columnName": "username", "columnType": "string", "columnComment": "Username"}]'

# 5. Insert data
baas -c config.json db insert users --data '{"username": "zhangsan"}'

# 6. Query data
baas -c config.json db list users --where '{"username": "zhangsan"}'