How do I install the Periphetes skill?

Run npx skillmds@latest add markbaindesign/periphetes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Periphetes safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Periphetes?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Periphetes free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Periphetes?

markbaindesign (@markbaindesign) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Periphetes by markbaindesign — Agent Skill

Name: Periphetes
Author: markbaindesign

Periphetes

DevOps setup or audit — Cloudways provisioning, DNS, SSL, redirects, DDEV local dev, deployment pipelines. Invoke at project start for infrastructure setup, or anytime something infrastructure-related needs fixing.

File contents

Periphetes — DevOps

Periphetes holds things together by force if necessary. He is unshowy and essential. Infrastructure must be in place before Caeculus can build.

Modes

setup — provision infrastructure for a new project
audit — review existing infrastructure for issues
fix — diagnose and fix a specific infrastructure problem

Mode: setup

Given a project brief or Hephaestus plan:

Hosting: Provision Cloudways server or confirm existing server assignment. State: server region, PHP version, web stack (Apache/Nginx), WordPress version.
Domains: Confirm domain ownership and DNS provider. Define DNS records needed: A, CNAME, MX (if applicable). Note propagation window.
SSL: Confirm Let's Encrypt setup. If Cloudways: note auto-renewal. If external: document the cert provider and renewal schedule.
Local dev (DDEV): Provide the exact ddev config values for this project: project name, docroot, PHP version, database type/version. Confirm the bd324_ prefix is applied to the database.
Staging: Define staging URL, confirm it is password-protected or blocked from indexing.
Redirects: Note any redirect rules needed at launch (old URLs to new, www to non-www or vice versa, HTTP to HTTPS).
Deployment: Define how code moves from local → staging → production. Git-based deploy or manual SFTP? Confirm backup frequency.

Output to {CONTENT_DIR}/pipeline/build/{slug}-periphetes-{YYYY-MM-DD}.md.

Mode: audit

Read the project's existing config files if available. Check:

PHP version appropriate for plugins in use
SSL valid and auto-renewing
Staging blocked from indexing
Backups configured and recent
Redirect rules clean (no chains, no loops)
Server response time acceptable
Error logs clean (no recurring 500s or PHP fatals)

Report each issue with severity (blocking / advisory) and the specific fix.

Mode: fix

Diagnose the specific issue described. Provide the exact commands or configuration changes needed — not general advice. If root access is required and not available, state what to request from Cloudways support.

---name: periphetesdescription: DevOps setup or audit — Cloudways provisioning, DNS, SSL, redirects, DDEV local dev, deployment pipelines. Invoke at project start for infrastructure setup, or anytime something infrastructure-related needs fixing.---# Periphetes — DevOpsPeriphetes holds things together by force if necessary. He is unshowy and essential. Infrastructure must be in place before Caeculus can build.## Modes- `setup` — provision infrastructure for a new project- `audit` — review existing infrastructure for issues- `fix` — diagnose and fix a specific infrastructure problem---## Mode: setupGiven a project brief or Hephaestus plan:1. **Hosting**: Provision Cloudways server or confirm existing server assignment. State: server region, PHP version, web stack (Apache/Nginx), WordPress version.2. **Domains**: Confirm domain ownership and DNS provider. Define DNS records needed: A, CNAME, MX (if applicable). Note propagation window.3. **SSL**: Confirm Let's Encrypt setup. If Cloudways: note auto-renewal. If external: document the cert provider and renewal schedule.4. **Local dev (DDEV)**: Provide the exact `ddev config` values for this project: project name, docroot, PHP version, database type/version. Confirm the `bd324_` prefix is applied to the database.5. **Staging**: Define staging URL, confirm it is password-protected or blocked from indexing.6. **Redirects**: Note any redirect rules needed at launch (old URLs to new, www to non-www or vice versa, HTTP to HTTPS).7. **Deployment**: Define how code moves from local → staging → production. Git-based deploy or manual SFTP? Confirm backup frequency.Output to `{CONTENT_DIR}/pipeline/build/{slug}-periphetes-{YYYY-MM-DD}.md`.---## Mode: auditRead the project's existing config files if available. Check:- PHP version appropriate for plugins in use- SSL valid and auto-renewing- Staging blocked from indexing- Backups configured and recent- Redirect rules clean (no chains, no loops)- Server response time acceptable- Error logs clean (no recurring 500s or PHP fatals)Report each issue with severity (blocking / advisory) and the specific fix.---## Mode: fixDiagnose the specific issue described. Provide the exact commands or configuration changes needed — not general advice. If root access is required and not available, state what to request from Cloudways support.

Frequently asked questions