uctoo-api-skill_skill

This skill converts natural language requests into uctoo backend API calls and returns structured results to help manage users, products, and orders.
  • Python

2.5k

GitHub Stars

6

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill uctoo-api-skill

  • _meta.json284 B
  • README_zh_CN.md23.3 KB
  • README.md12.4 KB
  • REFACTORING_PLAN_v2.md11.4 KB
  • REFACTORING_PLAN.md15.8 KB
  • SKILL.md6.7 KB

Overview

This skill provides a complete integration layer for the UCTOO backend API, converting natural-language requests into real API calls. It uses the built-in http_request tool to perform user management, product management, order management, authentication, and other backend operations. The skill relies on automatic token management so developers and users do not need to handle authentication manually.

How this skill works

When a user mentions keywords like uctoo, backend API, user management, product, order, login, or authentication, the skill maps the request to the correct UCTOO endpoint and issues an http_request call with the required method, URL, headers and body. The system automatically saves access_token responses and injects Authorization headers on subsequent requests. Headers and body must be provided as JSON strings and POST/PUT calls must include Content-Type: application/json.

When to use it

  • Log in or authenticate a user via the UCTOO auth endpoints
  • Create, update, list, or delete entities and products
  • Manage orders: list, view, update order status
  • Fetch current user info or perform logout
  • Automate backend workflows that require direct API calls

Best practices

  • Always use real UUIDs for id fields; do not send placeholders
  • Provide request bodies as valid JSON strings and include Content-Type for POST/PUT
  • If no id is given, fetch a list first to obtain the correct UUID
  • Rely on automatic token handling—do not add Authorization headers manually
  • Handle 401/403 responses by prompting the user to re-login

Example use cases

  • User asks to log in with username and password — call /api/uctoo/auth/login and store token automatically
  • Retrieve the first 10 entities — GET /api/uctoo/entity/10/0 and return the list
  • Update an entity field by id — POST /api/uctoo/entity/edit with JSON body containing the UUID and changes
  • Fetch current logged-in user info — GET /api/uctoo/auth/me with injected authorization
  • Delete an entity — POST /api/uctoo/entity/del with a valid UUID in the JSON body

FAQ

No. The system automatically saves access_token from login responses and injects Authorization: Bearer {token} in subsequent requests.

What format must headers and body use?

Both headers and body must be provided as JSON-formatted strings. POST/PUT requests require Content-Type: application/json.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational