agentsclimarketplace
Sign in

Ship readiness

Skill motao123/dev-workflow-kit/ship-readiness

Use when work is nearly complete and needs a final readiness check for merge, release, or deployment. This skill focuses on remaining blockers, verification state, risks, rollback awareness, and documentation gaps.From its SKILL.md

Install
npx -y skills add motao123/dev-workflow-kit --skill ship-readiness

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

  • 1 stars1 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.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, 308 tokens by cl100k_base, as published. Nobody here has run it

Ship Readiness

Use this skill near the end of a task to determine what is still missing before merge or release.

Trigger Conditions

Use this skill when:

  • the user asks what is left before merge
  • the branch appears done and needs a readiness pass
  • release notes, rollback concerns, or verification state matter
  • CI, docs, risk, or testing status must be summarized
  • the team needs a concise ship checklist

Do not use this skill at the beginning of implementation when the code has not yet been explored.

Workflow

  1. Summarize the intended change.
  2. Check local verification and known automation state.
  3. Identify remaining blockers and unresolved risks.
  4. Consider docs, migrations, rollout, and rollback concerns.
  5. Distinguish done items from open items.
  6. Recommend the next actions in the smallest sensible order.

Output

For non-trivial work, provide:

  • done vs open checklist
  • verification summary
  • known risks
  • release or merge concerns
  • next actions

Coordination

Before final shipping:

  • use fix-ci if automation is still red
  • use browser-verification and security-review when applicable
  • use docs-writer if documentation is missing

Invocation Examples

  • "Use ship-readiness and tell me what is left before merge."
  • "Use ship-readiness for this release candidate and list remaining blockers."
  • "Use ship-readiness and summarize done vs missing work for this branch."

What ships with it: 3 files

1.4 KB alongside SKILL.md

evals/

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.