strut SKILL.md skillA

strut from gfargo/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add gfargo/skills/strut@v1.0

Pins v1.0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
gfargo/skills
Path
plugins/devops/skills/strut/SKILL.md
Versions recorded
3
Latest version
v1.0, committed Aug 2, 2026
First version recorded
Jul 7, 2026
Size
5,024 bytes
Repository stars
3
License
MIT

Operate and manage Docker Compose stacks on VPS infrastructure with the strut CLI. Use for any strut task — deploying and releasing services, database backup and restore, debugging production issues, detecting config drift, rotating secrets and keys, setting up monitoring, configuring domains and SSL, validating stacks, or auditing and migrating existing servers.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# strut — VPS Stack Management

strut is a Bash CLI for managing Docker Compose stacks on VPS infrastructure. Commands follow the shape:

```
strut <stack> <command> [--env <name>] [options]
```

`--env <name>` selects the environment file `.<name>.env` (e.g. `--env prod` reads `.prod.env`). Most commands run against a VPS over SSH; some run locally.

## Command Quick Reference

```bash
# Deploy
strut <stack> deploy  --env prod          # deploy to wherever the stack lives
strut <stack> deploy  --env prod --local  # force the local Docker daemon
strut <stack> deploy  --env prod --no-sync  # restart without shipping new code
strut <stack> release --env prod          # alias for `deploy --require-remote`
strut <stack> rebuild --env prod          # build images on target + deploy
strut <stack> stop    --env prod          # stop containers
strut <stack> rollback --env prod         # restore previous deploy snapshot

# Inspect
strut <stack> status  --env prod          # container status
strut <stack> health  --env prod --json   # health checks
strut <stack> briefing --env prod         # one-call situation report: posture + prioritized actions
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5nthqd3pshrut6o3/1d7ee12ec1e17733a384e95d92690672a05df7667f30b19e45bb08570fbe76bc.json

Then /plugin install strut@markdownregistry-5nthqd3pshrut6o3 in Claude Code. It installs v1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add gfargo/skills/strut@sha256:1d7ee12ec1e17733

The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_5nthqd3pshrut6o3.svg)](https://markdownregistry.com/a/art_5nthqd3pshrut6o3)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in gfargo/skills/strut since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of strut from somewhere else? Ask it: where did my strut come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 3 versions of this file, between Jul 7, 2026 and Aug 2, 2026, about one every 13 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
v1.0 latest2026-08-02 d06aec1 5,024 BA view · diff
v1.02026-07-18 6648017 4,648 BA view · diff
v1.02026-07-07 95a6512 4,229 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (5024 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

gfargo/skills · 3 stars · license MIT · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_5nthqd3pshrut6o3
GET https://markdownregistry.com/api/v1/resolve?ref=gfargo/skills/strut
GET https://markdownregistry.com/api/v1/blob/1d7ee12ec1e17733a384e95d92690672a05df7667f30b19e45bb08570fbe76bc

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from gfargo/skills

gfargo-skills Plugin marketplace
gfargo/skills · .claude-plugin/marketplace.json · Griffen Fargo's published agentic coding skills, following the Agent Skills spec. (4 plugins: terminal, devops, games…
git:20261119.4e92a98 · audit A · 3 stars
ink-playing-cards SKILL.md skill
gfargo/skills · plugins/games/skills/ink-playing-cards/SKILL.md · Use when building terminal card games with ink-playing-cards, working with card components, deck management, zone…
git:20260807.4ace81e · audit A · 3 stars
pixelkiln SKILL.md skill
gfargo/skills · plugins/games/skills/pixelkiln/SKILL.md · Use PixelKiln to plan, generate, review, recover, audit, pack, and export manifest-driven pixel-art projects. Apply…
git:20261119.fe8e62f · audit A · 3 stars
doorman SKILL.md skill
gfargo/skills · plugins/security/skills/doorman/SKILL.md · Manage Vercel, Cloudflare, and Fastly WAF firewall rules as code with the Doorman CLI. Use for any firewall-as-code…
v1.0 · audit A · 3 stars
tui-design SKILL.md skill
gfargo/skills · plugins/terminal/skills/tui-design/SKILL.md · Design, build, refactor, or review terminal interfaces—full-screen TUIs, interactive prompts, and command-line tools…
git:20261028.70b288e · audit A · 3 stars
vhs-cli-demos SKILL.md skill
gfargo/skills · plugins/terminal/skills/vhs-cli-demos/SKILL.md · Generate deterministic screenshots and demo GIFs of command-line and terminal (TUI) applications using Charm VHS. Use…
git:20260718.5a1f2db · audit A · 3 stars

Every file in gfargo/skills

Browse by kind, by grade A, or by owner.