AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Substack Notes

skill-deupaxx-everyday-writer-substack-notes · by Deupaxx

A Claude skill from Deupaxx/EveryDay-Writer.

No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add skill-deupaxx-everyday-writer-substack-notes

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-deupaxx-everyday-writer-substack-notes)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Substack Notes? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

EW Skill — Substack Notes

Dependency: Read core/anti-ai-rules.md (all 8 sections including Section 0) before writing anything.


WHAT THIS SKILL IS FOR

Substack Notes is a discovery layer, not a second newsletter. It lives between X and a full post — longer than a tweet, shorter than an issue, more conversational than either.

Notes that work are fragments with actual ideas inside them. A thought that didn't make it into the newsletter but is too good to waste. A reaction to something you read. A question you're genuinely sitting with. An observation from the week that deserves to exist independently.

Notes that don't work are newsletters cut into smaller pieces, or promotional announcements dressed as thoughts.


THE DISTINCTION FROM FULL POSTS

A Note is not a miniaturized newsletter issue. The registers are different.

A newsletter issue: formal argument, built out, earned over the full length, structured for sustained attention.

A Note: fragment, opinion, question, or observation — valuable precisely because it's incomplete enough to invite a response. The incompleteness is not a failure; it's the feature.

Think of Notes as the margin notes of your writing life. The thoughts you'd share with someone smart over coffee that don't need a 1,500-word essay to justify existing.


WHAT NOTES ARE FOR

Thinking out loud on something you haven't resolved yet. Not a conclusion — a genuine question you're working through. The reader should feel like they caught you mid-thought, not like they're reading a prepared statement.

Link commentary with actual perspective. Not "Great piece by [Name]" — that's noise. "This essay by [Name] on [topic] is right about X but completely misses Y, which is the part that actually matters for [specific reason]." The link is the citation; your perspective is the Note.

An observation that doesn't need development. Something you noticed that's complete in one or two paragraphs. Sharp, specific, standalone. If it needs more than 3 paragraphs to make sense, it's a newsletter issue in disguise — let it grow into one.

A question that invites actual conversation. Specific enough that readers have a concrete answer to give. "What do you think about AI?" is not a conversation-starter. "What's the one use of AI that's actually improved your writing process, not just your output?" is.


FORMAT AND LENGTH

Notes live in a scrolling feed. They compete with everything. The rules:

Open with the idea, not the context. ❌ "I was reading something earlier this week that got me thinking about how we approach..." ✅ "The most-retweeted writing advice I've seen this year is also the most useless."

Short paragraphs, real line breaks. Notes are read on mobile. White space is not a formatting choice — it's a readability requirement.

Length: Most Notes should land between 100–400 words. Shorter is better if the idea is complete. Longer is fine if each paragraph earns it. Never pad a Note to look substantive — it reads as insecurity.

No bold-first bullets. If you need bullets in a Note, collapse them into a sentence.


THE DISCOVERY FUNCTION

Notes serve your newsletter's growth because they reach readers who haven't found your main publication yet. Every Note is a sample of your thinking. It should represent the quality of the newsletter, not the scraps left over from it.

The best Notes create a natural pull toward the newsletter: Not by saying "subscribe to my newsletter" (which is a waste of a Note) — but by demonstrating a quality of thinking that makes the reader want more. The advertisement is the work itself.

What to link, when: Link to a full issue when the Note expands on something the issue covers — not as self-promotion, as a genuine pointer to more depth. If the link feels forced, skip it. Notes stand alone.


VOICE ON NOTES

Notes are where your voice can be most unguarded. Use that. The newsletters get polished; the Notes get to be immediate.

That said — unguarded doesn't mean unthought. The best Notes feel spontaneous but aren't careless. The thought behind them is real; the presentation is just relaxed.

The writers who build audiences on Notes are the ones who show up with genuine curiosity and a distinct perspective, consistently, over months. Not the ones who have the best individual Note.


POST-GENERATION REVIEW

After producing any draft, stop. Re-read core/anti-ai-rules.md Sections 1–7 with the draft in front of you. Go line by line through the pre-publish checklist in Section 7. Fix every failure before presenting the output.

Notes are short — which means every word is load-bearing and AI patterns have nowhere to hide. The review pass is fast here. Do it.

PRE-POST CHECKLIST

  • [ ] Is this a genuine fragment of thought or a newsletter issue squeezed small?
  • [ ] Does it open with the idea, not the context?
  • [ ] Is it short enough — does every paragraph earn its place?
  • [ ] If it links to something: is there an actual perspective, not just a pointer?
  • [ ] Does it represent the quality of your newsletter, or the leftovers?
  • [ ] Have you run the relevant items from Sections 1–7 of core/anti-ai-rules.md?
  • [ ] No "subscribe to my newsletter" CTA dressed as a thought?

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.