New advertisers: 50% off your first month with code FIRSTMONTHSee slots

Developer article search and daily.dev feed access inside Claude Code, grounded in community-vetted sources.

version
0.34.0
GitHub stars
20.2K

What it does

  • Adds /daily-dev:ask, /daily-dev:trends, /daily-dev:daily-dev-routine, and a rotating headline band with Open and Hide controls
  • Covers technical Q&A with links to the articles used, plus curated headlines and most-upvoted posts of the day
  • Grounds answers in daily.dev's knowledge base and the public feed rather than model memory, with no API token to store
  • Designed for developers who want a daily reading brief matched to their current work, with OAuth sign-in through /mcp

Overcome LLM knowledge cutoffs with real-time developer content. daily.dev aggregates articles from thousands of sources, validated by community engagement, with structured taxonomy for precise discovery.

Add marketplace

/plugin marketplace add dailydotdev/daily

Run it inside Claude Code once, then install the plugin below.

Install

/plugin install daily-dev@daily.dev

Run it inside Claude Code after adding the marketplace.

Files

Discovered from source

daily.dev Ask

A developer-focused search tool — like WebSearch, but backed by a senior dev's reading list instead of the open web. Searches community-vetted developer articles ranked by upvotes and synthesizes grounded answers with source links.

User question

$ARGUMENTS

Connecting

Search through the daily.dev MCP tools this plugin provides. If they are missing, or only an authentication tool is listed for the daily-dev server, ask the user to run /mcp, pick daily-dev and sign in. There is no token to handle: never ask for one, and never look for one in the user's environment, files or OS secure storage.

Workflow

1. Search iteratively — treat daily.dev like a search engine

Use the tools below as many times as needed to explore the user's question. There is no hard limit on the number of queries — search like you would with web search.

Keyword search: getRecommendKeyword with q set to the core technical terms and limit 20.

Full-text search: getSearchPosts with q set to the user's own wording and limit 20. Use it as a fallback whenever keyword recommendations come back thin.

Both return:

{
  "data": [
    {
      "id": "...",
      "title": "Article title",
      "url": "https://...",
      "summary": "Article summary...",
      "tags": ["tag1", "tag2"],
      "readTime": 7,
      "numUpvotes": 342,
      "numComments": 28,
      "source": { "name": "Publisher Name" }
    }
  ]
}
Search strategy
  1. Initial searches — Start with a keyword search (core technical terms) and a full-text search (the full question). You can run these in parallel.

  2. Analyze and identify gaps — Review the results:

    • Did I find enough to fully answer the question?
    • Are there sub-topics or related concepts I haven't explored?
    • Did article titles/tags hint at related terms worth searching?
  3. Follow-up searches — For any gaps or interesting leads:

    • Search for specific tools, libraries, or frameworks mentioned in results
    • Try synonyms or alternative terminology
    • Search for sub-topics the user might care about
  4. Stop when done — Stop searching when:

    • You have enough articles to give a good answer, OR
    • Follow-up searches return no new results

2. Deduplicate results

Merge results from all search rounds, removing duplicates by id. Keep all unique articles.

3. Synthesize the answer

Using all collected articles, compose a response:


Answer the question directly, grounding your response in the article content. Reference specific articles when making claims. Use the summary, title, and tags to understand each article's angle.

Use engagement signals to weight credibility:

  • Higher numUpvotes = more community validation
  • Higher numComments = more discussion/nuance available
  • readTime helps gauge depth

Sources section — list the most relevant articles:

### Sources from daily.dev

1. [Article Title](url) — summary snippet (⬆️ upvotes · 💬 comments)
2. [Article Title](url) — summary snippet (⬆️ upvotes · 💬 comments)
...

4. Handle edge cases

  • No results: State that daily.dev's knowledge base doesn't have relevant articles on this topic yet.
  • Only some searches return results: Use whatever you got — partial results are fine.
  • API errors (401): The sign-in is missing or expired — ask the user to run /mcp and sign in to daily-dev again
  • API errors (429): Rate limited — wait briefly and retry automatically.

Important

  • Do NOT make up information — only use what the articles provide. If the articles don't cover part of the question, say so explicitly.
  • Always link to sources — every factual claim should trace back to an article.
  • Prefer recent articles — if two articles conflict, note both perspectives and mention which is newer.
  • Be honest about gaps — if the articles only partially answer the question, say "Based on available articles, here's what I found..." and note what's missing.

Readme

daily.dev plugin for Claude Code

Real-time developer content from daily.dev, inside Claude Code.

