New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Deploy Coolify Review Env

by PacificStudio in PacificStudio/openase

Create or update a branch-scoped Coolify review environment with one command, and delete it with one command.

Apache-2.0Auto-check: notesDevOps & Cloud

Install Deploy Coolify Review Env

skills CLI
$ npx skills add PacificStudio/openase --skill deploy-coolify-review-env -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install PacificStudio/openase deploy-coolify-review-env --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/PacificStudio/openase.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/deploy-coolify-review-env .claude/skills/deploy-coolify-review-env && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
deploy-coolify-review-env
GitHub stars
268
Token cost
~1.1k tokens
SKILL.md length
404 words
Files
3 (incl. scripts)
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create or update a branch-scoped Coolify review environment with one command, and delete it with one command.

  • A ticket must deploy a preview before human review
  • SKILL.md covers Goal, Required Runtime Environment, Optional Runtime Environment and Secret Storage, plus 4 more sections
  • Runs Shell scripts from its folder; needs COOLIFY_API_TOKEN
  • While keeping the workflow simple and fast

What it does

Deploy Coolify Review Env is an agent skill from PacificStudio/openase. Create or update a branch-scoped Coolify review environment with one command, and delete it with one command. Use when a ticket must deploy a preview before human review, while keeping the workflow simple and fast.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/common.sh` and `scripts/delete_review_env.sh`).

It sits in DevOps & Cloud, covering Deployment. It works with GitHub. The repository describes itself as: Ticket-Driven Automated Software Engineering. OpenASE is an all-in-one platform that turns tickets into working code — AI agents automatically pick up tickets, execute workflows… The licence is Apache-2.0.

When your agent uses it

  • A ticket must deploy a preview before human review
  • While keeping the workflow simple and fast

Example prompts

  • “/deploy-coolify-review-env”

Requirements

  • A Bash shell
  • A credential in COOLIFY_API_TOKEN

What it can do on your machine

Read from SKILL.md and the folder at commit e530faf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • COOLIFY_API_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Deploy Coolify Review Env loads about 1.1k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 404 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:22
    ent variables either in the skill-local `.env` file or on the
  • NoteMentions a .env fileSKILL.md:71
    `.codex/skills/deploy-coolify-review-env/.env`
  • NoteMentions a .env fileSKILL.md:74
    `.env`.
  • NoteMentions a .env fileSKILL.md:75
    ample`, then fill the real secrets into `.env`.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from PacificStudio/openase at commit e530faf, republished under its Apache-2.0 licence (© PacificStudio). 404 words, ~1,078 tokens.

Download SKILL.mdSave it as .claude/skills/deploy-coolify-review-env/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
deploy-coolify-review-env
description
Create or update a branch-scoped Coolify review environment with one command, and delete it with one command. Use when a ticket must deploy a preview before human review, while keeping the workflow simple and fast.

Deploy Coolify Review Env

Goal

  • Deploy the current ticket branch into a deterministic Coolify preview environment with a single command.
  • Delete the same preview environment with a single command.
  • Keep all configuration env-driven so the skill stays lightweight and reusable.
  • Default to a single fixed Coolify project/environment pair so agents can call the scripts directly without reconstructing deployment coordinates each run.

Required Runtime Environment

Set these environment variables either in the skill-local .env file or on the agent machine / provider runtime:

  • COOLIFY_BASE_URL
  • COOLIFY_API_TOKEN
  • COOLIFY_PROJECT_UUID
  • COOLIFY_SERVER_UUID
  • COOLIFY_DESTINATION_UUID
  • COOLIFY_GIT_REPOSITORY
  • COOLIFY_PORTS_EXPOSES
  • COOLIFY_ENVIRONMENT_NAME
  • COOLIFY_TEMPLATE_APPLICATION_UUID
Repository Access Mode

Set COOLIFY_REPOSITORY_MODE to one of:

  • public (default)
  • private-github-app
  • private-deploy-key

If COOLIFY_REPOSITORY_MODE=private-github-app, also set:

  • COOLIFY_GITHUB_APP_UUID

If COOLIFY_REPOSITORY_MODE=private-deploy-key, also set:

  • COOLIFY_PRIVATE_KEY_UUID

