agentleFS
fzfcleefzfclee/consulting-skills/skills/signal-vs-noise-filter/SKILL.md

signal-vs-noise-filter

Skill6 starsChanged 4 months agoApache-2.0View on GitHub

Use when a situation contains many facts, feelings, events, rumors, or weak cues and the real signal must be separated from noise. Use when applying signal detection, signal-versus-noise filtering, pattern relevance review, or decision-signal extraction.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to identify which observations should change the diagnosis or action plan.

    line 9
  2. Very specific:

    If an input is missing, mark it as missing, state the assumption used, and add a validation action.

    line 27
  3. Distinctive:

    Do not downgrade a real signal because it is politically uncomfortable.

    line 75
  4. Distinctive:

    Do not upgrade a weak cue because it fits the preferred story.

    line 76
  5. Distinctive:

    Keep the final signal list short enough to guide action.

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Signal vs Noise Filter

Use this skill to identify which observations should change the diagnosis or action plan.

Method Notes

  • A signal is information that changes the likely explanation, priority, risk, timing, or next action.
  • Noise may be true but not decision-relevant.
  • The method works best after an initial evidence map or fact clarification.

Required Inputs

Collect or infer these inputs before execution:

  • decision question or action choice
  • list of observations, events, facts, cues, and concerns
  • baseline expectation before the event
  • timing of key changes
  • available evidence strength

If an input is missing, mark it as missing, state the assumption used, and add a validation action.

When Not To Use

Do not use to repair unreliable evidence or fill basic situation gaps. Use evidence-map when facts, claims, sources, and confidence are mixed; use 5w1h-analysis when who, what, when, where, why, or how is missing. Use this method only after the input is good enough to judge decision relevance.

Step-by-Step Execution

StepRequired inputHow to executeOutput
State the baselinePrior expectation, normal pattern, status quo.Clarify what would have happened if nothing material changed.Baseline expectation.
List candidate signalsObservations, events, user concerns, timing.Convert each item into a candidate signal. Remove duplicates.Candidate signal list.
Rate decision relevanceDecision question, action options.Ask whether this item changes explanation, priority, risk, timing, stakeholder stance, or validation need.Relevance rating.
Rate evidence strengthSource, directness, recency, corroboration.Mark each candidate as strong, medium, weak, or missing.Evidence-strength rating.
Separate noiseLow-relevance or low-evidence items.Keep true-but-not-actionable items in a noise list so they do not dominate the plan.Noise list.
Name the core signalHigh-relevance and sufficiently evidenced items.Select the 1-3 signals most likely to change action.Core signal diagnosis.

Output Template

### 1. Baseline
- What we expected before the change:
- What changed:
- Why this matters:

### 2. Candidate Signal Table
| Candidate signal | Evidence strength | Decision relevance | Changes what? | Signal / noise / watchlist |
|---|---|---|---|---|
|  | strong / medium / weak / missing | high / medium / low | explanation / priority / risk / timing / stakeholder / validation |  |

### 3. Core Signals
1.
2.
3.

### 4. Noise and Watchlist
- Noise to avoid overreacting to:
- Watchlist item that needs more evidence:

### 5. Action Implication
- What the signal means:
- What it does not prove:
- Next validation:

Quality Gate

  • A signal must change a decision, not only feel interesting.
  • Do not downgrade a real signal because it is politically uncomfortable.
  • Do not upgrade a weak cue because it fits the preferred story.
  • Name what the signal does not prove.
  • Keep the final signal list short enough to guide action.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.