agentsclimarketplace
Sign in

Periphetes

Skill markbaindesign/bain-studio/.claude/skills/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.From its SKILL.md

Install
npx -y skills add markbaindesign/bain-studio --skill periphetes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, 489 tokens by cl100k_base, as published. Nobody here has run it

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:

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most ship operate skills give in 489 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

  • Document a rollback plan before deploymentin 41 of 779, across 22 files
  • Update the changelogin 21 of 779, across 19 files
  • Run the test suitein 20 of 779
  • Create an annotated git tagin 20 of 779
  • Clean up feature flags after full rolloutin 18 of 779, across 10 files
  • Verify deployment health after launchin 18 of 779, across 10 files
  • Test both feature flag statesin 17 of 779, across 9 files
  • Verify the working tree is cleanin 17 of 779
  • Make database migrations backward-compatiblein 16 of 779, across 8 files
  • Set up error monitoring before launchin 15 of 779, across 7 files
  • Monitor metrics at each rollout stagein 14 of 779, across 5 files
  • Create a GitHub releasein 14 of 779

Said here and by no other author read

  • state server region, PHP version, web stack, WordPress version
  • confirm domain ownership and DNS provider
  • confirm Let's Encrypt setup
  • provide exact DDEV config values for the project
  • apply the required database prefix
  • define staging URL and indexing restrictions

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.