Automated summary
Creates and curates email newsletters using the inference.sh CLI, with templates for link roundups, deep dives, essays, and interviews, plus content sourcing via search tools.
Strengths
- Provides multiple formatted templates for different newsletter styles
- Integrates with search tools for content sourcing
- Includes subscriber growth strategies
- Easy to use via CLI
Limitations
- Relies on external APIs (inference.sh, Tavily, Exa) requiring credentials
- Newsletter design is limited to HTML templates without visual editor
- Does not include built-in email sending functionality
When you need to quickly produce a curated newsletter with structured templates and automated content sourcing.
When you need a visual drag-and-drop newsletter builder or when you want to send the newsletter directly from the tool.
Security analysis
CautionThe skill recommends piping a remote script to a shell for installation, an anti-pattern that introduces supply chain risk. Additionally, the allowed Bash tool permits network-connected commands, which, while intended for content curation, could be leveraged for unintended actions. No destructive or exfiltrating instructions are present, but the combination warrants caution.
- •Uses curl-to-sh install pattern (https://cli.inference.sh piped to sh), which could be exploited if the domain is compromised, despite SHA-256 verification note.
- •Bash(infsh *) tool allows execution of arbitrary infsh commands, enabling network operations and potential misuse if the infsh CLI has exploitable features.
Examples
I want to create a weekly link roundup newsletter about AI developments. Use the inference.sh CLI to source the latest AI news and generate a newsletter with the link roundup template.Generate a deep dive newsletter on the topic of quantum computing breakthroughs this month. Include a 400-word analysis and 5-8 curated links using the deep dive format.Create an HTML header image for my newsletter 'Tech Bytes' using the html-to-image app with a gradient background and the issue number.name: newsletter-curation description: "Newsletter curation with content sourcing, editorial structure, and subscriber growth strategies. Covers issue formatting, link roundups, commentary style, and sending cadence. Use for: email newsletters, link roundups, weekly digests, curated content, creator newsletters. Triggers: newsletter, email newsletter, newsletter curation, weekly digest, link roundup, curated newsletter, newsletter writing, newsletter format, subscriber growth, newsletter strategy, content curation, newsletter template" allowed-tools: Bash(infsh *)
Newsletter Curation
Create and curate high-quality newsletters via inference.sh CLI.
Quick Start
curl -fsSL https://cli.inference.sh | sh && infsh login
# Find content to curate
infsh app run tavily/search-assistant --input '{
"query": "most important AI developments this week 2024"
}'
# Generate newsletter header
infsh app run infsh/html-to-image --input '{
"html": "<div style=\"width:600px;height:200px;background:linear-gradient(135deg,#1e293b,#334155);display:flex;align-items:center;padding:40px;font-family:system-ui;color:white\"><div><h1 style=\"font-size:32px;margin:0;font-weight:800\">The Weekly Signal</h1><p style=\"font-size:16px;opacity:0.7;margin-top:8px\">Issue #47 — January 15, 2025</p></div></div>"
}'
Install note: The install script only detects your OS/architecture, downloads the matching binary from
dist.inference.sh, and verifies its SHA-256 checksum. No elevated permissions or background processes. Manual install & verification available.
Newsletter Formats
1. Link Roundup
5-15 curated links with 1-3 sentence commentary per link.
## This Week's Top Picks
### [Article Title](url)
One to three sentences explaining why this matters and what the
reader will get from it. Add your take — don't just describe.
### [Article Title](url)
Your commentary here. The value is your curation and perspective,
not just the link.
2. Deep Dive + Links
One in-depth analysis (300-500 words) + 5-8 curated links.
## The Big Story
[300-500 word analysis of the week's most important topic]
## Also Worth Reading
- **[Title](url)** — One sentence commentary
- **[Title](url)** — One sentence commentary
...
3. Original Essay
One focused piece (500-1,000 words) with a clear thesis.
## [Essay Title]
[Your original analysis, opinion, or insight]
## What I'm Reading
- [Title](url) — brief note
- [Title](url) — brief note
4. Q&A / Interview
Feature conversation with an expert or practitioner.
5. Data/Trends
Numbers, charts, and analysis of trends in your space.
Issue Structure
The Template
# [Newsletter Name] — Issue #[N]
## 👋 Hello
[2-3 sentences of personal intro — what's on your mind,
what this issue covers, why it matters right now]
## 🔥 The Big Story
[Featured content — your deepest analysis or most
important curated piece with commentary]
## 📚 Worth Reading
### [Title 1](url)
[2-3 sentence commentary with your take]
### [Title 2](url)
[2-3 sentence commentary]
### [Title 3](url)
[2-3 sentence commentary]
## 💡 Quick Hits
- [One-liner + link](url)
- [One-liner + link](url)
- [One-liner + link](url)
## 📊 Stat of the Week
[One compelling data point with context]
## 💬 From the Community
[Reader reply, question, or discussion point]
---
That's it for this week. If you found this useful, forward
it to a colleague who'd enjoy it.
[Your name]
Content Sourcing
Where to Find Content
# Industry news
infsh app run tavily/search-assistant --input '{
"query": "[your niche] news this week latest developments"
}'
# Research and data
infsh app run exa/search --input '{
"query": "[your niche] research report statistics 2024"
}'
# Trending discussions
infsh app run tavily/search-assistant --input '{
"query": "site:reddit.com [your niche] discussion this week"
}'
# Academic/deep content
infsh app run exa/search --input '{
"query": "[your niche] analysis deep dive opinion"
}'
Source Categories
| Source Type | Examples | Best For | |------------|---------|----------| | News | TechCrunch, The Verge, industry press | Breaking developments | | Research | Papers, reports, surveys | Data-backed insights | | Blogs | Engineering blogs, personal blogs | Practitioner perspectives | | Social | Twitter threads, LinkedIn posts | Hot takes, discussions | | Tools | Product launches, updates | Practical recommendations | | Community | Reddit, HN, forums | Ground-level sentiment |
Curation Quality Filter
For each piece of content, ask:
| Question | If No → | |---------|---------| | Would I send this to a colleague 1-on-1? | Don't include | | Does it teach something actionable? | Consider skipping | | Is the source credible? | Find better source | | Is it timely/relevant this week? | Save for later or skip | | Can I add commentary that adds value? | Just linking isn't enough |
Writing Commentary
What Makes Good Commentary
❌ Just describing: "This article talks about React Server Components."
❌ Restating the headline: "React Server Components are here."
✅ Adding context: "React Server Components shipped last week, and this
is the first production teardown I've seen. Key insight: they reduced
initial JS bundle by 60%, but added complexity to the build pipeline."
✅ Giving your take: "I'm skeptical about the migration path here.
Most teams I've talked to are waiting for better tooling."
✅ Connecting dots: "This pairs well with Vercel's announcement last
month — the ecosystem is clearly converging on this pattern."
Commentary Formula
[What happened] + [Why it matters to the reader] + [Your take or prediction]
Sending Cadence
| Frequency | Best For | Open Rate Impact | |-----------|---------|-----------------| | Weekly | Most newsletters | Highest — predictable, not overwhelming | | Bi-weekly | Deep analysis, essays | Good if content is substantial | | Daily | News-focused, short format | Requires dedicated habit, risky | | Monthly | Research roundups | OK for depth, risks being forgotten |
Weekly is the sweet spot. Same day, same time, every week. Consistency builds habit.
| Day | Performance | |-----|------------| | Tuesday | Highest open rates | | Thursday | Second highest | | Wednesday | Third | | Monday | Lower (inbox overload) | | Friday | Lower (weekend mode) | | Weekend | Lowest (but some niches thrive) |
Subject Lines
| Formula | Example | |---------|---------| | Issue number + teaser | "#47: The framework nobody's talking about" | | Number + topic | "5 tools that changed my workflow this month" | | Question | "Is TypeScript dying?" | | This week + category | "This week in AI: GPT-5 rumors, open source wins" | | Direct value | "The SQL optimization guide I wish I had earlier" |
Keep under 50 characters. Mobile truncates at ~35.
Growth Strategies
| Strategy | Implementation | |----------|---------------| | Cross-promotion | Partner with complementary newsletters | | Social distribution | Post key insights on Twitter/LinkedIn with subscribe CTA | | Referral program | "Forward to 3 friends" or formal referral rewards | | SEO archive | Publish newsletter archive as blog posts | | Lead magnet | "Subscribe and get [free resource]" | | Consistent quality | The best growth strategy: be worth reading |
# Create social teaser for newsletter
infsh app run x/post-create --input '{
"text": "This week in The Weekly Signal:\n\n→ Why edge computing is eating the backend\n→ The database migration nobody talks about\n→ 5 tools I discovered this month\n\nJoin 2,000+ engineers: [link]\n\nIssue #47 drops tomorrow morning."
}'
Metrics That Matter
| Metric | Good | Great | Action If Low | |--------|------|-------|--------------| | Open rate | 30-40% | 40%+ | Improve subject lines | | Click rate | 3-5% | 5%+ | Better content curation, stronger CTAs | | Unsubscribe rate | < 0.5% per issue | < 0.2% | Check content quality, frequency | | Reply rate | Any replies | Regular replies | Ask questions, invite conversation | | Forward rate | Any forwards | — | Make content share-worthy | | Growth rate | 5-10% monthly | 10%+ | Increase distribution, referral program |
Common Mistakes
| Mistake | Problem | Fix | |---------|---------|-----| | No consistent schedule | Readers forget about you | Same day, same time, every week | | Links without commentary | You're a bookmark, not a newsletter | Add your take on every piece | | Too many links (15+) | Overwhelming, nothing stands out | 5-10 curated picks max | | Generic subject lines | Low open rates | Tease the best content, keep under 50 chars | | No personal voice | Reads like an RSS feed | Intro paragraph, opinions, personality | | Only promotional content | Readers unsubscribe | 90% value, 10% promotion max | | Inconsistent quality | Trust erodes | Skip an issue rather than send a weak one | | No CTA for engagement | One-way broadcast | Ask questions, invite replies, encourage forwards | | No archive/SEO | Missing growth channel | Publish issues as web pages |
Related Skills
npx skills add inference-sh/skills@email-design
npx skills add inference-sh/skills@content-repurposing
npx skills add inference-sh/skills@seo-content-brief
Browse all apps: infsh app list
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/newsletter-curation-and-subscriber-growth-mmbizjup/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/newsletter-curation-and-subscriber-growth-mmbizjup' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/newsletter-curation-and-subscriber-growth-mmbizjup/download' --output '.skill-downloads/newsletter-curation-and-subscriber-growth-mmbizjup/SKILL.md.part' && mv '.skill-downloads/newsletter-curation-and-subscriber-growth-mmbizjup/SKILL.md.part' '.skill-downloads/newsletter-curation-and-subscriber-growth-mmbizjup/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash(infsh *)
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/newsletter-curation-and-subscriber-growth-mmbizjup/SKILL.md' && test -s '.skill-downloads/newsletter-curation-and-subscriber-growth-mmbizjup/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/newsletter-curation' && cp -R '.skill-downloads/newsletter-curation-and-subscriber-growth-mmbizjup' '.claude/skills/newsletter-curation'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/newsletter-curation-and-subscriber-growth-mmbizjup'openskills read 'newsletter-curation-and-subscriber-growth-mmbizjup'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/newsletter-curation-and-subscriber-growth-mmbizjup/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Writing Fragments
Content
Mine raw writing fragments through a relentless interview, without imposing structure. Capture ideas, quotes, and leading words for later use.
UI Copywriting & Auditing
Content
Write or audit user-facing UI copy including buttons, errors, empty states, and tooltips across the monorepo, following the design system source of truth.
Music MIDI Extraction
Content
Extracts the MIDI or score from an existing music production via the CogMusic MCP tool and confirms availability.