hypothesis-synthesizer

Synthesize log anomalies, transcript evidence, and behavioral metrics into a testable If/Then/Because hypothesis.

Updated Jul 5, 2025
One-click install
npx skills add https://github.com/nsuberi/ai-prototype-hub --skill hypothesis-synthesizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hypothesis-synthesizer
Source: https://github.com/nsuberi/ai-prototype-hub/tree/main/apps/ai-builders-challenge/.claude/skills/hypothesis-synthesizer
Command: npx skills add https://github.com/nsuberi/ai-prototype-hub --skill hypothesis-synthesizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert scattered evidence from logs, participant transcripts, and behavioral metrics into one clear, testable hypothesis that guides what to change next.

Core Features & Use Cases

  • Triangulation across sources: Uses agreement across log anomalies, transcript evidence, and behavioral indicators to ensure the hypothesis reflects real user and system signals.
  • Test-first output: Produces a narrow If/Then/Because statement plus a draft deepeval test name and a primary assertion focus, rather than proposing fixes.
  • Evidence-based gating: Only writes hypotheses when at least 2 of 3 signals agree, reducing guesswork and improving experimental reliability.
  • Reproducibility planning: Suggests sessions to reproduce and specifies expected pre-fix FAIL versus post-fix PASS outcomes.

Quick Start

Ask the AI to synthesize a hypothesis from your Log Analyst report, transcript fixtures, and fixtures/behavioral.json, and return an If/Then/Because statement with a draft test name and primary assertion.

Frequently Asked Questions about hypothesis-synthesizer

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

FAQPage Schema
How do I turn log anomalies and user transcripts into a testable hypothesis?

To turn log anomalies and user transcripts into a testable hypothesis, you synthesize multi-source behavioral metrics using triangulation. The process requires at least two agreeing signals to generate a structured If/Then/Because statement and a draft test name.

What is triangulation in behavioral metrics and log analysis for test planning?

Triangulation in behavioral metrics and log analysis is the cross-referencing of log anomalies, transcript evidence, and behavioral indicators. It ensures a testable hypothesis reflects real user and system signals by requiring at least two of three sources to agree.

How do I create a deepeval test name from scattered evaluation signals?

You create a deepeval test name from scattered evaluation signals by synthesizing log anomalies and behavioral metrics into a test-first output. This yields a structured If/Then/Because statement, a primary assertion focus, and the expected draft test name.

Does hypothesis generation work if I only have behavioral metrics and no log anomalies?

Hypothesis generation requires triangulation where at least two of three signals agree, so it will not work with behavioral metrics alone. You must provide multi-source signals, such as behavioral metrics combined with transcript evidence, to pass the evidence-based gating.

How do I plan reproducible evaluation sessions from multi-source user data?

To plan reproducible evaluation sessions from multi-source user data, you synthesize the signals into a structured hypothesis that specifies expected pre-fix FAIL versus post-fix PASS outcomes. This approach suggests exact sessions to reproduce and measure.

Can I use this approach to automatically propose fixes for log anomalies?

You cannot use this approach to automatically propose fixes for log anomalies, as it focuses strictly on test-first output. Instead of proposing solutions, it produces a narrow If/Then/Because statement and a primary assertion to guide measurable changes.