research-fuzzer

Tracks open-ended investigations with an append-only notebook of predictions, outcomes, and coverage readings.

671|51|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/ARA-Labs/Agent-Native-Research-Artifact --skill research-fuzzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-fuzzer
Source: https://github.com/ARA-Labs/Agent-Native-Research-Artifact/tree/main/skills/research-fuzzer
Command: npx skills add https://github.com/ARA-Labs/Agent-Native-Research-Artifact --skill research-fuzzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Open-ended investigations by AI agents degrade into reactive sampling: the agent grinds one corner, forgets leads it noticed, and states conclusions without checking unexplained results. This Skill imposes a fuzzer-style feedback loop so every action is a recorded bet and every conclusion passes a gate.

Core Features & Use Cases

  • Append-only investigation notebook: Records frames, bets, settles, reframes, and claims as JSONL lines that survive context loss and session restarts.
  • Coverage panel: Computes explored areas, untried leads, novelty trends, open anomalies, and a blocked/open conclusion gate via scripts/tally.py.
  • Hard protocol rules: No action without a prior prediction, mandatory verdicts and updates, forced reframes after three anomalies, and a kill-shot requirement before any claim.
  • Use Case: While debugging a flaky test or investigating user churn, log each experiment as a bet with a falsifiable prediction, settle it with a verdict, and run the panel before drawing any conclusion to see which leads remain unexplored.

Quick Start

Start my investigation by creating a fuzz notebook frame for my research question, then log a bet before each action and show me the panel after every batch of results.

Frequently Asked Questions about research-fuzzer

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

FAQPage Schema
How do I keep an AI agent from going in circles during research?

Log every action as a bet with a falsifiable prediction before acting, then settle it with a verdict of confirmed, surprised, or anomaly. The panel counts recent verdicts and flags confirmed streaks as a leave signal, showing when a region yields no new information.

How do I track unexplored leads during an investigation?

Each settle record includes a doors field listing leads noticed but not tried. The tally script reports how many doors remain open, which were followed, and the oldest untried lead, giving an exact measure of remaining exploration.

Does research-fuzzer require any Python packages or network access?

No. Both scripts use only the Python standard library, and the entire protocol can be executed by hand with no tooling at all. There is no network access, no packages, and no framework dependency.

When should I not use an investigation tracking loop?

Skip it for single-step lookups and trivial fixes where the loop's overhead exceeds its value. It is built for probing an existing world, not for creative synthesis like designing systems or writing, except for investigative episodes inside that work.

What happens when anomalies accumulate in the notebook?

Three unresolved anomalies force a reframe: you publish a new frame version with the missing axis or sub-question. Open anomalies also block the conclusion gate until resolved or explicitly carried as limitations in a claim.