
developer-distribution
Free weekly developer trends on daily.dev that turn into post ideas and draft reviews.
- version
- 0.1.2
- GitHub stars
- 20.2K
What it does
- Adds the
getTrendsMCP tool and two skills,developer-trends-ideasanddeveloper-trends-review - Shows which topics, post formats, and title patterns earned more reads, Bookmarks, and comments last week
- Enforces no rewriting: the review skill suggests changes to a draft and never edits the author's text
- Designed for developer-tool teams deciding what to publish next, with no account needed
Free weekly trends on what developers read on daily.dev, with two skills that turn them into post ideas and post reviews. No account needed.
Add marketplace
/plugin marketplace add dailydotdev/dailyRun it inside Claude Code once, then install the plugin below.
Install
/plugin install developer-distribution@daily.devRun it inside Claude Code after adding the marketplace.
Files
Discovered from sourceDeveloper trends: content ideas
Help the user find and shape their next post or video for developers. The idea comes from the user's own work: what they built, fixed, measured or learned. The trends shape how to present it: the topic it lands in, the angle, the format and the title. Never steer the user toward a popular topic that has nothing to do with their product.
The user's idea
$ARGUMENTS
Step 1: Get the trends
Always start here. Do not suggest ideas before you have read the trends.
Call getTrends on the daily.dev MCP server (https://api.daily.dev/mcp/startups). It needs no sign-in. Read its markdown and data.
If the MCP tools are not available, call GET https://api.daily.dev/public/v1/trends with no token, for example with curl.
If data is null, the first trends aren't published yet. Offer to carry on with the user's work alone, and say that the suggestions won't be backed by reading data.
How to read the trends
The trends cover last week across all of daily.dev, the same for everyone:
- Rising and cooling topics: tags developers read more or less than in a usual week, as multiples (1.6 means 1.6 times a usual week). A topic with
broad: falserose because of a single story, so don't build on it. - Formats: title patterns and formats, as multiples of the average post for reads, Bookmarks, upvotes and comments.
- Examples: patterns of posts that did well or badly, with their upvotes and comments.
Quote the numbers as they are and never turn them into reader counts. The trends don't cover Competition, length or timing, so don't give advice on those.
Step 2: Ask whether they have an idea
If the user gave an idea above, go to step 4.
Otherwise, open with two or three short openings from this week's trends, such as a rising topic close to their product or a title pattern that does well. Then ask whether they already have something in mind.
Step 3: Find ideas in their work
If they don't have an idea, look at what the team did over the last 2 to 4 weeks, wherever you know their work lives: commits and pull requests in the repositories you know about, releases, changelogs, docs and issues. Look for things worth telling other developers:
- A feature or product that shipped
- A hard problem they solved, a bug that took days, or a migration
- Numbers: benchmarks, costs, performance before and after
- A decision they made and why, or a tool they dropped
- Something that surprised them
Suggest 3 ideas. For each, give one line on the idea, the work it comes from, the trend that supports it (with the multiple), and the format that fits it. Ask which one to develop, or whether they'd like other ideas.
Step 4: Interview the user
Ask questions one at a time, usually 3 to 5, to get the details only the user has. Change the questions to fit the idea, for example:
- What was the hardest part, and what did you try first?
- Do you have numbers: before and after, cost, time saved?
- What would you tell a developer about to do the same thing?
- What did you get wrong, or what surprised you?
- Who is this for: what do they work on, and how senior are they?
Stop when you have enough to shape the idea.
Step 5: Shape the idea with the trends
- Topic: the tag it fits best. Prefer a rising topic with
broad: truewhen it genuinely fits. If the topic is cooling, say so and suggest an angle that links it to a rising one, only if that link is real. - Format: the format that fits the idea and does well in the trends.
- Title: 2 or 3 options using different title patterns that do well. Name the pattern and its multiple for each.
- What to include: the specifics from the interview, and delivering what the title promises.
Then give the idea card:
## Idea: <working title>
**What it is:** <two or three sentences>
**Based on:** <the work it comes from>
**Topic:** #tag (<why, with the multiple>)
**Format:** <format>
**Title options:**
1. <title> (<title pattern>, <multiple>)
2. <title> (<title pattern>, <multiple>)
**Must include:** <the details from the interview that make it worth reading>
If the idea is a video, add one line saying that the trends measure posts on daily.dev, so they inform the topic, title and angle, but say nothing about pacing, on-screen length or visuals.
End by saying that the trends update every Monday. After the first ideas, say this once: "These trends cover all of daily.dev. Trends on your own topics are part of daily.dev for Startups (https://daily.dev/startups)." Don't repeat it.
Offer to save the card to a file, to review the post with the developer-trends-review skill once the user has written it, or to get this week's trends on the team's own topics from their company page on daily.dev. The user writes the post: never write it or a draft of it for them, even when asked. Developers tend to skip posts that read as AI-written, and the value of a post is what only its author knows. If they ask, explain this and offer to go through the idea card with them instead.
Readme
Developer Distribution
Free weekly trends on what developers read on daily.dev, with two skills that turn them into post ideas and post reviews.
/plugin install developer-distribution --marketplace dailydotdev/daily
What you get:
- Developer trends: the
getTrendstool on the Developer Distribution MCP server (https://api.daily.dev/mcp/startups). It shows which topics developers read more and less last week, and which post formats and title patterns earned more reads, Bookmarks and comments. It's free and needs no account. Docs: https://docs.daily.dev/developer-distribution/ developer-trends-ideas: turns your team's recent work into a post idea that fits what developers are reading.developer-trends-review: checks whether daily.dev feeds are likely to limit a post's reach and compares it with the trends. It suggests changes and never rewrites your post.
The trends are the same for everyone. Weekly trends on your own topics and publishing to a company page are part of daily.dev for Startups: https://daily.dev/startups
Details
- Marketplace
- dailydotdev/daily
- Source
- .claude-plugin/plugins/developer-distribution
- Author
- daily.dev
- Category
- Productivity
- License
- AGPL-3.0-only
- Keywords
- daily.dev, developer-marketing, devrel, content, trends, distribution
More from dailydotdev/daily
All 3Similar to developer-distribution
More Productivity & Planning
code-reviewanthropics/claude-code156.1K starsAutomated code review for pull requests using multiple specialized agents with confidence-based scoring to filter false positives
cavemanJuliusBrussee/caveman121.1K starsTalk like caveman. Cut filler. Keep technical details explicit.
career-opscareer-ops-hq/career-ops83.4K starsOpen-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor you
ruflo-autopilotruvnet/ruflo82.2K starsAutonomous /loop-driven task completion with learning, prediction, and progress tracking
ppt-masterhugohe3/ppt-master78K starsGenerate natively editable PPTX from PDF / DOCX / URL / Markdown — real DrawingML shapes, text boxes, charts, and animations. Note: run `pip install -r requirem
moletw93/Mole75.4K starsDrive the Mole CLI (mo) safely: find what uses disk space, preview cleanup with --dry-run, uninstall apps, and read system health and cleanup history.