agentleFS
notquenotque/vexjoy-agent/skills/infrastructure/deploy/SKILL.md

deploy

Skill448 starsChanged 4 days agoMITView on GitHub

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

  • Reads credentials

155 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pm-discovery, qa-phase and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ww-w-aiSkill

    pm-discovery

    PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.

    Also in 3 projects that use this

  • ww-w-aiSkill

    qa-phase

    Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.

    Also in 3 projects that use this

  • +10 more from ww-w-ai

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 138 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the request spans modes, compose the relevant sections.

    line 68
  2. Very specific:

    DNS: Create A/AAAA record. Verify: dig +short A <fqdn>.

    line 78
  3. Very specific:

    Verify: Run the 13-item security checklist.

    line 82
  4. Distinctive:

    AUDIT: Run all 9 checks via regex (verify matches not in comments):

    line 93
  5. Very specific:

    Create headless Claude Code cron jobs.

    line 115
  6. Very specific:

    Run python3 ~/.claude/scripts/install-doctor.py check and python3 ~/.claude/scripts/toolkit-health.py --json.

    line 129
  7. Very specific:

    If issues: guide user to ./install.sh --symlink.

    line 130
  8. Very specific:

    All backgrounded processes must redirect stdio: > out 2>&1 < /dev/null &.

    line 175
  9. Distinctive:

    All references below are >100 lines of domain-specific content.

    line 193

“Common” is measured: kept by at least 6 in 10 of the 138 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deploy Skill

Six modes. Match the request to a section.

SignalSection
Deploy site, HTTPS, nginx, go live, public siteA. Public Web Deploy
Cron job, scheduled task, audit cron scriptC. Cron Automation
Headless agent, wrapper script, recurring Claude taskD. Headless Cron Creator
Install toolkit, verify setup, health checkE. Toolkit Install
Fish shell, Zsh, shell config, migrationF. Shell Configuration
Background process, nohup, trap, PID, signalsG. 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.

  1. DNS: Create A/AAAA record. Verify: dig +short A <fqdn>. Gate: resolves to intended IP.
  2. Web Server: nginx server block with explicit docroot. Backend proxied to 127.0.0.1. Test: nginx -t && systemctl reload nginx.
  3. HTTPS: certbot --nginx -d <fqdn>. Verify renewal: certbot renew --dry-run. Verify redirect: curl -sI http://<fqdn> | grep -iE '301|308'.
  4. 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.
  5. 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.


C. Cron Automation

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

  1. DISCOVER: Locate scripts in scripts/*.sh, cron/*.sh, jobs/*.sh. Verify shell shebang.
  2. AUDIT: Run all 9 checks via regex (verify matches not in comments):
#CheckSeverityKey patterns
1Error handlingCRITICALset -e, set -o errexit
2Exit code checkingHIGH$?, if [ $? -eq
3Logging with timestampsHIGH>> *.log, $(date)
4Log rotationMEDIUMfind -mtime -delete, logrotate
5Working directoryHIGHcd "$(dirname", SCRIPT_DIR=
6PATH environmentMEDIUMPATH=, export PATH
7Lock file / concurrencyHIGH.lock, flock, .pid
8Cleanup on exitMEDIUMtrap ... EXIT
9Failure notificationLOWmail -s, curl *webhook
  1. 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.

  1. PARSE: Extract name (kebab-case), prompt, schedule, workdir, budget ($2.00 default).
  2. GENERATE: python3 ~/.claude/scripts/crontab-manager.py generate-wrapper --name <name> .... Verify: flock, --permission-mode auto, --max-budget-usd, tee logging, dry-run default.
  3. VALIDATE: bash -n scripts/<name>-cron.sh. Run 9-point cron checklist.
  4. INSTALL: Dry-run first (--dry-run), ask user confirmation, then install.
  5. 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

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

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


F. Shell Configuration

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

ConceptFishZsh
Variable assignmentset -gx VAR valueexport VAR=value
PATH managementfish_add_pathtypeset -U path; path=(...)
Completionscompletions/ directorycompinit + fpath
Conditionalstest, not [[ ]][[ ]] preferred
Interactive guardstatus is-interactive[[ -o interactive ]]

Load the shell-specific reference matching the task:

TaskFishZsh
Full configreferences/fish-shell-config.mdreferences/zsh-shell-config.md
Migration from Bashreferences/fish-bash-migration.mdreferences/zsh-bash-migration.md
Variables, special varsreferences/fish-quick-reference.mdreferences/zsh-quick-reference.md
Error audit, failure modesreferences/fish-preferred-patterns.mdreferences/zsh-preferred-patterns.md
Dev tool integrationreferences/fish-tool-integrations.mdreferences/zsh-tool-integrations.md

G. Process Management

Match the need to the pattern:

GoalCommand
Background job, exits with shellcmd &
Survive shell exitnohup cmd > log 2>&1 &
Detach from job controlcmd & disown
Full detach, new sessionsetsid cmd > log 2>&1 < /dev/null &
System daemonsystemd 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:

TaskReference
Process lifecycle patternsreferences/shell-process-patterns.md, references/starting-processes.md
PID capture and resolutionreferences/pid-resolution.md
Signal and trap disciplinereferences/signals-and-traps.md
Kill verification, stale PIDreferences/cleanup-verification.md
Shell gotchas (set -e, `true`)references/preferred-patterns.md

Deep References

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

ReferenceLinesDomain
references/public-web-deploy.md259Full public deploy workflow + security checklist
references/cron-automation.md1949-point cron audit checklist
references/headless-cron-creator.md150Headless cron job creation
references/install.md195Toolkit install and health check
references/shell-error-handling.md226Shell error handling patterns
references/concurrency-and-locks.md219Concurrency and locking
references/logging-and-rotation.md231Logging and rotation
references/starting-processes.md152Process start patterns
references/shell-process-patterns.md247Process lifecycle patterns
references/pid-resolution.md200PID capture and resolution
references/signals-and-traps.md259Signal and trap discipline
references/cleanup-verification.md253Kill-and-check verification
references/preferred-patterns.md354Shell gotchas and fixes
references/fish-shell-config.md247Fish shell configuration
references/fish-bash-migration.md149Bash-to-Fish migration
references/fish-quick-reference.md229Fish variable scope guide
references/fish-preferred-patterns.md240Fish failure modes
references/fish-tool-integrations.md318Fish dev tool patterns
references/zsh-shell-config.md310Zsh shell configuration
references/zsh-bash-migration.md248Bash-to-Zsh migration
references/zsh-quick-reference.md332Zsh parameter expansion
references/zsh-preferred-patterns.md290Zsh failure modes
references/zsh-tool-integrations.md368Zsh dev tool patterns

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.