qmt-bridge-event-calendar
通过 QMT Bridge 查询交易日历、节假日、交易时段,并支持用户自定义的财报/持仓事件检查规程。 在用户提到是否交易日、节假日、交易时间、财报日、日历时使用。只读。
38,472 Skills
搜索范围为本次公开目录;榜单和数量均为记录时的数据。
通过 QMT Bridge 查询交易日历、节假日、交易时段,并支持用户自定义的财报/持仓事件检查规程。 在用户提到是否交易日、节假日、交易时间、财报日、日历时使用。只读。
通过 QMT Bridge 对自选标的做行情快照:涨跌幅、现价、指数环境、交易日校验。 在用户提到看盘、自选监控、盘前检查、行情快照、大盘环境时使用。只读,不下单。
通过 QMT Bridge 做下单前执行预览:价格类型选择、涨跌停检查、分批建议。 在用户提到怎么下单、限价还是市价、分批、滑点、执行方案时使用。默认预览,提交须确认。
Set up the Fallow app in Codex after the plugin is installed: check the fallow installation, choose the default analysis scope, run the first analysis, and show the user where the dashboard, the Code Health tab, @Fallow mentions and the config editor are. Use when the user choose
Review AI-generated or human-written code changes with fallow's graph-grounded review brief. Subtracts deterministic concerns (unused code, complexity, duplication, styling) from the loop, ranks what to look at by blast radius and risk, and surfaces the few consequential structur
Set up or modernize code-quality tooling for JavaScript and TypeScript projects. Use when creating a project, adding code-health or CI quality checks, making a repository agent-ready, or consolidating dead-code, duplication, architecture, dependency, and changed-code analysis. Do
Sync the Logic-Lens working-copy skills/ into the installed plugin cache so content-evals test the EDITED skill, not the last published one. ALWAYS run this after editing any skills/**/SKILL.md or guide/_shared file and BEFORE running content-evals — otherwise the eval silently g
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating spec/PRD asked for?). Use when the user wants to review a bran
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, saved to `.plan/`.
目录记录日期:2026-11-21