A skill your agent uses when identifying a risk or uncertainty parameter is the bottleneck for a Journal of Risk and Uncertainty (JRU) manuscript — incentive-compatible elicitation in an experiment…

MITAuto-check passedResearch & Science

Install Jru Identification

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-identification -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jru-identification --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-identification .claude/skills/jru-identification && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
jru-identification
GitHub stars
1.2k
Token cost
~2.4k tokens
SKILL.md length
1,112 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when identifying a risk or uncertainty parameter is the bottleneck for a Journal of Risk and Uncertainty (JRU) manuscript — incentive-compatible elicitation in an experiment…

  • Identifying a risk
  • SKILL.md covers When to trigger, The JRU identification bar, Execution bridge (StatsPAI /… and Checklist, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Structural/empirical estimation of risk preferences

What it does

Jru Identification is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when identifying a risk or uncertainty parameter is the bottleneck for a Journal of Risk and Uncertainty (JRU) manuscript — incentive-compatible elicitation in an experiment, or structural/empirical estimation of risk preferences, VSL, or insurance demand. Stress-tests how the data pin the primitive; it does not invent evidence or citations.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Load testing and Citation management. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. | 覆盖主流期刊的… The licence is MIT.

When your agent uses it

  • Identifying a risk
  • Structural/empirical estimation of risk preferences
  • Insurance demand

Example prompts

  • “/jru-identification”

What it can do on your machine

Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Jru Identification loads about 2.4k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 1,112 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~92
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 1,112 words, ~2,353 tokens.

Download SKILL.mdSave it as .claude/skills/jru-identification/SKILL.md (or your agent's skills folder).
name
jru-identification
description
Use when identifying a risk or uncertainty parameter is the bottleneck for a Journal of Risk and Uncertainty (JRU) manuscript — incentive-compatible elicitation in an experiment, or structural/empirical estimation of risk preferences, VSL, or insurance demand. Stress-tests how the data pin the primitive; it does not invent evidence or citations.

Identification Strategy (jru-identification)

When to trigger

  • An experiment elicits a risk or ambiguity attitude but the mechanism may not be incentive-compatible (truthful revelation in doubt)
  • A choice-list / BDM / matching-probability design is used and a referee questions whether it measures the parameter cleanly
  • A structural model is estimated on field data and it is unclear what variation identifies the risk parameter (vs. beliefs, vs. constraints)
  • A VSL or insurance-demand estimate rests on regressions whose exclusion or selection assumptions are not defended

The JRU identification bar

At JRU "identification" means the mapping from choices to the risk/uncertainty primitive must be explicit and defended — whether that primitive is elicited in the lab or estimated from the field. Because the journal spans theory, experiment, and empirics, identification splits by branch. The unifying demand: the procedure must reveal the intended parameter and not confound it with utility curvature, beliefs, or constraints.

Branch A: Experimental elicitation of risk / ambiguity preferences
  • Incentive compatibility. State the mechanism and why it elicits truthfully: Becker–DeGroot–Marschak, multiple price lists / choice lists, the random-incentive (one-task-paid) system. Address the known threats — BDM is only IC under EU; the random-incentive system assumes isolation; multiple-switching in price lists signals confusion.
  • Estimand before estimator. Name what the task is meant to recover — a switching point, a certainty equivalent, a matching probability — and the structural parameter it maps to (curvature, w(p), ambiguity index).
  • Design that separates u from w. A single risk-attitude number cannot identify utility curvature and probability weighting jointly; use lottery menus designed to break that confound (e.g., varying probabilities at fixed outcomes).
  • Stakes, hypothetical vs. real, order, and house-money effects stated and, where they matter, randomized.
Branch B: Structural / empirical estimation (risk preferences, VSL, insurance)
  • Name the identifying variation. For VSL hedonic-wage: the wage–fatality-risk tradeoff, conditional on the compensating-differentials assumptions; defend why risk is not proxying for unobserved job disamenities. For insurance demand: the price/loss variation that moves takeup.
  • Beliefs vs. preferences. Field choices reflect both; say how the design separates a risk attitude from a subjective belief (e.g., independent belief elicitation, or variation that moves one but not the other).
  • Selection and measurement error in risk exposure addressed; report the estimating equation and the inference (clustered appropriately).
  • Estimation regularity for structural models: objective (MLE/GMM/MSM), starting values, and recovery of known parameters in simulation.
The confounds JRU referees probe most

Three confounds recur across both branches; name how the design defeats each:

  • Utility curvature vs. probability weighting. A single risk-attitude index cannot separate them; only a design that varies probabilities and outcomes independently can.
  • Preferences vs. beliefs. Field and even lab choices reflect subjective probabilities; either elicit beliefs separately or use variation that moves price/cost while holding beliefs fixed.
  • Preferences vs. constraints. Low takeup or conservative choices may reflect liquidity, not taste; control for or exploit variation in the constraint.

A clean identification section states, for each of these, whether the design breaks the confound or leaves it open — and the honest "leaves it open" entries belong in the limitations, not hidden.

Execution bridge (StatsPAI / Stata MCP)

Estimate and audit the design, don't only describe it. Full map: execution-with-mcp. JRU spans decision experiments and applied risk; randomization inference for experiments, DiD/IV for observational claims.

  • detect_design → recommend → fit with as_handle=true → audit_result.
  • Observational causal claims: staggered DiD (callaway_santanna / sun_abraham + bacon_decomposition + honest_did_from_result); IV (effective_f_test + anderson_rubin_ci); RDD (rdrobust + mccrary_test).
  • Experiments: randomization-based inference + romano_wolf for many-outcome control.
  • Sensitivity: oster_delta / sensemakr for observational claims.

Report the magnitude in interpretable units; route the full battery to the appendix. A run end-to-end (synthetic data, real returns) is in the JF execution walkthrough.

Checklist

  • Branch chosen; the choices-to-primitive mapping stated in one sentence
  • Experimental: mechanism named and its incentive-compatibility (and its assumptions) defended
  • Experimental: design separates utility curvature from probability weighting (or risk from ambiguity)
  • Empirical: the identifying variation is named; preferences are separated from beliefs and constraints
  • VSL: compensating-differentials / exclusion assumptions stated and probed
  • Inference appropriate to the design (clustering at randomization or assignment level)
  • The estimated parameter is not asked to carry interpretation the identification does not support
Show full SKILL.md (445 more words)Show less

Anti-patterns

  • Calling a single risk-attitude index "the" risk preference when curvature and weighting are confounded
  • Using BDM or a price list and claiming truthful revelation without noting the EU/isolation assumptions it rests on
  • A VSL estimate that ignores selection of workers into risky jobs and the publication-selection debate
  • Reading a field choice as a pure preference when it also reflects beliefs or liquidity constraints
  • "The estimator converged" presented as if it were identification (structural)

Referee pushback mapped to the identification fix

  • "Your 'risk preference' is just utility curvature times probability weighting — you can't tell them apart." → Add lottery menus that vary probabilities at fixed outcomes so w(p) is identified separately from u; report both.
  • "BDM is not incentive-compatible outside expected utility." → State the IC assumptions; where the paper studies non-EU agents, use a mechanism whose IC does not presume EU, or bound the bias.
  • "Low takeup could be misperceived risk, not a preference." → Elicit subjective probabilities independently; use price variation that moves cost holding beliefs fixed.
  • "Your VSL is contaminated by selection into risky jobs." → Probe selection (instrument or panel within-worker variation), and benchmark against the meta-analytic VSL distribution rather than a single estimate.

Worked vignette (illustrative)

A field study infers high risk aversion from low flood-insurance takeup. A referee notes this confounds preferences with beliefs (households may think the risk is near zero) and with constraints (premiums vs. liquidity). The JRU fix elicits subjective loss probabilities separately, then uses exogenous premium variation (say a subsidy lottery) to move price holding beliefs fixed — so the demand elasticity identifies a preference, not a misperception. The reported elasticity (illustrative −0.3) now means what the paper claims it means.

Second vignette: separating curvature from weighting (illustrative)

A lab paper reports a single "risk aversion" coefficient from a Holt–Laury price list. A referee points out the coefficient bundles utility curvature with probability weighting, so it cannot speak to whether the behavior is EU or CPT. The JRU revision adds a menu block that holds outcomes fixed while sweeping probabilities; the resulting certainty equivalents trace an inverse-S w(p) that pins weighting independently of u — turning one confounded number into two interpretable primitives.

Stating what is NOT identified

Every honest identification section closes a door it leaves open. Name explicitly what the design cannot recover — a population parameter beyond the experimental sample, a belief you could not elicit, a margin you could not exogenously vary. JRU referees treat a candid "we identify the preference but not the belief" far more kindly than an overclaim that the data cannot support, and it pre-empts the most damaging review verdict: that the headline number means something other than what the paper says.

Output format

text
【Journal】Journal of Risk and Uncertainty
【Skill】jru-identification
【Verdict】identified / patch design / re-estimate
【Branch】experimental elicitation / structural-empirical
【Choices-to-primitive mapping】one sentence
【Identification evidence】mechanism+IC / identifying variation + belief separation
【What it does NOT identify】<confounds left open>
【Source status】verified / 待核实 / not asserted
【Next skill】jru-robustness

© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in Journal-of-Risk-and-Uncertainty-Skills/skills/jru-identification of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Jru Identification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Jru Identification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jru Identification this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~2.4kAutomated safety check: PassMIT
What If OracleK-Dense-AI/scientific-agent-skills48k1 repos~2.9kAutomated safety check: PassCC-BY-NC-4.0
Paper ReviewEvoScientist/EvoSkills478—~4.5kAutomated safety check: PassApache-2.0
Data Finderbrycewang-stanford/Auto-Empirical-Research-Skills4.6k—~1.7kAutomated safety check: PassCustom licence
Weakness Scannerflonat/flonat-research146—~1.5kAutomated safety check: PassMIT
Ecta Identificationfranklee16/academic-research-skills2231 repos~1.9kAutomated safety check: PassNone

Similar skills

  • What If Oracle

    K-Dense-AI/scientific-agent-skills

    Supports structured what-if scenario analysis for research planning, experimental contingencies, and scientific project decisions.

    48k GitHub starsUsed in 1 repo~2.9k tokens
    Research & ScienceAuto-check passed
  • Paper Review

    EvoScientist/EvoSkills

    Guides self-review of YOUR OWN academic paper before submission with adversarial stress-testing.

    478 GitHub stars~4.5k tokensUpdated 9 days ago
    Research & ScienceAuto-check passed
  • Data Finder

    brycewang-stanford/Auto-Empirical-Research-Skills

    Find and assess datasets for a research question. An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.

    4.6k GitHub stars~1.7k tokensUpdated 4 days ago
    Research & ScienceAuto-check passed
  • Weakness Scanner

    flonat/flonat-research

    Identify recurring weak arguments, unsupported assumptions, and vulnerable inference patterns across a literature corpus.

    146 GitHub stars~1.5k tokensUpdated 10 days ago
    Research & ScienceAuto-check passed
  • Ecta Identification

    franklee16/academic-research-skills

    A skill your agent uses when the bottleneck is identification and inference for an Econometrica manuscript — identification conditions and asymptotic distribution theory for an estimator, or axioms…

    223 GitHub starsUsed in 1 repo~1.9k tokens
    Research & ScienceAuto-check passed
  • Jbv Topic Selection

    franklee16/academic-research-skills

    A skill your agent uses when shaping or stress-testing a research question for the Journal of Business Venturing (JBV) — confirming the entrepreneurial phenomenon is central, picking a…

    223 GitHub starsUsed in 1 repo~1k tokens
    Research & ScienceAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo
  • Aaag Data Analysis

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…

    1.2k GitHub stars~1.3k tokensUpdated 13 days ago
    Auto-check passed
  • Aaag Literature Positioning

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…

    1.2k GitHub stars~1.3k tokensUpdated 13 days ago
    Auto-check passed
  • Aaag Rebuttal

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…

    1.2k GitHub stars~1.4k tokensUpdated 13 days ago
    Auto-check passed
  • Aaag Research Design

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…

    1.2k GitHub stars~1.4k tokensUpdated 13 days ago
    Auto-check passed
  • Aaag Review Process

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…

    1.2k GitHub stars~1.3k tokensUpdated 13 days ago
    Auto-check passed
  • Aaag Submission

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…

    1.2k GitHub stars~1.6k tokensUpdated 13 days ago
    Auto-check passed

Questions about Jru Identification

What does Jru Identification do?

A skill your agent uses when identifying a risk or uncertainty parameter is the bottleneck for a Journal of Risk and Uncertainty (JRU) manuscript — incentive-compatible elicitation in an experiment…. Jru Identification is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when identifying a risk or uncertainty parameter is the bottleneck for a Journal of Risk and Uncertainty (JRU) manuscript — incentive-compatible elicitation in an experiment, or structural/empirical estimation of risk preferences, VSL, or insurance demand.

When should I use Jru Identification?

Jru Identification fits situations like: identifying a risk; structural/empirical estimation of risk preferences; insurance demand.

How do I install Jru Identification in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-identification -a claude-code`. Or copy the skill folder (Journal-of-Risk-and-Uncertainty-Skills/skills/jru-identification in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jru-identification in your project. Claude Code loads it when a task matches its description.

How do I install Jru Identification in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-identification -a codex`. Or copy the skill folder (Journal-of-Risk-and-Uncertainty-Skills/skills/jru-identification in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jru-identification in your project. Codex loads it when a task matches its description.

Can I use Jru Identification in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-identification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jru-identification, .gemini/skills/jru-identification, .github/skills/jru-identification and .opencode/skills/jru-identification in your project.

What does Jru Identification need to run?

SKILL.md names no scripts, command-line tools or credentials: Jru Identification is instructions for the agent only.

Does Jru Identification access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Jru Identification safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Jru Identification use?

Jru Identification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Jru Identification use?

About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Jru Identification?

Skills that share tags, products or a category with Jru Identification: What If Oracle (K-Dense-AI/scientific-agent-skills, 48k stars), Paper Review (EvoScientist/EvoSkills, 478 stars), Data Finder (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars) and Weakness Scanner (flonat/flonat-research, 146 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jru Identification?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.

Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.