Run any Skill in Manus with one click

econ-finance-data-sources

Stars1

Forks0

UpdatedJuly 1, 2026 at 23:17

Route empirical econ/finance data-source work across WRDS, CRSP, Compustat, SEC/EDGAR, NBER, SSRN, OpenAlex, Unpaywall, and common public finance/econ datasets. Use when the blocker is finding, joining, licensing, or documenting source data.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

BaranziniLab

BaranziniLab/biorouter-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

EconomistsLife, Physical, and Social Science Occupations·SOC 19-3011

SKILL.md

readonly

name	econ-finance-data-sources
description	Route empirical econ/finance data-source work across WRDS, CRSP, Compustat, SEC/EDGAR, NBER, SSRN, OpenAlex, Unpaywall, and common public finance/econ datasets. Use when the blocker is finding, joining, licensing, or documenting source data.
user-invocable	true
license	Apache-2.0

Economics and Finance Data Sources

Source adaptation: BioRouter-original synthesis inspired by Auto-Empirical Research Skills capability clusters, rewritten under Apache-2.0. This is native BioRouter guidance and does not copy upstream text.

When to Use

Use this skill when the user asks about WRDS, CRSP, Compustat, SEC/EDGAR, NBER, SSRN, OpenAlex, public finance/econ data, or data-source provenance. If the task is biomedical, clinical, or omics-specific, combine this with the appropriate BioSkills category and extension instead of treating the methods in isolation.

Intake

Collect:

Research question, estimand, and audience.
Dataset/source, file formats, licenses, access constraints, and identifiers.
Unit of analysis, time period, sample design, and outcome/treatment definitions.
Software stack and expected artifact: code, table, figure, memo, manuscript, appendix, or review response.
Whether the work is exploratory, confirmatory, replication, submission, or referee-response.

Method Gates

Before writing conclusions:

State the design and estimand before the model.
Preserve provenance for every dataset, variable, citation, and transformation.
Match inference to the sampling/assignment structure.
Identify weights, clusters, panels, repeated measures, or dependence before estimating.
Check robustness against the actual design threat, not decorative alternative models.
Keep code/table/figure outputs reproducible from a clean entry point.

BioRouter Routing

Use empirical-research-router for full workflow staging.
Use causal-identification-gates before causal language.
Use econometrics-toolkit, statistical-modeling-bayes, or financial-accounting-econometrics for adjacent method detail.
Use citation-temporal-integrity, claim-evidence-integrity, and replication-package-audit for publication-facing outputs.

Output Pattern

Return a compact plan with:

Primary route and why.
Required data/design evidence.
Minimal next command or artifact.
Failure modes.
Verification checklist before final claims.

More from this repository

same repository

computational-fluid-dynamics

BaranziniLab/biorouter-skills

Plan and review computational fluid dynamics workflows with meshes, boundary conditions, turbulence models, OpenFOAM/FluidSim-style solvers, validation cases, convergence checks, and reproducible simulation artifacts. Use when users mention CFD, fluid dynamics, Navier-Stokes, meshing, turbulence, OpenFOAM, or flow simulation.

2026-07-011

arbor-optimization

BaranziniLab/biorouter-skills

Run evaluator-driven hypothesis trees for improving research artifacts, prompts, analyses, and designs. Use when a task needs branch-and-prune exploration, rubric scoring, iterative refinement, or explicit comparison of competing scientific/workflow alternatives.

2026-07-011

autoskill-workflow-discovery

BaranziniLab/biorouter-skills

Detect repeated user workflows and draft native BioRouter skills, hooks, or checklist updates from observed work patterns. Use when users ask to turn repeated work, screen-history patterns, project routines, or recurring guardrails into reusable BioRouter skills.

2026-07-011

bids-neuroimaging

BaranziniLab/biorouter-skills

Plan and audit BIDS neuroimaging datasets, derivatives, validation, metadata, and reproducible preprocessing. Use when users mention BIDS, fMRI, MRI, EEG/MEG/iEEG, DICOM conversion, dataset_description.json, participants.tsv, or neuroimaging derivatives.

2026-07-011

clinical-ai-modeling

BaranziniLab/biorouter-skills

Plan and review clinical AI modeling workflows with EHR cohorts, PyHealth-style tasks, validation, bias checks, calibration, safety boundaries, and no-PHI handling. Use when users ask about clinical prediction models, risk scores, treatment-response ML, medical reports, or clinical model evaluation.

2026-07-011

general-time-series-forecasting

BaranziniLab/biorouter-skills

Plan and review general time-series forecasting with classical models, ML, foundation models, backtesting, leakage checks, and uncertainty. Use for non-omics forecasting, sensor streams, operations, finance, clinical vitals, demand, or irregular temporal data.

2026-07-011

name	econ-finance-data-sources
description	Route empirical econ/finance data-source work across WRDS, CRSP, Compustat, SEC/EDGAR, NBER, SSRN, OpenAlex, Unpaywall, and common public finance/econ datasets. Use when the blocker is finding, joining, licensing, or documenting source data.
user-invocable	true
license	Apache-2.0

Economics and Finance Data Sources

When to Use

Intake

Collect:

Research question, estimand, and audience.
Dataset/source, file formats, licenses, access constraints, and identifiers.
Unit of analysis, time period, sample design, and outcome/treatment definitions.
Software stack and expected artifact: code, table, figure, memo, manuscript, appendix, or review response.
Whether the work is exploratory, confirmatory, replication, submission, or referee-response.

Method Gates

Before writing conclusions:

State the design and estimand before the model.
Preserve provenance for every dataset, variable, citation, and transformation.
Match inference to the sampling/assignment structure.
Identify weights, clusters, panels, repeated measures, or dependence before estimating.
Check robustness against the actual design threat, not decorative alternative models.
Keep code/table/figure outputs reproducible from a clean entry point.

BioRouter Routing

Use empirical-research-router for full workflow staging.
Use causal-identification-gates before causal language.
Use econometrics-toolkit, statistical-modeling-bayes, or financial-accounting-econometrics for adjacent method detail.
Use citation-temporal-integrity, claim-evidence-integrity, and replication-package-audit for publication-facing outputs.

Output Pattern

Return a compact plan with:

Primary route and why.
Required data/design evidence.
Minimal next command or artifact.
Failure modes.
Verification checklist before final claims.