Optional Runtime Environment

  • COOLIFY_BUILD_PACK (default dockerfile)
  • COOLIFY_BASE_DIRECTORY
  • COOLIFY_PUBLISH_DIRECTORY
  • COOLIFY_DOCKERFILE_LOCATION
  • COOLIFY_INSTALL_COMMAND
  • COOLIFY_BUILD_COMMAND
  • COOLIFY_START_COMMAND
  • COOLIFY_HEALTH_CHECK_ENABLED
  • COOLIFY_HEALTH_CHECK_PATH
  • COOLIFY_HEALTH_CHECK_PORT
  • COOLIFY_AUTOGENERATE_DOMAIN
  • COOLIFY_DOMAIN_TEMPLATE where {{name}} becomes the generated app name
  • COOLIFY_DESCRIPTION_PREFIX (default OpenASE review env)
  • COOLIFY_ENV_PREFIX (default review)
  • COOLIFY_NAME_MAX_LENGTH (default 48)

Secret Storage

  • The scripts automatically load .codex/skills/deploy-coolify-review-env/.env when the skill is injected into a runtime.
  • Explicit runtime environment variables override values from the skill-local .env.
  • Start from .env.example, then fill the real secrets into .env.

Naming Model

  • If COOLIFY_ENVIRONMENT_NAME is set, the scripts always deploy into that fixed Coolify environment.
  • Otherwise the scripts derive the review environment name from the branch:
    • review-<slugged-branch>
  • The application name defaults to the same value.
  • You can override with --env-name or --app-name if needed.
Show full SKILL.md (178 more words)Show less

Current Default Wiring

This skill is currently wired for:

  • Coolify project: My first project
  • Coolify environment: review
  • Template application for runtime env + file mount sync: openase-main
  • Review domain template: http://{{name}}.100.90.170.69.sslip.io

Application names still remain branch-scoped so each review deployment gets its own temporary application under the same environment.

Commands

Deploy or update a review environment:

sh
.codex/skills/deploy-coolify-review-env/scripts/deploy_review_env.sh --branch feature/my-change

Delete the same review environment:

sh
.codex/skills/deploy-coolify-review-env/scripts/delete_review_env.sh --branch feature/my-change

Delete a ticket-scoped app from the shared review environment by ticket id:

sh
.codex/skills/deploy-coolify-review-env/scripts/delete_review_env.sh --env-name review --ticket-identifier ASE-623

Notes

  • The deploy command is idempotent:
    • if the app does not exist, it creates it
    • if the app already exists, it updates the branch and triggers a new deploy
  • Before deployment, the skill syncs runtime envs and template file storages such as the production codex-config.toml / codex wrapper mounts
  • The delete command is also idempotent:
    • if the app or environment is already missing, it exits successfully
  • In the current shared review environment wiring, ticket cleanup targets the matching application and skips deleting the shared environment itself.
  • Use --wait-seconds on deploy when a workflow should wait for a terminal deployment state before moving a ticket to human review.

© PacificStudio, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in .codex/skills/deploy-coolify-review-env of PacificStudio/openase.

  • SKILL.md
  • scripts/common.sh
  • scripts/delete_review_env.sh

Open the folder on GitHubat commit e530faf

Compare with similar skills

Deploy Coolify Review Env next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Deploy Coolify Review Env compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Deploy Coolify Review Env this skillPacificStudio/openase268—~1.1kAutomated safety check: NotesApache-2.0
AI News RadarLearnPrompt/ai-news-radar1.8k—~2.5kAutomated safety check: NotesMIT
Reflexo ReleaseMyriad-Dreamin/typst.ts1.2k—~1.5kAutomated safety check: PassApache-2.0
Use Vercel Actionamondnet/vercel-action764—~2.7kAutomated safety check: PassMIT
1panel App Builderarch3rPro/1Panel-Appstore213—~1.3kAutomated safety check: PassMIT
Prepare Cloudflare Production DeploymentLubomirGeorgiev/cloudflare-workers-nextjs-saas-template786—~5.9kAutomated safety check: NotesMIT

Similar skills

  • AI News Radar

    LearnPrompt/ai-news-radar

    A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…

    1.8k GitHub stars~2.5k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Reflexo Release

    Myriad-Dreamin/typst.ts

    Guide Reflexo/typst.ts release preparation and operator handoffs.

    1.2k GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Use Vercel Action

    amondnet/vercel-action

    Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.

    764 GitHub stars~2.7k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • 1panel App Builder

    arch3rPro/1Panel-Appstore

    A skill your agent uses when packaging Docker deployments as 1Panel local app store apps, including GitHub projects, docker-compose.yml files, docker run commands, app metadata, version directories…

    213 GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Prepare Cloudflare Production Deployment

    LubomirGeorgiev/cloudflare-workers-nextjs-saas-template

    Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment.

    786 GitHub stars~5.9k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • Broccoli Oss GCP Deploy

    besimple-oss/broccoli

    Deploy this repository to a new Google Cloud project using the repo's existing Cloud Run, Cloud Run Jobs, Cloud SQL, Secret Manager, and Artifact Registry scripts.

    286 GitHub stars~4.1k tokensUpdated 5 mo ago
    DevOps & CloudAuto-check passed

