Individual skill

jfm-robustness

Use when results may be sensitive to liquidity-measure choice, sample filters, microstructure noise, or inference for a Journal of Financial Markets (JFM) manuscript. Builds the design-based robustness ledger; it does not invent evidence or citations.

Journal-of-Financial-Markets-Skills/skills/jfm-robustness/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,409
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Robustness Strategy (jfm-robustness)

## When to trigger

- The headline holds with the chosen liquidity measure but you have not shown it survives alternatives
- Results may flip with a different sample period, asset universe, or filter rule
- Inference uses plain OLS standard errors on data that are autocorrelated and cross-correlated (panel of stocks over time)
- Microstructure noise (bid-ask bounce, stale quotes, discreteness) could be generating the effect
- A referee will ask "is this the mechanism or the measurement?" and you need each check mapped to a specific threat

## The JFM robustness ledger

JFM referees do not want a wall of robustness tables; they want **each check tied to a named threat** to the microstructure interpretation. Build the ledger threat-first.
Back to top