forge-failed-deploys SKILL.md skillA
forge-failed-deploys from gtapps/hermitd is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gtapps/hermitd/forge-failed-deploys@git:20261017.36ef834Pins git:20261017.36ef834 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gtapps/hermitd
- Path
plugins/hermitd-laravel-forge/skills/forge-failed-deploys/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.36ef834, committed Oct 17, 2026
- First version recorded
- Oct 2, 2026
- Size
- 3,181 bytes
- Repository stars
- 82
- License
- MIT
Routine check: scans the Forge estate for sites whose latest deployment is in a failure state. Runs daily via its own routine; findings are routed through the proposal pipeline as Evidence Source: scheduled-check/forge-failed-deploys.
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
# Forge Failed Deploys
Routine skill: scans the org-wide site list and flags any sites whose latest deployment status is `failed`, `failed-build`, or `cancelled`.
**Contract:** idempotent, read-only, no self-scheduling, short-running. Returns findings or silence — never creates proposals itself.
---
## Steps
1. **Run the estate scan.**
```bash
php ${CLAUDE_PLUGIN_ROOT}/php/forge.php failed-deploys
```
This pages through the org-wide site list via `organizationSites()->lazy()` and fetches the `deployment_status` field on each site. For sites in a failure state it fetches the latest `deployments()` detail. Rate limiting (429) is handled internally with conservative pacing.
2. **Parse the JSON output.** It prints `{"failures":[...]}`; on `{"error":...}`, report `Scan skipped: <error>` in place of `No actionable findings.`. Each entry has: `site_id`, `site_name`, `server_id`, `status`, optionally `deploy_id`, `deploy_status`, `commit`. An entry whose detail fetch was rate-limited instead carries an `error` key (and no `deploy_id`/`commit`): treat those as "failure, detail unavailable" and omit the commit line. Never assume all keys are present.
…Read the whole file at its exact version.
How to install
mdr add gtapps/hermitd/forge-failed-deploys@sha256:52e27ec2bdd647aeThe line at the top of this page pins the label git:20261017.36ef834, 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.
[](https://markdownregistry.com/a/art_dkeqgcsfikiq3lsy)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 2, 2026 and Oct 17, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.36ef834 latest | 2026-10-17 | 36ef834 | 3,181 B | A | view · diff |
| git:20261017.a454cba | 2026-10-17 | a454cba | 3,188 B | A | view · diff |
| git:20261017.2b1db51 | 2026-10-17 | 2b1db51 | 3,191 B | A | view · diff |
| git:20261002.2f2da1b | 2026-10-02 | 2f2da1b | 3,078 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3181 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
gtapps/hermitd · 82 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dkeqgcsfikiq3lsy GET https://markdownregistry.com/api/v1/resolve?ref=gtapps/hermitd/forge-failed-deploys GET https://markdownregistry.com/api/v1/blob/52e27ec2bdd647ae121cb7c8fe81c0a88ce6d0970450ed3a1b17df9c205160d3
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.