environments SKILL.md skillA
environments from phuryn/product-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phuryn/product-engineering/environments@git:20261108.3ac8c0bPins git:20261108.3ac8c0b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phuryn/product-engineering
- Path
app-stack/skills/environments/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261108.3ac8c0b, committed Nov 8, 2026
- First version recorded
- Oct 29, 2026
- Size
- 10,176 bytes
- Repository stars
- 643
- License
- MIT
Adding a variable or secret, 'set up production', a domain or a provider token, 'which database is this', a leaked key: dev and production for an AI-built app, backups, incidents.
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
# Environments — development, production, and what moves between them **Keep two of everything, never mixed.** Record every claim about which is which with the date checked. This skill covers separating environments, moving configuration and secrets, and changing schema while code still serves. It also covers leaks, failures and rebuilding. **Keep the principle and swap the mechanism on another stack.** These rules use Next.js (App Router), Supabase, Clerk and Netlify mechanisms after stating the principle. **The product's own instructions come first.** Follow its names for the environments doc, variables doc and branches. **Write to the product's existing records, whatever it calls them.** They hold: - The environments doc: which resource each environment uses, verified and dated, ending in the environment log, one row per environment event; - The variables doc: one row per variable, and where every copy of each secret lives; - The env schema: the one module that validates configuration, at build and at boot; - `.env`, the local configuration, never committed, and `.env.example`, its committed list of placeholders; …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_deah6gxx5qtxpizu/a851c38aca12c541e9cf6b818d9a6fc3cd0823252d2a00cd62500a15bd724f61.json
Then /plugin install environments@markdownregistry-deah6gxx5qtxpizu in Claude Code. It installs git:20261108.3ac8c0b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add phuryn/product-engineering/environments@sha256:a851c38aca12c541The line at the top of this page pins the label git:20261108.3ac8c0b, 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_deah6gxx5qtxpizu)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in phuryn/product-engineering/environments 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 environments from somewhere else? Ask it: where did my environments 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 5 versions of this file, between Oct 29, 2026 and Nov 8, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261108.3ac8c0b latest | 2026-11-08 | 3ac8c0b | 10,176 B | A | view · diff |
| git:20261108.7caf61e | 2026-11-08 | 7caf61e | 10,167 B | A | view · diff |
| git:20261102.73bc546 | 2026-11-02 | 73bc546 | 11,403 B | A | view · diff |
| git:20261029.e475447 | 2026-10-29 | e475447 | 11,370 B | A | view · diff |
| git:20261029.9b5b3c7 | 2026-10-29 | 9b5b3c7 | 11,163 B | A | view |
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.
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.
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.
Installed this file, say at .claude/skills/environments/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10176 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
phuryn/product-engineering · 643 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_deah6gxx5qtxpizu GET https://markdownregistry.com/api/v1/resolve?ref=phuryn/product-engineering/environments GET https://markdownregistry.com/api/v1/blob/a851c38aca12c541e9cf6b818d9a6fc3cd0823252d2a00cd62500a15bd724f61
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 phuryn/product-engineering
Every file in phuryn/product-engineering