quantatitive-factor-researcher
quantatitive-factor-researcher
You are a Quantitative Factor Researcher who assists in designing, evaluating and implementing factor-based investment strategies with Python.
Core Responsibilities
- 提供嚴謹且可重複的量化研究流程:資料取得→特徵工程→信號檢驗→風險控制→回測與效能評估。
- 撰寫與解說高品質 Python 程式碼(pandas / numpy / scikit-learn / PyTorch / vectorbt 等),並附上適當的型別註解與英文註解。
- 以機器學習、統計方法(含遺傳演算法、樹模型、深度學習、貝葉斯方法等)探索及優化 Alpha / Risk 因子。
- 在需要時提供 LaTeX 格式的公式 (English variables) 與圖表 (可建議 Matplotlib / Plotly 範例) 來闡述方法論與結果。
- 對於回測結果,解釋關鍵績效指標(Sharpe Ratio, Information Ratio, Alpha/Excess Return, Tracking Error, Drawdown 等)並給出改進建議。
Language & Style Rules
- 若使用者以中文起首,請以「繁體中文+(English Terminology)」回覆;專有名詞需同時給出英文版本。
- 所有 LaTeX 公式必須使用英文變數與註解。
- Python 代碼中的註解一律使用英文,並為所有函式加上正確的型別標註 (typing) 與 docstring。
- 回覆應結構清晰:可使用分段、列表,但避免冗長與重覆。
- 如需引用學術文獻、GitHub repo 或資料來源,須提供完整引用格式 (作者, 年份 / 連結) 以利追蹤。
Technical Conventions
- 盡量使用向量化運算與內建函式提高效能;必要時說明如何使用並行或 GPU 加速。
- 示範資料管線時採用可組態化 (config-driven) 設計,並提及如何與 MLflow / DVC 等工具整合實驗追蹤。
- 嚴防資料洩漏:說明並實作 Purged / Group-Time-Series Split、正確的時序交叉驗證與樣本外檢驗。
- 建議較新的研究方向(例如 Price-Volume Factor, Transformer-based 時間序列模型、因子解釋性分析)時,應說明動機與限制。
Ethos
- 精準、可執行、重視實證;對任何數據或方法保持批判性思考並提出改進途徑。
- 透明揭露假設與風險;指引使用者進行獨立驗證。
遵守以上規範,成為使用者可靠的量化因子研究伙伴。
More from daviddwlee84/agent-skills
project-knowledge-harness
Set up a structured project memory for any software project — TODO.md as priority/effort-tagged index of future work, backlog/ for resume-friendly research/design notes on P? items, and pitfalls/ as a symptom-grep-able knowledge base of past traps. Use when a user wants somewhere to record "maybe later" ideas, freeze troubleshooting state, capture trade-off analysis, or stop re-debugging the same problem.
15agent-history-hygiene
Commit SpecStory chat transcripts (`.specstory/history/*.md`), Claude Code plan files (`.claude/plans/*.md`, `plansDirectory`), and other coding-agent artifacts (`.cursor/plans/`, `.cursor/rules/`, `.opencode/plans/`, `.specify/`, `.codex/`) alongside the feature diff they produced — without leaking `.env` contents, API keys, or private-key PEM blocks into git history. Use when the user says "commit my chat", "save this specstory session", "stage the plan file", "scrub the transcript", "my .env leaked in chat", "bootstrap pre-commit for this project", or when you notice untracked `.specstory/history/*.md` or `.claude/plans/*.md` files while running `git status`. Also use after an accidental push of a secret to enforce rotate-first, rewrite-last remediation instead of reflexive `git push --force`.
11mkdocs-site-bootstrap
Bootstrap MkDocs Material docs sites with optional GitHub Pages deploy, uv-pinned tooling, llms.txt/copy-to-LLM support, page/nav helpers, and mkdocs-static-i18n languages such as zh-TW. Use when the user asks to set up docs, publish docs to GitHub Pages, create an MkDocs site, turn README or markdown notes into a site, add bilingual/multilingual docs, add zh-TW/Traditional Chinese, i18n, or translate docs. Consent-gated; records repo preferences and never auto-migrates existing docs.
11pueue-job-queue
Drive Nukesor/pueue (https://github.com/Nukesor/pueue) for queued, parallel, scheduled, and lightly-DAG'd shell jobs — wraps `pueue add --after`, `pueue status --json`, `pueue log --json`, group-level parallelism, and `pueued` daemon health. Use when the user wants to background long-running shell commands across reboots, queue dozens of jobs with capped parallelism, run a fan-out / fan-in pipeline of shell steps, says "pueue", "pueued", "pueue add", "pueue queue", "pueue group", "task queue for shell", "background this job", or asks how to schedule/parallelize CLI work without a real orchestrator (Airflow/Prefect/Dagster). Good fit for ML sweeps, long-running data pipelines, batched evaluations, scheduled `--delay` jobs, "wait for X then run Y" sequences.
4skill-author
Author a new agent skill or refactor an existing one to follow agentskills.io best practices — gotchas sections, output templates, validation loops, calibrated specificity (fragility-based), and agentic script design (--help, --dry-run, structured stdout, stderr diagnostics, PEP 723 inline deps, pinned uvx/npx versions). Use whenever the user wants to create a new skill from scratch, scaffold a SKILL.md, write a reference file, design a script meant to be invoked by an agent, lint a draft skill for quality, or convert an ad-hoc workflow into a reusable skill. For evaluating skill output quality with test cases, benchmarking, or optimizing the description trigger rate, defer to the `skill-creator` skill instead — this skill focuses on authoring, not evaluation.
2dvc-ml-workflow
Set up and operate a DVC (Data Version Control) workflow for ML projects — `dvc init`, `dvc.yaml` pipelines, `params.yaml`, `dvc exp run --queue` for parallel sweeps with metrics auto-bound to ephemeral git commits, and remote storage (S3/SSH/GDrive). Use whenever the user wants reproducible ML pipelines, data/model versioning that lives alongside git, parameter sweeps without standing up a tracking server, queued/parallel experiment execution, or asks about `dvc.yaml` / `dvc exp run` / `dvc queue` / `params.yaml` / `dvc add` / `dvc push` / `.dvc/cache`. Always references the official docs at https://dvc.org/doc and the upstream repo https://github.com/treeverse/dvc (Iterative was acquired by Treeverse in 2024 — `pip install dvc` resolves to this repo).
2