coreyhaines31/makerskills / skills/radar
radar
FlaggedWhen 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).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.9 KB |
| references/fetchers.md | markdown | 22.7 KB |
| references/scheduling.md | markdown | 7.5 KB |
| references/sources-schema.md | markdown | 6.2 KB |
| references/templates/digest.md | markdown | 1.1 KB |
| references/templates/sources.example.yaml | config | 4.5 KB |
references/sources-schema.md
View on GitHub# sources.yaml — schema
Lives at `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/radar/sources.yaml`. Private, gitignored, never in the repo.
## Shape
```yaml
defaults:
cadence: daily # daily | weekly | hourly
lookback_days: 2 # window to consider "new" on a normal run
first_run_lookback_days: 3 # window for a source with no state file yet
max_items_per_source: 15
auto_capture_at: 5 # score >= this → fetched + written to raw/ automatically
list_at: 3 # score >= this → listed in the digest as promotable
# below list_at → collapsed into the skipped block
sources:
- id: yt-greg-isenberg # kebab-case, unique, stable — state files key off this
type: youtube
target: "@GregIsenberg"
channel_id: UCG2fPDWk6C1RE0FbTexrJ2A # resolved once at add-time, cached here
focus: >
Business ideas with a real wedge, AI agent products, indie SaaS
teardowns. Not: generic motivation, guest interviews about fundraising.
tags: [business, ai]
enabled: true
```
## Fields
### `defaults`
Every key can be overridden per source. A source that needs a different `auto_capture_at` than the rest is usually a source with a `focus` that needs rewriting instead — check that first.
### Per source
| Field | Required | Notes |
|---|---|---|
| `id` | ✅ | Kebab-case, unique. Convention: `<type-prefix>-<slug>` (`yt-`, `rss-`, `rd-`, `hn-`, `x-`, `li-`, `kw-`). Changing an `id` orphans its state file and re-surfaces old items — rename deliberately. |
| `type` | ✅ | `youtube` \| `rss` \| `reddit` \| `hn` \| `bluesky` \| `mastodon` \| `x` \| `linkedin` \| `keyword` |
| `target` | ✅ | The human-readable handle/URL/query. What you'd type. |
| `focus` | ✅ | Free prose: what you want from this source **and what you don't**. The negative half does most of the filtering work. |
| `enabled` | | Default `true`. `pause` sets this to `false` rather than deleting — keeps the state file, so resuming doesn't re-surface a backlog. |
| `tags` | | Free labels. Used to group the digest and to run a subset (`/radar run --tag ai`). |
| `cadence` | | Overrides `defaults.cadence`. |
| `notes` | | Why this source is on the list. Useful at prune time. |
### Type-specific fields
| Type | Extra fields |
|---|---|
| `youtube` | `channel_id` (cached `UC…`), `shorts: false` to skip Shorts, `min_duration_seconds` |
| `rss` | `feed_url` (resolved at add-time), `full_text: true` if the feed carries whole articles (skips the URL fetch on capture) |
| `reddit` | `subreddit`, `sort: top\|new\|hot` (**default `top`**), `t: day\|week` (with `top`), `min_score` (upvotes floor — the cheapest possible pre-filter, and it only works on `top`/`hot`; see fetchers.md) |
| `hn` | `query`, `min_points` (default 50), `story_only: true` |
| `x` | `handle`, `min_likes` (real pre-filter — `favorite_count` is on every item), `include_replies: false`, `include_reposts: false` |
| `bluesky` | `handle`, `did` (cached at add-time), `min_likes`, `include_replies: false` |
| `mastodon` | `handle` (`@user@instance`), `instance`, `account_id` (both cached at add-time) |
| `linkedin` | `profile_url`, `company: true` for company pages (uses the `company/posts` endpoint) |
| `keyword` | `query`, `engines: [web, hn, reddit, youtube]`, `recency_days` |
## Writing a `focus` that works
This field is the entire filter. Three rules:
1. **Name concrete things, not categories.** "Server-side attribution, CAPI, consent-mode workarounds" filters. "Marketing tech" does not.
2. **Include the exclusions.** Most sources are 80% something you don't want; say what it is. "Not: hiring posts, conference recaps, anything gated behind a webinar signup."
3. **Tie it to an open question where you can.** "Anything that changes how TracerKit should handle iOS 17 link tracking" gives scoring a real bar to measure against, and it makes a 5 mean something.
## Picking the type when an account is on several platforms
With the ScrapeCreators key in place, `x` is a first-class source type rather than a last resort — reliability is no longer the tiebreaker it was. If someone cross-posts to X and Bluesky, either works; prefer whichever they actually put effort into, and prefer `bluesky` on a pure tie since it's free.
`linkedin` is the one type still worth hesitating over, and for a payload reason rather than an access one: the profile endpoint reliably returns post URLs and dates but often no body. Test the specific profile before adding it (see fetchers.md → linkedin).
Rewrite the `focus` when a source's capture rate goes wrong in either direction — too many 5s means it's too loose, a month of nothing means it's too tight or the source is dead weight.
## State files
`state/<source-id>.json`:
```json
{
"last_run": "2026-08-28T07:00:12Z",
"last_status": "ok",
"error": null,
"seen": ["yt:dQw4w9WgXcQ", "rss:https://example.com/post-slug"],
"stats": { "items_7d": 12, "captured_30d": 3 }
}
```
- `seen` is capped at the most recent 300 IDs, newest last.
- ID format is `<type>:<native-id>` — video ID, GUID or URL, Reddit `t3_…`, HN object ID, tweet ID, Bluesky rkey, Mastodon status ID. Feeds without a stable ID fall back to a SHA of `url + title`.
- Deleting a state file is the supported way to re-scan a source from scratch. It will re-surface items — that's the point.
## Run records
`runs/<YYYY-MM-DD>.json` backs `promote`, so it holds everything needed to fetch an item without re-polling:
```json
{
"date": "2026-08-28",
"runs": [{ "started": "2026-08-28T07:00:02Z", "sources": 9, "duration_s": 41 }],
"items": [
{
"n": 4,
"source_id": "yt-greg-isenberg",
"type": "youtube",
"native_id": "dQw4w9WgXcQ",
"title": "…",
"url": "https://…",
"published": "2026-08-28T02:11:00Z",
"score": 4,
"reason": "Names the exact attribution problem TracerKit solves",
"summary": "…",
"captured": false,
"raw_path": null
}
],
"degraded": [{ "source_id": "x-levelsio", "error": "no fetch strategy available" }]
}
```
`n` is stable for the day and shared with the digest — a second run continues the numbering rather than renumbering.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |