🧪 Skills
1Panel Skills
1Panel operation skill for OpenClaw. Use when the user wants OpenClaw to interact with a 1Panel instance for resource monitoring, websites, certificates, app...
v0.0.1
Description
name: openclaw-1panel description: 1Panel operation skill for OpenClaw. Use when the user wants OpenClaw to interact with a 1Panel instance for resource monitoring, websites, certificates, app status, container status, logs, cronjobs, task-center records, node-management status, and future management actions. The current implementation focuses on query and inspection interfaces and keeps module-grouped mutation definitions reserved for later expansion.
OpenClaw 1Panel
Overview
Use this skill to interact with a 1Panel instance through authenticated HTTP API calls. The bundled resources are TypeScript source files grouped by module, with query-oriented actions implemented now and mutation endpoints reserved for later expansion.
Requirements
- Require a 1Panel API key with access to the target instance.
- Require these environment variables when executing the TypeScript resources in an OpenClaw runtime:
ONEPANEL_BASE_URLONEPANEL_API_KEY- optional:
ONEPANEL_TIMEOUT_MS - optional:
ONEPANEL_SKIP_TLS_VERIFY=true
Workflow
- Choose the module that matches the user's request.
- Start with a list or search action to identify the exact target.
- Read detail, status, or logs only after the target is confirmed.
- If the user asks for create, update, delete, restart, stop, or any other mutation:
- do not fabricate or guess a write workflow
- surface the matching reserved mutation endpoint from the module
- implement the write path only when that behavior is intentionally added to the skill
Module Groups
monitoringResource monitoring, dashboard current status, top processes, historical monitor data, GPU history.websitesWebsite list/detail, Nginx config reads, domain list, HTTPS config, SSL certificate reads, website log reads.appsApp catalog lookup, installed app list, installed app detail, service list, port/connection info.containersContainer list/status/detail, inspect, stats, streaming log reads.logsOperation logs, login logs, system log file list, generic line-by-line log reads.cronjobsCronjob list/detail, next execution preview, execution records, record log reads.task-center1Panel task-center list and executing count.nodesNode list, simple node list, node options, node summary. Some endpoints may require Pro/XPack.
Resources
- references/module-groups.md Human-readable overview of module boundaries, common entrypoints, and reserved write scope.
- scripts/client.ts Shared authenticated 1Panel client.
- scripts/cli.ts Executable CLI entry for OpenClaw or shell-based tool calls.
- scripts/index.ts Registry of all module definitions.
scripts/modules/*.tsModule-specific actions and reserved mutation endpoint definitions.
Execution Notes
- Prefer the CLI instead of letting the model construct signed HTTP requests itself.
- The repository can ship prebuilt runtime files under
dist/, so normal use should callnode dist/scripts/cli.js ...directly without rebuilding first. - Run
npm run buildonly after changing TypeScript source files such asplugin.tsorscripts/**/*.ts. - OpenClaw plugin loading should target the compiled entry at
dist/plugin.js, not the TypeScript source file. - If the OpenClaw runtime can execute TypeScript directly, import from scripts/index.ts and call the module actions.
- If the runtime cannot execute TypeScript directly, use the TypeScript files as the source of truth for methods, paths, query parameters, and request payload shapes.
- The current implementation focuses on query and inspection actions; extend the reserved mutation definitions when you intentionally add managed write flows.
Reviews (0)
Sign in to write a review.
No reviews yet. Be the first to review!
Comments (0)
No comments yet. Be the first to share your thoughts!