rss-source-curator

name	rss-source-curator
description	Use when an agent needs to evaluate RSS source quality, review feed health, generate source curation actions, apply reviewed registry patches, or maintain RSS/OPML source registries.

RSS Source Curator

Overview

Use this skill to review and maintain RSS source quality. Keep the workflow portable: use explicit registry, health, patch, and output files, and avoid runtime-specific assumptions.

Workflow Selection

• Run direct registry commands with the resolved DigestPilot runtime command, using subscription-research rss only as the compatibility example.
• For source quality scoring, use evaluate-sources.
• For source health history from a local research workspace, use subscription-research source-health.
• For source-health patch proposals from repeated observations, use subscription-research source-health --format patch.
• For human review, use curate-sources --format markdown.
• For patch application, first generate machine-readable curation with curate-sources --format json > source-curation.json, then use apply-source-patch.
• For source status semantics, read references/source-governance.md.
• For safe registry maintenance, read references/registry-maintenance.md.

Runtime Command

Examples use subscription-research as a compatibility command. Before running commands, resolve the runtime command:

• When DIGESTPILOT_BACKEND_URL is available, product actions such as source checks, source-health review, or WebUI-backed source maintenance may use the Backend task API first, then read the resulting workspace output.
• If the Backend API is unavailable, keep using the local runtime command fallback below. Do not require WebUI, cloud, or a hosted service in generic Agent environments.
• Use DIGESTPILOT_RUNTIME_CMD when the environment provides a custom runtime command.
• Use digestpilot-runtime when it is available on PATH.
• Use subscription-research when only the legacy compatibility command is available on PATH.
• From a repository checkout without a linked command, replace subscription-research with node packages/research-cli/dist/src/cli.js.
• Run node scripts/doctor.mjs from the repository root to diagnose local runtime setup.
• If no runtime command is available but this repository or plugin package includes runtime source, run node scripts/bootstrap-runtime.mjs, then retry the command.

Core Commands

Evaluate source quality:

subscription-research rss evaluate-sources \
  --registry feeds.json \
  --health source-health.json

Review repeated source failures from a research workspace:

subscription-research source-health \
  --workspace research-workspace \
  --min-observations 2 \
  --disable-threshold 3 \
  --format markdown

Manually check one source from a local workspace:

subscription-research workspace check-sources \
  --workspace research-workspace \
  --source-id SOURCE_ID

Manually check all sources when the user accepts the cost and time:

subscription-research workspace check-sources \
  --workspace research-workspace \
  --all \
  --max-workers 6

Manual source checks write a report under the workspace data directory and record source-health observations. Disabled or candidate sources may be checked, but they must remain disabled until reviewed.

Generate reviewable registry patches from repeated source failures:

subscription-research source-health \
  --workspace research-workspace \
  --min-observations 2 \
  --disable-threshold 3 \
  --format patch > source-health-curation.json

Generate human-readable curation actions:

subscription-research rss curate-sources \
  --registry feeds.json \
  --health source-health.json \
  --format markdown

Generate machine-readable curation patches:

subscription-research rss curate-sources \
  --registry feeds.json \
  --health source-health.json \
  --format json > source-curation.json

Apply reviewed patches to a new registry:

subscription-research rss apply-source-patch \
  --registry feeds.json \
  --patch source-health-curation.json \
  --output feeds.curated.json \
  --apply

Boundaries

This skill owns source governance, not article digest generation. For daily reading reports or content discovery, use rss-ai-digest.

Do not delete, disable, or remove feeds automatically. Generate reviewable actions first, then apply reviewed patches to an explicit output file.