verify-in-the-target-environmentlisted
Install: claude install-skill RICK-ORPHEN/agent-discipline-skills
# Verify it in the environment that will receive it
> "You are making a different mistake again." — the owner
> (after the same tool was handed over three times and failed in their environment three times)
## When to use
- Handing over **a script or a procedure a human will run**
- **Wiring a checker into a build, CI, or a release gate**
- Writing code that resolves **aliases, credentials, or login state**
- Whenever you think "it passed on my machine, so it is fine" ← this is the real trigger
---
## 1. First write, in one line, whose environment and which credentials it runs on
If you cannot write it, you may not hand it over yet.
```
This tool runs on the user's machine / under the CLI's own login
This check runs on the user's machine / under the <provider> credential
In my environment I can execute up to ___. ___ only works on the real device
```
⚠ **If even one part is something you cannot execute, say so when you hand it over.**
`bash -n` and `test -x` check **syntax, not behaviour.**
---
## 2. For any lookup whose answer depends on the environment, plan for 0 / 1 / many
You have seen **one of the three.**
| Lookup | 0 | 1 | many |
|---|---|---|---|
| alias resolution | stop with "none" | passes | **stop with "several, cannot choose"** ← easily missed |
| login state | not logged in | logged in | several accounts mixed |
| a command on PATH | absent | present | several versions |
| a config file | absent | present | conflicting copies in a hierarchy |
###