hypothesis-tracking

Manage company hypotheses with a four-level confidence system and evidence trails.

3|2|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/blisspixel/primr --skill hypothesis-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hypothesis-tracking
Source: https://github.com/blisspixel/primr/tree/main/skills/hypothesis-tracking
Command: npx skills add https://github.com/blisspixel/primr --skill hypothesis-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Track and manage research hypotheses about companies with a structured confidence system, keeping evidence trails and expiration rules.

Core Features & Use Cases

Retrieve, update, and create hypotheses for any company using a four-level confidence lifecycle (untested, validated, invalidated, confirmed); enforce unique IDs per company and provide expiration handling per topic.

Quick Start

Start by creating a hypothesis for a company using save_hypothesis, then retrieve or update it with get_hypotheses and save_hypothesis as new evidence arrives.

Frequently Asked Questions about hypothesis-tracking

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

FAQPage Schema
How do I track research hypotheses with evidence and confidence levels?

To manage research hypotheses for a company, use save_hypothesis to create records with evidence trails, then retrieve or update them as new evidence arrives. Confidence levels span a four-stage lifecycle: untested, validated, invalidated, and confirmed.

What is a four-level confidence system for company research validation?

A four-level confidence system categorizes research validation into untested, validated, invalidated, and confirmed states. It tracks the lifecycle of company hypotheses while maintaining evidence trails and applying expiration rules per topic.

How do I update an existing company hypothesis when new evidence arrives?

Update an existing company hypothesis by calling save_hypothesis with new evidence. The system enforces unique IDs per company, handles expiration rules across topics, and adjusts the confidence level accordingly.

Does this hypothesis tracking system handle duplicate IDs and missing records?

Yes, the hypothesis tracking system enforces unique IDs per company and provides built-in error handling for missing records and duplicates. This ensures data integrity when retrieving, updating, or creating research entries.

Can I set expiration rules for research hypotheses across different topics?

Yes, you can set expiration rules for research hypotheses across different topics. The system manages these expiration parameters per topic, ensuring outdated company knowledge is flagged appropriately during validation.

What's the best way to manage knowledge validation for multiple companies without duplicates?

Manage knowledge validation for multiple companies by enforcing unique IDs per organization. The system's error handling prevents duplicates and manages missing records, while tracking confidence levels and expiration rules per topic.