workflow-environment-ready SKILL.md skillA
workflow-environment-ready from kensaurus/cursor-kenji is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kensaurus/cursor-kenji/workflow-environment-ready@git:20261001.3fce9fbPins git:20261001.3fce9fb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kensaurus/cursor-kenji
- Path
skills/workflow-environment-ready/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261001.3fce9fb, committed Oct 1, 2026
- First version recorded
- Aug 18, 2026
- Size
- 5,959 bytes
- Repository stars
- 9
- License
- MIT
Prove runtimes, installs, tools, services, env names, and the repo's verification commands work before a long run. Use when "preflight the repo", "set up the environment", or tests cannot start. Failing tests → workflow-green-repo.
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
# workflow-environment-ready — Preflight the Working Environment **Degree of freedom: MIXED.** READY/BLOCKED verdict `[HIGH freedom]`; executed probes and never echoing secrets `[LOW freedom — run exactly]`. Long autonomous runs fail most expensively at the end — the work is done, then the build won't run, a service is down, or a key is missing. This skill front- loads that risk: prove the environment can build, test, and reach its dependencies **before** implementation starts. > **Verify the environment can run the task, don't assume it.** Every check is > an executed command with observed output, not an inference from a config file. ## How to reason 1. **Detect** — required runtimes, services, env names, gate commands 2. **Probe** — run each check; record observed output 3. **Classify** — cannot-run (env) vs runs-and-fails (code) 4. **Verdict** — READY / READY WITH NOTES / BLOCKED ## Worked example > **Detect:** Node 22 + pnpm, `supabase/config.toml`, `.env.example` has `NEXT_PUBLIC_SUPABASE_URL`. > **Probe:** `node -v` 22.4; `pnpm install --frozen-lockfile` ok; `supabase status` not running. …
Read the whole file at its exact version.
How to install
mdr add kensaurus/cursor-kenji/workflow-environment-ready@sha256:86871b0dff135bd6The line at the top of this page pins the label git:20261001.3fce9fb, 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_54b6hso7pwcdmose)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 18, 2026 and Oct 1, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.3fce9fb latest | 2026-10-01 | 3fce9fb | 5,959 B | A | view · diff |
| git:20260923.68c095e | 2026-09-23 | 68c095e | 5,834 B | A | view · diff |
| git:20260821.2a41031 | 2026-08-21 | 2a41031 | 5,872 B | A | view · diff |
| git:20260820.950107c | 2026-08-20 | 950107c | 4,572 B | A | view · diff |
| git:20260818.274c4d7 | 2026-08-18 | 274c4d7 | 4,618 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 (5959 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
kensaurus/cursor-kenji · 9 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_54b6hso7pwcdmose GET https://markdownregistry.com/api/v1/resolve?ref=kensaurus/cursor-kenji/workflow-environment-ready GET https://markdownregistry.com/api/v1/blob/86871b0dff135bd60647cbc89115b3b58e3d98fd6d9232bf1303a22837a1c1e1
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 kensaurus/cursor-kenji
Every file in kensaurus/cursor-kenji