agentleFS
priyanshu-aryapriyanshu-arya/LinkedIn_Automation/.claude/skills/write-draft-substack-note/SKILL.md

write-draft-substack-note

Skill0 starsChanged 58 days agoMITView on GitHub

Use when the user asks to draft a Substack Note from a selected idea, run the Substack Notes Writer, or explicitly invokes /write-draft-substack-note. Converts an Idea Note claimed for the substack-note platform into a Draft Note in Drafts/ (platform:substack-note), grounded in its linked research and following Content-Learnings/voice-guide-substack.md's Notes section. Does not handle approval or publishing.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the Idea Note and every research note in its sources[].

    line 23
  2. Very specific:

    Read Content-Learnings/voice-guide-substack.md's Notes section, fresh each run.

    line 28
  3. Distinctive:

    Never invent a fact, statistic, or quote not present in the linked research notes.

    line 62
  4. Very specific:

    Never draft an idea that doesn't have a substack-note entry in platform_schedule.

    line 64
  5. Distinctive:

    Never use hashtags — not a Substack Notes convention.

    line 66
  6. Distinctive:

    Never mark anything approved, ready-to-publish, or published.

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Write Draft Substack Note (Substack Notes Writer)

Substack Notes' sibling to /write-draft-x — same short-form, single-post shape (Substack Notes have no thread concept), reusing Draft-Note.md rather than a new template, just a different voice source.

Arguments

  • idea-id (optional) — draft one specific idea for a Substack Note. If omitted, draft every idea with a substack-note entry in platform_schedule that doesn't already have a Substack Note draft linked to it.

Process (per idea)

1. Load context

Read the Idea Note and every research note in its sources[]. Same verify-or-drop discipline as every writer skill in this pipeline.

2. Read the voice guide and playbook

Read Content-Learnings/voice-guide-substack.md's Notes section, fresh each run. Check Content-Learnings/playbook-substack.md's Notes tables for an evidenced rule before falling back to the generic default.

3. Draft the note

Short, casual, conversational — more off-the-cuff than a polished feed post, per voice-guide-substack.md. No hashtags (Substack Notes don't use them). No thread concept — if an idea genuinely needs more room than one Note comfortably holds, that's a signal it belongs to /write-draft-x (as a thread) or /write-draft-substack-article instead, not a reason to force it into an oversized single Note.

4. Write the Draft Note

Copy _Templates/Draft-Note.md into Drafts/ as YYYY-MM-DD--kebab-slug.md, using the idea's platform_schedule entry for substack-note. Fill in idea_id, platform: substack-note, category, format, hook_style, hashtags: [], thread: [] (always empty here), sources, status: draft, history: [{action: created, date: today, note: ...}].

5. Update the idea

Same rule as the other writer skills: flip status: selected → drafted only if this was its last unclaimed platform.

Report back

Show the full note text and character count, and which research sources backed it.

Hard rules

  • Never invent a fact, statistic, or quote not present in the linked research notes.
  • Never draft an idea that doesn't have a substack-note entry in platform_schedule.
  • Never use hashtags — not a Substack Notes convention.
  • Never mark anything approved, ready-to-publish, or published.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.