Loading...
Loading...
Found 9,737 Skills
Analyze business cycle phases (expansion, peak, contraction, trough) and their implications for business strategy and policy response. Use this skill when the user needs to identify the current economic phase, anticipate cyclical turning points, or adapt business strategy to macroeconomic cycles — even if they say 'are we heading into a recession', 'how should we prepare for a downturn', or 'when will the economy recover'.
Build CTR prediction models for estimating ad click-through rates from features. Use this skill when the user needs to predict click probability, build an ad ranking model, or evaluate ad creative performance — even if they say 'predict click rate', 'ad relevance scoring', or 'which ad will get more clicks'.
Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. This includes the Loops HTTP API and official SDKs for server-side contact, contact-property, mailing-list, event, API-key-validation, and transactional-email workflows. Trigger on phrases like "Loops API", "Loops SDK", "send a Loops event from my app", "add a contact to Loops in a webhook", "send a transactional email from backend code", or any time the user wants to integrate Loops into their app, backend, webhook, or automation. Do not trigger for CLI or shell-only requests.
Guides a consultant in designing and activating a niche community strategy for a client — covering Facebook Groups, WhatsApp Communities, LinkedIn Groups, and private forums that serve the brand's audience rather than broadcasting at them. Invoke this skill when a client wants to build a owned community space, shift from page-based broadcasting to community-centred engagement, improve customer retention through belonging, or generate leads through trust networks.
Implement, debug, refactor, migrate, review, or explain Effect TypeScript code. Use when a task touches `effect` or `@effect/*` APIs, especially services, layers, schemas, runtime wiring, platform or CLI packages, Effect testing, or Promise-to-Effect migration.
Turns a free-form project description into PROJECT_MANIFEST.md and SOFTWARE_FACTORY_MANIFEST.md for a 6-agent software factory pipeline. Agent-agnostic: works in Claude Code, Codex CLI, Gemini CLI.
Intercept and debug HTTP traffic from any CLI, service, or script using HTTP Toolkit. Use when you need to inspect LLM API calls, backend requests, auth flows, or debug network-level issues across any language or runtime.
Use this skill when the user wants to read or search their Monologue notes through the Monologue Notes REST API. It covers authentication with the MONOLOGUE_API_KEY environment variable, safe token handling, listing notes, fetching a single note, pagination, filters, and error handling. The API is read-only and should be accessed with direct HTTP requests such as curl or any equivalent REST client.
Integrate InFlow stablecoin payments into any project. Use this skill when the user wants to: accept payments, add a checkout, request a payment, build a payment flow, integrate InFlow, accept USDC/USDT/EURC/PYUSD, set up consumer login via InFlow, register users with InFlow, handle payment webhooks, create spending policies for autonomous agents, build a 0-click headless payment flow, or add InFlow checkout to a marketplace app (note: native multi-recipient splits are not supported by the InFlow API). Also trigger on: 'add inflow', 'inflow payment', 'inflow checkout', 'stablecoin payment', 'crypto payment', 'accept stablecoins', 'pay with usdc', 'inflow webhook', 'inflow login', 'inflow policy'.
Language Server Protocol specialist building unified code intelligence systems through LSP client orchestration and semantic indexing
You are **LSP/Index Engineer**, a specialized systems engineer who orchestrates Language Server Protocol clients and builds unified code intelligence systems. You transform heterogeneous language s...
When translating product details into messaging, climb a 4-rung ladder from Feature → Product Truth → Functional Benefit → Emotional Benefit. Forces every emotional claim to have a credibility chain back to a verifiable feature, beating messaging that's either too technical (specs without meaning) or too floaty (emotion without proof).