Plugin marketplace
The plugin marketplace is where developers share what they build on top of the daily.dev API: agent skills, apps and tools that turn your feed, bookmarks and profile into new workflows. Browse it at daily.dev/marketplace.
What's in a plugin
Every plugin has a name, a short description and an about page that explains what it does and how to use it. On top of that, a plugin has one or both of:
- Agent instructions (SKILL.md): a markdown file your coding agent reads to learn the workflow. Plugins with one show an Agent skill label.
- A link: the plugin's homepage, repository, docs or anything else.
Apps count too. A web app, CLI, bot or dashboard built on the API is a plugin with a link: a bookmark triage tool, a quiz generator fed by your feed, a digest filtered by your tech stack, a game played with your bookmarks. If people connect their own daily.dev account to it, let them sign in with daily.dev instead of pasting a token.
Use a plugin
- Open a plugin from the marketplace.
- Read the about section to see what it does and what it needs.
- If the plugin has agent instructions, click SKILL.md. It opens the raw file at a link like
https://api.daily.dev/public/v1/plugins/<plugin-id>/skill.md. That link works without signing in, so you can hand it straight to your agent:
Read https://api.daily.dev/public/v1/plugins/<plugin-id>/skill.md and follow it using my daily.dev API token.
Most plugins call the daily.dev API on your behalf, so your agent needs a personal access token. See Setup and first query if you don't have one yet. If your agent is connected to the daily.dev MCP server, it already has the tools a SKILL.md refers to and can follow the instructions with those instead of raw HTTP calls.
Install from Claude Code, Codex or Cursor
Approved plugins that have a SKILL.md are also published to the daily.dev community marketplace, a plugin marketplace for coding agents at github.com/dailydotdev/marketplace. Add it once and install plugins the same way you install any other plugin in your agent. When a plugin is added, updated or removed on daily.dev, the change reaches the community marketplace after the daily.dev team reviews it.
Claude Code
claude plugin marketplace add dailydotdev/marketplace
claude plugin install <plugin-name>@daily-dev-community
Inside a Claude Code session you can run the same commands as /plugin marketplace add dailydotdev/marketplace and /plugin install <plugin-name>@daily-dev-community.
Codex
codex plugin marketplace add dailydotdev/marketplace
Then open /plugins and install plugins from the daily.dev community marketplace.
Cursor (Teams and Enterprise)
In the Cursor dashboard, go to Plugins & MCPs > Team Marketplaces, choose Import from Repo and paste https://github.com/dailydotdev/marketplace. Turn on Auto Refresh so new plugins show up as they are approved.
Plugin names in the community marketplace are lowercase with dashes, for example bookmark-recap. The list of plugins is in the repository's plugins/ folder. Plugins that only have a link, without a SKILL.md, are not part of it.
Submit a plugin
Anyone with a daily.dev account can submit a plugin. Go to daily.dev/marketplace/submit and fill in:
| Field | Required | Notes |
|---|---|---|
| Name | Yes | 3 to 60 characters. |
| Short description | Yes | Your pitch in 1 to 3 sentences, up to 300 characters. This is what people see on marketplace cards, so make it count. |
| About | Yes | What the plugin does and how to use it, up to 20,000 characters. Formatting like headings, lists and code blocks is fine, but links and images are not. |
| SKILL.md | One of these two | Agent instructions, up to 50,000 characters. |
| Link | One of these two | Homepage, repository or docs, up to 500 characters. If you leave out https://, daily.dev adds it. |
You need a SKILL.md, a link, or both.
Review and status
Every submission is reviewed by the daily.dev team before it appears in the marketplace. Track your submissions under Your plugins at daily.dev/marketplace/submissions:
| Status | What it means |
|---|---|
| In review | Waiting for the daily.dev team. |
| Not approved | The submission wasn't accepted. You can dismiss it from your list. |
Approved plugins move to your list of live plugins and appear in the marketplace.
Update, cancel or delete
From Your plugins:
- Edit a live plugin to send an update for review. The current version stays live until the update is approved. If you send another update while one is still in review, the newer one replaces it.
- Cancel a submission that's still in review to withdraw it.
- Dismiss a submission that wasn't approved to clear it from your list.
- Delete a live plugin to remove it from the marketplace. Its page and SKILL.md link stop working.
Plugins in the public API
The marketplace is also available through the public API and the daily.dev MCP server, so agents can find, submit and update plugins themselves:
| Endpoint | MCP tool | What it does |
|---|---|---|
GET /public/v1/plugins |
getPlugins |
List approved plugins, newest first. Use q to search names and descriptions. |
GET /public/v1/plugins/{id} |
getPluginsById |
Get one plugin, including its about section and skillMdUrl. |
POST /public/v1/plugins |
postPlugins |
Submit a plugin for review with name, description, about, and skillMd, url or both. |
PUT /public/v1/plugins/{id} |
putPluginsById |
Send an update to one of your live plugins for review, with the same fields as a submission. The current version stays live until the update is approved. |
Agent instructions aren't included in the JSON responses. Fetch them from the plugin's skillMdUrl, which needs no token.
Building an app?
If your plugin is an app or service that other developers use, register it as an OAuth app. People then sign in with daily.dev and approve access, and your app calls the API on their behalf without asking them to paste a personal access token.