Agent skill

Deploy

Deploy and infrastructure: web deploy, dev branches, cron, package install, shell configuration.

MITAuto-check: notesProductivity & Automation

Install Deploy

skills CLI

$ npx skills add notque/vexjoy-agent --skill deploy -a claude-code

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

GitHub CLI

$ gh skill install notque/vexjoy-agent deploy --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/notque/vexjoy-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/infrastructure/deploy .claude/skills/deploy && 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/

Paste into Claude Code

Install the "deploy" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/infrastructure/deploy into .claude/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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

$skill-installer install https://github.com/notque/vexjoy-agent/tree/main/skills/infrastructure/deploy

Type 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.

skills CLI

$ npx skills add notque/vexjoy-agent --skill deploy -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install notque/vexjoy-agent deploy --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/infrastructure/deploy .agents/skills/deploy && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "deploy" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/infrastructure/deploy into .agents/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.

skills CLI

$ npx skills add notque/vexjoy-agent --skill deploy -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install notque/vexjoy-agent deploy --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/infrastructure/deploy .cursor/skills/deploy && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "deploy" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/infrastructure/deploy into .cursor/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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

$ gemini skills install https://github.com/notque/vexjoy-agent.git --path skills/infrastructure/deploy

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add notque/vexjoy-agent --skill deploy -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install notque/vexjoy-agent deploy --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/infrastructure/deploy .gemini/skills/deploy && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "deploy" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/infrastructure/deploy into .gemini/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.

GitHub CLI

$ gh skill install notque/vexjoy-agent deploy

Installs 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).

skills CLI

$ npx skills add notque/vexjoy-agent --skill deploy -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/infrastructure/deploy .github/skills/deploy && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "deploy" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/infrastructure/deploy into .github/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.

skills CLI

$ npx skills add notque/vexjoy-agent --skill deploy -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install notque/vexjoy-agent deploy --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/infrastructure/deploy .opencode/skills/deploy && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "deploy" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/infrastructure/deploy into .opencode/skills/deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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: deploy
GitHub stars: 438
Token cost: ~2.6k tokens
SKILL.md length: 934 words
Files: 25 (incl. references)
Skills in repo: 61
Repo updated: Oct 3, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Deploy and infrastructure: web deploy, dev branches, cron, package install, shell configuration.

Works in 5 steps: DNS: Create A/AAAA record. Verify: dig… → Web Server: nginx server block with… → HTTPS: certbot --nginx -d . Verify… → …
Tasks that involve Scheduled and recurring tasks
SKILL.md covers A. Public Web Deploy, B. Dev-Branch Deploy, C. Cron Automation and D. Headless Cron Creator, plus 4 more sections
Calls python3, curl and git

What it does

Deploy is an agent skill from notque/vexjoy-agent. Deploy and infrastructure: web deploy, dev branches, cron, package install, shell configuration.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 25 other files, including reference files (for example `references/cleanup-verification.md`, `references/concurrency-and-locks.md` and `references/cron-automation.md`).

It sits in Productivity & Automation, covering Scheduled and recurring tasks. It works with NGINX. The repository describes itself as: VexJoy AI Agent with Jev Intelligent Routing - /do routes plain-English requests to the right specialist agent and gates the work with reviews, tests, and a learning loop. The licence is MIT.

When your agent uses it

Tasks that involve Scheduled and recurring tasks

Example prompts

“/deploy”

Requirements

Python 3
Pre-approved tools (allowed-tools): Read, Write, Bash, Grep, Glob, Edit, Agent

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

