environment-verification
Skill1 starsChanged 2 months agoApache-2.0View on GitHub
Compare explicitly requested service environments through deployed revisions, configuration and API evidence.
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- backend-code-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Read applicable rules and deployment/integration instructions.
- Distinctive: line 10
Start read-only. Compare the deployed revision, relevant non-secret settings, health and a scoped business response.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verify an environment
Resolve the target service and environment from current configuration rather than guessing names or endpoints. Read applicable rules and deployment/integration instructions. Prefer existing authenticated CLI/API routes. Start read-only. Compare the deployed revision, relevant non-secret settings, health and a scoped business response. A healthy process is not a business success; an API response is not proof of UI rendering. Changes to flags, data or deployments require the user's scope, a restoration plan and read-back verification. Report the source, observation time and evidence level. Never include credentials or full sensitive config dumps.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.