Readiness report

Skill jcdavis131/cursor-agent-skills/skills/readiness-report

Delivers a structured production-readiness handoff — numbered items needing operator input, each classified pre-existing vs introduced and tagged with repo issue IDs, plus exact verification commands. Use when a multi-task build is ready for operator review, before a deploy gate, or when decisions are the operator's to make.From its SKILL.md

Install

npx -y skills add jcdavis131/cursor-agent-skills --skill readiness-report

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 350 tokens by cl100k_base, as published. Nobody here has run it

Readiness Report

The handoff is the most-read part of a long session. Structure beats prose; the operator acts item-by-item without re-deriving state.

The shape

Needs your input to go to production

1. <Item> — <pre-existing|introduced> — <issue ID>.
2. ...

Ready for review: <seed command>, <serve command>, open <feature> on :<port>.

Required elements

Numbered list — only items genuinely the operator's call (credentials, brand, spec sign-off, prod provisioning).
Classify pre-existing vs introduced this session.
Tag with repo issue IDs (SEC-003, BLK-PROD) — grep-able, not prose.
Deliberate non-actions — what was skipped and why (document-non-action).
Exact kick-the-tires commands — seed, serve, port; no "how do I see it?" step.

What belongs in the list

Credentials, pricing/brand decisions, prod infra (Operator lane), spec sign-off, pre-existing security deferred without sign-off, evidence/claims that are product calls.

What does NOT belong

Recap of what was built (recap-on-long-session), internal TODOs yours to finish, vague "review the code".

Extended patterns

Open items with forward offers, release-gated prioritization, designed states, curated review tour, tool-gap alternatives: reference.md

Pair with

recap-on-long-session · document-non-action · validate-gate · respect-the-guard

What ships with it: 1 file

1.9 KB alongside SKILL.md

reference.md1.9 KB

Gives 0 of the 12 instructions most docs writing skills give in 350 tokens

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07

Announce the skill at startin 54 of 1637, across 26 files
Convert legacy doc files before editingin 45 of 1637, across 7 files
Predict questions readers might askin 42 of 1637, across 4 files
Generate clarifying questions for initial contextin 42 of 1637, across 3 files
Create document scaffold with placeholder textin 42 of 1637, across 3 files
Brainstorm content options for each sectionin 42 of 1637, across 3 files
Test the document with a fresh context-less instancein 42 of 1637, across 3 files
Include exact file paths in every taskin 42 of 1637, across 15 files
Ask interview questions one at a timein 42 of 1637, across 27 files
Apply surgical edits during refinementin 41 of 1637, across 2 files
Offer structured workflow or freeformin 40 of 1637, across 1 file
Ask for document meta-contextin 40 of 1637, across 2 files

Said here and by no other author read

list only items needing operator input
number the items
classify each item as pre-existing or introduced
tag each item with a repo issue ID
document deliberate non-actions and reasons
include exact seed serve and port commands

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.