aggregator

Files (1)

• SKILL.md

SKILL.md (first lines)

# Aggregator

Fires once per day on a cron the operator configures. Performs a strict-pipeline run over the source allowlist:

1. Fetch each source in `sources.toml` via the declared method (RSS / API / rate-limited scrape). The HTTP wrapper enforces the egress allowlist.
2. Normalize fetched items into candidate records: `title`, `source`, `date`, `url`, `body_excerpt`, `citation_json`.
3. Skip if the candidate's content hash is already in the seen set.
4. Score the candidate's relevance against the user's interests file (`<data_dir>/zirkel/interests.toml`). Output: a float in `[0, 1]` plus a one-line `why_surfaced` rationale that names the matched interest.
5. If the score crosses the keep threshold and no skip pattern matches, write the candidate to the local SQLite store. Otherwise, log the skip with reason.
6. After all sources fetched, cluster the run's kept candidates into emergent themes using a small local embedding model.
7. Render the digest as plain prose with footnote-ready citations on every item. Push to the configured channel adapter.

Aggregator does not synthesize claims about the world. The digest reads as *"N items kept, M skipped. Today's themes: [theme A: items 1, 4; theme B: items 2, 3, 7]. Each item links to its source with a one-line why-surfaced explanation."* No "today the regulators are saying X" prose.

This skill is `disable-model-invocation: true`. Reach it via `/aggregator` (manual run) or via the operator's cron that calls the underlying CLI command directly.

## State

- `<data_dir>/zirkel/zirkel.db` — SQLite database holding candidates, seen, themes, skipped_log, runs, and the cached interests snapshot per run.
- `<data_dir>/zirkel/interests.toml` — user-editable; reloaded at the start of every run; a hash of the file is recorded in the audit log so changes are visible run-to-run.
- `<data_dir>/zirkel/bodies/` — full bodies referenced by `candidates.body_full_path` for items where the excerpt is too small for retrieval.

The aggregator and librarian share this state; both skills are scoped to the same `<data_dir>/zirkel/` directory by their permissions blocks.

## Inputs the operator provides

- `sources.toml` (preset-level, alongside `preset.toml`) — the addressable public set of sources.
- `interests.toml` (per-user, in `<data_dir>/zirkel/`) — concepts, keywords, exclusions, optional source weight tweaks.
- Channel adapter pin and target (configured at preset install).

From gebruder/wirken, MIT.

More from gebruder/wirken