lyndonkl/skills/paid-tier-readiness-check
skills/paid-tier-readiness-check/SKILL.md
--- name: paid-tier-readiness-check description: 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. --- # Paid Tier Readi
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude skills/paid-tier-readiness-checkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 10:17 AM145.8s1 file scanned
SKILL.md
- name:
- paid-tier-readiness-check
- description:
- 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.
Paid Tier Readiness Check
Four gates
All four must pass for "ready":
- 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.
- Engagement: median open rate ≥40% across last 3 months (or documented reason low-rate is acceptable).
- 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.
- 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
**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.
- Engagement: pass. Median 54% over last 12 weeks.
- Section candidate: pass.
agent-workshopshows 62% avg open vs 54% baseline. - Writer capacity: pass. 14 posts in 12 weeks.
- Score: close (scale gate fails).
- Recommendation: Don't launch. Revisit at Q3 when scale crosses 1000.
Guardrails
- Never recommend launching if scale <500 unless explicitly asked.
- Engagement threshold is 40% median — well below Substack's 45-50% benchmark for well-engaged publications. Paid works below 45% with a strong candidate section.
- Section candidate is not just "has a section" — must show differential engagement.
- Writer capacity is about steady state, not spikes. Once-every-3-weeks is the floor.
- "Ready" requires all 4 gates. "Close" means 3 of 4. "Not-ready" means 2 or fewer.
Related Skills
lyndonkl/skills/zettel-note
development
VerifiedTrustedCommunity
--- name: zettel-note description: The note-writing discipline for this vault's evergreen knowledge graph, modeled on a Zettelkasten reading companion and governed by the vault conventions. Enforces declarative-claim titles, one claim per note (atomicity), own-words prose with no block quotes, the piped [[slug|Title]] link form, the labeled link-relationship vocabulary (Confirms/Contradicts/Extends/Context/Prerequisite/Builds-on/Applies/Example-of/Contrasts-with), 3-6 links per note, and search-
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-transfer-planner
development
VerifiedTrustedCommunity
Plans between-round FIFA World Cup Fantasy transfers — budgets the round's free transfer(s), forces out players whose nation has been eliminated, chases fixture-swing drops, upgrades on value, and decides when a rebuild is large enough to fire the Wildcard instead of spending free transfers one at a time. Ranks candidate in/out pairs by EV gain over each player's remaining survival horizon (delta xEV weighted by progression_carry) MINUS transfer cost (a free transfer is cheap, a points hit is real, churning the squad for marginal swings is a critic flag), and tags forced/fixture/upgrade priority. Emits a `transfer-plan` signal. Use when called by wc-squad-architect (whose transfer work this skill is the engine for) and by the strategists in the populate stage when their candidate is transfer-adjacent rather than a full rebuild.
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-tournament-state
testing
VerifiedTrustedCommunity
Reads and updates the FIFA World Cup Fantasy tournament state machine (footballfantasy/context/tournament-state.md) — the temporal backbone tracking phase (pre-tournament → group MD1-3 → R32 → R16 → QF → SF → final), budget ($100m group / $105m knockouts), nation cap (3 group, loosening in knockouts), chips remaining, surviving nations, each owned player's elimination-risk horizon, and deadlines. Validates state on load (count/feasibility checks), applies phase transitions, and appends to the append-only state log (never silent overwrite). Use to load state at the start of a run and to commit state changes after the manager makes a move.
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-signal-emitter
development
VerifiedTrustedCommunity
Validates and persists FIFA World Cup Fantasy signal files to signals/YYYY-MM-DD-<type>.md. Checks the required frontmatter (type, round, date, emitted_by, confidence, source_urls), range-checks declared numeric signals, confirms every factual claim carries a source URL or "manager-provided", rejects unknown signal types, and refuses to persist a signal that fails validation (logging the failure instead). Keeps the inter-agent signal layer auditable so downstream agents can trust what they read and never re-derive it. Use whenever an agent or skill writes a signal.
119SKILL.mdUpdated Jun 12, 2026