signal-verdict

Evaluate tracker skills for citable keyword mentions in published articles.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill signal-verdict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-verdict
Source: https://github.com/aaronjmars/aeon/tree/main/skills/signal-verdict
Command: npx skills add https://github.com/aaronjmars/aeon --skill signal-verdict

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It verifies that a fleet of tracker skills actually produces citable outward signals in published articles or newsletters, preventing “silent” or non-contributing trackers from continuing indefinitely.

Core Features & Use Cases

  • Weekly citation accountability: checks whether each configured tracker is represented by substantive keyword matches in outward content from the last 7 days.
  • Verdit bar enforcement: updates each tracker’s run history and PASS/FAIL status only when the configured deadline is reached, otherwise keeps it pending.
  • Operator-facing remediation signals: surfaces uncited trackers and generates a demotion queue recommendation to adjust schedules so weak performers get demoted or retired.
  • Self-updating memory artifacts: rewrites the tracked-skills table and appends a weekly log entry, creating a persistent audit trail.

Quick Start

Run the skill on its schedule and ensure memory/topics/tracked-skills.md contains the tracker list and the keyword map so it can score citations and notify you.

Frequently Asked Questions about signal-verdict

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

FAQPage Schema
How do I verify tracker skills generate citable signals in published newsletters?

Weekly citation accountability verifies tracker fleets by scanning article markdown content for keyword-based substantive mentions within a defined deadline window. It updates citation counters and PASS/FAIL status for each configured tracker.

What happens when a tracker skill fails to produce substantive keyword matches in outward content?

Failed trackers surface as operator-facing remediation signals, generating a demotion queue recommendation to adjust schedules so weak performers get demoted or retired from the publication fleet.

How do I set up weekly reporting for tracker fleets that scan article markdown?

Ensure memory configuration contains the tracker list and keyword map in tracked-skills.md, then run the skill on its schedule. It scans daily and weekly publication files while excluding ops/internal article types.

Can I automate content QA for recurring trackers without making external network calls?

Yes, content QA automation runs locally by reading memory configuration and scanning markdown content. It updates citation counters, status, and triggers notifications and log updates without any external network calls.

Does the weekly citation audit update memory artifacts automatically?

The audit rewrites the tracked-skills table and appends a weekly log entry, creating a persistent audit trail. Verdict bar enforcement updates run history and PASS/FAIL status only when the configured deadline is reached.

When should I not use a weekly citation accountability check for tracker fleets?

This approach suits recurring tracker fleets requiring evidenced keyword mentions in outward-facing articles. It is not designed for one-off tracking tasks or trackers lacking a defined keyword map and publication schedule.