Loading...
Loading...
Found 1,376 Skills
Discovers business domains in a Swift codebase by tracing what users can DO — not by reading folder names or architecture docs. Maps each domain's vertical slice (Types → Config → Repo → Service → Runtime → UI), identifies providers (external SDK bridges), and separates cross-cutting concerns. Produces a domain map that drives all downstream decisions: folder structure, SPM targets, enforcement specs, migration plans. Use this skill whenever the user wants to understand their codebase domains, find what's cross-cutting vs domain-specific, restructure a Swift project, figure out where code belongs, or map a product's capabilities to architectural boundaries. Triggers on "what are my domains", "where does this belong", "map this codebase", "what's cross-cutting", "organize this project", "is this a domain or infra", "restructure this", "architecture review", or any request to understand the business domain structure of a Swift codebase.
Uses the TweetSmash REST API to fetch bookmarks, inspect labels, and add or remove labels from saved tweets. Use when integrating TweetSmash into scripts, agents, workflows, cron jobs, or internal tools that need bookmark retrieval, filtering, pagination, or label management. Do not use for direct browser automation inside TweetSmash, unrelated X or Twitter APIs, or tasks that only need product marketing copy.
Extract comprehensive, production-ready JSON design specifications from visual inputs using a 7-pass serial architecture with cross-validation. Use when converting screenshots, mockups, or design exports into structured design tokens, component specs, accessibility analysis, and developer handoff artifacts.
Apply when reviewing or designing security-sensitive boundaries in VTEX IO apps. Covers public versus private exposure, trust assumptions at route and integration boundaries, sensitive data handling, validating what crosses the app boundary, and avoiding leakage across accounts, workspaces, users, or integrations. Use for route hardening, data exposure review, or evaluating whether a service boundary is too permissive.
Meltwater platform help — media intelligence, social listening, media relations (journalist database + outreach), influencer marketing, social media management, consumer intelligence, Mira AI, API, and integrations. Use when Meltwater Explore searches return noisy results, media monitoring is missing coverage, journalist contacts are outdated, influencer campaigns aren't tracking properly, social publishing isn't scheduling, Meltwater API or Mira AI isn't returning expected data, or CRM/BI integrations aren't syncing. Do NOT use for cross-platform social listening strategy (use /sales-social-listening), cross-platform media relations strategy (use /sales-media-relations), cross-platform influencer marketing strategy (use /sales-influencer-marketing), or email deliverability (use /sales-deliverability).
BrandJet AI platform help — multi-channel outreach sequences, unified inbox, brand monitoring, AI visibility tracking, lead discovery, social listening, email warmup, Artemis AI agent, and integrations. Use when outreach sequences aren't getting replies, brand mentions going unnoticed, multi-channel sequences feel disjointed, unified inbox is overwhelming, or AI visibility scores are dropping. Do NOT use for designing cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), social listening strategy (use /sales-social-listening), or enriching contacts (use /sales-enrich).
Arrfounder platform help — founder revenue directory by @Folyd (2024) that auto-extracts MRR/ARR + products from Twitter/X bios via AI, lists 1000+ founders on sortable leaderboards (ARR / followers / products / recently added), free Airtable submission with 24-48h manual approval, auto-syncs within hours of bio changes. Social-proof verification only (no Stripe / Lemon Squeezy / Polar API integration) — built for peer discovery and community browsing, not acquisition-grade proof. Use when getting listed on Arrfounder, writing a Twitter/X bio that passes the MRR/ARR extractor, fixing a profile that didn't get approved or stopped updating after a bio edit, deciding Arrfounder vs TrustMRR or StartuPage for verified-revenue display, benchmarking against peers in the $1K-$10M+ ARR tiers, or using Arrfounder as a comp-check tool before pricing a sale or fundraise. Do NOT use for selling/buying a project or cross-marketplace valuation (use /sales-side-project-valuation).
Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty. Use when iterating toward product/market fit, designing MVPs, deciding whether to pivot or persevere, setting up actionable metrics, or accelerating the Build-Measure-Learn loop. Triggers include 'how do we test this idea fast', 'what should our MVP look like', 'our metrics look good but we're not growing', 'should we pivot', 'we're building features no one uses', 'how do we measure validated learning', 'vanity metrics vs real metrics', 'how to do innovation accounting'. NOT for companies with proven product/market fit scaling a known playbook (use Crossing the Chasm), not for determining Market Type (use Four Steps), not for sales methodology (use SPIN Selling), not for pricing strategy (use Monetizing Innovation).
This skill should be used when interacting with Google Workspace services via the gws CLI — Gmail (search, triage, send, labels, filters, drafts), Calendar (agenda, events, Meet conferencing), Drive (upload, list, share, download), Sheets (read, append), Docs, Tasks, Chat (send), People/Contacts, and cross-service workflows (standup, meeting prep, weekly digest, email-to-task). Triggers on queries like "check my email", "search Gmail", "send email", "calendar agenda", "create calendar event", "upload to Drive", "read spreadsheet", "create a task", "triage inbox", "find contact", "post to Chat".
Read-only observability dashboard plugin for Hermes Agent — journeys, crossings, guideposts, and reports.
Error-to-fix playbook for every known failure mode on the OpenFinance backend — Polymarket, Relay, Hyperliquid, Privy delegation, and Solana RPC issues. Use this the moment a call fails, returns an unexpected status, or behaves inconsistently with on-chain state. Triggers on ANY of these error signatures verbatim or in paraphrase. Polymarket: "allowance: 0 but on-chain shows max", "CLOB reports allowance 0", "approvals confirmed but order rejected", "404 upstream" on market orders, "tick size" rejection, "order size below minimum", USDC.e vs pUSD vs native USDC confusion, V1 vs V2 exchange confusion. Relay: "InstructionFallbackNotFound", "Custom:101", "Custom:6000", "AnchorError", "Blockhash not found", "TransactionExpired", "No valid authorization signatures were provided", "Solana wallet is not delegated to the app", 412 delegation errors, quote succeeded but execute failed, stuck funds on Solana, stuck funds cross-chain, topupGas forced off. Hyperliquid: "Insufficient perp account value", "price out of bounds", WebSocket stale data, spot vs perp balance confusion. General: any "why is X failing", "why does on-chain and API state disagree", "what does this error mean". Read this BEFORE assuming a bug in the MCP or backend — most of these errors are already catalogued with known fixes.
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.