Individual skill

repo-readiness-audit

Use when a user asks whether an identified repository is ready for further development, release work, a new feature, handoff, or a new contributor, requiring a disciplined read-only audit before an evidence-backed verdict.

skills/repo-readiness-audit/SKILL.md

Read pinned source

Source commit 367f8a35ff4703cec722b0678ad853814032ba7f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
127
Repository last updated
Oct 26, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Repository Readiness Audit

## Overview

Use this skill to answer a broad repository-state question before new work
begins. It determines whether the repository is ready for further
development, release work, a new feature, a handoff, or a new contributor.

This is a **read-only evidence audit**. It does not repair findings. It does not
equate a clean working tree, passing tests, or a green local build with overall
repository readiness. It verifies each relevant surface independently and
records any surface that could not be checked.

This skill covers repository-level readiness. Packaging integrity, upgrade
rehearsal, registry publication, signed artifacts, deployment verification, and