newsjack-monitor-setup

What it does

Guides the user through creating a monitor profile for newsjack-detector so it can run on a schedule. It asks for onboarding details (company standing, topics, competitors, proof assets, spokespeople), selects RSS feeds, sets an X trend preference, and handles scheduling. In Full Mode, it saves the profile, seeds a brief, schedules the monitor, tests offline, runs a real check, and reviews results with the user. In Limited Mode, it drafts the profile and client brief without filesystem changes. It enforces use of the bundled newsjack binary if present and advises mode based on environment checks.

How it works

• Determines mode (Full vs Limited) by checking for shell access and presence of the newsjack CLI.
• If Full Mode: prompts for monitoring frequency, then runs newsjack monitor init <slug> --profile profile.json to save the profile and create a blank brief.md.
• Fills brief.md with sections: Audience, We pitch, We never pitch, How to surface, based on user answers.
• Sets up the schedule with newsjack monitor schedule <slug> --runtime <runtime> --every "<frequency>" according to user choice (8am and 2pm, daily 8am, or 1h).
• Performs a quick offline test via newsjack monitor test <slug> --mock to verify pipeline basic flow.
• Executes a real run inside the agent: newsjack monitor run <slug> and then uses newsjack-detector to write run.md with strongest stories or a "nothing pitch-ready" summary.
• Reviews results with the user, allowing adjustments to topics, competitors, feeds, proof assets, frequency, or exclusions, and updates brief.md accordingly for future runs.
• In Limited Mode: drafts the profile and client brief in chat, and instructs the user to switch to Full Mode to save, schedule, test, and run.

When to use it

• Use when the user wants to set up monitoring, create or configure a monitor profile, schedule recurring newsjack scans, choose RSS/news feeds, or prepare a profile for newsjack-detector. For an initial broad intro to newsjack, use the getting-started flow instead.

What it can touch

• The profile is saved via newsjack monitor init <slug> --profile profile.json and the brief is written to brief.md.
• Scheduling uses newsjack monitor schedule with --runtime and --every options.
• Testing uses newsjack monitor test <slug> --mock and a real run with newsjack monitor run <slug> followed by run.md generation by the detector.

Caveats

• Requires the bundled newsjack binary to be present and accessible (Full Mode verification steps included).
• The flow assumes user responses fill the brief.md only with what was stated by the user; blanks are allowed as placeholders.
• In Limited Mode, no filesystem changes are performed; the agent only drafts in chat.