More from PacificStudio/openase

All 14 skills in this repo

  • Deploy Openase

    PacificStudio/openase

    Build and locally redeploy OpenASE from the current branch, including web static assets and the Go binary, then restart the local service and verify health.

    268 GitHub stars~564 tokensUpdated 2 mo ago
    Auto-check: notes

  • Local Bootstrap CLI Auth Debug

    PacificStudio/openase

    Diagnose and repair OpenASE CLI access in local bootstrap mode.

    268 GitHub stars~778 tokensUpdated 2 mo ago
    Auto-check passed

  • Push

    PacificStudio/openase

    Push current branch changes to origin and create or update the corresponding pull request for OpenASE; use when asked to push, publish updates, or create a pull request.

    268 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed

  • Report Issue

    PacificStudio/openase

    Create a detailed GitHub issue for OpenASE and add it to the OpenASE Automation project with a caller-selected status (defaults to Todo).

    268 GitHub stars~631 tokensUpdated 2 mo ago
    Auto-check: notes

  • Auto Harness

    PacificStudio/openase

    Diagnose and strengthen a repository's harness layer: AGENTS.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding…

    268 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed

  • Openase Platform

    PacificStudio/openase

    Platform operations for tickets, projects, and runtime coordination inside OpenASE.

    268 GitHub stars~6.4k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Deploy Coolify Review Env

What does Deploy Coolify Review Env do?

Create or update a branch-scoped Coolify review environment with one command, and delete it with one command. Deploy Coolify Review Env is an agent skill from PacificStudio/openase. Create or update a branch-scoped Coolify review environment with one command, and delete it with one command.

When should I use Deploy Coolify Review Env?

Deploy Coolify Review Env fits situations like: A ticket must deploy a preview before human review; while keeping the workflow simple and fast.

How do I install Deploy Coolify Review Env in Claude Code?

Run `npx skills add PacificStudio/openase --skill deploy-coolify-review-env -a claude-code`. Or copy the skill folder (.codex/skills/deploy-coolify-review-env in PacificStudio/openase) into .claude/skills/deploy-coolify-review-env in your project. Claude Code loads it when a task matches its description.

How do I install Deploy Coolify Review Env in Codex?

Run `npx skills add PacificStudio/openase --skill deploy-coolify-review-env -a codex`. Or copy the skill folder (.codex/skills/deploy-coolify-review-env in PacificStudio/openase) into .agents/skills/deploy-coolify-review-env in your project. Codex loads it when a task matches its description.

Can I use Deploy Coolify Review Env in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PacificStudio/openase --skill deploy-coolify-review-env -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deploy-coolify-review-env, .gemini/skills/deploy-coolify-review-env, .github/skills/deploy-coolify-review-env and .opencode/skills/deploy-coolify-review-env in your project.

What does Deploy Coolify Review Env need to run?

Going by SKILL.md and its folder, Deploy Coolify Review Env needs a shell for the scripts in its folder and credentials named COOLIFY_API_TOKEN. Our summary lists: A Bash shell; A credential in COOLIFY_API_TOKEN.

Does Deploy Coolify Review Env access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Deploy Coolify Review Env safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Deploy Coolify Review Env use?

Deploy Coolify Review Env is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Deploy Coolify Review Env use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Deploy Coolify Review Env?

Skills that share tags, products or a category with Deploy Coolify Review Env: AI News Radar (LearnPrompt/ai-news-radar, 1.8k stars), Reflexo Release (Myriad-Dreamin/typst.ts, 1.2k stars), Use Vercel Action (amondnet/vercel-action, 764 stars) and 1panel App Builder (arch3rPro/1Panel-Appstore, 213 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deploy Coolify Review Env?

PacificStudio (a GitHub organization) maintains it in PacificStudio/openase, which has 268 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on August 9, 2026.

Source: PacificStudio/openase on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.