solicitation-monitor

Poll solicitation responses and log counts to the comms log.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill solicitation-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solicitation-monitor
Source: https://github.com/dimagi-internal/ace/tree/main/skills/solicitation-monitor
Command: npx skills add https://github.com/dimagi-internal/ace --skill solicitation-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about solicitation-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate tracking incoming solicitation responses for open opportunities?

Automate solicitation response tracking by scheduling a recurring polling process to check for new submissions, pull full response details, and log updated counts and time-to-deadline without manual intervention.

What is the best way to monitor solicitation deadlines and submission counts asynchronously?

Monitor solicitation deadlines and submission counts by running automated recurring polls that count new responses, track time remaining until the deadline, and log updates to the team's comms log.

Can I check for new solicitation submissions without modifying existing opportunity state files?

Yes, you can check for new submissions using a read-only polling mode that logs tick updates to the comms log without mutating core opportunity state files or run data.

How do I avoid re-pulling solicitation submissions that have already been processed?

Avoid re-pulling processed submissions by using automated state diffing, which compares new responses against existing local files to ensure only newly arrived submissions are retrieved in full.

What are the different monitoring modes for polling open solicitation responses?

Three operational modes exist: a quick mode for low-cost response count checks, a default monitor mode to pull full details of new responses, and a close mode to finalize solicitation status when the deadline passes.

Does solicitation monitoring work with Connect Labs opportunity workflows?

Yes, solicitation monitoring operates within Connect opportunity workflows by using Connect Labs tools to list and retrieve solicitation responses and track time remaining until open opportunity deadlines.