Install the "substack-writer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/substack-writer into .claude/skills/substack-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substack-writer", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add FerroxLabs/wayland --skill substack-writer -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "substack-writer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/substack-writer into .agents/skills/substack-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substack-writer", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add FerroxLabs/wayland --skill substack-writer -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "substack-writer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/substack-writer into .cursor/skills/substack-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substack-writer", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add FerroxLabs/wayland --skill substack-writer -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "substack-writer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/substack-writer into .gemini/skills/substack-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substack-writer", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add FerroxLabs/wayland --skill substack-writer -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "substack-writer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/substack-writer into .github/skills/substack-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substack-writer", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add FerroxLabs/wayland --skill substack-writer -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "substack-writer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/marketing-sales/substack-writer into .opencode/skills/substack-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "substack-writer", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
substack-writer
GitHub stars
608
Token cost
~4.5k tokens
SKILL.md length
1,837 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0
At a glance
Newsletter business strategy covering niche positioning, free versus paid tier design, subscriber acquisition, growth tactics, writing cadence, community features, monetization math, and…
Works in 5 steps: Gather requirements. Ask the user… → Analyze the situation. Review the… → Develop the framework. Create a… → …
The user asks about substack writer
SKILL.md covers When to Use, Process, Questions to Ask First and Niche Positioning, plus 7 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Substack Writer is an agent skill from FerroxLabs/wayland. Newsletter business strategy covering niche positioning, free versus paid tier design, subscriber acquisition, growth tactics, writing cadence, community features, monetization math, and cross-promotion for sustainable newsletter revenue. Use when the user asks about substack writer or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.
Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Newsletters. It works with Substack. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.
When your agent uses it
The user asks about substack writer
Needs help with related topics
Unrelated domains
A more specialized skill exists
Example prompts
“/substack-writer”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
1Gather requirements. Ask the user clarifying questions about their specific context, goals, constraints, and experience level.
2Analyze the situation. Review the information provided and identify key factors, challenges, and opportunities relevant to substack writer.
3Develop the framework. Create a structured approach tailored to the user's needs, incorporating best practices and domain-specific…
4Deliver actionable output. Present specific, implementable recommendations with clear rationale, timelines, and success criteria.
5Address edge cases. Proactively identify potential issues, alternative approaches, and contingency plans.
What it can do on your machine
Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Substack Writer loads about 4.5k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 1,837 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~102
When it runs· the whole SKILL.md, loaded when a task matches
~4.5k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/substack-writer/SKILL.md (or your agent's skills folder).
name
substack-writer
description
Newsletter business strategy covering niche positioning, free versus paid tier design, subscriber acquisition, growth tactics, writing cadence, community features, monetization math, and cross-promotion for sustainable newsletter revenue. Use when the user asks about substack writer or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
newsletter writing content-marketing
metadata.category
marketing-sales
metadata.subcategory
seo-growth
metadata.disclaimer
none
metadata.difficulty
intermediate
Substack Writer
When to Use
Process
Gather requirements. Ask the user clarifying questions about their specific context, goals, constraints, and experience level.
Analyze the situation. Review the information provided and identify key factors, challenges, and opportunities relevant to substack writer.
Develop the framework. Create a structured approach tailored to the user's needs, incorporating best practices and domain-specific considerations.
Deliver actionable output. Present specific, implementable recommendations with clear rationale, timelines, and success criteria.
Address edge cases. Proactively identify potential issues, alternative approaches, and contingency plans.
Use this skill when:
User needs guidance on substack writer
User asks about substack writer best practices or techniques
User wants a structured approach to substack writer
Do NOT use this skill when:
A more specialized skill exists for the specific subtopic
The request is outside the scope of substack writer
Questions to Ask First
Before launching a newsletter, work through these fundamentals:
What is your unique perspective or expertise? What do you know that others would pay to read?
Who is your ideal reader? What are their job titles, interests, and daily challenges?
Can you articulate your newsletter's value in one sentence? ("I help [audience] with [specific value]")
What is your writing background? How fast can you produce quality long-form content?
Are you building a paid newsletter business, or using free newsletters to drive another business?
How often can you realistically publish without burning out? Weekly? Twice a week?
Do you have an existing audience anywhere? (Twitter/X, LinkedIn, blog, YouTube, podcast)
What newsletters in your space do you respect? What gap do they leave unfilled?
Are you comfortable with personal writing, or do you prefer purely informational content?
What does success look like at 1 year? (Subscriber count, revenue, authority, book deal)
Niche Positioning
The Newsletter Positioning Matrix
Strong newsletters sit at the intersection of three elements:
Expertise: What you know deeply
Audience Need: What people actively want to learn/read about
Unique Angle: How you say it differently from everyone else
Positioning Statement Template
[Newsletter Name] is a [frequency] newsletter for [specific audience]
who want to [desired outcome]. Unlike [competitor/category], we focus on
[unique angle] through [content format/approach].
Examples:
"The Data Stack is a weekly newsletter for data engineers who want to stay current on tooling without reading 50 blogs. Unlike aggregator newsletters, every issue includes original analysis of one tool with hands-on benchmarks."
"Kitchen Margins is a biweekly newsletter for restaurant owners who want to improve profitability. We focus exclusively on the numbers behind menu engineering with real P&L breakdowns."
Validating Your Niche
Search Substack: Are there 3-10 newsletters in your space? (Good -- proves demand)
Check subscriber counts: Use Substack Leaderboard or third-party tools
Read competitors: Where are the gaps in their coverage?
Ask your network: "Would you read a newsletter about X?" (Be specific)
Write 3 sample posts: If they come easily, the niche fits your voice
Monitor engagement: Post your newsletter concept on Twitter/LinkedIn, measure response
Free vs Paid Tier Design
Free Tier Strategy
The free tier is your growth engine. It must be genuinely valuable.
What to include in free:
Your flagship content (the thing that makes people subscribe)
At least 1 post per week
Enough value that readers feel slightly guilty getting it for free
Occasional "preview" of paid content (first section free, rest paywalled)
What NOT to do with free:
Make it a teaser with no substance
Publish inconsistently
Treat free subscribers as second-class
Paid Tier Strategy
Paid content must deliver differentiated value. Options:
Paid Content Type
Works For
Example
Deep-dive analysis
Expert niches
Weekly 3,000-word breakdown
Data/research
Industry newsletters
Original survey results, data sets
Community access
Niche professionals
Discussion threads, AMAs
Templates/tools
Practitioners
Spreadsheets, frameworks, checklists
Podcast/audio
Commuter audience
Weekly subscriber-only interview
Early access
News/trends
Get insights before free subscribers
Archive access
Evergreen content
Full back catalog for paid only
The Free-to-Paid Funnel
Discover newsletter (social, search, referral)
--> Subscribe free (deliver immediate value)
--> Read 5-8 free issues (build trust and habit)
--> Hit paywall on compelling piece (trigger conversion)
--> Convert to paid ($5-15/month)
--> Retain through ongoing value + community
Conversion rate benchmarks: 5-10% of free subscribers converting to paid is excellent. 2-5% is normal.
Growth Strategies
The Subscriber Acquisition Playbook
Phase 1: First 100 subscribers (Personal network)
Email everyone you know with a personal note (not blast)
Post on every social platform you're active on
Ask friends to forward to 1 person who'd find it valuable
Cross-post your first essay on LinkedIn/Medium/Twitter threads
Substack recommendation network (the single most powerful growth tool)
Cross-promotion swaps with similarly-sized newsletters
Twitter/X threads that link to your newsletter
Podcast appearances (have a clear CTA to subscribe)
SEO-optimize your archive (Substack posts rank on Google)
Referral program: Substack lets you reward subscribers for sharing
Phase 4: 10,000+ subscribers (Scale and diversify)
Paid growth experiments (Twitter ads, sponsoring other newsletters)
Media mentions and PR
Speaking engagements
Book deal or major content project that drives back to newsletter
Hire help for growth (social media manager, growth marketer)
Substack-Specific Growth Features
Recommendations: When readers subscribe to you, suggest partner newsletters (and vice versa). This is the highest-converting growth channel on Substack.
Notes: Substack's social layer. Post short-form content to drive discovery.
Restacks: Share other writers' posts to build relationships.
Network effects: Every subscriber's social graph becomes a potential distribution channel.
Writing Cadence
Sustainable Publishing Schedules
Frequency
Best For
Subscriber Expectation
Daily
News, curation, short-form
High commitment from you and reader
3x/week
Prolific writers, current events
Strong growth, high burnout risk
2x/week
Most growth-focused newsletters
Good balance of growth and quality
Weekly
Deep-dive, analysis, long-form
Gold standard for most writers
Biweekly
Research-heavy, side project
Acceptable if content is exceptional
Monthly
Premium research reports
Too slow for growth, only works if established
The Weekly Newsletter Production Schedule
Monday: Topic selection + research (1-2 hours)
Tuesday: Outline + first draft (2-3 hours)
Wednesday: Revision + editing (1-2 hours)
Thursday: Final polish + formatting + schedule (1 hour)
Friday: Publish (morning) + engage with comments (30 min)
Weekend: Social promotion of this week's post + idea capture for next
Writing Formulas That Work for Newsletters
The Insight Sandwich:
Open with a story or observation
--> Introduce the insight/framework
--> Provide evidence and examples
--> Give actionable takeaways
--> Close with a memorable line or callback to the opening
The Listicle Deep-Dive:
Brief intro establishing why this list matters
--> Item 1 with 2-3 paragraphs of analysis
--> Item 2...
--> Final item (strongest, most interesting)
--> Synthesis: what the list reveals about the bigger picture
The Contrarian Take:
State the conventional wisdom
--> Present the evidence against it
--> Offer your alternative framework
--> Acknowledge nuances and when conventional wisdom DOES apply
--> Clear recommendation for the reader
Speaking: Conference and podcast appearances ($500-5,000/event)
Book deals: Newsletter as proof of audience ($10,000-100,000 advance)
Job board: If your niche is professional ($200-500 per listing)
Cross-Promotion Strategy
Finding Cross-Promotion Partners
Ideal partners have:
Similar audience size (0.5x to 2x yours)
Adjacent but non-competing topic
Similar quality standards
Engaged readership
Mutual respect for each other's work
Cross-Promotion Formats
Recommendation swap: Add each other to your Substack recommendation list
Shared post: Co-write a post that goes to both audiences
Guest post: Write for each other's newsletters
Newsletter mention: Genuine endorsement in your regular content
Referral exchange: "If you like my newsletter, you'll love [partner]"
Joint webinar/event: Collaborative event marketed to both audiences
Outreach Template
Subject: Cross-promotion idea - [Your Newsletter] x [Their Newsletter]
Hi [Name],
I'm a reader and fan of [their newsletter]. Your piece on [specific post]
really resonated with my thinking on [related topic].
I write [Your Newsletter], a [frequency] newsletter for [audience] covering
[topic]. We have [subscriber count] subscribers and a [open rate]% open rate.
I think our audiences would benefit from knowing about each other's work.
Would you be interested in:
- Adding each other to our Substack recommendations
- A guest post swap
- [Other specific proposal]
Happy to share more details about my audience demographics if helpful.
[Your name]
[Link to your best post]
Advanced Substack Tactics
SEO for Substack
Write evergreen posts with keyword-rich titles
Use H2 and H3 headers with target keywords
Substack posts can rank on Google -- treat them like blog posts
Internal linking: reference your past posts within new content
Custom domain improves SEO authority (yourname.com vs yourname.substack.com)
Email Deliverability
Maintain clean list (remove inactive subscribers quarterly)
Monitor open rates: below 30% may signal deliverability issues
Retention Strategies
Welcome sequence: Automated emails for new subscribers (Substack supports this)
Best-of roundups: Periodically resurface your best content for new readers
Reader surveys: Ask what they want more of (and less of)
Personal responses: Reply to reader emails and comments
Consistent quality: One great post per week beats three mediocre ones
Common Mistakes
Starting paid too early: Build to 1,000+ free subscribers before turning on paid
No clear value proposition: "My thoughts on stuff" is not a newsletter
Inconsistent publishing: Missing weeks kills momentum and trust
All promotion, no substance: Social media should showcase your best thinking, not just "subscribe to my newsletter"
Ignoring analytics: Open rates, click rates, and growth trends tell you what's working
Not engaging with readers: Newsletters are conversations, not broadcasts
Underpricing: $5/month often converts at the same rate as $8/month, leaving money on the table
No cross-promotion: Trying to grow entirely alone is the hardest path
Perfectionism: Ship consistently, iterate based on feedback
Neglecting the archive: New subscribers judge your newsletter by your past posts -- make your archive browsable and compelling
Output Format
Deliver the response as a structured document with clear headings and actionable content. Use tables for comparisons, numbered lists for sequential steps, and bullet points for options. Include specific examples where applicable.
[Substack Writer deliverable]
1. Context and objectives
2. Analysis or framework
3. Specific recommendations with rationale
4. Action items with timeline
Example
Input: "Help me with substack writer for a mid-size project."
Output: A complete substack writer framework tailored to the specific context, with actionable steps, relevant considerations, and measurable outcomes.
Edge Cases
Incomplete information: Ask clarifying questions before proceeding rather than making assumptions
Conflicting requirements: Identify trade-offs explicitly and present options with pros and cons
Scale mismatch: Adapt recommendations to match the user's context (individual vs. team vs. organization)
Domain crossover: When the request overlaps with other skill domains, address what falls within scope and reference specialized skills for the rest
Substack Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Advanced content and topic research skill that analyzes trends across Google Analytics, Google Trends, Substack, Medium, Reddit, LinkedIn, X, blogs, podcasts, and YouTube to generate data-driven…
Produce publish-ready Chinese and English writing packages across WeChat articles, Medium/Substack essays, research notes, founder memos, op-eds, speeches, data storytelling, statistical graphics…
Interviews you about objective, audience and context, then designs an end-of-article call to action with copy, placement, A/B test plan and accessibility check.
Analyzes long-form content (transcripts, articles, interviews, webinars, podcast notes) and extracts the 3 best content ideas for any publishing platform — LinkedIn, Substack, blog, newsletter…
Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.
End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.
Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…
Newsletter business strategy covering niche positioning, free versus paid tier design, subscriber acquisition, growth tactics, writing cadence, community features, monetization math, and…. Substack Writer is an agent skill from FerroxLabs/wayland. Newsletter business strategy covering niche positioning, free versus paid tier design, subscriber acquisition, growth tactics, writing cadence, community features, monetization math, and cross-promotion for sustainable newsletter revenue.
When should I use Substack Writer?
Substack Writer fits situations like: the user asks about substack writer; needs help with related topics; unrelated domains; A more specialized skill exists.
How do I install Substack Writer in Claude Code?
Run `npx skills add FerroxLabs/wayland --skill substack-writer -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/marketing-sales/substack-writer in FerroxLabs/wayland) into .claude/skills/substack-writer in your project. Claude Code loads it when a task matches its description.
How do I install Substack Writer in Codex?
Run `npx skills add FerroxLabs/wayland --skill substack-writer -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/marketing-sales/substack-writer in FerroxLabs/wayland) into .agents/skills/substack-writer in your project. Codex loads it when a task matches its description.
Can I use Substack Writer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill substack-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/substack-writer, .gemini/skills/substack-writer, .github/skills/substack-writer and .opencode/skills/substack-writer in your project.
What does Substack Writer need to run?
SKILL.md names no scripts, command-line tools or credentials: Substack Writer is instructions for the agent only.
Does Substack Writer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Substack Writer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Substack Writer use?
Substack Writer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Substack Writer use?
About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Substack Writer?
Skills that share tags, products or a category with Substack Writer: Content Trend Researcher (alirezarezvani/claude-code-skill-factory, 879 stars), Shakespeare Writing Studio (ZCZHAO-1999/shakespeare-writing-studio, 178 stars), Serenity Reply (leslieyeo/serenity-reply, 136 stars) and End-of-Article CTA Designer (samber/cc-skills, 228 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Substack Writer?
FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.
Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.