메뉴
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에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
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 직업 분류 기준
| 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"