Newsletter source research

Skill Get-Maito/newsletter-skills/skills/newsletter/newsletter-source-research

Open-source agent skills for newsletter operators.

Install

npx -y skills add Get-Maito/newsletter-skills --skill newsletter-source-research

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user asks to find, clean, verify, organize, or curate sources, links, ideas, expert quotes, product updates, industry news, trend signals, or research queues for a newsletter issue.

SKILL.md

2.1 KB, as published. Nobody here has run it

Newsletter Source Research

Find and organize source material for a newsletter issue.

Core Rule

Prepare source material that an issue builder can use safely. Keep verified facts, useful context, weak claims, and excluded items separate.

Source Types

Use the user's known source list first. Add relevant sources from:

Official company, product, organization, or event pages
Industry publications, blogs, newsletters, podcasts, and reports
Expert posts, interviews, talks, filings, papers, or changelogs
Community forums, Reddit, LinkedIn, X, Discord, Slack, or niche groups when appropriate
Search, archives, trend tools, analytics exports, and prior issues
Local calendars and local sources when the newsletter is city/community focused

Workflow

Confirm topic, audience, date range, source types, excluded topics, and issue angle.
Collect candidate sources with title, URL, author/source, date, summary, and relevance.
Verify primary sources for claims that will appear in the issue.
Remove duplicates, outdated items, weak reposts, and low-fit sources.
Group sources by section, angle, audience value, and confidence.
Identify gaps that need manual checking, expert input, or follow-up research.
Save or hand off the source queue for issue building.

Output Format

Use a table with:

Status	Source	Date	Section fit	Audience value	Claim or idea	URL	Notes

Then include:

Best sources for the issue
Backup sources
Items needing manual verification
Excluded items and why
Source gaps and next checks

Guardrails

Prefer primary sources for factual claims.
Do not treat social posts or reposts as verified facts without support.
Do not invent dates, statistics, quotes, prices, or product details.
Keep uncertain items out of final issue copy until verified.