signal-verdict

Identify trackers lacking citable signals in outward content and flag them for review.

Updated Jun 2, 2026

Search Tags:#audit #citation #notification #signal #weekly #tracker #outward-content

Ready to run

npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill signal-verdict-atrium-hermes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: signal-verdict
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/signal-verdict
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill signal-verdict-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly accountability checks are needed to ensure tracker outputs are actually generating citable signals in public content; this skill surfaces uncited trackers so operators can update schedules or retire underperforming ones.

Core Features & Use Cases

Automated tracker signal validation: Verifies each configured tracker produces citable signals in outward content (articles/newsletters) within a rolling window.
Visibility and governance: Surfaces uncited trackers for operator review and demotion or retirement decisions.
Lifecycle updates: Writes verdicts to memory/topics/tracked-skills.md and prepares operator notifications.

Quick Start

Run this skill weekly to audit trackers, surface uncited signals, and generate a verdict notification for operator review.

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 find uncited signals in weekly content?▼

To audit trackers for uncited signals, run a weekly validation check across the past 7 days of outward content like articles and newsletters. This process flags trackers that fail to produce citable signals for operator review.

What is tracker signal validation for outward content?▼

Tracker signal validation verifies that each configured tracker generates citable signals within public outward content. It checks a rolling 7-day window of articles and newsletters to ensure accountability and surface underperforming trackers.

How do I surface uncited trackers for lifecycle retirement decisions?▼

Surfacing uncited trackers requires applying an automated check to past weekly content outputs. The system identifies trackers failing to generate citations, updates memory topics with verdicts, and prepares notifications for operator review.

Can I use this tracker audit skill without external dependencies?▼

Yes, you can run this tracker audit skill without external dependencies. It operates internally by analyzing configured trackers against outward content, updating tracked skills memory files, and generating concise operator notifications.

What is the best way to maintain weekly tracker accountability for published articles?▼

Maintaining weekly tracker accountability involves automating a citation check across published articles and newsletters. This approach verifies tracker outputs, updates memory topics with verdicts, and keeps operators informed about uncited signals.

Why does my tracker fail to produce citable signals in newsletters?▼

Trackers fail to produce citable signals when their outputs are not referenced in outward content like newsletters over a 7-day period. Running a weekly audit identifies these uncited trackers for schedule updates or retirement.