Loading...
Loading...
Found 305 Skills
Complete Hyperliquid playbook — perpetuals and spot trading, margin/leverage, TWAP, real-time WebSocket data, and historical candles. Use for any Hyperliquid task. Trading triggers: place perp/spot orders (Gtc/Ioc/Alo), market-like fills, take-profit/stop-loss grouping, modify or cancel orders, batch cancels, TWAP orders (place/track fills/terminate), change leverage (cross vs isolated), adjust isolated margin, transfer USDC between spot and perp accounts (usd_class_transfer), get the EVM deposit address to fund Hyperliquid. Data triggers: read account summary (perp margin, positions, liquidation price, unrealized PnL), spot balances, portfolio, open orders, historical orders, single order status, fills (latest or by time window), funding history, rate limits, market metas (perp + spot, szDecimals), perp-only metas, spot-only metas, mid prices for all coins, L2 orderbook per coin, spot token details, allDexsAssetCtxs snapshot (funding/OI/mark prices across assets). Real-time WebSocket: wss://api.hyperliquid.xyz/ws with channels allMids, allDexsAssetCtxs (backend manages a shared subscription — agent can subscribe/unsubscribe and read the cached snapshot), l2Book, trades, candle, orderUpdates, userFills, userFundings. Historical OHLCV candles via direct POST https://api.hyperliquid.xyz/info {type: 'candleSnapshot'} — supports 1m/3m/5m/15m/30m/1h/2h/4h/8h/12h/1d/3d/1w/1M intervals up to 5000 candles. Covers all routes under /agent/trading/* (market/metas|mids|perp-metas|spot-metas|l2-book|token|all-dexs-asset-ctxs, deposit-address, account, account/spot, portfolio, rate-limit, orders, orders/details, orders/history, orders/:oid/status, twap, twap/fills, twap/:id, fills, fills/by-time, funding, leverage, margin, transfer). Triggers on mentions of Hyperliquid, "HL", perp, perpetual, funding rate, TWAP, isolated margin, cross margin, "deposit to Hyperliquid", "HIP-3", "HLP", or "HL vault". Prerequisite: openfin-setup.
Reference and consulting skill for OpenClaw — a messaging gateway that connects AI agents to multiple communication platforms (Telegram, Discord, Slack, WhatsApp, iMessage, and more). Use when working with OpenClaw configuration, channels, Gateway setup, skills, cron jobs, MCP servers, memory, OAuth, or troubleshooting. Also use when the user asks how to implement a use case on their OpenClaw bot (daily morning brief, research workflows, competitive radar, decision playbook), how to add a new channel, or how to connect the CodeAlive context engine. Triggers on requests like "configure openclaw", "add Discord to my bot", "set up morning brief", "gateway not starting", "connect CodeAlive search", "OAuth re-auth", or any close paraphrase. Companion of install-openclaw-to-yc — install both together.
Manage Oodle notifiers, notification policies, and muting rules — routing alerts to the right channels and silencing during maintenance.
Architect Unity 6 data and decoupling with ScriptableObjects: config/data assets, shared runtime variables, event channels, and runtime sets/registries. Use when designing data-driven systems, replacing singletons/managers, creating .asset data with CreateAssetMenu, or when the user mentions ScriptableObject, SO architecture, or data assets.
Test Supabase Realtime WebSocket channels for unauthorized subscriptions and data exposure.
Expert in building and managing thriving Discord communities. Covers server architecture, role systems, bot ecosystems, engagement features, and moderation at scale. Understands Discord-specific culture and patterns. Use when "discord server, discord community, discord setup, discord bots, discord moderation, discord channels, " mentioned.
React vendoring and react-server layer boundaries. Use when editing entry-base.ts, $$compiled.internal.d.ts, compiled/react* packages, or taskfile.js copy_vendor_react. Covers the entry-base.ts boundary (all react-server-dom-webpack/* imports must go through it), vendored React channels, type declarations, Turbopack remap to react-server-dom-turbopack, ComponentMod access patterns, and ESLint suppression for guarded requires.
Complete Lightning Network lifecycle. Audits channels, routing, invoices. Plans capacity, executes rebalancing, verifies payments. Every run does all. Auto-invoke when: files contain lightning/lnd/bolt11/invoice, imports lightning packages, references LND_* env vars, channel handlers modified.
When the user wants to plan, create, or repurpose visual content (images, infographics, social post images) across channels. Also use when the user mentions "content images," "social media images," "infographic," "visual content," "post image," "image specs," "visual repurposing," "content visuals," or "image for social post."
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company."
Use Huly platform APIs for swarm communication across tasks, channels, and documents.
Comprehensive growth strategy expertise combining SEO/SMO/CRO implementation, marketplace and network effects frameworks (Andrew Chen), growth loops methodology (Brian Balfour/Reforge), and Silicon Valley growth thinking. Use when building growth strategy, designing growth loops, improving SEO/SMO/CRO, planning acquisition channels, building network effects, or scaling product-led growth. Growth is not marketing — it's systematic application of product, engineering, and data.