[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMTTSZEMBWZ956GD10N55K":3,"skill-same:01M7EMTTSZEMBWZ956GD10N55K":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},"01M7EMTTSZEMBWZ956GD10N55K","digest-emails",null,"Create digest emails — curated summaries, personalization, frequency strategy, and engagement optimization.","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-digest-emails\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: digest-emails\ndescription: Create digest emails — curated summaries, personalization, frequency strategy, and engagement optimization.\ncategory: enterprise-communication\n---\n\n## Overview\n\nDigest emails (daily\u002Fweekly summaries) keep users informed without real-time interruption: activity summaries, content roundups, and team updates. This skill covers designing digests people actually open — curation, personalization, frequency, and the engagement mechanics that prevent the digest from becoming inbox wallpaper.\n\n\nDigest emails — daily\u002Fweekly summaries of activity, content, or updates — are the highest-retention email format for platforms: they deliver ongoing value in one predictable package, drive habitual re-engagement, and are far less annoying than per-event notifications. The skill is curation: making each edition feel personally relevant rather than automated noise.\n## When to use\n\n- Building daily\u002Fweekly digest emails\n- Improving digest open and click rates\n- Reducing notification email volume via digests\n- Designing personalized content roundups\n- Launching team\u002Fcompany update emails\n- Fixing digest fatigue\n\n- Re-engaging dormant users with activity summaries\n- Curating content newsletters\n- Replacing noisy per-event emails\n- Summarizing community or forum activity\n- Delivering personalized learning paths\n## Core concepts\n\n**Curation over completeness.** A digest is an editorial product: the 5–10 most important items, not everything that happened. Rank by: relevance to the recipient, importance, recency, and actionability. \"Everything\" belongs in the app; the digest carries what matters.\n\n**Personalization.** By role, interests, behavior, and relationships (updates from people you work with rank higher). Even simple personalization (name, relevant items first) lifts engagement significantly. The best digests feel hand-picked.\n\n**Frequency strategy.** Daily for fast-moving contexts (sales activity, support queues), weekly for most content\u002Fupdates, and user choice where possible. Match frequency to content velocity — a weekly digest with 2 items feels empty; a daily with 50 feels like spam.\n\n**Anatomy.** Subject line (specific + fresh: \"3 updates need your input\" beats \"Your weekly digest\"), personalized greeting optional, top story featured, grouped sections with clear headers, one-line summaries per item (not just links), single primary CTA per section, and footer with preference controls.\n\n**Engagement mechanics.** \"What you missed\" framing, social proof (\"most discussed\"), unfinished business (items awaiting your action — highest CTR), and freshness (never repeat yesterday's content). Every digest should contain at least one item worth clicking.\n\n**Consolidation.** Digests should replace individual notification emails, not add to them. When launching a digest, turn off the real-time emails it covers (with user control). Net email reduction is the goal.\n\n\n**Curation algorithms.** Rank candidate items by: personal relevance (involves the user or their network), recency, popularity\u002Fsocial proof, and diversity (not 10 items from one source). The top 5–7 items make the digest; everything else waits. Personalization depth separates beloved digests (GitHub, Strava) from ignored ones — invest in the ranking, not just the template.\n\n**Cadence and control.** Daily for high-activity products, weekly for most, with user-selectable frequency. The frequency selector is itself a retention feature — users who choose weekly over unsubscribing are saved. Default new users to the gentlest effective cadence; let engagement earn frequency.\n\n**The subject line.** Digests live or die by subject lines: include the most compelling item (\"Sarah mentioned you + 4 updates\") not generic labels (\"Your weekly digest\"). Dynamic subject lines reflecting top content lift open rates 15–25%.\n\n**Send-time personalization.** Deliver when each user typically engages — morning readers vs. evening readers.\nTime-zone-aware batching prevents 3am digests.\nTest send times per cohort; defaults are averages that fit nobody.\n**Content freshness.** Digests must feel current — stale items signal irrelevance.\nSet recency cutoffs (nothing older than 7 days for weeklies).\n evergreen content gets its own format, not digest filler.\n## Practical workflow\n\n1. **Define the digest's job.** What should the reader know\u002Fdo after reading? One clear purpose per digest. If you can't state it, don't send it.\n2. **Design curation rules.** Scoring: recency × relevance × importance × actionability. Minimum quality bar (don't send thin digests), maximum items (5–10), and deduplication against previous digests.\n3. **Build personalization.** Start with: role-based sections, behavioral ranking (their projects, their mentions first), and preference inputs. Increase sophistication as data allows.\n4. **Write the template.** Scannable sections, one-line summaries, clear CTAs, mobile-first design (most digests are read on phones), and prominent preference\u002Funsubscribe controls.\n5. **Launch and consolidate.** Ship the digest, migrate users off redundant real-time emails, communicate the change (\"fewer emails, better summaries\"), and offer frequency choice.\n6. **Optimize.** Track: open rate, CTR per section, items-per-open, unsubscribe rate, and preference changes. A\u002FB test subject lines and section order. Prune sections nobody clicks. Survey annually: still useful?\n\n**Curation scoring example:** score = (recency decay) × (relationship weight: direct mention 3x, team 2x, org 1x) × (actionability: needs-you 2x) — take top N above threshold.\n\n\n**Digest anatomy:** personalized greeting → hero item (the single most relevant update) → 4–6 ranked items with rich previews → one clear CTA per item (not a generic \"view all\") → footer with frequency controls. Mobile-first design — 60%+ of digest opens are mobile. Keep total length scannable in under 60 seconds.\n\n**Optimization loop:** track open rate, click-through per position (position decay reveals ranking quality), unsubscribe rate, and re-activation (dormant users returning). A\u002FB test: subject line formulas, item count, send day\u002Ftime, and hero selection logic. Quarterly: survey a sample on relevance — quantitative metrics miss the \"this feels generic\" problem.\n## Common pitfalls\n\n- **Completeness over curation.** Dumping everything. Digests are editorial — curate ruthlessly.\n- **Stale content.** Repeating items across digests. Track what's been sent; never repeat.\n- **Adding without subtracting.** New digest on top of existing notification emails. Consolidate — net reduction.\n- **Generic for everyone.** Same digest for all roles. Personalize or perish (in the spam folder).\n- **Weak subject lines.** \"Your weekly digest\" every week. Specific, fresh subjects referencing actual content.\n- **No preference control.** Forcing frequency. Let users choose daily\u002Fweekly\u002Foff.\n- **Ignoring mobile.** Desktop-designed digests read on phones. Mobile-first, always.\n- **Kitchen-sink digests.** Including everything to avoid choosing. Curation is the product — if everything is included, nothing is curated.\n- **Stale personalization.** \"Recommended for you\" that clearly is not. Bad personalization is worse than none — it signals you do not know the user.\n- **No sunset for non-openers.** Continuing daily digests to users who never open. Suppress or downshift chronic non-openers to protect deliverability.\n- **Identical digests for all.** No personalization beyond the name. Segment by interest or behavior — relevance is the product.\n- **Broken links.** Digest links rotting. Validate links before sending; broken links train users to stop clicking.\n","## Overview\n\nDigest emails (daily\u002Fweekly summaries) keep users informed without real-time interruption: activity summaries, content roundups, and team updates. This skill covers designing digests people actually open — curation, personalization, frequency, and the engagement mechanics that prevent the digest from becoming inbox wallpaper.\n\n\nDigest emails — daily\u002Fweekly summaries of activity, content, or updates — are the highest-retention email format for platforms: they deliver ongoing value in one predictable package, drive habitual re-engagement, and are far less annoying than per-event notifications. The skill is curation: making each edition feel personally relevant rather than automated noise.\n## When to use\n\n- Building daily\u002Fweekly digest emails\n- Improving digest open and click rates\n- Reducing notification email volume via digests\n- Designing personalized content roundups\n- Launching team\u002Fcompany update emails\n- Fixing digest fatigue\n\n- Re-engaging dormant users with activity summaries\n- Curating content newsletters\n- Replacing noisy per-event emails\n- Summarizing community or forum activity\n- Delivering personalized learning paths\n## Core concepts\n\n**Curation over completeness.** A digest is an editorial product: the 5–10 most important items, not everything that happened. Rank by: relevance to the recipient, importance, recency, and actionability. \"Everything\" belongs in the app; the digest carries what matters.\n\n**Personalization.** By role, interests, behavior, and relationships (updates from people you work with rank higher). Even simple personalization (name, relevant items first) lifts engagement significantly. The best digests feel hand-picked.\n\n**Frequency strategy.** Daily for fast-moving contexts (sales activity, support queues), weekly for most content\u002Fupdates, and user choice where possible. Match frequency to content velocity — a weekly digest with 2 items feels empty; a daily with 50 feels like spam.\n\n**Anatomy.** Subject line (specific + fresh: \"3 updates need your input\" beats \"Your weekly digest\"), personalized greeting optional, top story featured, grouped sections with clear headers, one-line summaries per item (not just links), single primary CTA per section, and footer with preference controls.\n\n**Engagement mechanics.** \"What you missed\" framing, social proof (\"most discussed\"), unfinished business (items awaiting your action — highest CTR), and freshness (never repeat yesterday's content). Every digest should contain at least one item worth clicking.\n\n**Consolidation.** Digests should replace individual notification emails, not add to them. When launching a digest, turn off the real-time emails it covers (with user control). Net email reduction is the goal.\n\n\n**Curation algorithms.** Rank candidate items by: personal relevance (involves the user or their network), recency, popularity\u002Fsocial proof, and diversity (not 10 items from one source). The top 5–7 items make the digest; everything else waits. Personalization depth separates beloved digests (GitHub, Strava) from ignored ones — invest in the ranking, not just the template.\n\n**Cadence and control.** Daily for high-activity products, weekly for most, with user-selectable frequency. The frequency selector is itself a retention feature — users who choose weekly over unsubscribing are saved. Default new users to the gentlest effective cadence; let engagement earn frequency.\n\n**The subject line.** Digests live or die by subject lines: include the most compelling item (\"Sarah mentioned you + 4 updates\") not generic labels (\"Your weekly digest\"). Dynamic subject lines reflecting top content lift open rates 15–25%.\n\n**Send-time personalization.** Deliver when each user typically engages — morning readers vs. evening readers.\nTime-zone-aware batching prevents 3am digests.\nTest send times per cohort; defaults are averages that fit nobody.\n**Content freshness.** Digests must feel current — stale items signal irrelevance.\nSet recency cutoffs (nothing older than 7 days for weeklies).\n evergreen content gets its own format, not digest filler.\n## Practical workflow\n\n1. **Define the digest's job.** What should the reader know\u002Fdo after reading? One clear purpose per digest. If you can't state it, don't send it.\n2. **Design curation rules.** Scoring: recency × relevance × importance × actionability. Minimum quality bar (don't send thin digests), maximum items (5–10), and deduplication against previous digests.\n3. **Build personalization.** Start with: role-based sections, behavioral ranking (their projects, their mentions first), and preference inputs. Increase sophistication as data allows.\n4. **Write the template.** Scannable sections, one-line summaries, clear CTAs, mobile-first design (most digests are read on phones), and prominent preference\u002Funsubscribe controls.\n5. **Launch and consolidate.** Ship the digest, migrate users off redundant real-time emails, communicate the change (\"fewer emails, better summaries\"), and offer frequency choice.\n6. **Optimize.** Track: open rate, CTR per section, items-per-open, unsubscribe rate, and preference changes. A\u002FB test subject lines and section order. Prune sections nobody clicks. Survey annually: still useful?\n\n**Curation scoring example:** score = (recency decay) × (relationship weight: direct mention 3x, team 2x, org 1x) × (actionability: needs-you 2x) — take top N above threshold.\n\n\n**Digest anatomy:** personalized greeting → hero item (the single most relevant update) → 4–6 ranked items with rich previews → one clear CTA per item (not a generic \"view all\") → footer with frequency controls. Mobile-first design — 60%+ of digest opens are mobile. Keep total length scannable in under 60 seconds.\n\n**Optimization loop:** track open rate, click-through per position (position decay reveals ranking quality), unsubscribe rate, and re-activation (dormant users returning). A\u002FB test: subject line formulas, item count, send day\u002Ftime, and hero selection logic. Quarterly: survey a sample on relevance — quantitative metrics miss the \"this feels generic\" problem.\n## Common pitfalls\n\n- **Completeness over curation.** Dumping everything. Digests are editorial — curate ruthlessly.\n- **Stale content.** Repeating items across digests. Track what's been sent; never repeat.\n- **Adding without subtracting.** New digest on top of existing notification emails. Consolidate — net reduction.\n- **Generic for everyone.** Same digest for all roles. Personalize or perish (in the spam folder).\n- **Weak subject lines.** \"Your weekly digest\" every week. Specific, fresh subjects referencing actual content.\n- **No preference control.** Forcing frequency. Let users choose daily\u002Fweekly\u002Foff.\n- **Ignoring mobile.** Desktop-designed digests read on phones. Mobile-first, always.\n- **Kitchen-sink digests.** Including everything to avoid choosing. Curation is the product — if everything is included, nothing is curated.\n- **Stale personalization.** \"Recommended for you\" that clearly is not. Bad personalization is worse than none — it signals you do not know the user.\n- **No sunset for non-openers.** Continuing daily digests to users who never open. Suppress or downshift chronic non-openers to protect deliverability.\n- **Identical digests for all.** No personalization beyond the name. Segment by interest or behavior — relevance is the product.\n- **Broken links.** Digest links rotting. Validate links before sending; broken links train users to stop clicking.\n",{"name":5,"category":24,"description":7},"enterprise-communication","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-digest-emails",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 digest-emails",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill digest-emails",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill digest-emails","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-digest-emails\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",[],[]]