[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV3FPZJ90B4BPFDM7748PR":3,"skill-same:01M7EV3FPZJ90B4BPFDM7748PR":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EV3FPZJ90B4BPFDM7748PR","newsletter-pro",null,"Run professional newsletters — content strategy, writing, growth, deliverability, and monetization.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-newsletter-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: newsletter-pro\ndescription: Run professional newsletters — content strategy, writing, growth, deliverability, and monetization.\ncategory: enterprise-communication\n---\n\n## Overview\n\nNewsletters are owned-audience gold: direct, algorithm-free relationships with readers. This skill covers running newsletters professionally — positioning, content systems, writing that gets opened, growth tactics, deliverability, and monetization — for company newsletters, executive briefings, and creator publications alike.\n\n\nNewsletters are the highest-trust owned channel: subscribers invite you into their inbox regularly, and great newsletters get forwarded, saved, and anticipated.\nMastery covers positioning, curation, writing voice, growth loops, and monetization — the full business of newsletters, not just the sending.\n## When to use\n\n- Launching a newsletter\n- Growing subscriber counts\n- Improving open and click rates\n- Writing better newsletter content\n- Fixing deliverability issues\n- Monetizing a newsletter\n\n- Launching a newsletter from zero\n- Growing an existing subscriber base\n- Monetizing through sponsorships or paid tiers\n- Building authority in a niche\n## Core concepts\n\n**Positioning.** One sentence: who it's for and what transformation each issue delivers. \"5-minute AI briefing for product managers\" beats \"our company newsletter.\" Niche, specific promises grow faster than generic updates.\n\n**Content system.** Repeatable sections (lead story, 3 quick hits, one deep dive, community spotlight), curation + original mix, and a voice readers recognize. Systems beat inspiration — design issues you can produce consistently.\n\n**Writing.** Subject lines (curiosity + specificity, under 50 chars), preview text (don't waste it), scannable structure (headers, bullets, short paragraphs), one idea per section, and a personal voice (write like a smart friend, not a press release). The intro sets the tone — make the first 3 lines unskippable.\n\n**Growth.** Lead magnets (best-of compilations, templates), cross-promotion with similar newsletters, social threads summarizing issues, guest features, referral programs (reward sharing with perks), and website placement (every page, not just a footer link). Paid acquisition only with proven LTV math.\n\n**Deliverability.** Authenticate (SPF, DKIM, DMARC), warm new domains gradually, clean inactive subscribers, avoid spam triggers, monitor placement (inbox vs. promotions vs. spam), and make unsubscribing easy (frustrated subscribers mark spam — worse than unsubscribing).\n\n**Monetization.** Sponsorships (priced on engaged opens, not list size), paid tiers (premium content — needs genuine differentiation), affiliate recommendations (only products you'd endorse free), and services\u002Fproducts sold to readers (highest margin). Audience trust is the asset — monetize without burning it.\n\n\n**Positioning.** One sentence: who it is for and what they get (\"A 5-minute weekly briefing on AI policy for busy executives\").\nSpecific beats broad — \"tech news\" competes with everyone; \"AI regulation for fintech compliance officers\" owns a niche.\nTest positioning with 20 target readers before committing; confusion at this stage compounds.\n**Curation vs. creation.** Curation (link roundups with commentary) is sustainable and valuable; creation (original essays) builds deeper authority but demands more.\nMost successful newsletters blend: curation for consistency, original pieces for differentiation.\nYour commentary is the product — links without insight are just RSS.\n**Voice and format.** Consistent structure readers can scan (sections, headers), a recognizable voice (write like you talk, then edit), and scannable length (5-minute read is the sweet spot for most).\nTemplate the format so writing each edition is assembly, not invention.\n**Growth loops.** Referral programs (\"get 3 friends, unlock premium\"), cross-promotions with adjacent newsletters, guest appearances, lead magnets, and social repurposing.\nNewsletters grow linearly through content and exponentially through referrals — build the referral engine early.\n## Practical workflow\n\n1. **Define.** Audience, promise, cadence (weekly is the sweet spot for most), format (sections), and voice. Write the positioning sentence first.\n2. **Set up.** Platform choice (deliverability + ease), authentication, template design (mobile-first, clean), welcome email (sets expectations + delivers any lead magnet), and preference\u002Farchive pages.\n3. **Build the content engine.** Idea capture system, section templates, writing cadence (batch when possible), and an editing pass (cut 20% — tight newsletters get read).\n4. **Launch and grow.** Announce to existing audiences, lead magnet + landing page, cross-promos (5–10 similar newsletters), social repurposing of each issue, and referral program once you have 1,000+ engaged readers.\n5. **Optimize.** Track: open rate, CTR, growth rate, unsubscribes per issue, and replies (the engagement gold). A\u002FB test subject lines. Survey readers annually: what's most\u002Fleast valuable?\n6. **Monetize carefully.** Wait for real engagement (40%+ opens) before sponsors. Price on results. Disclose sponsorships. Never sell the list.\n\n**Welcome email essentials:** what they'll get → how often → who you are (credibility) → what to do now (reply with their biggest challenge? download the lead magnet?) → set the reply expectation (you read every reply).\n\n\n**Launch sequence:** define positioning → write 3 sample editions → build landing page with samples → seed initial 100 subscribers (personal network, communities) → publish consistently (weekly minimum) → implement referral program at 500 subscribers → cross-promote at 1,000+.\nConsistency for 6 months before judging — newsletters compound slowly then suddenly.\n**Edition workflow:** collect items all week (capture system) → draft (write fast, edit slow) → subject line (write 5, pick best) → proofread (read aloud) → test send → schedule at optimal time → promote on social → review metrics.\nBatch the process; context-switching kills newsletter quality.\n**Monetization paths:** sponsorships (CPM $25–50 for niche B2B) → paid tiers (premium content, community) → affiliate recommendations → products and services.\nMonetize only after product-market fit (40%+ open rates, growing organically) — premature monetization stunts growth.\n## Common pitfalls\n\n- **Inconsistent cadence.** Sporadic sending trains readers to ignore. Weekly, like clockwork.\n- **Company-update syndrome.** \"What we did this month\" nobody asked for. Reader-first content always.\n- **Weak subject lines.** The open rate killer. Spend real time; test relentlessly.\n- **No growth engine.** Publishing and hoping. Active promotion every issue.\n- **Buying lists.** Spam complaints, blacklists, dead engagement. Grow organically.\n- **Ignoring deliverability.** Landing in spam while blaming content. Monitor placement; maintain list hygiene.\n- **Monetizing too early.** Sponsors before trust. Build the audience; revenue follows.\n- **Inconsistent publishing.** Skipping weeks kills momentum. Pick a cadence you can sustain for years — weekly beats ambitious-daily-that-dies.\n- **No clear value proposition.** \"My thoughts on things\" is not a newsletter concept. Specific promise, specific audience, specific cadence.\n- **Ignoring deliverability.** Landing in spam or promotions tab. Authenticate (SPF\u002FDKIM\u002FDMARC), maintain list hygiene, and monitor placement.\n- **Writing for everyone.** Broad content pleases nobody. Niche down until the audience is obvious — you can expand later.\n","## Overview\n\nNewsletters are owned-audience gold: direct, algorithm-free relationships with readers. This skill covers running newsletters professionally — positioning, content systems, writing that gets opened, growth tactics, deliverability, and monetization — for company newsletters, executive briefings, and creator publications alike.\n\n\nNewsletters are the highest-trust owned channel: subscribers invite you into their inbox regularly, and great newsletters get forwarded, saved, and anticipated.\nMastery covers positioning, curation, writing voice, growth loops, and monetization — the full business of newsletters, not just the sending.\n## When to use\n\n- Launching a newsletter\n- Growing subscriber counts\n- Improving open and click rates\n- Writing better newsletter content\n- Fixing deliverability issues\n- Monetizing a newsletter\n\n- Launching a newsletter from zero\n- Growing an existing subscriber base\n- Monetizing through sponsorships or paid tiers\n- Building authority in a niche\n## Core concepts\n\n**Positioning.** One sentence: who it's for and what transformation each issue delivers. \"5-minute AI briefing for product managers\" beats \"our company newsletter.\" Niche, specific promises grow faster than generic updates.\n\n**Content system.** Repeatable sections (lead story, 3 quick hits, one deep dive, community spotlight), curation + original mix, and a voice readers recognize. Systems beat inspiration — design issues you can produce consistently.\n\n**Writing.** Subject lines (curiosity + specificity, under 50 chars), preview text (don't waste it), scannable structure (headers, bullets, short paragraphs), one idea per section, and a personal voice (write like a smart friend, not a press release). The intro sets the tone — make the first 3 lines unskippable.\n\n**Growth.** Lead magnets (best-of compilations, templates), cross-promotion with similar newsletters, social threads summarizing issues, guest features, referral programs (reward sharing with perks), and website placement (every page, not just a footer link). Paid acquisition only with proven LTV math.\n\n**Deliverability.** Authenticate (SPF, DKIM, DMARC), warm new domains gradually, clean inactive subscribers, avoid spam triggers, monitor placement (inbox vs. promotions vs. spam), and make unsubscribing easy (frustrated subscribers mark spam — worse than unsubscribing).\n\n**Monetization.** Sponsorships (priced on engaged opens, not list size), paid tiers (premium content — needs genuine differentiation), affiliate recommendations (only products you'd endorse free), and services\u002Fproducts sold to readers (highest margin). Audience trust is the asset — monetize without burning it.\n\n\n**Positioning.** One sentence: who it is for and what they get (\"A 5-minute weekly briefing on AI policy for busy executives\").\nSpecific beats broad — \"tech news\" competes with everyone; \"AI regulation for fintech compliance officers\" owns a niche.\nTest positioning with 20 target readers before committing; confusion at this stage compounds.\n**Curation vs. creation.** Curation (link roundups with commentary) is sustainable and valuable; creation (original essays) builds deeper authority but demands more.\nMost successful newsletters blend: curation for consistency, original pieces for differentiation.\nYour commentary is the product — links without insight are just RSS.\n**Voice and format.** Consistent structure readers can scan (sections, headers), a recognizable voice (write like you talk, then edit), and scannable length (5-minute read is the sweet spot for most).\nTemplate the format so writing each edition is assembly, not invention.\n**Growth loops.** Referral programs (\"get 3 friends, unlock premium\"), cross-promotions with adjacent newsletters, guest appearances, lead magnets, and social repurposing.\nNewsletters grow linearly through content and exponentially through referrals — build the referral engine early.\n## Practical workflow\n\n1. **Define.** Audience, promise, cadence (weekly is the sweet spot for most), format (sections), and voice. Write the positioning sentence first.\n2. **Set up.** Platform choice (deliverability + ease), authentication, template design (mobile-first, clean), welcome email (sets expectations + delivers any lead magnet), and preference\u002Farchive pages.\n3. **Build the content engine.** Idea capture system, section templates, writing cadence (batch when possible), and an editing pass (cut 20% — tight newsletters get read).\n4. **Launch and grow.** Announce to existing audiences, lead magnet + landing page, cross-promos (5–10 similar newsletters), social repurposing of each issue, and referral program once you have 1,000+ engaged readers.\n5. **Optimize.** Track: open rate, CTR, growth rate, unsubscribes per issue, and replies (the engagement gold). A\u002FB test subject lines. Survey readers annually: what's most\u002Fleast valuable?\n6. **Monetize carefully.** Wait for real engagement (40%+ opens) before sponsors. Price on results. Disclose sponsorships. Never sell the list.\n\n**Welcome email essentials:** what they'll get → how often → who you are (credibility) → what to do now (reply with their biggest challenge? download the lead magnet?) → set the reply expectation (you read every reply).\n\n\n**Launch sequence:** define positioning → write 3 sample editions → build landing page with samples → seed initial 100 subscribers (personal network, communities) → publish consistently (weekly minimum) → implement referral program at 500 subscribers → cross-promote at 1,000+.\nConsistency for 6 months before judging — newsletters compound slowly then suddenly.\n**Edition workflow:** collect items all week (capture system) → draft (write fast, edit slow) → subject line (write 5, pick best) → proofread (read aloud) → test send → schedule at optimal time → promote on social → review metrics.\nBatch the process; context-switching kills newsletter quality.\n**Monetization paths:** sponsorships (CPM $25–50 for niche B2B) → paid tiers (premium content, community) → affiliate recommendations → products and services.\nMonetize only after product-market fit (40%+ open rates, growing organically) — premature monetization stunts growth.\n## Common pitfalls\n\n- **Inconsistent cadence.** Sporadic sending trains readers to ignore. Weekly, like clockwork.\n- **Company-update syndrome.** \"What we did this month\" nobody asked for. Reader-first content always.\n- **Weak subject lines.** The open rate killer. Spend real time; test relentlessly.\n- **No growth engine.** Publishing and hoping. Active promotion every issue.\n- **Buying lists.** Spam complaints, blacklists, dead engagement. Grow organically.\n- **Ignoring deliverability.** Landing in spam while blaming content. Monitor placement; maintain list hygiene.\n- **Monetizing too early.** Sponsors before trust. Build the audience; revenue follows.\n- **Inconsistent publishing.** Skipping weeks kills momentum. Pick a cadence you can sustain for years — weekly beats ambitious-daily-that-dies.\n- **No clear value proposition.** \"My thoughts on things\" is not a newsletter concept. Specific promise, specific audience, specific cadence.\n- **Ignoring deliverability.** Landing in spam or promotions tab. Authenticate (SPF\u002FDKIM\u002FDMARC), maintain list hygiene, and monitor placement.\n- **Writing for everyone.** Broad content pleases nobody. Niche down until the audience is obvious — you can expand later.\n",{"name":5,"category":24,"description":7},"enterprise-communication","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-newsletter-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill newsletter-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill newsletter-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill newsletter-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-newsletter-pro\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]