Install
$ agentstack add skill-adeerkhan-vitruvius-hypothesis-generation ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Hypothesis Generation
Generate evidence-bounded engineering hypotheses. This skill freezes the observation, frames the question, establishes evidence boundaries, generates rival candidates, and derives discriminating predictions. It never scores, ranks, or selects hypotheses — that is a human decision.
Invocation
/hypothesis-generation
Include: the observed phenomenon, context, and any relevant engineering domain (materials, structures, thermal, etc.).
Methodology
- Freeze the observation — write the exact observation before interpreting. Distinguish what was measured from what is inferred. Timestamp the observation date.
- Frame the research question — restate as a falsifiable engineering question. Identify the claim type: descriptive, associational, predictive, causal, or mechanistic.
- Establish evidence boundary — document: search date, databases consulted, query terms, inclusion/exclusion criteria, limitations. "Not located within documented search boundary" — never "no prior work exists".
- Generate rival hypotheses — produce 3-5 candidates from DIFFERENT explanatory classes (e.g., material defect, design error, environmental, manufacturing process, maintenance). Each must be falsifiable. No two hypotheses from the same class.
- Declare claim type and estimand — specify what would be measured, the expected direction/magnitude, and the population/context where it applies.
- Derive discriminating predictions — for each hypothesis, state: condition, observable, expected pattern, falsifier (what result would be incompatible), and rival contrast (how does this prediction differ from the others?).
- Prevent HARKing — timestamp the generation. Preserve this document as the pre-registration record. Any deviation in testing must be reported as a deviation, not hidden.
Output
Inline Summary (chat response)
- Observation (frozen, dated)
- Research question + claim type
- Evidence boundary (date, sources, queries, limitations)
- 3-5 rival hypotheses with class labels
- For each: discriminating prediction + falsifier
Full Record (saved to disk)
Save to outputs/hypothesis/.md:
# Hypothesis Generation:
## Observation (Frozen)
- **Date observed:**
- **Phenomenon:**
- **Distinguish:** measured vs inferred
- **Context:**
## Research Question
- **Question:**
- **Claim type:** descriptive / associational / predictive / causal / mechanistic
## Evidence Boundary
- **Search date:**
- **Databases:**
- **Query terms:**
- **Inclusion:**
- **Exclusion:**
- **Limitations:**
## Rival Hypotheses
### H1: ()
- **Mechanism:**
- **Prediction:**
- **Falsifier:**
- **Rival contrast:**
(repeat for H2, H3...)
## Discriminating Tests
- **Test that separates H1 from H2:**
- **Test that separates H1 from H3:**
- ...
## Pre-registration Record
- **Generated:**
- **Status:** candidate (never scored/selected by tool)
- **Deviations:** none yet
Scope and Boundaries
- This skill generates hypothesis candidates — it does NOT score, rank, or select. Status must remain
candidate. - Research-only, not for final engineering sign-off. Hypothesis selection requires human engineering judgment.
- Never fabricate evidence to support a hypothesis. If a hypothesis lacks evidence, mark it
unverified, notinferred. - Evidence quality: see
references/evidence-quality-tiers.md.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: adeerkhan
- Source: adeerkhan/vitruvius
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.