webjs-ready-for-dev SKILL.md skillA
webjs-ready-for-dev from webjsdev/webjs is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add webjsdev/webjs/webjs-ready-for-dev@git:20260808.e7eb5dcPins git:20260808.e7eb5dc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- webjsdev/webjs
- Path
.claude/skills/webjs-ready-for-dev/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260808.e7eb5dc, committed Aug 8, 2026
- First version recorded
- Aug 6, 2026
- Size
- 17,359 bytes
- Repository stars
- 27
- License
- MIT
Use this skill when the user asks to get one or more tracked issues ready for development. Trigger phrases include "get #1253, #1264 ready for development", "ready these issues for dev", "prep #1265 for development", "make these todos implementation-ready", "write the implementation plans for these issues", "scope these issues out", or any ask whose deliverable is a verified implementation plan written INTO an existing issue body rather than shipped code. The skill runs one autonomous…
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
# Get tracked issues ready for development "Ready for development" is a definition of done for PLANNING, not for code. An issue is ready when a cold AI agent, with zero access to the conversation that produced it, can implement it end to end without a discovery phase and without asking a single question. This skill takes a list of issue numbers and, for each one in parallel, spawns a fully autonomous background agent that verifies the issue against the current codebase, settles every open call, rewrites the issue body into a complete plan, and moves the card to **Ready** on the project board. Nothing here writes code. The deliverable is the issue body. ## Inputs - **Issue numbers.** Parse them from the prompt (`#1253`, `1253`, "the low risk ones we listed"). If the user names a set from an earlier turn, use that set. - **Nothing else is required.** The skill is autonomous by design: it never asks the user to settle a design question, because settling those questions IS the work. Every call is decided from industry standard practice, the prior art in the sibling framework clones, and the repo's own conventions, and the plan records what settled it. ## Steps …
Read the whole file at its exact version.
How to install
mdr add webjsdev/webjs/webjs-ready-for-dev@sha256:0efe03e7c4912072The line at the top of this page pins the label git:20260808.e7eb5dc, 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_7c4ngfg6pifnrwka)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 6, 2026 and Aug 8, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260808.e7eb5dc latest | 2026-08-08 | e7eb5dc | 17,359 B | A | view · diff |
| git:20260806.e48b190 | 2026-08-06 | e48b190 | 14,856 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 (17359 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
webjsdev/webjs · 27 stars · license MIT · pushed 2026-10-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7c4ngfg6pifnrwka GET https://markdownregistry.com/api/v1/resolve?ref=webjsdev/webjs/webjs-ready-for-dev GET https://markdownregistry.com/api/v1/blob/0efe03e7c49120727384e057f1fc8e4d44b549e3056059b8802709e0d617cc1b
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.