agentleFS
itseffiitseffi/agentic-os/.agents/skills/signal-identification/SKILL.md

signal-identification

Skill114 starsChanged 10 months agoMITView on GitHub

Design efficient early signals to validate assumptions. Find the fastest way to learn if you're right.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you have a prioritized assumption and need the fastest way to validate it.

    line 12
  2. Distinctive:

    Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

    line 66

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Identification

Design efficient early signals to validate product assumptions.

When to Use

When you have a prioritized assumption and need the fastest way to validate it.

The Quality Bar

A good signal is:

  • Early: Obtainable at idea/prototype stage
  • Cheap: Minimal cash/time
  • Attributable: Directly reduces uncertainty
  • Decisive: Has clear success/failure threshold
  • Suitable: Appropriate for your context

Method Selection by Context

ContextGood MethodsAvoid
Enterprise B2BDesign partner LOIs, security questionnaires, ROI calculators, reference checksSmoke tests, consumer ad funnels
SMB SaaSDiscovery calls, lightweight trials, email tests, usage analytics-
ConsumerAd-driven intent, waitlist conversion, community polls, preorders-
RegulatedStandards mapping, SME review, regulatory preflightCollecting sensitive data
FeasibilityEngineering spikes, benchmarks, vendor evalsUser-facing experiments

The Process

1. Classify the Assumption

What lens? Desirability, Feasibility, Viability, or Usability?

2. Brainstorm Signals (5+)

For each, note:

  • What would constitute positive evidence?
  • How to obtain quickly?
  • Why suitable for this context?

3. Select Best Signal

Document:

  • Signal description
  • Method (step-by-step)
  • Participants/sample needed
  • Timebox and cost
  • Success threshold (quantified)
  • Data captured
  • Risks and mitigations
  • What to do next if positive

Output

  • Brainstorm list (5+ signals)
  • Selected signal with full details
  • Summary explaining choice

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

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.