Check Corpus Readiness
Checks whether the substacker corpus has enough material to justify a Curator run. Counts published posts, time-gates against the last review, and reports go/no-go with the specific gate that failed. Use before any Curator run, and on cold start to decide whether to propose sections yet. Trigger keywords — readiness, corpus ready, gate check, cadence gate, pre-flight.
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill check-corpus-readinessgit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/check-corpus-readiness ~/.claude/skills/check-corpus-readinessPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Check Corpus Readiness
## Gates
- Minimum 28 days since last Curator review (`ops/curator/YYYY-MM-DD-review.md`).
- Minimum 4 new published posts since last review.
- Cold start: `section-map.md` empty requires ≥10 posts in `corpus/published/**`.
## Output
```python
{
"ready": bool,
"gate_failed": str or None, # which gate, if any
"days_elapsed": int,
"new_posts": int,
"total_posts": int,
"rationale": str
}
```
## Worked example
- Corpus has 21 posts. Last review 2026-03-10 (44 days ago). New posts since: 5. → `{ready: true, gate_failed: None, ...}`.
- Corpus has 15 posts. Last review 2026-04-05 (18 days ago). → `{ready: false, gate_failed: "28-day-floor", days_elapsed: 18, ...}`. Skip this run.
- Cold start, corpus has 9 posts. → `{ready: false, gate_failed: "cold-start-10-post-floor", ...}`. Abort.
## Guardrails
1. Abort if corpus has shrunk. Posts disappearing is not a Curator concern.
2. A user-invoked early run still reports `ready: false` with a too-recent warning in the output, but doesn't block. Writer decides.
3. First step of every Curator run. If this fails, all other skills skip.Details
- Skill name
check-corpus-readiness- Repository
- lyndonkl/claude
- Path
skills/check-corpus-readiness/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Check Corpus Readiness skill do?
Checks whether the substacker corpus has enough material to justify a Curator run. Counts published posts, time-gates against the last review, and reports go/no-go with the specific gate that failed. Use before any Curator run, and on cold start to decide whether to propose sections yet. Trigger keywords — readiness, corpus ready, gate check, cadence gate, pre-flight.
How do I install the Check Corpus Readiness skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Check Corpus Readiness popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Chi
213TerminalSkills/skills
Chi is a lightweight Go HTTP router built on net/http, with composable middleware, route groups, URL parameters and sub-routers. Use when building a REST API or web service in Go, adding middleware (logging, timeouts, auth, CORS, client IP), nesting routes under /api, loading a resource into the request context, or migrating from gorilla/mux or the standard ServeMux.
Changesets
213TerminalSkills/skills
Changesets manages versions and changelogs for JavaScript/TypeScript packages and monorepos with small markdown files committed alongside code changes. Use when automating semantic versioning, generating changelogs from PRs, coordinating multi-package releases, or publishing to npm. Trigger words: changesets, versioning, changelog, npm publish, monorepo release, semver.
Click
213TerminalSkills/skills
Click is the Python library for building command-line tools from decorated functions: it parses options and arguments, validates types, prompts for missing values, and writes the --help pages. Use when a user asks to "build a Python CLI", "add a subcommand", "add an option with an environment variable fallback", "prompt for a password", "test a click command with CliRunner", "package a CLI with pyproject.toml scripts", or "add shell completion". Covers Click 8.2 to 8.5.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.