Loading...
Loading...
Found 770 Skills
Mutating operations on the user's Longbridge recurring-investment (DCA) plans — list (read-only), create a plan, update / pause / resume / stop a plan, view trade history, check eligibility. Requires longbridge login WITH TRADE SCOPE because every plan automatically commits real money on a schedule. Every mutation requires a two-step preview + confirm protocol, and `create` requires the user to read back amount / frequency / symbol / start date / end date before confirming. Use only when the user gives a clear imperative ("create a monthly DCA on AAPL for 500 USD", "停止定投 700.HK"); ambiguous prompts ("帮我看看定投") must be rejected with a "please be specific" reply rather than triggered. Triggers: "创建定投", "新建定投计划", "设置定投", "暂停定投", "停止定投", "恢复定投", "修改定投", "建立定投", "建立定投計劃", "設置定投", "暫停定投", "停止定投", "恢復定投", "修改定投", "create DCA", "create recurring investment", "set up DCA plan", "pause DCA", "stop DCA plan", "resume DCA", "monthly DCA on X", "weekly recurring buy".
Guides product support specialist work—customer tickets about how the product works, configuration, permissions, workflows, and expected behavior; empathetic replies, triage and routing, macro and KB guidance, feature-request capture, and escalation to technical support or product when needed. Use when answering "how do I…" questions, clarifying plan limits, drafting support responses, deciding bug vs education vs config issue, or documenting feedback—not for deep log/API debugging and engineering repro (support-engineer), billing/dunning programs (customer-ops-specialist), exec/VIP escalation programs (community-executive-escalations-program-manager), or public API reference authoring (tech-writer-researcher), or structured developer training programs (developer-education-lead).
Wire the Prisma Next runtime — `db.ts` setup using `postgres<Contract>(...)` from `@prisma-next/postgres/runtime`, middleware composition (telemetry from `@prisma-next/middleware-telemetry`; lints and budgets), `DATABASE_URL` config, per-environment branching, switching between Postgres and Mongo façades. Use for db.ts, postgres(), mongo(), middleware, telemetry, lints, budgets, DATABASE_URL, .env, connection pool, poolOptions, dev vs prod config, transactions, db.transaction, read replicas, multi-database, script won't exit, hangs, close connection, db.end, db.close, pool.end, [Symbol.asyncDispose], await using.
Audit and reduce JavaScript package dependency footprint across npm, pnpm, Yarn, and Bun projects. Use when asked to remove unused dependencies, deduplicate workspace dependency versions, lockfiles or node_modules, analyze direct dependencies' transitive lockfile closure, find low-risk upgrades that reduce dependency trees, inline trivial dependencies, or apply e18e dependency replacement recommendations.
Apply CUDA Graphs to PyTorch workloads — API selection (torch.compile, PyTorch make_graphed_callables, TE make_graphed_callables, MCore CudaGraphManager, FullCudaGraphWrapper, manual torch.cuda.graph), code compatibility, capture workflows, dynamic pattern handling, and troubleshooting. Triggers: CUDA graph, torch.cuda.graph, make_graphed_callables, reduce-overhead, graph capture, graph replay, kernel launch overhead, CudaGraphManager, FullCudaGraphWrapper, full-iteration graph, stream capture.
Find sites ranking for target keywords, score every prospect with Ahrefs domain authority and page-level traffic, identify the strongest pitch angle per row ("links to competitor", "mentions brand without linking", "top-3 SERP", "resource page", "outdated content"), generate brand-voice-matched outreach emails using an outreach-type-aware template (unlinked-mention claim, competitor-link replacement, resource-page inclusion, outdated-content replacement, topical niche-edit), and propose a concrete in-article link placement as three artifacts — the verbatim source sentence, the same sentence rewritten with the link spliced in, or a fully-drafted new insertion if no natural fit exists. Use when user asks to find link building opportunities, prospect link partners, recover unlinked brand mentions, replace competitor links, build a tiered outreach list, or run cold email outreach for SEO link building.
Debug Python: pdb REPL + debugpy remote (DAP).
Use when users need Rust quantitative SDK or TQSDK Rust capabilities: real-time market data/quote/market depth/K-line/tick, product/contract list, main continuous contract/continuous contract, option chain, contract specification, metadata/direct query, historical data download/cache/CSV/Greeks, trading account/order placement/order cancellation/order status, TargetPosTask/risk control/multi-account/strategy execution, low-latency trading desk, stream/fan-out, replay/backtest/live-sim-replay; also applicable when agents need real-time or historical quantitative data, transaction execution substrate, or trading desk capabilities, even if TQSDK is not explicitly mentioned.
Migrate Kotlin (and Java) code from kotlinx.collections.immutable 0.3.x / 0.4.x to the latest 0.5.x. The 0.5.x line renames every copy-returning method on PersistentList / PersistentMap / PersistentSet / PersistentCollection to a participial form per KEEP-0459 (add→adding, removeAt→removingAt, set→replacingAt, put→putting, clear→cleared, …) and deprecates the old names (WARNING, with ReplaceWith). Driven by the compiler: bump the version, recompile, and apply the rename each deprecation warning names. Use when the user mentions kotlinx.collections.immutable 0.5.x, PersistentList migration, "Use adding() instead", KEEP-0459, or sees deprecation warnings from kotlinx.collections.immutable.
Ultra-compressed replies that cut ~75% of tokens by dropping filler, articles, and pleasantries while keeping full technical accuracy. User-invoked only.
Modernizes UIKit apps for multi-window environments by replacing legacy shared-state APIs with context-appropriate modern alternatives. This includes references to mainScreen, interfaceOrientation, application and scene lifecycle, as well as safe area inset updates.
Apply a structured migration workflow from native mini-program projects to weapp-vite and wevu. Use when converting Page/Component code to Vue SFC, replacing setData-heavy state updates with ref/reactive, migrating properties/observers/triggerEvent contracts, introducing platform guards, and building migration-focused e2e validation and rollback checkpoints.