feature-f12-open-limitup-block

Blocks re-entry when a stock opens at limit-up and was sold earlier same day.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/13g7895123/littile-bao --skill feature-f12-open-limitup-block
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-f12-open-limitup-block
Source: https://github.com/13g7895123/littile-bao/tree/main/.github/skills/feature-f12-open-limitup-block
Command: npx skills add https://github.com/13g7895123/littile-bao --skill feature-f12-open-limitup-block

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky re-entry by blocking trades when a stock opens at the limit-up price and has already been sold once by the system that same day.

Core Features & Use Cases

  • F12 Entry Block: When open_limit_up is true and sold_today is true, it stops the entry logic from placing another order for the same scenario.
  • Main Switch Control: Uses f12_enabled (default True) to turn the behavior on or off.
  • Boundary Safety Clarity: It only strengthens the protection for open-limit-up cases; ordinary limit-up re-entry is handled separately by entry_blocked, not by this rule.

Use case: If a stock opens at涨停 and the system already sold it earlier that day, the Skill blocks any further attempt to buy it again on that same open-limit-up trigger.

Quick Start

Enable f12_enabled (default True) in the configuration referenced by the engine so that open-limit-up entries are blocked once sold_today is set.

Frequently Asked Questions about feature-f12-open-limitup-block

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

FAQPage Schema
How do I block re-entry on a stock that opens at limit-up after selling it?

To block re-entry on an open-limit-up stock after selling, enable the f12_enabled configuration flag. The engine evaluates open_limit_up and sold_today states during the _tick() flow to prevent placing another buy order for that same day.

What is the difference between open-limit-up entry blocking and ordinary limit-up re-entry?

Open-limit-up entry blocking specifically prevents buying a stock that triggered open_limit_up after a completed sell_today action. Ordinary limit-up re-entry scenarios are handled separately by the entry_blocked state, not by this F12 rule.

How do I disable the open-limit-up sell tracking protection?

To disable the open-limit-up sell tracking protection, set the f12_enabled configuration value to False. This turns off the F12 rule, allowing the engine entry logic to place orders even if sold_today and open_limit_up conditions are true.

When should I use open-limit-up entry blocking in my trading strategy?

Use open-limit-up entry blocking when your trading strategy requires strict risk control against buying a stock back on the same day. It applies during engine entry decisions to stop orders if a stock opens at limit-up and was already sold.

Does the F12 entry block work without universe scanning data?

No, the F12 entry block relies on open_limit_up data from universe scanning and sold_today from completed sell actions. Without these inputs evaluated during the _tick() flow, the rule cannot trigger to prevent the order placement.

Why does my trading system keep buying a stock sold at open limit-up?

Your trading system keeps re-entering because the f12_enabled flag is likely False or missing. Ensure your configuration sets f12_enabled to True so the engine checks open_limit_up and sold_today to block the order.