Paid Tier Readiness Check
Evaluates whether substacker has the four preconditions for launching a paid tier — enough subs, healthy engagement, a clear candidate section, writer capacity. Produces readiness score (not-ready / close / ready) with named gaps. Used when the "should we launch paid?" question is selected or at writer's explicit request. Trigger keywords — paid tier, paid readiness, monetization, Substack paid, launch paid, 1000 subscribers.
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 paid-tier-readiness-checkgit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/paid-tier-readiness-check ~/.claude/skills/paid-tier-readiness-checkPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Paid Tier Readiness Check
## Four gates
All four must pass for "ready":
1. **Scale**: ≥1,000 free subs OR explicit request to evaluate sub-1,000. At sub-500, refuse with reason: 2-5% conversion × 500 = 10-25 paid, below the threshold where paid changes behaviour.
2. **Engagement**: median open rate ≥40% across last 3 months (or documented reason low-rate is acceptable).
3. **Section candidate**: at least one section has ≥5 posts AND shows differential engagement vs publication baseline. This is the section paid subs would pay for.
4. **Writer capacity**: published at least once every 3 weeks for the last quarter. Launching paid adds pressure; irregular base breaks the writer.
## Workflow
```
Per check:
- [ ] Step 1: Load Growth Analyst most recent report (for subs, open rate)
- [ ] Step 2: Load section-map.md
- [ ] Step 3: Check each of the 4 gates
- [ ] Step 4: Assign score: not-ready | close | ready
- [ ] Step 5: Name the specific gap(s)
- [ ] Step 6: One-line recommendation
```
## Output
```markdown
**Scale**: pass | fail — {N} free subs ({threshold})
**Engagement**: pass | fail — median {N}% ({threshold})
**Section candidate**: pass | fail — {section} is candidate | no section qualifies yet
**Writer capacity**: pass | fail — {N} posts in last 12 weeks
**Score**: not-ready | close (gate {X} fails) | ready
**Recommendation**: {don't launch | revisit in Q+N after X | launch with offer}
```
## Worked example (at 847 subs, Q2)
- Scale: fail. 847 < 1000.Details
- Skill name
paid-tier-readiness-check- Repository
- lyndonkl/claude
- Path
skills/paid-tier-readiness-check/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Paid Tier Readiness Check skill do?
Evaluates whether substacker has the four preconditions for launching a paid tier — enough subs, healthy engagement, a clear candidate section, writer capacity. Produces readiness score (not-ready / close / ready) with named gaps. Used when the "should we launch paid?" question is selected or at writer's explicit request. Trigger keywords — paid tier, paid readiness, monetization, Substack paid, launch paid, 1000 subscribers.
How do I install the Paid Tier Readiness Check 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 Paid Tier Readiness Check 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.
Paragraph Rhythm Check
200lyndonkl/claude
Checks paragraph rhythm in a substacker draft — long/short mix, one-sentence paragraph at pivots, no walls, avoid monotony. Flags drafts where >3 consecutive paragraphs share the same length bucket, where the pivot lacks a one-sentence paragraph, or where any paragraph exceeds 120 words. Use in the Editor's structural pass. Trigger keywords — rhythm, paragraph length, wall of text, one-sentence paragraph, pivot, monotone.
Opener Critique
200lyndonkl/claude
Evaluates the first 1-3 sentences of a substacker draft against the writer's signature opener patterns — confession / "I hadn't done X" / reframe / small concrete admission. Classifies opener as confession | reframe | admission | news-hook | generic-opener and flags news-hook/generic as tier-1. The opener sets the voice contract for the essay. Use on every draft. Trigger keywords — opener, hook, first sentence, opening, confession opener, news hook, generic opener.
Principle Attack the Premise
100adriannoes/awesome-agentic-ai
Apply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.