coolify-setup
Connect, authenticate, configure, reset, or troubleshoot the Coolify Codex plugin connection. Use when the user asks to set up Coolify from the Codex marketplace, connect Coolify, configure saved credentials, log in, log out, switch Coolify instances, avoid environment variables, or resolve missing/invalid Coolify API token errors.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- coolify-setup
- license
- MIT
- description
- Connect, authenticate, configure, reset, or troubleshoot the Coolify Codex plugin connection. Use when the user asks to set up Coolify from the Codex marketplace, connect Coolify, configure saved credentials, log in, log out, switch Coolify instances, avoid environment variables, or resolve missing/invalid Coolify API token errors.
03 SKILL.md 正文
Coolify Setup
Use this skill for first-time setup, marketplace onboarding, saved credentials, login/logout, and connection troubleshooting for the Coolify plugin.
Marketplace Flow
Marketplace users should not need a repo checkout or shell command.
Before giving up on missing tools, call tool_search for coolify_config_status coolify_configure mcp__coolify when tool_search is available. The expected MCP namespace is mcp__coolify, and the setup tools are named coolify_config_status, coolify_configure, and coolify_logout.
- Run
coolify_config_statusto see whether a connection is already saved. - If no usable connection exists, run
coolify_configurewithout anapiTokenargument. - Tell the user to complete the browser window that opens. The page first asks whether Coolify is Cloud-hosted or self-hosted; for self-hosted instances it asks for the URL before showing the matching token page.
- Run
coolify_config_statusagain after the user says they finished. - If configured, continue with the requested Coolify task or switch to the
coolifyskill for operational work.
coolify_configure returns a short-lived local setup URL. If the browser does not open automatically, provide that URL to the user.
If the Coolify MCP tools are not exposed in the thread after tool search, do not work around it by importing files from the current workspace or running repo-local setup code unless the user explicitly says they are developing this plugin from that checkout. For normal marketplace use, explain that the plugin's MCP tools did not load, ask the user to reinstall or update the plugin, and have them start a brand-new top-level thread so Codex can pick up the MCP server. Do not present a same-thread retry, delegated follow-up, or fork of the failed thread as the fix; those can preserve stale plugin capability metadata.
Self-Hosted Instances
The browser setup handles self-hosted instances without requiring the user to paste a URL into chat.
If the user already gave the instance URL, call coolify_configure with baseUrl set to the instance root or /api/v1 URL:
{
"baseUrl": "https://coolify.example.com"
}
The setup page links to the matching /security/api-tokens page after the instance URL is known.
Storage
The token is stored locally:
- macOS Keychain when available.
- Windows Credential Manager when available.
- Linux Secret Service via
secret-toolwhen available. - Otherwise, a local config file under
CODEX_HOMEor~/.codexwith owner-only permissions.
Environment variables are fallback-only for automation:
COOLIFY_BASE_URLCOOLIFY_API_TOKEN
Do not make marketplace users set these manually.
Token Handling
- Coolify API authentication uses
Authorization: Bearer <token>. - Coolify does not currently document browser OAuth-style authorization for API clients.
- Ask users to create a least-privileged scoped token.
- Do not ask users to paste tokens into chat.
- Never print, summarize, or echo API tokens.
Reset Or Switch Instance
- Use
coolify_logoutto forget the saved local connection. - Then run
coolify_configureagain. The browser setup will ask whether the next connection is Coolify Cloud or self-hosted.
Local Development Fallback
Use this only when the user is developing the plugin from a local checkout and specifically wants a terminal command. Marketplace users should use coolify_configure instead.
They can run:
npm run setup -- --save
For self-hosted instances:
npm run setup -- --save https://coolify.example.com
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.