KO
|
EN
gitlite — search
Search
#typescript
#ai-agents
#ai
#dsh-plugin
#deepseek-harness
#open-source
#cli
#claude-code
#codex
#developer-tools
#react
#windows
ai-asset-pricing
★ 58
Open GitHub ↗
Empirical Asset Pricing Tools
Download README (.md)
Explore Similar Repositories
ClawEnvKit
:
Open-source Environment toolkit of claw-like agents, support task/harness generation and evaluation
Kmdb
:
No description available.
IMS_VAROS
:
OfficialSchedulerBlockModuleFor OxygenOS/ColorOS/RealmeUI
FusionUI
:
A C++23 retained-mode UI library with declarative syntax, animations and styling! Currently in experimental stage*
LatentUM
:
No description available.
// repository documentation
Was this content helpful?
★ 0
(0 ratings)
Select Rating:
★
★
★
★
★
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
ai-asset-pricing
?
Download (.md)
[](https://raw.githubusercontent.com/Alexander-M-Dickerson/ai-asset-pricing/main/LICENSE) [](https://www.python.org/downloads/) # ai-asset-pricing `ai-asset-pricing` is an AI-assisted empirical asset pricing research repo for WRDS data work, factor-model workflows, PyBondLab package use, automation of repeated research tasks, and LaTeX paper writing. The main promise is simple: clone the repo, ask your agent to onboard the repo, and get to a research-ready workflow without hand-editing machine-specific config inside the shared tree. ## Clone to Research-Ready ### Claude Code users Ask Claude Code to onboard the repo. The standard Claude entry point is `/onboard`. Under the hood, `/onboard` should drive the shared cold-start flow: 1. use `tools/onboard.ps1` or `tools/onboard.sh` to find or install Python 3.11+ 2. hand off to `tools/onboard_driver.py` 3. let that driver run the shared `tools/bootstrap.py` engine The Python-level bootstrap engine is still: 1. `tools/bootstrap.py audit` 2. execute the emitted `bootstrap_plan` 3. `tools/bootstrap.py apply` 4. rerun `tools/bootstrap.py audit` ### Codex and Gemini CLI users Ask Codex or Gemini CLI in chat to onboard or set up the repo. They should first find or install a working Python interpreter, ask once whether you have WRDS, and then run the same shared flow for you without the Claude slash command wrapper: 1. `tools/bootstrap.py audit` 2. execute the required commands from `bootstrap_plan` 3. run `tools/bootstrap.py apply` 4. rerun `tools/bootstrap.py audit` Codex starts from `AGENTS.md`. Gemini CLI uses `GEMINI.md`, which imports the same shared routing layer. ## What It Covers - WRDS-oriented data extraction and query workflows - factor-model research setup and reusable automation - `fintools/` shared utilities - `fintools.figures` publication-quality plotting, house-style and FT-style figure suites, and Word proof packs - `packages/PyBondLab/` package install, testing, and research workflows - LaTeX paper scaffolding, drafting, auditing, and compilation - shared repo context for Claude Code, Codex, and Gemini CLI ## Repo Layout ```text AGENTS.md # Codex routing and repo rules CLAUDE.md # Claude adapter and commands GEMINI.md # Gemini adapter .claude/ # Claude-native rules, skills, agents, hooks docs/ai/ # Shared cross-tool context tools/bootstrap.py # Shared onboarding audit/apply engine tools/onboard_driver.py # Python orchestration layer after Python exists tools/onboard.ps1 # PowerShell cold-start onboarding entrypoint tools/onboard.sh # Bash cold-start onboarding entrypoint tools/onboard_probe.py # Shared environment probe implementation tools/onboarding_smoke_test.py # Temp-clone onboarding smoke test tools/context_drift.py # Documentation drift detector tools/release_preflight.py # Release/readiness checker tools/figure_examples.py # FINS/FT validation figure gallery generator fintools/ # Shared Python utilities packages/PyBondLab/ # Portfolio construction package ``` ## Prerequisites - Claude Code, Codex, or Gemini CLI - Python 3.11+ available somewhere on the machine so the shared bootstrap can run - Bash on `PATH` for Claude hook automation and Bash bootstrap commands - Windows Claude users should install Git for Windows / Git Bash and ensure `bash` is on `PATH` - internet access for first-run package installation - a WRDS account if you need live data access ## Local State and Synced Folders The canonical local state lives **outside the repo** in a per-user OS-specific directory reported by `tools/bootstrap.py audit`. That canonical local state includes tool paths and local files such as: - `local_env.md` - `claude.local.md` - `settings.local.json` Repo-root compatibility shims may still be generated when explicitly requested: - `LOCAL_ENV.md` - `CLAUDE.local.md` Those shims are legacy compatibility files only. In shared Dropbox/OneDrive working trees, the canonical local state should stay external so machine-local paths do not sync across users. `.claude/settings.local.json` is ignored maintainer-local Claude state. It is not release payload and should not be committed. ## Manual WRDS Files If onboarding has not created them yet, you still need: 1. `~/.pg_service.conf` 2. `~/.pgpass` 3. `~/.ssh/config` entry for `Host wrds` if you need SSH/TAQ workflows Minimal `~/.pg_service.conf`: ```ini [wrds] host=wrds-pgdata.wharton.upenn.edu port=9737 dbname=wrds user=YOUR_WRDS_USERNAME ``` Minimal `~/.pgpass`: ```text wrds-pgdata.wharton.upenn.edu:9737:wrds:YOUR_WRDS_USERNAME:YOUR_PASSWORD ``` Then set restrictive permissions: ```bash chmod 600 ~/.pgpass ``` ## Without WRDS WRDS is optional. The repo is still useful without live WRDS access: - AI skills, rules, and agents for writing, auditing, and project scaffolding - `fintools` package work - publication-quality plotting examples from frozen public validation fixtures - `PyBondLab` install/import and bundled-data smoke coverage - LaTeX boilerplate and paper setup - local onboarding and release/readiness checks The agent should ask once whether the user has a WRDS account. If the answer is no, onboarding should skip WRDS setup and still complete successfully once the base repo is ready. WRDS is only required for live data extraction, WRDS connectivity checks, and running research workflows on real WRDS-backed data. ## Tool Entry Points - Codex: `AGENTS.md` - Claude Code: `CLAUDE.md` - Gemini CLI: `GEMINI.md` - onboarding: `docs/ai/onboarding.md` - WRDS workflow: `docs/ai/wrds.md` - PyBondLab workflow: `docs/ai/pybondlab.md` - writing and LaTeX workflow: `docs/ai/writing.md` - publication figures workflow: `docs/ai/figures.md` The `.claude/agents/*.md`, `.claude/skills/*.md`, and `.claude/rules/*.md` files are plain markdown and can be reused across tools. ## Maintainer Preflight Before publishing shared changes, run: ```bash <python> tools/release_preflight.py --strict ``` Strict preflight auto-cleans repo temp artifacts when possible, including test temp folders and `__pycache__`, and it tolerates gitignored repo-root local artifacts such as `.venv/`, `venv/`, `.claude/settings.local.json`, `.tmp-pytest-current/`, `.tmp-uv-cache/`, and `.Rhistory`. It still fails if the release tree contains `LOCAL_ENV.md` or `CLAUDE.local.md`. ## Acknowledgements - [Piotr Orlowski](https://github.com/piotrek-orlowski) and the [`claude-wrds-public`](https://github.com/piotrek-orlowski/claude-wrds-public/tree/main/agents) agent set, which provided the starting point for some WRDS-oriented agent materials used here and then heavily augmented for this repo. - [Scott Cunningham's `MixtapeTools`](https://github.com/scunning1975/MixtapeTools), which provided some base rules and skills that were also heavily augmented for this workflow. ## License This project is licensed under the MIT License. See [LICENSE](LICENSE) for details.
