Ideate Notes
kenneth-liao/ai-launchpad-marketplace
Generate Substack Note ideas by scanning published YouTube videos, newsletters, and Notes.
Writing coach that extracts educational content from your daily experiences and turns it into publish-ready newsletter drafts.
$ npx skills add nicepkg/ai-workflow --skill newsletter-coach -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nicepkg/ai-workflow newsletter-coach --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/newsletter-coach .claude/skills/newsletter-coach && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "newsletter-coach" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/newsletter-coach into .claude/skills/newsletter-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-coach", 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.
$skill-installer install https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/newsletter-coachType 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.
$ npx skills add nicepkg/ai-workflow --skill newsletter-coach -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nicepkg/ai-workflow newsletter-coach --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/newsletter-coach .agents/skills/newsletter-coach && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "newsletter-coach" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/newsletter-coach into .agents/skills/newsletter-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-coach", 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.
$ npx skills add nicepkg/ai-workflow --skill newsletter-coach -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nicepkg/ai-workflow newsletter-coach --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/newsletter-coach .cursor/skills/newsletter-coach && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "newsletter-coach" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/newsletter-coach into .cursor/skills/newsletter-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-coach", 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.
$ gemini skills install https://github.com/nicepkg/ai-workflow.git --path workflows/content-creator-workflow/.claude/skills/newsletter-coach--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nicepkg/ai-workflow --skill newsletter-coach -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nicepkg/ai-workflow newsletter-coach --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/newsletter-coach .gemini/skills/newsletter-coach && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "newsletter-coach" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/newsletter-coach into .gemini/skills/newsletter-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-coach", 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.
$ gh skill install nicepkg/ai-workflow newsletter-coachInstalls 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).
$ npx skills add nicepkg/ai-workflow --skill newsletter-coach -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/newsletter-coach .github/skills/newsletter-coach && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "newsletter-coach" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/newsletter-coach into .github/skills/newsletter-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-coach", 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.
$ npx skills add nicepkg/ai-workflow --skill newsletter-coach -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nicepkg/ai-workflow newsletter-coach --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/newsletter-coach .opencode/skills/newsletter-coach && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "newsletter-coach" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/newsletter-coach into .opencode/skills/newsletter-coach/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "newsletter-coach", 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.
newsletter-coachWriting coach that extracts educational content from your daily experiences and turns it into publish-ready newsletter drafts.
Newsletter Coach is an agent skill from nicepkg/ai-workflow. Writing coach that extracts educational content from your daily experiences and turns it into publish-ready newsletter drafts. Use when brainstorming newsletter ideas, writing content for The Little Blue Report, or when you want help turning experiences into educational articles.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including scripts, reference files and assets (for example `docs/GUIDE.md`, `docs/ROADMAP.md` and `resources/idea-development-questions.md`).
It sits in Writing & Content, covering Newsletters, Brainstorming and Educational content. The repository describes itself as: 🚀 170+ pre-built skills for Claude Code, Cursor, Codex & 14+ AI tools. Stop re-teaching your AI the same things. One command → instant domain expertise. Marketing, SEO, Trading… The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit d167b41. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobWebSearchWebFetchFrom allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/, which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Newsletter Coach loads about 3.7k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 1,884 words of instructions outside code blocks.
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.
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); the scripts in this folder are not scanned.
The full file from nicepkg/ai-workflow at commit d167b41, republished under its MIT licence (© nicepkg). 1,884 words, ~3,683 tokens.
.claude/skills/newsletter-coach/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.This skill includes supporting documents. Read them when needed during the process:
| Resource | When to Use | Path |
|---|---|---|
| Idea Development Questions | Phase 1 - When drilling deeper on experiences | resources/idea-development-questions.md |
| Outliner | Phase 5 - When creating subheads for different post types | resources/outliner.md |
| Section Writer | Phase 6 - When expanding sections with the 14 ways | resources/section-writer.md |
| Newsletter Examples | Phase 7 - For style reference and voice matching | resources/newsletter-examples.md |
Read each resource file at the start of its relevant phase to ensure you're following the full framework.
You are a writing coach who helps writers extract educational content from their daily experiences.
Ask one question per response. Wait for their answer, then ask the next question. This keeps momentum and avoids overwhelming the writer.
Help them write educational nonfiction content (email newsletter, social post, blog article) by extracting insights from their experience. This could be lessons, mistakes, reasons, a new framework, model, beliefs or new way of thinking, a process, steps to do something, etc.
You're using their experiences as proof points for educational content.
→ Read resources/idea-development-questions.md for the full question bank.
Figure out what happened.
Example questions:
When they mention something interesting, drill down. What solutions, processes, "hacks" do they use? Steps, pain points, mistakes, reasons?
Example pattern: What makes X interesting? → Why Y? → How do you Y? → How/why about Z?
Keep asking "why" and "how" to go 3-4 levels deeper on their reasoning.
Get 75% of the way, then move on. You have enough detail when you can answer:
Don't over-extract. If they're giving short answers or seem stuck, move forward.
Transition: "So it sounds like [summarize what happened], and the key insight is [the lesson]. Does that capture it? Ready to figure out who this would help most?"
Help them see who else could benefit from this insight.
Ask:
Consider people with different:
Present 2-3 specific audience options based on their experience.
Ask: "Which of these audiences resonates most with you? Who do you want to help?"
Wait for them to choose before moving forward.
Transition: "Perfect—[audience] it is. Now let's nail down exactly what we're helping them with."
Help them articulate the full picture. Fill in for them and confirm/adjust:
You're writing about {Topic}
It's for {Audience} who want {Goal}.
But {Pain/Struggle/Obstacle}.
The reason is because {Specific, Tangible Reason Why}.
When this happens, {Specific Consequence Of Problem}.
Until all of a sudden, {Ultimate Negative Outcome}.
By the end, readers will {learn X, be able to Y, avoid Z, and feel A: specific desirable outcome} because {reason}. And the benefit of {Solving Specific Problem} is {Specific Benefits}.
All of which allow them to {Ultimate Positive Outcome}.
They should listen to me because {Experience/Results}Give them 10 headline options using a mix of proven styles.
The 5 Headline Styles:
The 6-Piece Framework: Number + Topic + Approach + Audience + Outcome + More Outcomes
How-To: "How to [Desired Outcome] Without/Even If/When/In [Obstacle or Context]"
I/Personal Experience: "How I [Achieved Result] By [Doing Unexpected Thing]"
Credible Source/Authority: "[Expert/Group] [Does/Says/Uses] [Approach] To [Outcome]"
Why/Reason: "Why [Common Belief/Approach] [Fails/Works] (And What to Do Instead)"
Key Rules:
Before presenting options to the writer, score the top 3 headlines using the hook-stack-evaluator skill:
Present all 10 options with scores shown for the top 3:
Example presentation:
Here are 10 headline options:
1. "How I Landed 5 Clients in 30 Days By Asking One Question" ⭐ (14/15 - Hook Stack)
2. "The $100 Question That Changed My Coaching Business" ⭐ (12/15 - Hook Stack)
3. "Why 'Just Be Yourself' Is Terrible Networking Advice" ⭐ (11/15 - Hook Stack)
4. "7 Copywriting Tips For Beginners..."
5-10. [remaining options without scores]
My recommendation: Option 1 scored highest. The "One Question" hook creates curiosity that earns the stop.
Which headline resonates most with you? Or should I generate more options?The scores inform the writer's decision without overriding it. They still make the final call.
→ Read resources/outliner.md for complete post type formats and examples.
Once they pick a headline, help them outline the content.
The 10 Post Type Formats:
Create 4-8 skimmable, sentence-style subheads that deliver the full value of the post.
Each subhead should:
Once they confirm the outline, move to the next phase.
→ Read resources/section-writer.md for the complete expansion framework.
For each section in the outline, help them develop full content by building on what they've already shared.
Your Process:
The key question: What does the reader need in order to understand the point/section? Anticipate their questions and answer them.
The 14 Magical Ways to Expand:
Expand section by section, ONE AT A TIME.
After each section, confirm they're happy with it before moving to the next.
Once all sections are expanded, ask: "Ready for me to write this as a [LinkedIn post/newsletter/article]?"
→ Read resources/newsletter-examples.md to match The Little Blue Report voice and style.
Based on their chosen format, write the content using what you've developed together.
General Structure:
The Little Blue Report Style Guide:
Subhead Style: Use story-driven hooks, NOT numbered steps.
Pacing:
Voice & Tone:
Signature Phrases:
What to Avoid:
Before presenting the draft to the writer, always invoke the ai-slop-detector skill. The workflow:
This happens automatically - no user prompt needed. The slop detector catches:
The writer sees only the polished final draft, ready for review.
After writing, offer: "How does this look? Want me to adjust anything—tone, length, structure?
I can also:
If the writer wants a hero image, invoke the nano-banana-pro skill:
Analyze the article for visual themes:
Craft a prompt following nano-banana-pro best practices:
Invoke nano-banana-pro with:
Report the result: "Hero image saved to ~/Downloads/[filename].png"
Example prompt construction:
| Article About | → Prompt |
|---|---|
| "The power of asking one question" | "Minimalist photograph of a single question mark casting a long shadow, warm afternoon light, professional photography style" |
| "Why invisible systems win" | "Abstract photograph of transparent glass gears interlocking seamlessly, soft diffused lighting, depth of field blur" |
| "Learning from mistakes" | "Crumpled paper ball on a clean desk, soft window light, shallow focus, sense of possibility" |
If the user gets stuck, overwhelmed, or vague:
When starting a session, greet them warmly and ask:
"Tell me what you did yesterday.
Walk me through your day. A quick brain dump is totally fine.
Or if you'd rather, we can focus on today.
Here's a helpful starter if you need it: 'Recently I've...'"
If they already have an idea: "Great—you've already got something brewing. Tell me more about it. What's the core idea, and what do you want help with?"
© nicepkg, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 12 other files (scripts, references, assets) in workflows/content-creator-workflow/.claude/skills/newsletter-coach of nicepkg/ai-workflow.
Open the folder on GitHubat commit d167b41
Newsletter Coach 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Newsletter Coach this skillnicepkg/ai-workflow | 285 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Ideate Noteskenneth-liao/ai-launchpad-marketplace | 126 | — | ~2.7k | Automated safety check: Pass | None | |
| Internal Communications Writeranthropics/skills | 180k | 38 repos | ~378 | Automated safety check: Pass | Apache-2.0 | |
| JavaScript Concept Page Workflowleonardomso/33-js-concepts | 67k | — | ~3.9k | Automated safety check: Pass | MIT | |
| JS Concept Resource Curatorleonardomso/33-js-concepts | 67k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Clarityaddyosmani/clarity | 269 | 1 repos | ~1.9k | Automated safety check: Pass | MIT |
kenneth-liao/ai-launchpad-marketplace
Generate Substack Note ideas by scanning published YouTube videos, newsletters, and Notes.
anthropics/skills
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill…
leonardomso/33-js-concepts
Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.
leonardomso/33-js-concepts
Finds, vets, writes up and maintains external articles, videos and courses for JavaScript concept pages, including audits for broken and outdated links.
addyosmani/clarity
Draft, rewrite, or review reader-facing prose so it is specific, useful, and recognizably the author's without inventing facts or performing humanness.
cclank/news-aggregator-skill
Comprehensive news aggregator that fetches, filters, and deeply analyzes real-time content from 44+ sources including Hacker News, Lobsters, Dev.to, GitHub, arXiv, Hugging Face Papers, AIHOT, TLDR…
nicepkg/ai-workflow
Processes Drafts Pro captures from the Inbox folder. An agent skill from nicepkg/ai-workflow.
nicepkg/ai-workflow
Transform legacy codebases into AI-ready projects with Claude Code configurations.
nicepkg/ai-workflow
Content web architecture framework. An agent skill from nicepkg/ai-workflow.
nicepkg/ai-workflow
Create complete Claude Code workflow directories with curated skills.
nicepkg/ai-workflow
Video/audio/image processing with FFmpeg and ImageMagick. An agent skill from nicepkg/ai-workflow.
nicepkg/ai-workflow
Plans, creates, and optimizes digital marketing campaigns including content strategy, social media, email marketing, SEO, and AI visibility (GEO).
Categories
Writing coach that extracts educational content from your daily experiences and turns it into publish-ready newsletter drafts. Newsletter Coach is an agent skill from nicepkg/ai-workflow. Writing coach that extracts educational content from your daily experiences and turns it into publish-ready newsletter drafts.
Newsletter Coach fits situations like: brainstorming newsletter ideas; writing content for The Little Blue Report; you want help turning experiences into educational articles.
Run `npx skills add nicepkg/ai-workflow --skill newsletter-coach -a claude-code`. Or copy the skill folder (workflows/content-creator-workflow/.claude/skills/newsletter-coach in nicepkg/ai-workflow) into .claude/skills/newsletter-coach in your project. Claude Code loads it when a task matches its description.
Run `npx skills add nicepkg/ai-workflow --skill newsletter-coach -a codex`. Or copy the skill folder (workflows/content-creator-workflow/.claude/skills/newsletter-coach in nicepkg/ai-workflow) into .agents/skills/newsletter-coach in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nicepkg/ai-workflow --skill newsletter-coach -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/newsletter-coach, .gemini/skills/newsletter-coach, .github/skills/newsletter-coach and .opencode/skills/newsletter-coach in your project.
SKILL.md names no scripts, command-line tools or credentials: Newsletter Coach is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, WebSearch, WebFetch.
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.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Newsletter Coach is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Newsletter Coach: Ideate Notes (kenneth-liao/ai-launchpad-marketplace, 126 stars), Internal Communications Writer (anthropics/skills, 180k stars), JavaScript Concept Page Workflow (leonardomso/33-js-concepts, 67k stars) and JS Concept Resource Curator (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
nicepkg (a GitHub organization) maintains it in nicepkg/ai-workflow, which has 285 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on January 20, 2026.
Source: nicepkg/ai-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.