process-signal-queue

Scan raw signal files, analyze ICP signals, and archive processed inputs.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/antonyfmunoz/OS --skill process-signal-queue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: process-signal-queue
Source: https://github.com/antonyfmunoz/OS/tree/main/skills/Research/process_signal_queue
Command: npx skills add https://github.com/antonyfmunoz/OS --skill process-signal-queue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents outreach from running on stale or unprocessed market signals by turning raw inbox items into structured ICP-ready insights and archiving them so the queue stays at zero.

Core Features & Use Cases

  • Signal-to-ICP Processing Pipeline: Scans 01_Inbox/raw_signals, analyzes each signal with skills/Research/analyze_icp_signal.md, and persists HIGH/MEDIUM matches as ICP insights in 07_Knowledge/ICP.
  • Reliable Queue Hygiene: Moves every processed (or failed/malformed) signal into 01_Inbox/processed_signals to eliminate duplicate processing risk.
  • Operational Safety Guardrails: Flags abnormal volume when more than 50 signals are queued to detect scraper issues and supports measured outcomes like queue clearance, insight yield, and processing latency.

Quick Start

Run the process-signal-queue skill to analyze every file in 01_Inbox/raw_signals, save ICP insights to 07_Knowledge/ICP, and move processed items into 01_Inbox/processed_signals until the queue is cleared.

Frequently Asked Questions about process-signal-queue

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

FAQPage Schema
How do I convert raw signal files into structured ICP intelligence for outreach?

To convert raw signals into structured ICP intelligence, scan your inbox directory and analyze each file to extract HIGH or MEDIUM priority insights. Save these as structured ICP markdown files to maintain outreach readiness.

What is the best way to prevent duplicate processing of market signals in a data pipeline?

The best way to prevent duplicate processing is to archive every analyzed signal by moving it from the raw inbox to a processed signals folder. This ensures recurring outreach cycles only process new items.

How do I handle malformed or empty inputs when analyzing an ICP signal queue?

When processing an ICP signal queue, malformed or empty inputs must still be archived to the processed signals directory. This prevents pipeline blockages and ensures the queue stays at zero.

Does queue management for signal processing support limits on daily volume?

Queue management for signal processing flags abnormal volume when the queue exceeds 50 signals. This operational guardrail detects potential scraper issues and supports measured processing latency outcomes.

Why does outreach run on stale market signals and how can I clear the inbox?

Outreach runs on stale signals when raw inbox items are not analyzed. Clear the inbox by invoking an ICP analysis process on each signal file, saving valid insights, and archiving all inputs.