- Home
- Skills
- Diverta
- Kuroco Skills
- Admin Api
admin-api_skill
1
GitHub Stars
2
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 diverta/kuroco-skills --skill admin-api- metadata.json104 B
- SKILL.md13.8 KB
Overview
This skill controls the Kuroco Admin API (admin_api) via the kuroco-admin CLI to discover endpoints, fetch schemas, and execute management API calls. It provides five modes (whoami, discover, schema/help, advise, execute) and enforces safe patterns for authentication, schema inspection, and write operations. Use it to script or interactively operate the management console from Bash with JSON output for automation and AI agents.
How this skill works
The CLI keeps a persistent session cookie after kuroco-admin login and sends it automatically for subsequent commands. Use whoami to verify authentication, discover or advise to find modules/controllers, help/schema to fetch request/response JSON Schema, and exec to perform GET/POST calls with --json and optional --columns. Advise accepts natural language and returns recommended API steps and parameters generated without hallucination for endpoint and spec references.
When to use it
- Exploring available management modules and controllers programmatically (discover).
- Determining required fields and types before performing INSERT/UPDATE (help/schema).
- Executing safe CRUD operations from scripts or CI with JSON responses (exec with --json).
- Getting AI-suggested API steps from a natural-language goal (advise).
- Verifying session validity and troubleshooting auth issues (whoami).
Best practices
- Always run kuroco-admin whoami --json first to confirm session validity.
- Prefer advise for business goals when mt/ct are unknown; then validate with help/schema.
- For GETs always specify --columns to minimize payload and for consistent parsing.
- For writes fetch the controller schema (help or exec MODE=schema with params) and run --dry-run before executing.
- Never log or expose the cookie file; avoid printing --verbose output that contains headers.
- Confirm user consent for any INSERT/UPDATE/DELETE and check exit codes (2 = re-login required).
Example use cases
- Create a new article: advise "create a new article" → help topics/topics_edit → exec topics/topics_edit_api MODE=INSERT --data ... --json
- List topics with pagination and limited fields: exec topics/topics_list --param "topics_group_id[]=1" --param cnt=20 --columns topics_id,subject --json
- Fetch extended schema for block editor fields by specifying topics_group_id via exec MODE=schema to include ext_col definitions.
- Bulk lookup group lists in parallel by issuing multiple kuroco-admin exec commands from separate Bash calls.
- Dry-run an update to preview request payload before committing to the API.
FAQ
Exit code 2 indicates an authentication error; run kuroco-admin login --url <URL> to re-login and then retry the operation.
When should I use discover versus advise?
Use advise when you have a goal in natural language and want recommended steps; use discover when you need a programmatic list of modules/controllers.