spec-readiness-setup skillA
spec-readiness-setup is agent-read markdown (skill) from eltmon/overdeck: Create a customized wrapper for the spec-readiness skill. Configures branding, issue tracker bindings, field mappings, and org-specific conventions. Generates a ready-to-use wrapper skill directory with config.yaml and SKILL.md..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Spec Readiness Setup — Wrapper Creator
This skill creates a customized wrapper for the `spec-readiness` core skill. The wrapper binds your organization's branding, issue tracker, field names, and conventions to the generic scoring engine.
## What Gets Created
```
~/.overdeck/skills/spec-readiness-{name}/
SKILL.md # Wrapper skill that invokes the core with your config
config.yaml # Branding, tracker bindings, field mappings, conventions
```
After creation, the wrapper is immediately available. Users invoke it by name (e.g., `spec readiness acme MIN-704`) or the core skill auto-detects it.
---
## Workflow
### Step 1: Gather Information
Ask the user the following questions. Use `AskUserQuestion` with sensible defaults. Skip questions the user has already answered in their prompt.
**1. Wrapper name** (used in directory name and skill name):
- "What should this wrapper be called? This becomes the skill name, e.g., `spec-readiness-acme`"
- Default: derive from company name (lowercase, kebab-case)
- Validation: kebab-case, no spaces, alphanumeric + hyphens only
**2. Company / Organization name** (for report branding):
…Read the whole file at its exact version.
How to install
mdr add eltmon/overdeck/spec-readiness-setup@git:20260618.e501626mdr add eltmon/overdeck/spec-readiness-setup@sha256:7faac05414fee1a3Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ces6sm42jmbbhhr7)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260618.e501626 latest | 2026-06-18 | e501626 | 11,387 B | A | view · diff |
| git:20260618.ccb1e75 | 2026-06-18 | ccb1e75 | 11,405 B | A | view · diff |
| git:20260522.817c2c7 | 2026-05-22 | 817c2c7 | 11,411 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 (11387 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
eltmon/overdeck · 28 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ces6sm42jmbbhhr7 GET https://markdownregistry.com/api/v1/resolve?ref=eltmon/overdeck/spec-readiness-setup GET https://markdownregistry.com/api/v1/blob/7faac05414fee1a33c7e80d3fe6da9313914e0d95f6118291091ca814720bf86
Your agent 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.