Os Usage
goinfinite/os
A skill your agent uses when deploying or managing applications on an Infinite OS instance — maps the dashboard, CLI, and REST API, and gives the core deployment workflows.
Check and deploy Signal (the remote-api service in remote/) to production from a release tag.
Install Signal Deploy
$ npx skills add nightly-labs/openbot --skill signal-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nightly-labs/openbot signal-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/nightly-labs/openbot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/signal-deploy .claude/skills/signal-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 "signal-deploy" agent skill from https://github.com/nightly-labs/openbot/tree/main/.agents/skills/signal-deploy into .claude/skills/signal-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-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/nightly-labs/openbot/tree/main/.agents/skills/signal-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 nightly-labs/openbot --skill signal-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nightly-labs/openbot signal-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nightly-labs/openbot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/signal-deploy .agents/skills/signal-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 "signal-deploy" agent skill from https://github.com/nightly-labs/openbot/tree/main/.agents/skills/signal-deploy into .agents/skills/signal-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-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 nightly-labs/openbot --skill signal-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nightly-labs/openbot signal-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nightly-labs/openbot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/signal-deploy .cursor/skills/signal-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 "signal-deploy" agent skill from https://github.com/nightly-labs/openbot/tree/main/.agents/skills/signal-deploy into .cursor/skills/signal-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-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/nightly-labs/openbot.git --path .agents/skills/signal-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 nightly-labs/openbot --skill signal-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nightly-labs/openbot signal-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nightly-labs/openbot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/signal-deploy .gemini/skills/signal-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 "signal-deploy" agent skill from https://github.com/nightly-labs/openbot/tree/main/.agents/skills/signal-deploy into .gemini/skills/signal-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-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 nightly-labs/openbot signal-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 nightly-labs/openbot --skill signal-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nightly-labs/openbot.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/signal-deploy .github/skills/signal-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 "signal-deploy" agent skill from https://github.com/nightly-labs/openbot/tree/main/.agents/skills/signal-deploy into .github/skills/signal-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-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 nightly-labs/openbot --skill signal-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 nightly-labs/openbot signal-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nightly-labs/openbot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/signal-deploy .opencode/skills/signal-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 "signal-deploy" agent skill from https://github.com/nightly-labs/openbot/tree/main/.agents/skills/signal-deploy into .opencode/skills/signal-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "signal-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
signal-deploy- GitHub stars
- 489
- Token cost
- ~2k tokens
- SKILL.md length
- 984 words
- Files
- 2
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Check and deploy Signal (the remote-api service in remote/) to production from a release tag.
- Works in 5 steps: Find the running version → Check for regressions → Check the secrets → …
- Asked to deploy
- SKILL.md covers When to deploy, Rules, 1. Find the running version and 2. Check for regressions, plus 4 more sections
- Calls git, ssh and curl; reaches signal.openbot.run and api.openbot.run
What it does
Signal Deploy is an agent skill from nightly-labs/openbot. Check and deploy Signal (the remote-api service in remote/) to production from a release tag. Use when asked to deploy, redeploy, update or roll back Signal, to check that a Signal deployment has all its secrets and no regressions, or when a release tag changes remote/ or packages/contracts/src/signal-protocol.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in DevOps & Cloud, covering Deployment. The repository describes itself as: A local-first desktop workspace for persistent AI teammates. Run Codex, Claude, and Grok with dedicated workspaces, task queues, file sharing, browser control, and agent-to-agent…
When your agent uses it
- Asked to deploy
- Roll back Signal
- Check that a Signal deployment has all its secrets and no regressions
- A release tag changes remote/
Example prompts
- “/signal-deploy”
Requirements
- Docker
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Find the running version
- Check for regressions
- Check the secrets
- Deploy
- Verify
What it can do on your machine
Read from SKILL.md and the folder at commit c7d6ee9. 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
Shell commands in SKILL.md call:
gitsshcurlbundocker
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
signal.openbot.runapi.openbot.run
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
Signal Deploy loads about 2k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 984 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:32
the host, or log an environment value, `.env.keys`, a container environment, - NoteMentions a .env fileSKILL.md:34
eads the host files `/opt/openbot/remote/.env.production` and `.env.keys` through - NoteMentions a .env fileSKILL.md:35
symlinks, not the `remote/.env.production` of the tag. The two files can differ. - NoteMentions a .env fileSKILL.md:94
git show <tag>:remote/.env.production | grep -vE '^#|^$' | cut -d= -f1 | sort - NoteMentions a .env fileSKILL.md:95
ia "grep -vE '^#|^$' /opt/openbot/remote/.env.production | cut -d= -f1 | sort" - NoteMentions a .env fileSKILL.md:99
`.env.keys` decrypts the encrypted values of the tag file. - NoteMentions a .env fileSKILL.md:101
file, run `bin/dotenvx get -f <file> -fk .env.keys` for each file, and print - NoteMentions a .env fileSKILL.md:105
`cp .env.production .env.production.bak-<date>-<reason>`. Do not replace the whole host file.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 984 words (~2,017 tokens).
“Signal runs on sui-alexandria in the Compose project openbot-remote (/opt/openbot/remote). It has no database: a restart closes the signalling WebSockets and empties the in-memory rooms, routes and resume-token cache. Active WebRTC data channels stay up. coturn is a separate container.”
- name
- signal-deploy
Files
SKILL.md and 1 other file in .agents/skills/signal-deploy of nightly-labs/openbot.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit c7d6ee9
Compare with similar skills
Signal 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 |
|---|---|---|---|---|---|---|
| Signal Deploy this skillnightly-labs/openbot | 489 | — | ~2k | Automated safety check: Notes | Custom licence | |
| Os Usagegoinfinite/os | 361 | — | ~4.8k | Automated safety check: Notes | GPL-2.0 | |
| Protocol Deploymentsablier-labs/evm-monorepo | 353 | — | ~3.8k | Automated safety check: Notes | Custom licence | |
| Release Allpaperboytm/spool | 592 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| AI ServerOpentrons/opentrons | 523 | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Monstermq Broker Configvogler75/monster-mq | 143 | — | ~2.2k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Protocol Deployment
sablier-labs/evm-monorepo
Deploy Sablier protocols to a new EVM chain. An agent skill from sablier-labs/evm-monorepo.
Release All
paperboytm/spool
Publish the complete Spool CLI release train: synchronized versions, npm packages, the GitHub release, and the matching production web deployment.
AI Server
Opentrons/opentrons
Conventions for the opentrons-ai-server FastAPI service — project structure, uv dependency management, settings, testing, Docker, and deployment.
Monstermq Broker Config
vogler75/monster-mq
Guide for configuring, deploying, and operating the MonsterMQ broker.
Deploy
clacky-ai/openclacky
Deploy Rails applications to Railway. An agent skill from clacky-ai/openclacky.
More from nightly-labs/openbot
All 15 skills in this repoBiome Anti Slop
nightly-labs/openbot
Install and configure vendored Biome anti-slop GritQL rules in a local TypeScript or JavaScript repository.
Release Upgrade Safety
nightly-labs/openbot
Audit a pending OpenBot release for upgrade and data-loss hazards before the version is bumped or tagged.
Babysit
nightly-labs/openbot
Babysit a pull request through the NorbiAI review loop until no valid issue remains.
Openbot Export
nightly-labs/openbot
Export the user's Grok Bot agents into one .zip file that OpenBot imports, with instructions, avatars, skills, routines, memories, group chats, and optional workspace files.
Ship
nightly-labs/openbot
Ship the current branch to main. An agent skill from nightly-labs/openbot.
Smoke
nightly-labs/openbot
Start one or more local OpenBot dev instances and smoke test the features that the current changes or a pull request add.
Related
Categories
Questions about Signal Deploy
What does Signal Deploy do?
Check and deploy Signal (the remote-api service in remote/) to production from a release tag. Signal Deploy is an agent skill from nightly-labs/openbot. Check and deploy Signal (the remote-api service in remote/) to production from a release tag.
When should I use Signal Deploy?
Signal Deploy fits situations like: asked to deploy; roll back Signal; check that a Signal deployment has all its secrets and no regressions; A release tag changes remote/.
How do I install Signal Deploy in Claude Code?
Run `npx skills add nightly-labs/openbot --skill signal-deploy -a claude-code`. Or copy the skill folder (.agents/skills/signal-deploy in nightly-labs/openbot) into .claude/skills/signal-deploy in your project. Claude Code loads it when a task matches its description.
How do I install Signal Deploy in Codex?
Run `npx skills add nightly-labs/openbot --skill signal-deploy -a codex`. Or copy the skill folder (.agents/skills/signal-deploy in nightly-labs/openbot) into .agents/skills/signal-deploy in your project. Codex loads it when a task matches its description.
Can I use Signal 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 nightly-labs/openbot --skill signal-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/signal-deploy, .gemini/skills/signal-deploy, .github/skills/signal-deploy and .opencode/skills/signal-deploy in your project.
What does Signal Deploy need to run?
Going by SKILL.md and its folder, Signal Deploy needs the command-line tools its instructions call (git, ssh, curl, bun and docker). Our summary lists: Docker.
Does Signal Deploy access the network?
SKILL.md names 2 domains. In commands or code: signal.openbot.run and api.openbot.run; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Signal Deploy 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. Review the folder before installing.
What licence does Signal Deploy use?
Signal Deploy has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Signal Deploy use?
About 2k tokens (SKILL.md is roughly 8.1k 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 Signal Deploy?
Skills that share tags, products or a category with Signal Deploy: Os Usage (goinfinite/os, 361 stars), Protocol Deployment (sablier-labs/evm-monorepo, 353 stars), Release All (paperboytm/spool, 592 stars) and AI Server (Opentrons/opentrons, 523 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Signal Deploy?
nightly-labs (a GitHub organization) maintains it in nightly-labs/openbot, which has 489 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.
Source: nightly-labs/openbot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.