community-check
Before you adopt a tool or technique, find out what the daily.dev community actually thinks. Reads the most-discussed posts and their comment threads on a topic and summarizes the consensus, the disse
SKILL.mdplugins/community-check/skills/community-check/SKILL.md
GitHubCommunity Check
Answer the question "what do developers on daily.dev actually think about X?" by reading discussions, not just articles. Articles tell you what authors claim; comment threads tell you what happened in production.
Requirements
One of:
- The daily.dev MCP server (
https://api.daily.dev/mcp) connected to your agent, or - A daily.dev personal access token in
DAILY_DEV_TOKEN(create one at https://daily.dev/settings/api). Base URLhttps://api.daily.dev/public/v1, headerAuthorization: Bearer $DAILY_DEV_TOKEN. Never send the token anywhere exceptapi.daily.dev.
Each step below lists the MCP tool first and the REST call after it.
Steps
- Find the posts. Run both and merge:
getSearchPostswithqset to the topic andlimit15 (REST:GET /search/posts?q=<topic>&limit=15).getFeedsDiscussedwithlimit20 andperiod30, filtered withtagwhen the topic is a known tag (REST:GET /feeds/discussed?limit=20&period=30&tag=<tag>). UsegetSearchTags(GET /search/tags?q=) to confirm the tag name first.
- Pick the conversations. From the merged list keep the 4–6 posts with the most
numComments. Ignore posts with fewer than 3 comments. - Read the threads. For each kept post call
getPostsByIdCommentswithlimit30 (REST:GET /posts/{id}/comments?limit=30). Read replies too, they are nested underchildren. - Synthesize. Group what you read into:
- Consensus: claims repeated across threads by different people.
- Dissent: credible disagreement, with the strongest version of the argument.
- Gotchas from production: specific failures, migrations, costs, performance numbers.
- Open questions: things people asked that nobody answered well.
- Cite. Every claim gets the post title linked to its
commentsPermalink. Quote comments sparingly and attribute them byauthor.username.
Output
Keep it under 400 words unless asked for more. Lead with a one-sentence verdict, then the four groups, then a "Sources" list. Include upvote and comment counts next to each source so the reader can judge weight.
Guardrails
- Read-only. Don't upvote, bookmark or comment.
- If fewer than two posts have real discussion, say so instead of inventing a consensus.
- Each call uses one request of the user's daily.dev API quota. Stay under ~10 calls per check.