Total 55,561 skills
Showing 12 of 55561 skills
Use this skill whenever writing frontend code that talks to a backend for database queries, authentication, file uploads, AI features, real-time messaging, or edge function calls — especially if the project uses InsForge or @insforge/sdk. Trigger on any of these contexts: querying/inserting/updating/deleting database rows from frontend code, adding login/signup/OAuth/password-reset flows, uploading or downloading files to storage, invoking serverless functions, calling AI chat completions or image generation, subscribing to real-time WebSocket channels, or writing RLS policies. If the user asks for these features generically (e.g., "add auth to my React app", "fetch data from my database", "upload files") and you're unsure whether they use InsForge, consult this skill and ask. For backend infrastructure (creating tables via SQL, deploying functions, CLI commands), use insforge-cli instead.
This skill should be used when the user asks to 'swap tokens', 'trade ETH for USDC', 'buy tokens', 'sell tokens', 'exchange crypto', 'convert tokens', 'swap SOL for USDC', 'get a swap quote', 'execute a trade', 'find the best swap route', 'cheapest way to swap', 'optimal swap', 'compare swap rates', or mentions swapping, trading, buying, selling, or exchanging tokens on Solana, Ethereum, Base, BSC, Polygon, Arbitrum, or any of 20+ supported chains. Aggregates liquidity from 500+ DEX sources for optimal routing and price. Supports slippage control, price impact protection, and cross-DEX route optimization. Do NOT use for general programming questions about swap code, or for analytical questions about historical swap volume.
Use the `googlemail-client` mops package whenever the user asks the canister to send email, compose a draft, list or read Gmail messages, or fetch the authenticated user's Gmail profile. The package wraps the Gmail REST API v1 at `https://gmail.googleapis.com` via outbound HTTPS calls.
ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
Extract and interpret embedded metadata from files. Use when analyzing EXIF/GPS data in photos, checking a document's author or software, reading camera model or timestamps, or investigating file provenance from images, PDFs, or Office docs.
Deep-dive a social media profile — map the account, its network and content, extract location and pattern-of-life signals, and pivot to other identities.
Enumerate a username or handle across hundreds of platforms and pivot from matched accounts to real-identity, contact, and content selectors.
End-to-end workflow to establish where and when a photo or video was captured and whether it is authentic — evidentiary handling, metadata extraction, reverse image search for provenance, visual geolocation, chronolocation from shadows, and manipulation checks, ending in a location finding with a stated confidence radius.
Trace cryptocurrency addresses and transactions on public blockchains. Use when following a Bitcoin or Ethereum wallet, investigating crypto payments, clustering addresses, identifying exchanges or mixers, or attributing on-chain activity.
Investigate a phone number — normalize and classify it, identify carrier and line type, and pivot to owner identity, messaging apps, and linked accounts.
Corporate due-diligence workflow — resolve a brand or website to its registered legal entity, map group structure and beneficial ownership, profile officers and directors, enumerate the digital estate, and screen litigation, insolvency, procurement, sanctions, PEP, and adverse media. Use for vendor and counterparty risk, KYC/KYB, M&A diligence, investor checks, or shell-company assessment.
Passive reconnaissance workflow for a domain, website, or IP — maps DNS, subdomains, infrastructure, tech stack, history, and ownership without touching the target.