BREAKER DELTA
浪尖レーダー
OverviewGetting StartedReading the SiteCLI ReferenceConfigurationSkill & MCPExtensionDeploy Your Own

日本語版は準備中です。このページは英語版を表示しています。

Skill & MCP

Fetching and scoring are code, but grading candidates into Must / Watch / Echo takes judgment — and that part is delegated to an agent. Breaker Delta writes that judgment down as fixed instructions (a Skill), so any agent running it produces the same structure and standards instead of improvising.

Use it as a Skill

  • Install skills/breaker-delta/ from the engine repo into your agent harness (Claude Code, Codex and others support Skill folders), or simply have the agent read SKILL.md and follow it.
  • The agent's fixed routine per edition: read the ledger first → run the CLI's scan for the candidate file → grade against the methodology's thresholds (resonance, growth, freshness, relevance to your config's topic weights) → dedupe against the ledger (old topics only report state changes) → write back with record → report in the fixed format.
  • Missing sources (usually only X, plus anything that failed that edition) are filled in by the agent scanning the web and are labeled as such in the report; sources you disabled in config are not missing and are not filled in.
  • Scheduling is entirely yours: your agent's cron, GitHub Actions, or manual runs. The radar prescribes no frequency, and no fixed schedule appears in its copy.

Use it as an MCP server

The same single-file bundle is also a stdio MCP server. Register this command in your agent harness (with your own data dir):

bun apps/cli/dist/breaker-delta.mjs --data-dir /path/to/your-data mcp
  • radar_scan: run one edition's fetch layer and return candidates with per-source status.
  • radar_review: return the topics due for their 14-day review.
  • Grading, write-back and reporting still follow the Skill flow; MCP simply exposes the two most-used actions as tools the agent can call directly.

Boundaries

  • Read-only access to public information: no posting, no liking, no interacting.
  • No invented numbers or links; a source that cannot be checked is reported as missing, never substituted.
  • Secrets travel via environment variables only, never into the repo.