Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Newsletter curation with content sourcing, editorial structure, and subscriber growth strategies. Covers issue formatting, link roundups, commentary style, a...
Newsletter curation with content sourcing, editorial structure, and subscriber growth strategies. Covers issue formatting, link roundups, commentary style, a...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Create and curate high-quality newsletters via inference.sh CLI.
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.
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.
Feature conversation with an expert or practitioner.
Numbers, charts, and analysis of trends in your space.
# 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 TypeExamplesBest ForNewsTechCrunch, The Verge, industry pressBreaking developmentsResearchPapers, reports, surveysData-backed insightsBlogsEngineering blogs, personal blogsPractitioner perspectivesSocialTwitter threads, LinkedIn postsHot takes, discussionsToolsProduct launches, updatesPractical recommendationsCommunityReddit, HN, forumsGround-level sentiment
For each piece of content, ask: QuestionIf No โWould I send this to a colleague 1-on-1?Don't includeDoes it teach something actionable?Consider skippingIs the source credible?Find better sourceIs it timely/relevant this week?Save for later or skipCan I add commentary that adds value?Just linking isn't enough
โ 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."
[What happened] + [Why it matters to the reader] + [Your take or prediction]
FrequencyBest ForOpen Rate ImpactWeeklyMost newslettersHighest โ predictable, not overwhelmingBi-weeklyDeep analysis, essaysGood if content is substantialDailyNews-focused, short formatRequires dedicated habit, riskyMonthlyResearch roundupsOK for depth, risks being forgotten Weekly is the sweet spot. Same day, same time, every week. Consistency builds habit. DayPerformanceTuesdayHighest open ratesThursdaySecond highestWednesdayThirdMondayLower (inbox overload)FridayLower (weekend mode)WeekendLowest (but some niches thrive)
FormulaExampleIssue 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.
StrategyImplementationCross-promotionPartner with complementary newslettersSocial distributionPost key insights on Twitter/LinkedIn with subscribe CTAReferral program"Forward to 3 friends" or formal referral rewardsSEO archivePublish newsletter archive as blog postsLead magnet"Subscribe and get [free resource]"Consistent qualityThe 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." }'
MetricGoodGreatAction If LowOpen rate30-40%40%+Improve subject linesClick rate3-5%5%+Better content curation, stronger CTAsUnsubscribe rate< 0.5% per issue< 0.2%Check content quality, frequencyReply rateAny repliesRegular repliesAsk questions, invite conversationForward rateAny forwardsโMake content share-worthyGrowth rate5-10% monthly10%+Increase distribution, referral program
MistakeProblemFixNo consistent scheduleReaders forget about youSame day, same time, every weekLinks without commentaryYou're a bookmark, not a newsletterAdd your take on every pieceToo many links (15+)Overwhelming, nothing stands out5-10 curated picks maxGeneric subject linesLow open ratesTease the best content, keep under 50 charsNo personal voiceReads like an RSS feedIntro paragraph, opinions, personalityOnly promotional contentReaders unsubscribe90% value, 10% promotion maxInconsistent qualityTrust erodesSkip an issue rather than send a weak oneNo CTA for engagementOne-way broadcastAsk questions, invite replies, encourage forwardsNo archive/SEOMissing growth channelPublish issues as web pages
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
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.