Install it from the daily.dev marketplace (Claude Code 2.1.275 or later does this in one step):

/plugin install daily-dev --marketplace dailydotdev/daily

The first time a daily.dev skill needs your account, run /mcp, pick daily-dev and sign in. daily.dev opens in your browser, where you sign in or create an account and approve access. There is no API token to create or store, and you can disconnect any time from Settings > API on daily.dev.

Moving from the daily.dev plugin

Versions before 0.30.0 were published as daily.dev. Replace it with this one:

claude plugin uninstall daily.dev@daily.dev
claude plugin install daily-dev@daily.dev

Skills are now under /daily-dev:, for example /daily-dev:trends. If you added https://api.daily.dev/mcp to Claude Code yourself, you can remove that server: the plugin brings its own.

What you get:

  • daily.dev MCP server — the plugin connects Claude Code to https://api.daily.dev/mcp, with OAuth sign-in. Every skill below uses it.
  • daily.dev skill — query feeds, search posts, and pull personalized content from your daily.dev account. Works with any daily.dev account.
  • /daily-dev:daily-dev-ask skill — answers technical questions from daily.dev's knowledge base, with links to the articles it used.
  • /daily-dev:trends skill — today's curated headlines and most-upvoted posts, no token needed.
  • /daily-dev:daily-dev-onboarding skill — sets up your daily.dev account from the agent: sign in or create the account, then tags, sources, squads and preferences based on what you work on.
  • /daily-dev:daily-dev-routine skill — a daily or weekly brief of what is worth reading on daily.dev for what you are working on, run on a schedule.
  • /daily-dev:daily-dev-profile skill — makes your daily.dev profile credible: photo, headline, current role, About me, links and stack.
  • For daily.dev for Startups companies — daily-dev-content-strategy plans what your page publishes with you, daily-dev-content-ideas and daily-dev-content-review shape posts with your weekly intel, and daily-dev-growth-routine schedules a daily report on your page, posts and boosts, with reminders at the content cadence you choose and a weekly or monthly review against your strategy.
  • Headlines — rotating daily.dev headlines while you wait, in a band above the prompt with Open and Hide. Curated major headlines interleaved with the community's most-upvoted posts of the day, refreshed every 10 minutes, rotating every ~60 seconds. Headlines are clickable in terminals with hyperlink support (iTerm2, Kitty, WezTerm, Ghostty).

Headlines setup

Nothing to set up. On Claude Code 2.1.275 or later the plugin ships a hooks module that shows the headline band as soon as the plugin is installed, with no edits to your settings.json. Your own statusLine setting, if you have one, keeps working alongside it. Press Hide on the band to dismiss it for the current session.

Upgrading from the old statusline

Versions before 0.7.0 wired the headlines into statusLine in ~/.claude/settings.json. Leaving that in place next to the new hooks module shows the headline twice. Run:

/daily-dev:statusline

and Claude removes the old entry. If you prefer to do it by hand, delete the statusLine key whose command points at statusline/statusline.mjs.

Older Claude Code

Claude Code before 2.1.275 does not load the hooks module, so the band does not appear. The old setup still works there: run /daily-dev:statusline and Claude wires the script into ~/.claude/settings.json, or point statusLine at the plugin's script yourself. The glob keeps it working across plugin updates:

{
  "statusLine": {
    "type": "command",
    "command": "node \"$(ls -td \"$HOME/.claude/plugins/cache/daily-dev/daily-dev\"/*/ | head -1)statusline/statusline.mjs\"",
    "refreshInterval": 10
  }
}

This replaces any custom statusline you already have, since Claude Code user settings hold a single statusLine.

Notes

  • Requires node on your PATH. Honors NO_COLOR.
  • Content is fetched anonymously from the public daily.dev API and cached in ~/.cache/dailydev-claude/.
  • The hooks module runs the same statusline/statusline.mjs script, so caching, the 24h no-repeat history and click attribution behave the same either way.

Telemetry

The headlines report anonymous impressions (which headlines were shown) to daily.dev analytics, using the same anonymous tracking id a logged-out daily.dev visitor gets. No code, file paths, or session content is ever collected — events carry only the shown post id and plugin version.

Opt out any time:

export DAILY_DEV_TELEMETRY=0

Details

Marketplace
dailydotdev/daily
Source
.claude-plugin/plugins/daily-dev
Author
daily.dev
Category
Productivity
License
AGPL-3.0-only
Keywords
daily.dev, api, developer, content, feed, dailydotdev

More from dailydotdev/daily

All 3

Similar to daily-dev

More Productivity & Planning