DNS: Create A/AAAA record. Verify: dig +short A . Gate: resolves to intended IP.
Web Server: nginx server block with explicit docroot. Backend proxied to 127.0.0.1. Test: nginx -t && systemctl reload nginx.
HTTPS: certbot --nginx -d . Verify renewal: certbot renew --dry-run. Verify redirect: curl -sI http:// | grep -iE '301|308'.
Hardening: Firewall (ufw allow 80/443/SSH only), nginx deny rules (location ~ /. { deny all; }), security headers (HSTS…
Verify: Run the 13-item security checklist. Spot-check: curl -s https:///.env -w '%{http_code}\n' (expect 403/404), ss -tlnp (no app ports…

What it can do on your machine

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

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Write
- Bash
- Grep
- Glob
- Edit
- Agent
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python3
- curl
- git
- fly
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl and git, which can reach the network depending on how they are called.
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

Deploy loads about 2.6k tokens when it runs, and up to ~54k if it reads all its reference files. Until then it costs about 26 tokens; SKILL.md has 934 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~26
When it runs · the whole SKILL.md, loaded when a task matches: ~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~54k

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:86

ist. Spot-check: `curl -s https://<fqdn>/.env -w '%{http_code}\n'` (expect 403/404), `ss -tlnp` (no app ports public).

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Write, Bash, Grep, Glob, Edit, Agent
```

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 notque/vexjoy-agent at commit 5218674, republished under its MIT licence (© notque). 934 words, ~2,556 tokens.

Download SKILL.mdSave it as .claude/skills/deploy/SKILL.md (or your agent's skills folder). This skill also uses 24 other files; get the full folder from GitHub.

name: deploy
description: Deploy and infrastructure: web deploy, dev branches, cron, package install, shell configuration.
allowed-tools: Read, Write, Bash, Grep, Glob, Edit, Agent
user-invocable: true
routing.force_route: true
routing.not_for: Kubernetes or Helm (use kubernetes skill), Ansible (agents handle directly), code review (use review), security scanning (use security)
routing.triggers: deploy website, deploy site, go live, public site, public website, static site, landing page, make it public, make public, set up https, nginx public site…
routing.category: infrastructure
routing.pairs_with: assessment, kubernetes, pr-workflow

Deploy Skill

Six modes. Match the request to a section.

Signal	Section
Deploy site, HTTPS, nginx, go live, public site	A. Public Web Deploy
Dev branch, Concourse dev lane, hermes/maia	B. Dev-Branch Deploy
Cron job, scheduled task, audit cron script	C. Cron Automation
Headless agent, wrapper script, recurring Claude task	D. Headless Cron Creator
Install toolkit, verify setup, health check	E. Toolkit Install
Fish shell, Zsh, shell config, migration	F. Shell Configuration
Background process, nohup, trap, PID, signals	G. Process Management

When the request spans modes, compose the relevant sections.

A. Public Web Deploy

Serve public sites through nginx/Caddy/Apache -- never a raw dev server. Local preview binds 127.0.0.1; public sites require HTTPS + hardened nginx.

5-phase workflow: DNS -> Web Server -> HTTPS -> Hardening -> Verify.

DNS: Create A/AAAA record. Verify: dig +short A <fqdn>. Gate: resolves to intended IP.
Web Server: nginx server block with explicit docroot. Backend proxied to 127.0.0.1. Test: nginx -t && systemctl reload nginx.
HTTPS: certbot --nginx -d <fqdn>. Verify renewal: certbot renew --dry-run. Verify redirect: curl -sI http://<fqdn> | grep -iE '301|308'.
Hardening: Firewall (ufw allow 80/443/SSH only), nginx deny rules (location ~ /\. { deny all; }), security headers (HSTS, X-Content-Type-Options, CSP in Report-Only), rate limiting (limit_req), fail2ban.
Verify: Run the 13-item security checklist. Spot-check: curl -s https://<fqdn>/.env -w '%{http_code}\n' (expect 403/404), ss -tlnp (no app ports public).

Load references/public-web-deploy.md for the full 13-item checklist, nginx config blocks, and error handling.

B. Dev-Branch Deploy

Test Hermes or Maia stack changes in a live lab region before merging to master via Concourse dev lane.

Preflight: Verify dev branch on both repos + pipeline wired.
Merge feature into dev branch: git checkout <stack>-dev-branch && git merge --no-ff origin/<feature> && git push. Never force-push.
Validate: Dev lane green. fly -t <target> watch -j <stack>/deploy-to-dev-<region>.
Merge to master via PR after dev validation.

Load references/dev-branch-deploy.md for stack parameters, preflight commands, and pipeline regeneration.

C. Cron Automation

Static analysis of cron scripts against a 9-point reliability checklist. Read-only -- never execute scripts.

DISCOVER: Locate scripts in scripts/*.sh, cron/*.sh, jobs/*.sh. Verify shell shebang.
AUDIT: Run all 9 checks via regex (verify matches not in comments):

#	Check	Severity	Key patterns
1	Error handling	CRITICAL	`set -e`, `set -o errexit`
2	Exit code checking	HIGH	`$?`, `if [ $? -eq`
3	Logging with timestamps	HIGH	`>> *.log`, `$(date)`
4	Log rotation	MEDIUM	`find -mtime -delete`, `logrotate`
5	Working directory	HIGH	`cd "$(dirname"`, `SCRIPT_DIR=`
6	PATH environment	MEDIUM	`PATH=`, `export PATH`
7	Lock file / concurrency	HIGH	`.lock`, `flock`, `.pid`
8	Cleanup on exit	MEDIUM	`trap ... EXIT`
9	Failure notification	LOW	`mail -s`, `curl *webhook`

REPORT: Per-script scores with paste-ready fixes for every FAIL/WARN. Aggregate summary for multi-script audits.

Load references/cron-automation.md for the best-practices reference script.

D. Headless Cron Creator

Create headless Claude Code cron jobs. All crontab mutations go through crontab-manager.py.

PARSE: Extract name (kebab-case), prompt, schedule, workdir, budget ($2.00 default).
GENERATE: python3 ~/.claude/scripts/crontab-manager.py generate-wrapper --name <name> .... Verify: flock, --permission-mode auto, --max-budget-usd, tee logging, dry-run default.
VALIDATE: bash -n scripts/<name>-cron.sh. Run 9-point cron checklist.
INSTALL: Dry-run first (--dry-run), ask user confirmation, then install.
REPORT: Script path, schedule, log dir, budget, management commands.

Load references/headless-cron-creator.md for the full methodology and schedule conversion table.

E. Toolkit Install

Run python3 ~/.claude/scripts/install-doctor.py check and python3 ~/.claude/scripts/toolkit-health.py --json.
If issues: guide user to ./install.sh --symlink. Fix permissions and deps as needed.
Show inventory: python3 ~/.claude/scripts/install-doctor.py inventory.
Show MCP status: python3 ~/.claude/scripts/mcp-registry.py list.
Orient: /do, /comprehensive-review, /install commands.

Load references/install.md for full diagnostic steps and error handling.

Show full SKILL.md (351 more words)Show less

F. Shell Configuration

Detect target shell first. Fish and Zsh have incompatible syntax.

Concept	Fish	Zsh
Variable assignment	`set -gx VAR value`	`export VAR=value`
PATH management	`fish_add_path`	`typeset -U path; path=(...)`
Completions	`completions/` directory	`compinit` + `fpath`
Conditionals	`test`, not `[[ ]]`	`[[ ]]` preferred
Interactive guard	`status is-interactive`	`[[ -o interactive ]]`

Load the shell-specific reference matching the task:

Task	Fish	Zsh
Full config	`references/fish-shell-config.md`	`references/zsh-shell-config.md`
Migration from Bash	`references/fish-bash-migration.md`	`references/zsh-bash-migration.md`
Variables, special vars	`references/fish-quick-reference.md`	`references/zsh-quick-reference.md`
Error audit, failure modes	`references/fish-preferred-patterns.md`	`references/zsh-preferred-patterns.md`
Dev tool integration	`references/fish-tool-integrations.md`	`references/zsh-tool-integrations.md`

G. Process Management

Match the need to the pattern:

Goal	Command
Background job, exits with shell	`cmd &`
Survive shell exit	`nohup cmd > log 2>&1 &`
Detach from job control	`cmd & disown`
Full detach, new session	`setsid cmd > log 2>&1 < /dev/null &`
System daemon	systemd unit file

All backgrounded processes must redirect stdio: > out 2>&1 < /dev/null &. Order matters: > out 2>&1 is correct; 2>&1 > out is almost always a bug.

Key rule: verify the observable state (port free, PID dead) after every kill -- do not assume kill succeeded.

Load deep references for specific tasks:

Task	Reference
Process lifecycle patterns	`references/shell-process-patterns.md`, `references/starting-processes.md`
PID capture and resolution	`references/pid-resolution.md`
Signal and trap discipline	`references/signals-and-traps.md`
Kill verification, stale PID	`references/cleanup-verification.md`
Shell gotchas (`set -e`, `

Deep References

All references below are >100 lines of domain-specific content. Load as directed by the sections above.

Reference	Lines	Domain
`references/public-web-deploy.md`	259	Full public deploy workflow + security checklist
`references/dev-branch-deploy.md`	156	Concourse dev-branch workflow
`references/cron-automation.md`	194	9-point cron audit checklist
`references/headless-cron-creator.md`	150	Headless cron job creation
`references/install.md`	195	Toolkit install and health check
`references/shell-error-handling.md`	226	Shell error handling patterns
`references/concurrency-and-locks.md`	219	Concurrency and locking
`references/logging-and-rotation.md`	231	Logging and rotation
`references/starting-processes.md`	152	Process start patterns
`references/shell-process-patterns.md`	247	Process lifecycle patterns
`references/pid-resolution.md`	200	PID capture and resolution
`references/signals-and-traps.md`	259	Signal and trap discipline
`references/cleanup-verification.md`	253	Kill-and-check verification
`references/preferred-patterns.md`	354	Shell gotchas and fixes
`references/fish-shell-config.md`	247	Fish shell configuration
`references/fish-bash-migration.md`	149	Bash-to-Fish migration
`references/fish-quick-reference.md`	229	Fish variable scope guide
`references/fish-preferred-patterns.md`	240	Fish failure modes
`references/fish-tool-integrations.md`	318	Fish dev tool patterns
`references/zsh-shell-config.md`	310	Zsh shell configuration
`references/zsh-bash-migration.md`	248	Bash-to-Zsh migration
`references/zsh-quick-reference.md`	332	Zsh parameter expansion
`references/zsh-preferred-patterns.md`	290	Zsh failure modes
`references/zsh-tool-integrations.md`	368	Zsh dev tool patterns

Files

SKILL.md and 24 other files (references) in skills/infrastructure/deploy of notque/vexjoy-agent.

SKILL.md
references/cleanup-verification.md
references/concurrency-and-locks.md
references/cron-automation.md
references/dev-branch-deploy.md
references/fish-bash-migration.md
references/fish-preferred-patterns.md
references/fish-quick-reference.md
references/fish-shell-config.md
references/fish-tool-integrations.md
references/headless-cron-creator.md
references/install.md
references/logging-and-rotation.md
references/pid-resolution.md
references/preferred-patterns.md
references/public-web-deploy.md
references/shell-error-handling.md
references/shell-process-patterns.md
references/signals-and-traps.md
references/starting-processes.md
… and 5 more

Open the folder on GitHubat commit 5218674

Compare with similar skills

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.

Deploy compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Deploy this skillnotque/vexjoy-agent	438	—	~2.6k	Automated safety check: Notes	MIT	5 days ago
Cronalytics8bit64k/cronalytics	112	—	~4.7k	Automated safety check: Pass	MIT	3 mo ago
Schedule Recipemohitagw15856/pm-claude-skills	1.4k	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Wp Wpcli And Opsjorgerosal/wordpress-skills	101	—	~326	Automated safety check: Pass	MIT	4 mo ago
Shadowvpn Deploy Clientmadeye/shadowvpn	101	—	~2.4k	Automated safety check: Notes	MIT	1 mo ago
Gram Temporalspeakeasy-api/gram	272	—	~2.6k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Cronalytics
8bit64k/cronalytics
Analyze, diagnose, and optimize Hermes cron jobs via the cronalytics CLI.
112 GitHub stars~4.7k tokensUpdated 3 mo ago
Productivity & AutomationAuto-check passed
Schedule Recipe
mohitagw15856/pm-claude-skills
Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner.
1.4k GitHub stars~1.1k tokensUpdated yesterday
Productivity & AutomationAuto-check passed
Wp Wpcli And Ops
jorgerosal/wordpress-skills
WordPress WP-CLI and operations review for Codex. An agent skill from jorgerosal/wordpress-skills.
101 GitHub stars~326 tokensUpdated 4 mo ago
Productivity & AutomationAuto-check passed
Shadowvpn Deploy Client
madeye/shadowvpn
Deploy, install, and run the ShadowVPN client in a target environment — Linux (systemd), macOS (launchd), or Windows (Wintun, foreground launcher or scheduled-task service).
101 GitHub stars~2.4k tokensUpdated 1 mo ago
Productivity & AutomationAuto-check: notes
Gram Temporal
speakeasy-api/gram
A skill your agent uses when adding or changing background work in gram — a Temporal workflow, activity, schedule, signal, or ContinueAsNew loop; anything reacting to chat messages, tool calls, MCP…
272 GitHub stars~2.6k tokensUpdated today
DevOps & CloudAuto-check passed
Hunting For Persistence Mechanisms In Windows
mukul975/Anthropic-Cybersecurity-Skills
Systematically hunts for adversary persistence mechanisms across Windows endpoints, covering registry Run/RunOnce keys, services, startup folders, scheduled tasks, and WMI event subscriptions.
34k GitHub stars~1.2k tokensUpdated 1 mo ago
Productivity & AutomationAuto-check passed

Questions about Deploy

What does Deploy do?

Deploy and infrastructure: web deploy, dev branches, cron, package install, shell configuration. Deploy is an agent skill from notque/vexjoy-agent. Deploy and infrastructure: web deploy, dev branches, cron, package install, shell configuration.

When should I use Deploy?

Deploy fits situations like: tasks that involve Scheduled and recurring tasks.

How do I install Deploy in Claude Code?

Run `npx skills add notque/vexjoy-agent --skill deploy -a claude-code`. Or copy the skill folder (skills/infrastructure/deploy in notque/vexjoy-agent) into .claude/skills/deploy in your project. Claude Code loads it when a task matches its description.

How do I install Deploy in Codex?

Run `npx skills add notque/vexjoy-agent --skill deploy -a codex`. Or copy the skill folder (skills/infrastructure/deploy in notque/vexjoy-agent) into .agents/skills/deploy in your project. Codex loads it when a task matches its description.

Can I use 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 notque/vexjoy-agent --skill 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/deploy, .gemini/skills/deploy, .github/skills/deploy and .opencode/skills/deploy in your project.

What does Deploy need to run?

Going by SKILL.md and its folder, Deploy needs the command-line tools its instructions call (python3, curl, git, fly and bash). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Bash, Grep, Glob, Edit, Agent.

Does Deploy access the network?

SKILL.md contains no URLs. Its commands use curl and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Deploy safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Deploy use?

Deploy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Deploy use?

About 2.6k tokens (SKILL.md is roughly 10k 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 51k tokens, read only when the agent opens those files.

What are the alternatives to Deploy?

Skills that share tags, products or a category with Deploy: Cronalytics (8bit64k/cronalytics, 112 stars), Schedule Recipe (mohitagw15856/pm-claude-skills, 1.4k stars), Wp Wpcli And Ops (jorgerosal/wordpress-skills, 101 stars) and Shadowvpn Deploy Client (madeye/shadowvpn, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deploy?

notque (a GitHub user) maintains it in notque/vexjoy-agent, which has 438 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on October 3, 2026.

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

Install Deploy

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Deploy Skill

A. Public Web Deploy

B. Dev-Branch Deploy

C. Cron Automation

D. Headless Cron Creator

E. Toolkit Install

F. Shell Configuration

G. Process Management

Deep References

Files

Compare with similar skills

Similar skills

More from notque/vexjoy-agent

Related

Questions about Deploy