Stats
Actions
Tags
From thinking-frameworks-skills
Checks whether a substacker corpus has enough published posts and time elapsed since last review to justify a Curator run. Reports go/no-go with the specific gate that failed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/thinking-frameworks-skills:check-corpus-readinessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Minimum 28 days since last Curator review (`ops/curator/YYYY-MM-DD-review.md`).
ops/curator/YYYY-MM-DD-review.md).section-map.md empty requires ≥10 posts in corpus/published/**.{
"ready": bool,
"gate_failed": str or None, # which gate, if any
"days_elapsed": int,
"new_posts": int,
"total_posts": int,
"rationale": str
}
{ready: true, gate_failed: None, ...}.{ready: false, gate_failed: "28-day-floor", days_elapsed: 18, ...}. Skip this run.{ready: false, gate_failed: "cold-start-10-post-floor", ...}. Abort.ready: false with a too-recent warning in the output, but doesn't block. Writer decides.npx claudepluginhub lyndonkl/claude --plugin thinking-frameworks-skillsIdentifies substacker seeds older than 30 days that are stale orphans (status=seed, no incoming related_seeds links) and recommends keep/promote-to-draft/kill based on density score. Emits a review list for writer review.
Generates Substack Note ideas by scanning YouTube videos, newsletters, and prior Notes. Orchestrates fetching, processed-log management, duplicate prevention, and delegation to idea extraction. Use for content repurposing and posting cadence.
Run the daily content pipeline to fetch signals, analyze relevance, draft output, edit for voice fidelity, and deliver the brief