Weekly Newsletter

langchain-ai/weekly-newsletter

Produce the weekly 'This Week in Music' customer newsletter by researching the distributor's top genres in parallel and assembling a styled HTML page. Use when asked to create, write, or send the weekly newsletter or a music-news roundup.

361 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/langchain-ai/lca-deepagents --skill weekly-newsletter

What it tells the agent to use

found in the instruction text

Task spawns other agents

The instruction itself

6 sections, as written by the author

A parallel-research task. Coordinate; let the researchers do the digging.

1. Pick the genres

If Jane named genres, use those. Otherwise ask chinook-analyst for the

top 4 genres by revenue across the catalogue and feature those.

2. Research in parallel

For each genre, delegate to a genre-researcher subagent with the

task tool — fire them all off together so they run in parallel.

Tell each researcher its one genre and a private folder

(/research/<genre>/) for raw notes. Ask for a single ~120–180 word

Markdown segment headed ## <Genre>.

Do not research genres yourself — your job is to assemble.

3. Assemble

Collect the returned segments into one Markdown document:
# This Week in Music title
a one-sentence intro
the genre segments, in order

4. Render and save

Call markdown_to_html on the assembled Markdown.
Use the code interpreter to get today's date: new Date().toISOString().slice(0, 10).
write_file the returned HTML to /outputs/newsletter-<date>.html.

Done

Tell Jane where the newsletter was saved and list the genres covered.

How to use it

Copy the folder

Take langchain-ai/weekly-newsletter from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.