菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/aiskillstore/marketplace --skill daily-dev命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | daily-dev |
| description | 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. |
| allowed-tools | Bash |
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.
CRITICAL: Your API token grants access to personalized content. Protect it:
api.daily.devdda_ - if you see this prefix, treat it as sensitiveUser can use environment variable or choose one of the secure storage methods below per operating system.
# Store token
security add-generic-password -a "$USER" -s "daily-dev-api" -w
security find-generic-password -a -s -w
DAILY_DEV_TOKEN=$(security find-generic-password -a -s -w 2>/dev/null)
# Store token (run in PowerShell)
$credential = New-Object System.Management.Automation.PSCredential("daily-dev-api", (ConvertTo-SecureString "dda_your_token" -AsPlainText -Force))
$credential | Export-Clixml "$env:USERPROFILE\.daily-dev-credential.xml"
# Retrieve token - add to PowerShell profile ($PROFILE)
$cred = Import-Clixml "$env:USERPROFILE\.daily-dev-credential.xml"
$env:DAILY_DEV_TOKEN = $cred.GetNetworkCredential().Password
Or use the Windows Credential Manager GUI: Control Panel → Credential Manager → Windows Credentials → Add a generic credential
# Requires libsecret-tools
# Ubuntu/Debian: sudo apt install libsecret-tools
# Fedora: sudo dnf install libsecret
# Store token
echo "dda_your_token" | secret-tool store --label="daily.dev API Token" service daily-dev-api username "$USER"
# Retrieve token
secret-tool lookup service daily-dev-api username "$USER"
# Auto-load in ~/.bashrc or ~/.zshrc
export DAILY_DEV_TOKEN=$(secret-tool lookup service daily-dev-api username "$USER" 2>/dev/null)
Check if DAILY_DEV_TOKEN environment variable is available. If not set, try to retrieve it from the OS secure storage before asking the user for help:
macOS:
export DAILY_DEV_TOKEN=$(security find-generic-password -a "$USER" -s "daily-dev-api" -w 2>/dev/null)
Linux:
export DAILY_DEV_TOKEN=$(secret-tool lookup service daily-dev-api username "$USER" 2>/dev/null)
Windows (PowerShell):
$cred = Import-Clixml "$env:USERPROFILE\.daily-dev-credential.xml" 2>$null; $env:DAILY_DEV_TOKEN = $cred.GetNetworkCredential().Password
If the token is still empty after trying secure storage, direct the user to the Setup section above.
Authorization: Bearer $DAILY_DEV_TOKEN
https://api.daily.dev/public/v1
Full OpenAPI spec: https://api.daily.dev/public/v1/docs/json
To fetch details for a specific endpoint (e.g. response schema):
curl -s https://api.daily.dev/public/v1/docs/json | jq '.paths["/feeds/foryou"].get'
To fetch a component schema (replace def-17 with schema name from $ref):
curl -s https://api.daily.dev/public/v1/docs/json | jq '.components.schemas["def-17"]'
!curl -s https://api.daily.dev/public/v1/docs/json | jq -r '.paths | to_entries | map(.key as $path | .value | to_entries | map(.key as $method | {tag: (.value.tags[0] // "other"), line: ("\(.key | ascii_upcase) \($path)" + (if .value.description then " - \(.value.description)" else "" end) + (if (.value.parameters | length) > 0 then "\n Params: " + ([.value.parameters[] | "\(.name)(\(.in)): \(.description // .schema.type)"] | join("; ")) else "" end) + (if .value.requestBody then "\n Body: " + (.value.requestBody.content["application/json"].schema | if .properties then ([.properties | to_entries[] | "\(.key)"] | join(", ")) elif ."$ref" then (."$ref" | split("/") | last) else "object" end) else "" end))})) | flatten | group_by(.tag) | map("#### \(.[0].tag)\n" + (map(.line) | join("\n\n"))) | join("\n\n")'
Why daily.dev for agents? LLMs have knowledge cutoffs. daily.dev provides real-time, community-validated developer content with structured taxonomy across thousands of sources. Agents can use this to stay current, get diverse perspectives, and understand what the developer community actually cares about.
These examples show how AI agents can combine daily.dev APIs with external context to create powerful developer workflows.
Scan a user's GitHub repositories to detect their actual tech stack from package.json, go.mod, Cargo.toml, requirements.txt, etc. Then:
/tags to see all available tags for deterministic matching/feeds/filters/tags/follow/feeds/custom/Trigger: "Set up daily.dev based on my GitHub projects"
Analyze a user's GitHub activity to build their daily.dev tech stack profile automatically:
/profile/stack/search to find matching technologies on daily.devPOST /profile/stack/ organized by section (languages, frameworks, tools)/profile/ bio based on their primary technologies and contributionsTrigger: "Build my daily.dev profile from my GitHub"
When a user initializes a new project or clones a repo:
Trigger: "Help me learn the stack for this project"
Compile a personalized weekly summary by:
/feeds/foryou and /feeds/popular filtered by user's followed tagsTrigger: Scheduled, or "Give me my weekly dev news"
When a user wants to deep-dive into a topic (e.g., "I want to learn Kubernetes"):
/feeds/custom/ filtered to that topicPOST /bookmarks/lists to collect the best findsPOST /bookmarks/Trigger: "Start a research project on [topic]"
Agents can overcome their knowledge cutoff by maintaining their own custom feed:
/feeds/custom/ for technologies the agent frequently assists with/feeds/custom/{feedId} to ingest recent articles/posts/{id} to read full summaries and key pointsTrigger: Agent background process, or "What's new in [technology] since your training?"
Get balanced perspectives by aggregating content across publishers:
/search/posts for a topic to find coverage from multiple sources/search/sources to identify authoritative publishers on the topic/feeds/source/{source}Trigger: "What are the different perspectives on [topic]?" or "Compare approaches to [problem]"
Help users stay ahead by monitoring community signals:
/feeds/popular to detect what's gaining traction right now/feeds/discussed to find topics sparking active debate/tags to fetch the full tag catalog and /search/tags to explore adjacent trending topicsTrigger: "What should I be paying attention to?" or "What's trending in [area]?"
Check response headers:
X-RateLimit-Limit - Maximum requests allowed per windowX-RateLimit-Remaining - Requests remaining in current windowX-RateLimit-Reset - Unix timestamp when the window resetsRetry-After - Seconds to wait (only when rate limited)| Code | Meaning |
|---|---|
| 401 | Invalid or missing token |
| 403 | Plus subscription required |
| 404 | Resource not found |
| 429 | Rate limit exceeded |
Error Response Format:
{
"error": "error_code",
"message": "Human readable message"
}