Loading...
Loading...
Found 2,771 Skills
Event-driven investment strategy — identify and analyse corporate events (M&A, spinoffs, buybacks, index rebalancing, lockup expiry) that create pricing dislocations. Framework: event identification → sentiment scoring → historical price reaction → position sizing. Uses Longbridge news / filings / calendar data as signal inputs. Triggers: "事件驱动", "并购套利", "指数调整", "解禁套利", "事件策略", "公司事件策略", "事件投资", "套利机会", "事件驅動", "並購套利", "指數調整", "解禁套利", "事件策略", "公司事件策略", "event-driven", "event strategy", "merger arbitrage", "index rebalancing", "lockup expiry", "event investing", "corporate event trading", "special situation", "spinoff", "buyback catalyst".
Resiliency features in Megatron Bridge including fault tolerance, straggler detection, in-process restart, preemption, and re-run state machine.
How to read data from the Sui network. Use when choosing or implementing a data access strategy — queries for on-chain state, indexing pipelines, historical lookups, event subscriptions, cross-chain reads, or off-chain blob storage. Covers the three live Sui APIs (gRPC, GraphQL RPC, deprecated JSON-RPC), the Archival Store, the General-Purpose Indexer, the `sui-indexer-alt` custom indexing framework, and Walrus for off-chain blobs.
Design and operate an advanced AI agent memory system on HelixDB using hybrid graph + vector + BM25 search. Use when building long-term memory, user profiles, document/chunk RAG, recall/remember features, memory extraction, deduplication, consolidation, versioning, updating, forgetting/deletion, categorisation, or connector-backed ingestion. Covers tenant-safe Helix data modeling, modality decision rules, the full write/maintain lifecycle, and the product layers an agent must implement around Helix. TypeScript-first (@helix-db/helix-db); a Rust DSL variant is in EXAMPLES.rust.md.
Use when building AI agent storage workflows on Tigris — forks for isolated dataset copies, workspaces for per-agent buckets with TTL, checkpoints for snapshot/restore, and coordination for event-driven pipelines via bucket webhooks. Triggers on "@tigrisdata/agent-kit", "agent storage", "agent workspace", "agent fork", "isolated agent environment", "checkpoint and restore", "bucket webhook", "multi-agent pipeline"
Use when the user asks to analyze code for test coverage, list what test cases are needed, or review testing strategy — WITHOUT generating actual test code.
Complete guide for building Moldable apps. Use this skill when creating new apps with scaffoldApp, modifying existing apps, implementing workspace-aware storage, integrating with the Moldable desktop via postMessage APIs (moldable:show-in-folder, moldable:set-chat-input, moldable:set-chat-instructions, moldable:save-file), configuring workspaces, managing skills/MCPs, or troubleshooting app issues. Essential for any Moldable app development task.
Apply when deciding where and how a VTEX IO app should store and read data. Covers when to use app settings, configuration apps, Master Data, VBase, VTEX core APIs, or external stores, and how to avoid duplicating sources of truth or abusing configuration stores for operational data. Use for new data flows, caching decisions, refactors, or reviewing suspicious storage and access patterns in VTEX IO apps.
Persist Riverpod notifier state offline with Storage and persist(); riverpod_sqflite, JsonPersist, key, destroyKey, cache duration, testing with in-memory storage. Use when saving state across app restarts or offline. Use this skill when the user asks about offline persistence, persisting state, or Riverpod storage.
Refactor MoonBit code to be idiomatic: shrink public APIs, convert functions to methods, use pattern matching with views, add loop invariants, and ensure test coverage without regressions. Use when updating MoonBit packages or refactoring MoonBit APIs, modules, or tests.
Cloudflare Workers KV global key-value storage. Use for namespaces, caching, TTL, or encountering KV_ERROR, 429 rate limits, consistency issues.
Write or refresh Python test coverage. Use when Codex needs to add coverage, replace stale tests, prefer executable doctest examples in public docstrings, or lock down Python behavior in repos that use `uv`, `pytest`, `nox`, and `mise`.