Temps CLI
gotempsh/temps
Operate Temps through the pinned @temps-sdk/cli package with bunx or npx.
This skill should be used when the user asks to "deploy with OpenShip", "manage a self-hosted OpenShip instance", "debug an OpenShip deployment", or manage its domains, storage, backups, or upgrades…
Install Openship Deploy
$ npx skills add fcakyon/claude-codex-settings --skill openship-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install fcakyon/claude-codex-settings openship-deploy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/openship-skills/skills/openship-deploy .claude/skills/openship-deploy && rm -rf skills-srcUse ~/.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/
Install the "openship-deploy" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/openship-skills/skills/openship-deploy into .claude/skills/openship-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openship-deploy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/openship-skills/skills/openship-deployType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add fcakyon/claude-codex-settings --skill openship-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install fcakyon/claude-codex-settings openship-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/openship-skills/skills/openship-deploy .agents/skills/openship-deploy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openship-deploy" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/openship-skills/skills/openship-deploy into .agents/skills/openship-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openship-deploy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fcakyon/claude-codex-settings --skill openship-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install fcakyon/claude-codex-settings openship-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/openship-skills/skills/openship-deploy .cursor/skills/openship-deploy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openship-deploy" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/openship-skills/skills/openship-deploy into .cursor/skills/openship-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openship-deploy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/fcakyon/claude-codex-settings.git --path plugins/openship-skills/skills/openship-deploy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add fcakyon/claude-codex-settings --skill openship-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install fcakyon/claude-codex-settings openship-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/openship-skills/skills/openship-deploy .gemini/skills/openship-deploy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openship-deploy" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/openship-skills/skills/openship-deploy into .gemini/skills/openship-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openship-deploy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install fcakyon/claude-codex-settings openship-deployInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add fcakyon/claude-codex-settings --skill openship-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/openship-skills/skills/openship-deploy .github/skills/openship-deploy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openship-deploy" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/openship-skills/skills/openship-deploy into .github/skills/openship-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openship-deploy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fcakyon/claude-codex-settings --skill openship-deploy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install fcakyon/claude-codex-settings openship-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fcakyon/claude-codex-settings.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/openship-skills/skills/openship-deploy .opencode/skills/openship-deploy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openship-deploy" agent skill from https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/openship-skills/skills/openship-deploy into .opencode/skills/openship-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openship-deploy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
openship-deploy- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 450 words
- Files
- 22 (incl. references)
- Skills in repo
- 43
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
This skill should be used when the user asks to "deploy with OpenShip", "manage a self-hosted OpenShip instance", "debug an OpenShip deployment", or manage its domains, storage, backups, or upgrades…
- Works in 4 steps: Inspect the repository, existing project… → Use the companion openship-config skill… → Run openship --json config validate,… → …
- Asks to deploy with OpenShip
- SKILL.md covers Choose the instance and command, Deploy an application and Maintain the self-hosted…
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Openship Deploy is an agent skill from fcakyon/claude-codex-settings. This skill should be used when the user asks to "deploy with OpenShip", "manage a self-hosted OpenShip instance", "debug an OpenShip deployment", or manage its domains, storage, backups, or upgrades through the CLI.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 24 other files, including reference files.
It sits in DevOps & Cloud, covering Deployment and Backup and disaster recovery. The repository describes itself as: Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support. The licence is Apache-2.0.
When your agent uses it
- Asks to deploy with OpenShip
- Manage a self-hosted OpenShip instance
- Debug an OpenShip deployment
- Manage its domains
Example prompts
- “deploy with OpenShip”
- “manage a self-hosted OpenShip instance”
- “debug an OpenShip deployment”
- “/openship-deploy”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Inspect the repository, existing project link, build entry point, service topology, persistent volumes, and current domain ownership. Use…
- Use the companion openship-config skill to author a small openship.json. When only this ZIP is installed, use the official config guide…
- Run openship --json config validate, then use deployment commands for the appropriate repository or folder deploy. A valid file does not…
- Check deployment completion, the active deployment, service health, logs, and the public URL. Report the deployed revision and any checks…
What it can do on your machine
Read from SKILL.md and the folder at commit a035b4e. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
openship.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Openship Deploy loads about 1k tokens when it runs, and up to ~36k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 450 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from fcakyon/claude-codex-settings at commit a035b4e, republished under its Apache-2.0 licence (© fcakyon). 450 words, ~1,017 tokens.
Download SKILL.mdSave it as
.claude/skills/openship-deploy/SKILL.md (or your agent's skills folder). This skill also uses 21 other files; get the full folder from GitHub.- name
- openship-deploy
- description
- This skill should be used when the user asks to "deploy with OpenShip", "manage a self-hosted OpenShip instance", "debug an OpenShip deployment", or manage its domains, storage, backups, or upgrades through the CLI.
Deploy and operate OpenShip
Prefer the CLI and an existing self-hosted instance. Use a cloud or desktop workflow when the user requests it. Keep application deployments separate from installing or upgrading the OpenShip control plane.
Choose the instance and command
- Check
openship --versionandopenship context list. Select the intended self-hosted context before a remote operation. Never assume the active context points to the user's server. - Use native commands with the global
--jsonflag. Read CLI access for context and authentication details, and automation for CI logins and scripts that pass explicit project IDs. Do not print stored tokens. - Check the installed command's
--help. Useopenship apifor routes without a working command, after checking the matching implementation. In v0.8.0,server sshis a stub despite appearing in help. A successful help command does not prove an operation works. - upstream.json records the bundled release, exact source URLs, and hashes. If the installed CLI or server differs, verify the relevant source at that version before relying on a flag or API contract.
Deploy an application
- Inspect the repository, existing project link, build entry point, service topology, persistent volumes, and current domain ownership. Use projects and services for commands.
- Use the companion
openship-configskill to author a smallopenship.json. When only this ZIP is installed, use the official config guide. Keep repeatable build and routing choices in the repository. Keep actual credentials in the instance's environment settings. - Run
openship --json config validate, then use deployment commands for the appropriate repository or folder deploy. A valid file does not prove its image builds or that the destination has sufficient capacity. - Check deployment completion, the active deployment, service health, logs, and the public URL. Report the deployed revision and any checks still pending. Use edge and monitoring and logs for diagnosis, and build failures when the deploy goes red.
Show full SKILL.md (141 more words)Show less
Read only the guide needed for the operation:
- Self-hosted GitHub App: repository authorization and automatic deployment.
- Domains: ownership, DNS, ports, and HTTPS. Reconcile existing ownership before moving a hostname. Domain and SSL failures covers certificates that do not issue.
- Rollback and redeploy: return to a previous version or rebuild one from scratch.
- Persistent storage: volumes and data that must survive redeployment.
Maintain the self-hosted instance
Use self-host infrastructure for servers and backups, and running OpenShip for lifecycle commands. Inspect how the instance was installed and whether it has a custom updater before selecting an upgrade command.
- Updates: CLI and server lifecycle.
- Backups and restore: protection and recovery of application data.
- Instance migration: control-plane export and import.
Use the user's existing authorization for the requested operation. Preparing a deployment is not authorization to replace a running instance or restore over its data.
© fcakyon, 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 21 other files (references) in plugins/openship-skills/skills/openship-deploy of fcakyon/claude-codex-settings.
- SKILL.md
- LICENSE
- references/cli/access.mdx
- references/cli/automation.mdx
- references/cli/deploy.mdx
- references/cli/edge.mdx
- references/cli/index.mdx
- references/cli/projects.mdx
- references/cli/run.mdx
- references/cli/self-host.mdx
- references/guides/backups-restore.mdx
- references/guides/custom-domains.mdx
- references/guides/logs-monitoring.mdx
- references/guides/migrate-control-plane.mdx
- references/guides/persistent-storage.mdx
- references/guides/rollback-redeploy.mdx
- references/guides/self-hosted-github-app.mdx
- references/guides/updating.mdx
- … and 4 more
Open the folder on GitHubat commit a035b4e
Compare with similar skills
Openship Deploy 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openship Deploy this skillfcakyon/claude-codex-settings | 1.2k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Temps CLIgotempsh/temps | 822 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Azure Resource Manager Mysql Dotnetmicrosoft/skills | 3.1k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Azure Resource Manager Postgresql Dotnetmicrosoft/skills | 3.1k | 6 repos | ~4k | Automated safety check: Pass | MIT | |
| Routing Architecturemajiayu000/litellm-rs | 116 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Supercheck Infrastructure Deploymentsupercheck-io/supercheck | 215 | — | ~1.4k | Automated safety check: Notes | AGPL-3.0 |
Similar skills
- Official
Azure Resource Manager Mysql Dotnet
microsoft/skills
Azure MySQL Flexible Server SDK for .NET. An agent skill from microsoft/skills.
- Official
Azure Resource Manager Postgresql Dotnet
microsoft/skills
Azure PostgreSQL Flexible Server SDK for .NET. An agent skill from microsoft/skills.
Routing Architecture
majiayu000/litellm-rs
LiteLLM-RS Routing Architecture. An agent skill from majiayu000/litellm-rs.
Supercheck Infrastructure Deployment
supercheck-io/supercheck
Work on Supercheck Docker Compose, K3s, Kubernetes manifests, gVisor, OpenTofu/Hetzner, secrets, external services, autoscaling, backups, disaster recovery, DNS/TLS, or production deployment.
- Official
Preset
microsoft/GitHub-Copilot-for-Azure
Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions.
More from fcakyon/claude-codex-settings
All 43 skills in this repoSlides
fcakyon/claude-codex-settings
Create and edit presentation slide decks (.pptx) with PptxGenJS, bundled layout helpers, and render/validation utilities.
Openobserve API
fcakyon/claude-codex-settings
This skill should be used when user asks to "query OpenObserve", "create OpenObserve dashboard", "edit OpenObserve panel", "fetch OpenObserve logs", "run OpenObserve search", "list OpenObserve…
Supabase JS
fcakyon/claude-codex-settings
This skill should be used when user asks to "use supabase-js", "query Supabase database", "supabase auth", "supabase storage", "supabase realtime", "supabase edge functions", or works with the…
Yolo Training
fcakyon/claude-codex-settings
This skill should be used when user asks to "improve my mAP", "why is my model overfitting", "my training is diverging", "read my results.csv", "interpret my training curves", "my AP50 is good but…
Dokploy Deploy
fcakyon/claude-codex-settings
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure…
Openship Config
fcakyon/claude-codex-settings
This skill should be used when the user asks to "create openship.json", "configure an OpenShip deployment", "make a repo deployable on OpenShip", or fix "openship config validate" errors.
Related
Categories
Questions about Openship Deploy
What does Openship Deploy do?
This skill should be used when the user asks to "deploy with OpenShip", "manage a self-hosted OpenShip instance", "debug an OpenShip deployment", or manage its domains, storage, backups, or upgrades…. Openship Deploy is an agent skill from fcakyon/claude-codex-settings. This skill should be used when the user asks to "deploy with OpenShip", "manage a self-hosted OpenShip instance", "debug an OpenShip deployment", or manage its domains, storage, backups, or upgrades through the CLI.
When should I use Openship Deploy?
Openship Deploy fits situations like: asks to deploy with OpenShip; manage a self-hosted OpenShip instance; debug an OpenShip deployment; manage its domains.
How do I install Openship Deploy in Claude Code?
Run `npx skills add fcakyon/claude-codex-settings --skill openship-deploy -a claude-code`. Or copy the skill folder (plugins/openship-skills/skills/openship-deploy in fcakyon/claude-codex-settings) into .claude/skills/openship-deploy in your project. Claude Code loads it when a task matches its description.
How do I install Openship Deploy in Codex?
Run `npx skills add fcakyon/claude-codex-settings --skill openship-deploy -a codex`. Or copy the skill folder (plugins/openship-skills/skills/openship-deploy in fcakyon/claude-codex-settings) into .agents/skills/openship-deploy in your project. Codex loads it when a task matches its description.
Can I use Openship Deploy 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 fcakyon/claude-codex-settings --skill openship-deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openship-deploy, .gemini/skills/openship-deploy, .github/skills/openship-deploy and .opencode/skills/openship-deploy in your project.
What does Openship Deploy need to run?
SKILL.md names no scripts, command-line tools or credentials: Openship Deploy is instructions for the agent only.
Does Openship Deploy access the network?
SKILL.md names 1 domain. As links in the text: openship.io. This is read from the text; nothing was executed.
Is Openship Deploy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Openship Deploy use?
Openship Deploy is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Openship Deploy use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 35k tokens, read only when the agent opens those files.
What are the alternatives to Openship Deploy?
Skills that share tags, products or a category with Openship Deploy: Temps CLI (gotempsh/temps, 822 stars), Azure Resource Manager Mysql Dotnet (microsoft/skills, 3.1k stars), Azure Resource Manager Postgresql Dotnet (microsoft/skills, 3.1k stars) and Routing Architecture (majiayu000/litellm-rs, 116 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openship Deploy?
fcakyon (a GitHub user) maintains it in fcakyon/claude-codex-settings, which has 1,163 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 6, 2026.
Source: fcakyon/claude-codex-settings on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.