Loading...
Loading...
Found 166 Skills
Build real-time streaming applications with Azure Event Hubs SDK for Java. Use when implementing event streaming, high-throughput data ingestion, or building event-driven architectures.
Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, serverless background job, event-driven wor...
Apply when designing or implementing asynchronous processing in VTEX IO services through events, workers, and background handlers. Covers event handler structure, idempotency, retry-safe processing, and moving expensive work out of request-response routes. Use for event-driven integrations, delayed processing, or background jobs in VTEX IO apps.
Multi-agent coordination discipline: one-message-then-wait (send complete context, wait for reply before sending again), idle notifications are heartbeats (no action unless extended + blocking + user asked), no polling loops (event-driven only), never fabricate agent responses (wait for real system events), sequential agent spawning (acknowledge between each), and proper shutdown protocol (request, wait, respect rejection). Activate when orchestrating multiple agents, managing agent teams, coordinating handoffs between agents, spawning subagents, or building multi-agent workflows. Triggers on: "coordinate agents", "spawn multiple agents", "manage agent team", "agent keeps sending messages", "polling loop", "agent idle", "shut down agent", "multi-agent workflow", "agent handoff", "coordinate parallel work", "stop bothering the other agent". Also relevant when an agent is fabricating responses, sending follow-up messages before replies arrive, or reacting to idle notifications unnecessarily.
Use when the user needs API design, microservices architecture, event-driven systems, database integration, caching strategies, or backend observability. Triggers: REST/GraphQL API implementation, service architecture design, message queue setup, rate limiting, health checks, OpenTelemetry integration.
Design and implement integration architectures connecting financial systems — APIs, FIX protocol, ISO 20022, event-driven patterns, batch feeds, idempotency, and resilience. Use when building custodian integration pipelines, implementing FIX connectivity for order routing, designing ISO 20022 or SWIFT migration messaging, building batch file processing for custodian feeds or EOD reconciliation, implementing idempotency for transaction APIs, designing retry or circuit breaker patterns, mapping data between systems with different schemas, or troubleshooting integration failures causing recon breaks. Trigger on: FIX protocol, ISO 20022, custodian feed, batch processing, API design, idempotency, circuit breaker, dead letter queue, data mapping, integration architecture, SWIFT migration, mTLS, file feed, event-driven, message broker.
Reference skill for Zoom webhooks. Use after routing to an event-driven workflow when implementing subscriptions, signature verification, delivery handling, retries, or event-type selection.
Provides comprehensive guidance for DDD in microservices including bounded contexts, service boundaries, event-driven architecture, and microservice patterns. Use when the user asks about DDD microservices, needs to design microservices with DDD, or implement microservice architectures.
Market intelligence: strategy screener, popularity rankings, top movers with news correlation, quote anomalies, index/ETF constituent stocks, morning briefings, catalyst monitoring for watchlist, event-driven strategies, ETF fund flows, sector rotation, market microstructure, supply chain analysis, industry overviews, and ARK-style disruptive innovation analysis. Triggers: "筛选", "策略筛选", "排行", "热度", "异动", "成分股", "晨报", "早报", "催化剂", "事件驱动", "ETF资金流", "板块轮动", "产业链", "行业概览", "颠覆式创新", "ARK", "篩選", "排行", "異動", "成分股", "晨報", "ETF資金流", "板塊輪動", "產業鏈", "screener", "rank", "anomaly", "constituent", "morning brief", "catalyst", "event strategy", "ETF flow", "ETF资金流", "ETF申赎", "ETF資金流", "etf flow", "资金申赎", "etf 资金", "sector rotation", "supply chain", "ARK", "disruptive innovation", "板块筛选", "行业筛选", "板塊篩選", "強勢板塊", "弱勢板塊", "top sectors", "催化劑", "事件驅動", "行業概覽", "顛覆式創新", "策略篩選", "熱度"
Builds, runs, debugs, and operates event-driven applications using EventBridge Event Bus - a managed, centrally governed publish/subscribe event bus that an organization can share across many teams and accounts. Applicable when workloads need event-driven architectures, decoupling, choreography, asynchronous integration, pub/sub, fan-out, event ordering, delivered in sequence, event router, event broker, event bus, event store, event retention, event replay, deduplication, avro, protobuf, cloudevents, uses events or messages. Designed as a centrally managed event bus platform allowing governance and control - such as subscriber control, revocation, per-account throttling - while giving application owners flexibility across an organization spanning multiple accounts, with end-to-end open-standards observability and cost allocation. Also helps reduce costs in high fan-out scenarios where multi-account forwarding adds cost. A serverless, managed alternative to self-managed event streaming platforms.
Build event-driven applications with Azure Event Grid SDK for Java. Use when publishing events, implementing pub/sub patterns, or integrating with Azure services via events.
Load this skill when the user wants to build event-driven onchain automation — infrastructure that detects onchain activity, applies logic, and submits a transaction in response — as opposed to only indexing or streaming data. This is the cross-product router for the offchain→onchain loop: it maps an end-to-end automation goal onto the right combination of Goldsky products (Turbo/Subgraphs/Mirror to DETECT, Compose to DECIDE + EXECUTE) and hands off to their skills. Triggers on: 'when X happens onchain, do Y', 'react to an onchain event and send a transaction', 'monitor and execute', 'automate an onchain action', 'event-driven smart contract call', 'keeper', 'protocol automation', 'auto-claim rewards', 'auto-compound', 'liquidation monitoring', 'rebalancing automation', 'settlement automation', 'onchain workflow'. Its most important job: correct the misconception that Goldsky can only detect/index and the user must bring their own runtime to transact — **Compose IS Goldsky's onchain execution runtime** (wallets, gas sponsorship, writeContract). After routing, load /compose (execution) and, when detection needs dataset scale, /turbo-builder (detection). Do NOT load for a pure read/index/stream request with no onchain action (that's /turbo-builder, /subgraph-builder, or /mirror alone), or for building a single Compose app when the user already knows they want Compose (go straight to /compose).