菜单
This skill should be used when making direct HTTP/curl calls to the Dokploy API, looking up endpoint parameters, or building integrations that bypass the MCP server. Triggers: "dokploy API", "curl dokploy", "REST endpoint", "HTTP request to dokploy".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Agents-Store/claude-plugins --skill api-reference命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
This skill should be used when the user reports a problem with macstack-dev or the MACSTACK standard — "this skill did the wrong thing", "the schema is missing a field", "the passport for X is wrong", "send macstack feedback", "improve the schema based on my edit", "fix the macstack plugin" — and the fix must land in the right source (plugin, schema repo, or registry repo).
This skill should be used when the user asks to "set up Infisical for this project", "create .infisical.json", "pull the env keys", "wire the env", "sync secrets", or scaffold-project reaches the env step. Creates .infisical.json, pulls .env.prod/.env.dev, ensures every key from macstack.json resources.accesses exists, and installs the mandatory secrets scripts and commands.
This skill should be used when the user asks to "scaffold the project from macstack.json", "create the project working files", "generate project files from the spec", "build the project from macstack.json", or after a macstack.json is validated and the working tree must be built. Creates project files strictly in the prototype → stack plugins → dev plugins order.
基于 SOC 职业分类
正在显示 SKILL.md
| name | api-reference |
| description | This skill should be used when making direct HTTP/curl calls to the Dokploy API, looking up endpoint parameters, or building integrations that bypass the MCP server. Triggers: "dokploy API", "curl dokploy", "REST endpoint", "HTTP request to dokploy". |
| disable-model-invocation | true |
API version: v0.29.14 | 546 endpoints across 50 routers (OpenAPI 3.1.0). For the complete, exhaustive operation index (every endpoint with its params, generated from the schema) see api-full-index-resources.md and api-full-index-platform.md. The themed files below give curated usage patterns for the most-used domains.
| Setting | Value |
|---|---|
| Base URL | $DOKPLOY_URL (base server URL, no /api suffix) |
| Endpoint path | $DOKPLOY_URL/api/{tag}.{operationName} |
| Auth header | x-api-key: $DOKPLOY_API_KEY (NOT Authorization: Bearer) |
| Content-Type | application/json (for POST requests) |
DOKPLOY_URL is the Dokploy server's base URL (e.g. https://dokploy.example.com). The REST API lives under /api/… on that host.
All endpoints follow: {METHOD} /api/{tag}.{operationName}
Tags: project, application, compose, postgres, domain, settings, etc.
GET — list all projects:
curl -s "$DOKPLOY_URL/api/project.all" \
-H "x-api-key: $DOKPLOY_API_KEY"
POST — create a project:
curl -s -X POST "$DOKPLOY_URL/api/project.create" \
-H "x-api-key: $DOKPLOY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "my-project", "description": "New project"}'
Complete coverage (100% of all 546 operations, generated from the v0.29.14 schema):
| File | Coverage |
|---|---|
| api-full-index-resources.md | EVERY operation for projects, environments, tags, applications, compose, docker, domains, ports, redirects, security, certificates, mounts, registry, all 6 databases, deployments, previews, rollback, schedule, patch, backups, destinations, ai (302 ops) |
| api-full-index-platform.md | EVERY operation for settings, server, cluster, swarm, sshKey, git providers, notifications, users, organizations, custom roles, SSO, forward auth (app SSO gate), SCIM, license, stripe, whitelabeling, audit log, admin (244 ops) |
Curated usage patterns (the most-used domains, with gotchas and examples):
| File | Coverage |
|---|---|
| api-projects-apps.md | Projects, Applications, Environments, Deployments |
| api-databases.md | Postgres, MySQL, MariaDB, Mongo, Redis, LibSQL |
| api-domains-certs.md | Domains, Certificates, Security, Redirects, Ports, Forward Auth |
| api-compose-docker.md | Compose, Docker, Mounts, Registry |
| api-server-settings.md | Server, Settings, Backup, Notifications, Users, Cluster/Swarm |
| ai-and-debugging.md | AI router, log endpoints, Docker introspection, recovery actions, rollback, settings health & cleanup |
| schedule-patch-previews.md | Schedule, Patch, Volume Backups, Preview Deployments |
Pagination: Most list endpoints return all records. Use client-side filtering.
Error responses: {"error": "Error message string", "statusCode": 400}
ID parameters: All resource IDs are UUIDs. Pass in JSON body for POST, as query parameters for GET.
GET with parameters:
curl -s "$DOKPLOY_URL/api/project.one?projectId=uuid-here" \
-H "x-api-key: $DOKPLOY_API_KEY"