signal-redundancy-audit

Identify signals declared in methodology YAMLs that never influence strategy selection.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/michaelarutyunov/interview-system-v2 --skill signal-redundancy-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-redundancy-audit
Source: https://github.com/michaelarutyunov/interview-system-v2/tree/main/.claude/skills/signal-redundancy-audit
Command: npx skills add https://github.com/michaelarutyunov/interview-system-v2 --skill signal-redundancy-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit signal configurations across methodology YAMLs to identify dead, dormant, or non-decisive signals that can be safely removed. Combines static YAML analysis with empirical simulation data to produce removal recommendations.

Core Features & Use Cases

  • Static analysis: detects signals declared but never used in signal_weights across all methodologies.
  • Empirical analysis: leverages simulation data to quantify signal impact and decisiveness.
  • Removal guidance: provides a clear protocol and rationale for removing dead, dormant, or marginal signals.
  • Report generation: outputs structured findings per methodology to support drift checks and audits.

Quick Start

Run the audit against your methodology YAMLs to identify dead or dormant signals and prepare removal recommendations.

Frequently Asked Questions about signal-redundancy-audit

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

FAQPage Schema
How do I find unused signals declared in methodology YAML configs?

To find unused signals in methodology YAML configs, run a static analysis that cross-references signal declarations against signal_weights to identify signals that never influence strategy selection. This surfaces dead or dormant candidates for removal.

What is signal redundancy analysis in simulation methodologies?

Signal redundancy analysis in simulation methodologies is the process of auditing YAML configurations to detect dead or non-decisive signals. It combines static YAML parsing with empirical simulation data to quantify signal impact and guide safe removals.

Do I need simulation data to audit dead signals in YAML files?

You do not need simulation data to audit dead signals in YAML files. Static analysis alone can detect signals declared but missing from signal_weights, but empirical simulation data is required to quantify signal impact and dormancy.

How do I generate a removal report for dormant signals across methodologies?

To generate a removal report for dormant signals across methodologies, apply the audit across all YAML configs to analyze both declarations and signal_weights. The output provides structured findings and rationale for removing marginal signals per methodology.

What's the best way to clean up methodology YAML signal declarations?

The best way to clean up methodology YAML signal declarations is combining static YAML analysis with empirical simulation data to identify non-decisive signals, then applying the structured removal protocol to safely trim dead configurations.