agentleFS
rubiconrubicon/ai-skills/skills/rubicon-wordpress-version-lab/SKILL.md

rubicon-wordpress-version-lab

Skill1 starsChanged 3 months agoMITView on GitHub

Use when the user wants to create, list, stop, remove, or troubleshoot isolated Docker-only WordPress version test labs on an SSH-reachable host (such as a Synology NAS) — older WordPress installs, side-by-side WordPress containers, or WordPress/PHP compatibility checks run with docker compose. Also use to set or change the saved connection/identity config the skill uses.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create and manage isolated Docker Compose WordPress test labs on an SSH-reachable host.

    line 14
  2. Distinctive:

    Ensure config exists (above).

    line 30
  3. Very specific:

    Run scripts/create_wp_lab.sh.

    line 36
  4. Very specific:

    Never delete or overwrite an existing lab unless the user explicitly asks.

    line 52
  5. Distinctive:

    Treat very old WordPress/PHP combinations as best effort: old official Docker tags may be missing for the host's CPU architecture.

    line 56
  6. Very specific:

    Use references/troubleshooting.md for config, SSH/Docker access, image-pull, WP-CLI, permission, port, and site-URL issues.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Rubicon WordPress Version Lab

Create and manage isolated Docker Compose WordPress test labs on an SSH-reachable host. Each lab is its own Compose project (separate WordPress + MariaDB + WP-CLI containers) on a shared external network, so multiple WordPress versions run side by side.

First-run configuration

The skill keeps no infrastructure details in its files. Connection and identity values live in a local config outside the repo at ~/.config/rubicon-wp-lab/config.env (mode 600), managed by scripts/config_wp_lab.sh.

On first use, if config_wp_lab.sh --show reports no config, gather SSH host (an ssh alias or user@host) and access host (the hostname/IP the user browses to — it becomes the WordPress site URL), then save them:

scripts/config_wp_lab.sh --set --ssh-host <host> --access-host <host>

Optional saved defaults: --base-parent (default /volume1/docker), --network (default wordpress_lab_default), --admin-user (default admin), --admin-email, --tz (default UTC), --umask (default 002). Change any later with another --set; inspect with --show; remove with --reset --confirm.

Required workflow (create)

  1. Ensure config exists (above). Any saved value can be overridden per run with the matching flag.
  2. Gather or infer:
    • --site-name: short lowercase slug (container/project prefix).
    • --wp-version: exact WordPress version, e.g. 6.4.5, 5.9.10, 4.9.26.
    • --php-version: pass auto to recommend from references/wordpress-php-compatibility.md, or set explicitly.
    • --port: pass auto to find a free port (8080–8999), or set explicitly.
  3. Run scripts/create_wp_lab.sh. It returns the lab URL, the credentials path on the NAS, and management commands.

Commands

ActionCommand
Configure / reconfigurescripts/config_wp_lab.sh --set ... · --show · --path · --reset --confirm
Create a labscripts/create_wp_lab.sh --site-name <slug> --wp-version <ver> [--php-version auto] [--port auto]
List labsscripts/list_wp_labs.sh
Stop a labscripts/stop_wp_lab.sh --site-name <slug>
Remove a labscripts/remove_wp_lab.sh --site-name <slug> --confirm

create_wp_lab.sh --help lists every override flag.

Safety rules

  • Never delete or overwrite an existing lab unless the user explicitly asks. create refuses to overwrite an existing compose.yaml without --force, and backs it up (timestamped) before overwriting.
  • remove deletes the lab's containers, database, and files; it requires --confirm.
  • Passwords are generated randomly (unless overridden), transferred inside a private per-run staging directory (never on a command line), and stored only in the lab's credentials.txt on the NAS at mode 600.
  • Published ports bind to all interfaces on the NAS. Never expose old WordPress labs publicly — warn the user to keep router/firewall rules closed. These are local compatibility labs.
  • Treat very old WordPress/PHP combinations as best effort: old official Docker tags may be missing for the host's CPU architecture. Note such deviations as Needs Verification.

Troubleshooting

Use references/troubleshooting.md for config, SSH/Docker access, image-pull, WP-CLI, permission, port, and site-URL issues.

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.