bump-core-req
Updates the minimum core version requirement for a fleet plugin in all three canonical places: `required_core_version` and `requires["claude-code-hermit"]` in…
Gap-driven discovery of new RSS/web sources for feed-sources.md. Interactive runs WebFetch-verify candidates and auto-add them; --scheduled runs queue unverified candidates for operator review (no WebFetch, per the domain-allowlist rule). Complements source-health (removal) with
$ npx -y skills add gtapps/claude-code-hermit --skill source-scout --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/source-scoutContext preview
The summary Claude sees to decide when to auto-load this skill.
Gap-driven discovery of new RSS/web sources for feed-sources.md. Interactive runs WebFetch-verify candidates and auto-add them; --scheduled runs queue unverified candidates for operator review (no WebFetch, per the domain-allowlist rule). Complements source-health (removal) with
name: source-scout description: >- Gap-driven discovery of new RSS/web sources for feed-sources.md. Interactive runs WebFetch-verify candidates and auto-add them; --scheduled runs queue unverified candidates for operator review (no WebFetch, per the domain-allowlist rule). Complements source-health (removal) with discovery (addition). Invoke with /feed-hermit:source-scout.
Proactively discover and add new RSS/web sources to `feed-sources.md`. Complements `source-health` (removal) with discovery (addition). Runs as the `source-scout` routine with `feed-hermit:source-scout --scheduled`.
rule restricting automated WebFetch to domains already in `feed-sources.md` means the step-3 verification fetch cannot run — candidates are queued **unverified** for operator review instead of being auto-added.
auto-add — since the operator's live presence satisfies the security rule's intent.
1. **Read current state** (in parallel):
2. **Identify gaps:**
3. **Discover candidates** (up to 3 total across all gaps). Use WebSearch to find RSS feeds — for a category gap, search for RSS feeds / newsletters covering that category; for an arc gap, search for feeds covering the arc's Watch keywords.
**No flag (interactive):** for each candidate, verify the feed URL with WebFetch (valid RSS/Atom XML). Discard any that 404 or return non-feed content.
**`--scheduled`:** do NOT WebFetch candidate URLs — they are not yet in `feed-sources.md`, so an automated fetch would violate the domain-allowlist rule. Collect candidates from WebSearch results as-is (name, URL, gap addressed, why it surfaced), explicitly marked unverified. Skip to step 4.
4. **Filter against existing sources:**
5. **Add / queue — branch on invocation context:**
**No flag (interactive):** source additions are free (no operator approval needed). For each verified candidate:
**`--scheduled`:** do NOT touch `feed-sources.md` — these candidates are unverified.
In both modes, write `.claude-code-hermit/compiled/source-candidates-<YYYY-MM-DD>.md` with frontmatter (`title`, `type: source-candidates`, `created`, `tags: [source-scout]`) listing each candidate's name, URL, the gap it addresses, and a one-line "why this looked promising" note.
**`--scheduled` only:** notify the operator per CLAUDE.md § Operator Notification with a one-line summary ("N unverified source candidate(s) found — see .claude-code-hermit/compiled/source-candidates-<date>.md"). Don't queue a micro-approval: verification requires an interactive WebFetch only the operator can trigger. The operator reviews the file and, for any candidate they want, runs `/source-scout` interactively (or edits `feed-sources.md` manually) so verification happens with them present.
6. **Log and report:**
If you know Claude Tag, the idea will feel familiar: hand Claude work through a channel, such as Discord, Telegram, or your custom integration, and get results back there.
Repo: gtapps/claude-code-hermit
Updates the minimum core version requirement for a fleet plugin in all three canonical places: `required_core_version` and `requires["claude-code-hermit"]` in…
Changelog and commit — lightweight motion for day-to-day plugin dev work in the monorepo. One commit per plugin scope; CHANGELOG and staging routed by detected…
Documentation-drift audit for the plugin monorepo. Audits either each scoped plugin's unreleased changelog claims or its latest shipped release from the…
Explain in plain language what a fix, feature, PR, or plan will actually change for downstream hermits and the operators chatting with them — a before/after…
Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings…
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, which branches went stale, and GitHub…