signal-verdict

Audit configured trackers for citable signals in outward content.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/swarm-ai-research/aeon --skill signal-verdict-swarm-ai-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-verdict
Source: https://github.com/swarm-ai-research/aeon/tree/main/skills/signal-verdict
Command: npx skills add https://github.com/swarm-ai-research/aeon --skill signal-verdict-swarm-ai-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly accountability checks on a fleet of tracker skills to ensure each tracker publishes citable signals in articles or newsletters, and to surface trackers that fail to produce citations so operators can demote or retire them.

Core Features & Use Cases

  • Citeability verification: checks whether each tracker produces a citable signal in outward content.
  • Uncited tracker surfacing: surfaces trackers with no citations for potential action or retirement.
  • Config-driven scope: reads memory/topics/tracked-skills.md to determine which trackers are under review and what keywords to monitor.
  • Automated weekly oversight: runs on a schedule and generates notifications and running logs to support governance.

Quick Start

Run signal-verdict to audit your configured trackers and surface any uncited signals before the next publication cycle.

Frequently Asked Questions about signal-verdict

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

FAQPage Schema
How do I audit trackers to verify they produce citable signals in published articles?

Tracker audits verify citeability by scanning recent outward content over the past 14 days for keyword mentions defined in your tracked-skills configuration, surfacing uncited trackers for potential demotion or retirement.

What is a citable signal in newsletter or article content tracking?

A citable signal is a keyword mention from a configured tracker that appears in outward content like articles or newsletters, proving the tracker produces actionable intelligence worth retaining in your active fleet.

How do I set up weekly accountability checks for a fleet of tracker skills?

Define trackers and monitored keywords in memory/topics/tracked-skills.md, then run the audit weekly. It reads this config and memory/MEMORY.md to generate notifications and running logs for automated governance.

Can I use memory files to configure which trackers are under review for citation checks?

Yes, the audit reads memory/topics/tracked-skills.md to determine which trackers to review and what keywords to monitor, making the scope entirely config-driven from your existing memory files.

When should I retire or demote a tracker that produces no citations?

When a tracker fails to produce citable signals in outward content over the 14-day analysis window, the audit surfaces it for potential demotion or retirement, letting operators clean up unproductive tracker fleets.