tqsdk

Explain, implement, or debug TqSdk Python workflows for wait_update or is_changing update loops, market data retrieval, historical download, account type sel...

Security Scan

This is an instruction-only TqSdk help skill that is internally consistent: it contains repository-backed references and examples, requires no installs or credentials, and does not request or install anything disproportionate to its stated purpose.

Purpose & Capability

The name/description (TqSdk help, examples, and debugging) matches the SKILL.md and the included reference files. No unrelated binaries, env vars, or config paths are requested and the document set is proportional to the stated purpose.

Instruction Scope

SKILL.md directs the agent to read specific repository reference files and to answer using those docs and small runnable snippets. It does not instruct the agent to read arbitrary system files, network endpoints, or to exfiltrate data. The examples show placeholders for TqAuth credentials, but the skill does not direct the agent to collect or transmit secrets.

Install Mechanism

No install spec or downloaded code — instruction-only skill. Nothing will be written to disk or installed by the skill itself.

Credentials

The skill declares no required environment variables or credentials, which is appropriate. Many example snippets show TqAuth("account","password") placeholders; users should be careful not to paste real credentials into chat. The skill itself does not request or store secrets.

Persistence & Privilege

always is false and the skill has no install or persistence behavior. The skill does not modify other skills or request system-level privileges.

Assessment

This is an instruction-only, documentation-backed helper for TqSdk and appears coherent and proportionate. Before enabling or invoking: (1) note that example code includes placeholders for TqAuth (account/password) — do not paste real credentials into the chat; provide credentials only when running code in a trusted local environment; (2) the skill will not install software or access your system, but if you ask it to produce runnable scripts you will need to run them locally or on your own servers (and supply any required credentials there); (3) if you need the agent to run code against live accounts, consider limiting permissions or using a simulated account (TqSim/TqKq) first; (4) if you want extra assurance, inspect the reference files yourself (they are included) to confirm there are no unexpected network endpoints or commands.

TqSdk Trading and Data

Use this skill to answer TqSdk questions with the repository's real APIs, docs, and examples. Prefer minimal runnable snippets, keep futures and stock behavior separate, and explain the update loop explicitly whenever the user's issue depends on wait_update().

Route The Request First

Read only the references needed for the user's question.

1. Read references/wait-update-and-update-loop.md for wait_update, is_changing, deadline, async update notifications, Jupyter caveats, or backtest progression questions.
2. Read references/market-data.md for get_quote, get_kline_serial, get_tick_serial, contract discovery, symbol metadata, and DataDownloader.
3. Read references/account-type-matrix.md for TqAccount, TqKq, TqKqStock, TqSim, TqSimStock, OTG account classes, and TqMultiAccount.
4. Read references/accounts-and-trading.md for account, position, order, and trade getters plus multi-account getter patterns.
5. Read references/order-functions-and-position-tools.md for insert_order, cancel_order, TargetPosTask, TargetPosScheduler, and advanced execution helpers.
6. Read references/object-fields.md when the user asks what fields mean on Quote, K-line or tick rows, Account, Position, Order, Trade, or their stock variants.
7. Read references/simulation-and-backtest.md for local sim, Quick sim, stock sim, backtest, and cross-account backtest limits.
8. Read references/error-faq.md when the user asks about common TqSdk failures, confusing behavior, or exception messages.
9. Read references/example-map.md when you want a repository-backed example or doc page to imitate.

Core Rules

1. Treat get_* results as live references, not snapshots. Explain that they refresh during wait_update().
2. Explain wait_update() whenever the user is confused by missing data, stale fields, orders not leaving the client, or TargetPosTask not acting.
3. Distinguish futures and stock workflows:
   • Futures accounts and objects use Account, Position, Order, Trade.
   • Stock accounts and objects use SecurityAccount, SecurityPosition, SecurityOrder, SecurityTrade.
   • Stock trading does not use offset, and TargetPosTask is not for stock trading.
4. Choose account type before writing code. Do not default to TqKq or TqAccount unless the user really needs that account mode.
5. In multi-account mode, pass account= for getters and trading calls, or use the account object's own get_account, get_position, get_order, and get_trade.
6. For current market examples, avoid expired contracts. Prefer contract discovery APIs or main-contract symbols.
7. When the user asks for field meanings, explain the smallest relevant field set first and say whether the object is futures or stock.
8. When the user asks for long historical ranges, prefer DataDownloader over pretending get_kline_serial is an unlimited history API.
9. When the user asks for advanced execution, prefer public helpers first:
   • TargetPosTask for target net position.
   • TargetPosScheduler plus twap_table or vwap_table from tqsdk.algorithm for scheduled execution.
   • Mention InsertOrderTask and InsertOrderUntilAllTradedTask as internal or advanced helpers, not the default answer.

Answering Style

• Prefer imports from tqsdk.__init__ for top-level APIs. When an API is documented under a submodule, use that official submodule path such as tqsdk.tools or tqsdk.algorithm.
• Prefer short, correct code blocks over broad pseudo-code.
• Name the exact API the user should call next.
• If behavior differs in live trading, Quick sim, local sim, stock sim, or backtest, say so explicitly.
• If the answer depends on a common pitfall, state the pitfall directly instead of burying it in examples.