daily.dev

View saved version →

---
name: daily-dev
description: Use the daily.dev Public API to explore a user's personalized feed, trending posts, bookmarks, custom feeds, filters, notifications, and profile, or make requested changes to those resources.
---

# daily.dev

Use this skill when the user asks about their daily.dev account or developer reading feed. The canonical API reference is https://docs.daily.dev/public-api/ and its OpenAPI specification is https://api.daily.dev/public/v1/docs/json. Use of the API is subject to https://r.daily.dev/tos. Check the live specification for endpoint parameters and request bodies before an unfamiliar operation; do not guess fields.

## Connect and choose tools

In ChatGPT Work, use the daily.dev MCP connection bundled with this plugin. When it is not linked, guide the user through the connection's OAuth sign-in; do not ask for a personal access token in chat. Once linked, inspect the connected MCP tool names, descriptions, and input schemas and select the tool matching the task. Do not invent a tool name or call the REST API from a hosted environment in place of the connected tool. Report a connection or scope error as such.

The endpoint map below helps choose a workflow and supports local environments. MCP tool names and input schemas are authoritative for MCP calls; the OpenAPI spec is authoritative for direct REST calls. Do not assume one-to-one tool names or arguments from REST paths.

## Local REST fallback and token

Only if a local agent has no MCP connection and can access `api.daily.dev`, the Public REST API uses `https://api.daily.dev/public/v1` and `Authorization: Bearer <token>`. The user can generate a personal access token at https://daily.dev/settings/api. Use `DAILY_DEV_TOKEN` from the local environment or an existing secure credential store if available. If absent, explain setup in their own environment; never request a token in chat. Do not print, log, commit, include in a URL, or transmit it to any host other than `api.daily.dev`. Treat a token beginning `dda_` as secret.

Use an HTTP-capable tool or terminal for the fallback only when network access is permitted. If neither a connected MCP tool nor local REST access is available, describe the concrete setup needed and avoid implying account data was fetched.

## Find the right endpoint

Paths below are relative to the REST base URL. They are a practical map, not MCP tool names or a substitute for the live OpenAPI request and response schemas.

| Task | Endpoint and useful parameters |
| --- | --- |
| Personalized reading | `GET /feeds/foryou?limit=10`; use `cursor` for later pages. |
| Trending or active discussion | `GET /feeds/popular` (`tags` is a comma-separated list); `GET /feeds/discussed` (`period` is 1–30 days, with optional `tag` or `source`). |
| Topic or publisher feed | `GET /feeds/tag/{tag}` or `/feeds/source/{source}`. Search names first if needed. |
| Search content | `GET /search/posts?q=...` with optional `time=day|week|month|year|all`; `GET /search/tags?q=...`; `GET /search/sources?q=...`. |
| Post and discussion | `GET /posts/{id}` and `GET /posts/{id}/comments` (optional `sort`, `limit`, `cursor`). |
| Saved reading | `GET /bookmarks/` (optional `unreadOnly`, `listId`); `GET /bookmarks/search?q=...`; `GET /bookmarks/lists`. |
| Custom feeds | `GET /feeds/custom/`, `/feeds/custom/{feedId}`, and `/feeds/custom/{feedId}/info`; `GET /feeds/custom/advanced-settings` lists available advanced settings. |
| Personal settings | `GET /feeds/filters/` for global filters or `/feeds/filters/{feedId}` for one custom feed; `GET /profile/`, `/profile/experiences/`, `/profile/stack/`. |
| Notifications and catalog | `GET /notifications/`, `/notifications/unread/count`, and `/tags/`. |

Most list routes accept `limit` and `cursor`; the OpenAPI spec supplies the exact range for each route. Use `GET /profile/stack/search?query=...` to find a tool before adding it to the profile.

## Common changes

For MCP changes, inspect the selected tool'

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: daily-dev-ask
description: Research a technical question using daily.dev's community-curated article recommendations, then answer with links and clear limits of the retrieved evidence.
---

# daily.dev Ask

Use this skill for technical questions when the user asks for daily.dev sourced research or community-vetted developer articles. This skill uses the Public API, subject to https://r.daily.dev/tos. The recommendations endpoints are experimental and can change. Check https://api.daily.dev/public/v1/docs/json for current parameters and availability.

## Access

In ChatGPT Work, use the bundled daily.dev MCP connection and its OAuth sign-in. Inspect the available search or recommendation tools and their schemas; do not invent names or assume REST parameters are MCP parameters. Follow the token handling instructions in `daily-dev` only for a local REST fallback. Never ask the user to paste a token in chat. These recommendation capabilities are not available to every account; report access errors accurately. If neither a connected MCP tool nor local REST access is available, say that live daily.dev research could not run.

## Research

The experimental REST recommendation endpoints differ from ordinary `GET /search/posts`: they return compact article metadata and community engagement signals intended for research. Verify current availability in the MCP tool list or, for local REST, the OpenAPI spec.

| Search | Endpoint | Best use |
| --- | --- | --- |
| Keyword | `GET /recommend/keyword?q=...&limit=20` | Specific technologies, names, and technical terms. Supports `cursor` for another page. |
| Full text | `GET /search/posts?q=...` | Natural-language questions, and a fallback whenever keyword recommendations return little. |

For direct REST, both accept a `time` filter such as `month`, `year`, or `all`; `limit` is 1–20 for recommendations and 1–50 for search. URL-encode the query. With `DAILY_DEV_TOKEN` set locally, one shell pattern is:

```bash
curl --fail-with-body --silent --show-error --get \
  -H "Authorization: Bearer $DAILY_DEV_TOKEN" \
  --data-urlencode 'q=RAG vs fine-tuning' \
  --data-urlencode 'limit=20' \
  'https://api.daily.dev/public/v1/recommend/keyword'
```

1. Start with a focused keyword query, then widen with a full-text search using the user's own wording. Use a recent time window for current topics; broaden when results are sparse. Follow up on relevant terms, frameworks, or gaps; stop when searches cease adding useful articles.
2. Merge results by post `id`. Inspect `title`, `url`, `summary`, `tags`, `source`, `readTime`, `numUpvotes`, and `numComments` when returned. Upvotes and comments help prioritize reading, but do not prove technical correctness. A short summary may omit crucial caveats.
3. Open the most relevant original articles for precise claims and, when the question concerns current software behavior, check official documentation too. Note publication dates and conflicting perspectives. If only titles and summaries are available, limit the answer to what those fields support.
4. Answer directly with links near the supported claims. Include a compact list of the most useful articles with title, publisher, and relevant engagement data when helpful. Say what the available material does not answer. If no results appear, report the gap instead of inventing sources.

For MCP authorization errors, guide the user through reconnecting OAuth. For local REST 401, guide the user to regenerate a token at https://daily.dev/settings/api. A 403 may mean a missing scope, a capability the account does not have, or that account confirmation is required. On 429, respect `Retry-After` and retry only as needed; do not run unlimited queries.