excel-template-contract-fill

Transform SHFE, DCE, CZCE, and GFEX futures data into unified Excel templates.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/cx-qk/Calendar-Spread-Arbitrage --skill excel-template-contract-fill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: excel-template-contract-fill
Source: https://github.com/cx-qk/Calendar-Spread-Arbitrage/tree/main/.cursor/skills/excel-template-contract-fill
Command: npx skills add https://github.com/cx-qk/Calendar-Spread-Arbitrage --skill excel-template-contract-fill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines semantic rules to transform raw futures market data from SHFE, DCE, CZCE, and GFEX into a unified contract template and outputs to the 合约数据(整理后)/ directory. It emphasizes rule-based data conversion rather than fixed scripts, enabling AI to adapt to changing input formats and newly listed products.

Core Features & Use Cases

  • Semantic field mapping across four exchanges to produce standardized columns: 合约代码, 商品名称, 交割月, 收盘价, 持仓量, 最低保证金, 最低保证金率.
  • Robust handling of variable input formats, missing columns, and 新品种 with guidance for dictionary updates.
  • Output artifacts include standardized workbooks per exchange and a 缺失原因汇总 report for auditing and improvement.

Quick Start

Place raw data into 原始数据/期货数据/ and 原始数据/合约信息/; then run the reference conversion tool to generate the standardized outputs.

Frequently Asked Questions about excel-template-contract-fill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I normalize raw futures data from multiple exchanges into a unified Excel template?

To normalize raw futures data, semantic field mapping is applied to extract and standardize columns like contract code, commodity name, and closing price from SHFE, DCE, CZCE, and GFEX into a unified Excel template.

What is the best way to handle missing columns and new futures products during data transformation?

Handling missing columns and new futures products requires rule-based semantic conversion that adapts to variable input formats, ensuring robust numeric parsing and generating a missing data log for auditing.

How does semantic field mapping work for standardizing futures contract data?

Semantic field mapping works by applying rule-based logic to identify and extract exchange-specific fields, transforming variable raw input formats into standardized columns like delivery month, open interest, and minimum margin.

Can I use this data normalization approach for newly listed futures contracts across different exchanges?

Yes, this data normalization approach supports newly listed futures contracts by using adaptive semantic rules rather than fixed scripts, allowing it to process format variations across SHFE, DCE, CZCE, and GFEX.

Where are the standardized futures contract outputs and missing data logs saved?

Standardized futures contract outputs and missing data logs are saved directly into the 合约数据(整理后)/ directory, providing unified workbooks per exchange alongside a missing reason summary report.

Why does my futures data transformation fail when raw exchange formats change?

Futures data transformation may fail when raw exchange formats change if using fixed scripts; this approach uses semantic rules to adapt to format variations and outputs a missing data log to diagnose parsing errors.