--- layout: tap site_name: daily tap_name: brief description: "Daily briefing from Calendar + Reminders" intent: read columns: - type - title - detail - source args: - name: save type: string default: false description: "Save to Apple Notes" args_json: | {"save":{"type":"string","default":"false","description":"Save to Apple Notes"}} health_json: | {"min_rows":1,"non_empty":[]} example_args: "" source_url: https://github.com/LeonTing1010/tap-skills/blob/main/community/daily/brief.plan.json license: MIT ---

What it does

Daily briefing from Calendar + Reminders

Install Taprun once

Taprun ships as a single MCP server exposing a catalog of compiled taps. One-time setup on macOS / Linux:

brew install LeonTing1010/tap/taprun
tap mcp connect

Or drop this into your claude_desktop_config.json (works identically in Claude Code, Cursor, Cline, Windsurf — any MCP host):

{
  "mcpServers": {
    "tap": {
      "command": "tap",
      "args": ["mcp", "start"]
    }
  }
}

Call daily/brief

Terminal, once installed:

tap run daily/brief

From the MCP host — exact same compiled plan, deterministic replay, zero LLM tokens:

tap.run({ site: "daily", name: "brief" })

Why compile it once

This plan was forged once — the AI read daily, picked stable structural addresses (JSON-LD, ARIA, RSS, or declared API endpoints, in that priority order), and saved them to a .plan.json. Every replay since then has used zero LLM tokens. When daily ships a site change that breaks the extraction, tap verify surfaces it before your data goes stale — not after your pipeline silently writes garbage for a week.