Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Substack Content Planner

ASecurity

Use when the user wants a weekly or monthly Substack content calendar, a plan for Notes and posts, a posting cadence, section-by-section planning for a multi-section publication, or asks to schedule or automate a run of Substack content. Not for writing the pieces themselves (use the writer skills).

3 stars
0 votes
0 copies
0 views
Added 9/19/2026
ai-agentsgoaws

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add Arin117Kaushik/substack-skills --skill substack-content-planner --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Substack Content Planner?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Substack Content Planner
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/arin117kaushik-substack-content-planner/badge)](https://www.skillsdirectory.com/skills/arin117kaushik-substack-content-planner)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: substack-content-planner
description: Use when the user wants a weekly or monthly Substack content calendar, a plan for Notes and posts, a posting cadence, section-by-section planning for a multi-section publication, or asks to schedule or automate a run of Substack content. Not for writing the pieces themselves (use the writer skills).
---

# Substack Content Planner

Plan Notes and posts the user can actually produce, per section, and get them scheduled the way Substack allows.

## Before planning

Read `references/platform-limits.md`, `references/notes-taxonomy.md`, and `~/.substack-skills/voice-profile.md` and `~/.substack-skills/story-bank.md` if they exist.

Always return the calendar. When topics are unknown, fill dates, sections, formats and Note types from what the user said, mark angles `needs input`, and put up to 3 questions after the calendar.

## Output

**1. Cadence line:** posts per week per section, Notes per week, and the one day each section publishes.

**2. Calendar table**, one row per piece:

| Date | Section | Format | Working title or Note angle | Note type | Source |
|---|---|---|---|---|---|

- Format is `Post` or `Note`. Note type comes from the taxonomy.
- Source names the Story Bank entry, file, or user message the piece draws on, or `needs input`. Never invent angles that depend on experiences the user hasn't described.
- Each post gets 1 or 2 Notes around it (a teaser the day of, a follow-up later).
- Monthly sections land in the same week each month.

**3. How it gets scheduled.** Substack's Terms of Use prohibit processes that run while the user isn't logged in, so never propose cron jobs, Task Scheduler, scripts, or browser automation that post unattended. Say that in one line if the user asked for automation, then give the allowed routes:
- **Notes:** Substack's native Notes scheduler (web, iOS, Android, since April 2026). Scheduled Notes sit in the Notes Drafts tab.
- **Posts:** schedule in Substack's editor, or with `substack-publisher` (`--at`), which hands the release to Substack.
- **Batch session:** draft the week in one sitting, approve and schedule each piece then.

## Common mistakes

| Mistake | Fix |
|---|---|
| Saying Notes can't be scheduled | They can, natively, since April 2026 |
| Offering unattended automation "if you want" | Never. Native schedulers only |
| All Notes the same type | Vary types by goal |
| Planning more than the user's stated cadence | Plan to their cadence, not an ideal one |
| Replying with only questions | Calendar first, questions after |

Attribution

Arin117KaushikArin117Kaushik
View sourceMore from Arin117Kaushik →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

1023331 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3331 votes

catchup

Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.

611 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →