跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

joinquant-skill

Generate accurate, runnable quantitative strategy code for the JoinQuant (聚宽) platform. Use this skill when the user asks to write a stock/ETF/futures backtest, paper-trading, or live-trading strategy on JoinQuant — the skill provides progressive-disclosure access to the complete JoinQuant API knowledge base (14 categories, 294KB official docs), 5 production-ready strategy templates (single-stock MA, multi-factor, ETF rotation, momentum, mean-reversion), and a lint tool that catches hallucinated APIs, future-function violations, and unset price-mode/slippage/commission. Chinese-friendly. Code generated by this skill should paste directly into the JoinQuant online editor without modification.

gaaiyun · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add gaaiyun/joinquant-skill --skill joinquant-skill

技能说明


name: joinquant-skill description: Generate accurate, runnable quantitative strategy code for the JoinQuant (聚宽) platform. Use this skill when the user asks to write a stock/ETF/futures backtest, paper-trading, or live-trading strategy on JoinQuant — the skill provides progressive-disclosure access to the complete JoinQuant API knowledge base (14 categories, 294KB official docs), 5 production-ready strategy templates (single-stock MA, multi-factor, ETF rotation, momentum, mean-reversion), and a lint tool that catches hallucinated APIs, future-function violations, and unset price-mode/slippage/commission. Chinese-friendly. Code generated by this skill should paste directly into the JoinQuant online editor without modification.

JoinQuant Skill

Generate quantitative strategy code that runs on the JoinQuant platform without modification.

When to Use This Skill

Yes:

  • Stock backtest / paper trading / live trading on JoinQuant (聚宽)
  • ETF rotation, multi-factor stock selection, momentum, mean reversion strategies
  • Futures (期货) strategies on JoinQuant
  • Margin trading (融资融券) strategies
  • Strategy code review / lint to catch hallucinated APIs and future-function violations
  • Translating a strategy idea into JoinQuant API calls

No:

  • Local data analysis without JoinQuant (use jqdatasdk directly, or pandas/numpy)
  • Strategy backtesting on other platforms (vectorbt, backtrader, vn.py — use those skills instead)
  • Pure machine learning model training (no JoinQuant-specific API needed)
  • Live trading on broker APIs other than JoinQuant simulated trading (CTP, Interactive Brokers, etc. need different skills)

Default Mode

Most user requests fall into one of three patterns. Detect the pattern first, then route:

PatternTriggerAction
Quick code"帮我写一个 X 策略" / "用聚宽实现 Y"Pick template, fill in user-specific parts, return ready-to-paste code
API question"聚宽里 get_price 的 fq 参数是什么意思" / "set_option 都有哪些选项"Load matching references/XX-*.md and answer based on it
Code review"帮我审一下我这段聚宽代码" / paste of existing codeRun mental strategy_lint.py against it (or actually call it), point out hallucinated APIs and missing safeguards

Progressive Disclosure: 14 API Categories

DO NOT load all references at once (294KB total, would burn context). Pattern-match the user request and load only the relevant category file:

CategoryReference fileTriggered by keywords
策略设置references/01-strategy-setup.mdinitialize, set_benchmark, set_option, set_order_cost, set_slippage, run_daily, run_weekly, run_monthly
数据获取references/02-data-getters.mdget_price, attribute_history, history, get_current_data, get_fundamentals, get_money_flow, get_concept, get_industry
jqlib 因子库references/03-jqlib.mdalpha101, alpha191, technical_analysis, jqfactor
数据处理references/04-data-processing.mdget_factor_values, calc_factor_history, neutralize, winsorize, standardlize
组合优化references/05-portfolio-optimization.mdoptimizer, max_sharpe, min_variance, target_return, mean_variance
交易函数references/06-trading.mdorder, order_value, order_target, order_target_value, cancel_order, get_open_orders
对象references/07-objects.mdOrder, Position, Portfolio, OrderCost, OrderStyle, MarketOrderStyle, LimitOrderStyle
其他函数references/08-misc-functions.mdrecord, log, write_file, send_message
多投资组合references/09-multi-portfolio.mdset_subportfolios, SubPortfolioConfig, transfer_cash
Tick 级references/10-tick-strategy.mdtick, get_ticks, every_tick
融资融券references/11-margin-trading.mdmargincash_open, margincash_close, marginsec_open, marginsec_close, set_margin_rate
期货references/12-futures.mdget_dominant_future, futures, set_future_commission
归因分析references/13-attribution-analysis.mdbrinson, factor analysis, attribution
引擎机制references/14-strategy-engine.md撮合, 复权, 滑点, 税费, 风险指标, alpha, beta, sharpe, max drawdown

If the user mentions a function name not in any keyword list, use scripts/api_search.py <keyword> to find it across all references.

Templates

5 production-ready templates in templates/:

TemplateWhen to use
01-basic-single-stock.pyFirst-time users, single stock, simple MA crossover. The "hello world" of JoinQuant.
02-multi-factor.pyMulti-factor stock selection (PE / market cap / momentum), monthly rebalance. Most common "real" strategy structure.
03-etf-rotation.pyETF rotation by momentum ranking. Popular among retail investors.
04-momentum-stock.pyCross-sectional momentum on stock pool, weekly rebalance.
05-mean-reversion.pyBollinger / RSI mean reversion. Volatility-aware.

When generating code, start from a template, modify, do not write from scratch. Reasons:

  1. Templates already include the boilerplate (set_benchmark, set_option, set_order_cost, set_slippage)
  2. Templates have correct timing (run_daily / run_weekly with proper time arg)
  3. Templates avoid future-function pitfalls (count-based instead of date-based slicing)

Lint Tool

Before returning generated code to user, mentally (or actually) run strategy_lint.py:

python scripts/strategy_lint.py <user_strategy.py>

Critical checks:

  • ❌ Hallucinated API calls (e.g., jqdata.get_stock_data() doesn't exist)
  • ❌ Future function: using non-count get_price or attribute_history with hardcoded future dates
  • ❌ Missing set_option('use_real_price', True) (mandatory for accurate backtest)
  • ❌ Missing set_order_cost(...) and set_slippage(...)
  • ❌ Order placed in before_trading_start / after_trading_end (forbidden, will be rejected)
  • ❌ Use of deprecated APIs (update_universe etc.)
  • ⚠️ Recommend g. global vars for state across bars instead of module globals
  • ⚠️ Recommend cluster-aware sizing for high-correlation assets

Things That Must Survi

阅读完整来源 ↗