# Radar

When you want to monitor known sources on a schedule and feed the good stuff into your...

- Repository: https://github.com/coreyhaines31/makerskills (880 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add coreyhaines31/makerskills --skill radar -g -a claude-code -y`
Codex: `npx skills add coreyhaines31/makerskills --skill radar -g -a codex -y`
Cursor: `npx skills add coreyhaines31/makerskills --skill radar -g -a cursor -y`
Gemini CLI: `npx skills add coreyhaines31/makerskills --skill radar -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add coreyhaines31/makerskills`

## Description

When you want to monitor known sources on a schedule and feed the good stuff into your second brain. Configure sources once (YouTube, RSS/newsletters, subreddits, Hacker News, Bluesky, Mastodon, X, LinkedIn, keyword searches); each run fetches only what's new, scores it against your stated focus, writes one digest to the vault, and auto-captures high-signal items into raw/. Everything else waits in the digest until you promote it. Modes, run, digest, promote, add / sources / pause, doctor, schedule (daily launchd or systemd job). Triggers on \"/radar,\" \"run my radar,\" \"check my sources,\" \"what's new from my sources,\" \"add a source,\" \"monitor this channel,\" \"watch this subreddit,\" \"track this account,\" \"daily digest,\" \"promote item 4,\" \"radar doctor.\" Complements second-brain (radar fills raw/, second-brain compiles it) and deep-research (standing surveillance vs a one-off dive).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /radar, Standing surveillance on the sources you care about

`deep-research` answers a question you asked. `radar` surfaces the answers to questions you haven't asked yet, from sources you already trust, every day, without you going to look.

## Mental model

```
sources.yaml  →  fetch new only  →  score  →  digest  →  promote  →  raw/  →  /sb compile
  (config)        (state files)     (1, 5)    (vault)    (you)      (vault)     (wiki)
```

Two hard rules keep this from becoming noise:

1. **Only one thing is written per run by default**, the digest. Individual `raw/` captures happen only for items that clear the auto-capture bar, or that you explicitly promote.
2. **Nothing is fetched twice.** Every source has a state file of seen item IDs. A run at 7am and a manual run at 9am produce no duplicates.

## Layout

| Path | What |
|---|---|
| `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/radar/sources.yaml` | The source list (private, gitignored) |
| `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/radar/interests.local.md` | Global relevance context, what you care about right now |
| `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/radar/state/<source-id>.json` | Seen-item IDs + last run per source |
| `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/radar/runs/<date>.json` | Machine-readable run record (backs `promote`) |
| `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/radar/logs/<date>.log` | Unattended-run stdout, for debugging a silent morning |
| `<vault>/outputs/radar/<YYYY-MM-DD>.md` | The human digest |
| `<vault>/raw/<type>-<slug>.md` | Captured items, in second-brain's schema |

`<vault>` is `${SECOND_BRAIN_VAULT:-$HOME/Documents/SecondBrain}`.

## Step 0, Parse mode

The rest: https://github.com/coreyhaines31/makerskills/blob/HEAD/skills/radar/SKILL.md