/daily-dev-ask

name: daily-dev-ask
description: Your agent's WebSearch for development. Search community-vetted developer articles ranked by upvotes — like having a senior dev's reading list. Answers are grounded in real sources, never hallucinated.
argument-hint: "<your technical question>"
allowed-tools: Bash

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

Security

**CRITICAL:** Your API token grants access to personalized content. Protect it:

• **NEVER send your token to any domain other than `api.daily.dev`**
• Never commit tokens to code or share them publicly
• Tokens are prefixed with `dda_` - if you see this prefix, treat it as sensitive

Setup

1. **Create a token** at https://daily.dev/settings/api - every account can create one, no subscription needed 2. Store your token securely (environment variables, secrets manager)

If the agent is already connected to the daily.dev MCP server (`https://api.daily.dev/mcp`), skip the token steps: the calls below map to the `getSearchPosts` and `getPostsById` tools.

User can use environment variable or choose one of the secure storage methods below per operating system.

Secure Token Storage (Recommended)

macOS - Keychain

# Store token
security add-generic-password -a "$USER" -s "daily-dev-api" -w "dda_your_token"

# Retrieve token
security find-generic-password -a "$USER" -s "daily-dev-api" -w

# Auto-load in ~/.zshrc or ~/.bashrc
export DAILY_DEV_TOKEN=$(security find-generic-password -a "$USER" -s "daily-dev-api" -w 2>/dev/null)

Windows - Credential Manager

# 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

Linux - Secret Service (GNOME Keyring / KWallet)

# 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)

Workflow

1. Determine the API token

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.

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

Use the endpoints 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 endpoint:**

curl -s -H "Authorization: Bearer $DAILY_DEV_TOKEN" "https://api.daily.dev/public/v1/recommend/keyword?q={keywords}&limit=20"

**Full-text search endpoint** (use the user's own wording, and as a fallback whenever keyword recommendations come back thin):

curl -s -H "Authorization: Bearer $DAILY_DEV_TOKEN" "https://api.daily.dev/public/v1/search/posts?q={query}&limit=20"

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

3. Deduplicate results

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

4. 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
• `rea