What problem does it solve?
Manually tracking incoming solicitation responses for open opportunities is time-consuming and error-prone, especially when responses arrive asynchronously over time and teams need to stay updated on submission counts and remaining time until the deadline.
Core Features & Use Cases
- Three Operational Modes: Use --quick for low-cost response count checks, --monitor (default) to pull full details of new responses, and --close to finalize solicitation status when the deadline passes.
- Automated State Diffing: Automatically compares new responses against existing local files to avoid re-pulling already processed submissions.
- Read-Only Safe Operation: Runs without mutating core opportunity state files, ensuring no accidental changes to solicitation status or run data until explicit close actions are implemented.
- Use Case: For a team managing an open solicitation for a Connect opportunity, schedule this skill to run on a cron to automatically check for new responses, pull full details for new submissions, and log updated counts and time-to-deadline to the team's comms log without manual intervention.
Quick Start
Use the solicitation-monitor skill to check for new solicitation responses for your current open opportunity and log the latest response count and time remaining until the deadline to your comms log.