Loading...
Loading...
Found 12,159 Skills
Use when the user asks to "grow my email list", "design a lead magnet / signup incentive", "set up double opt-in", or "plan a referral / recommendation loop"; produces a list-growth plan — acquisition channels, lead-magnet / incentive concepts, a compliant double-opt-in capture-flow spec, referral-loop mechanics, and subscriber-growth / cost-per-opt-in targets (labeled Estimated) — that feeds SEND-S (consent quality captured at acquisition) and SEND-N (lifecycle entry). Not for the signup page/popup UX itself — use landing-optimizer; not for recording the opt-in — use consent-registry; not for the confirmation-email copy — use email-creative-builder. 邮件列表增长/lead magnet/双重确认/推荐环
This skill should be used when the user asks to "animate this diagram", "build a flowchart that reveals step by step", "animate an architecture/sequence diagram", "make a chart animate in", "grow the bars / draw the line / count up the number", "show data flowing along a connector", or "turn a static diagram into a guided reveal". Covers SVG, Framer Motion, D3, and Remotion.
BOM (Bill of Materials) management for electronics projects — the workflow skill that coordinates DigiKey, Mouser, LCSC, element14, JLCPCB, PCBWay, and KiCad skills around a unified BOM lifecycle. Create, update, and maintain BOMs with part numbers, costs, quantities stored as KiCad symbol properties. ALWAYS trigger this skill for any task involving component sourcing, pricing, ordering, distributor searches, BOM export, or fabrication preparation — even if the user names a specific distributor or fab house (e.g. "search DigiKey for...", "generate JLCPCB BOM", "order from Mouser"). This skill analyzes the schematic for sourcing gaps, recommends which distributor/fab skills to call for each gap, and writes results back as symbol properties — the agent (or user) performs the actual searches via the called skills. Also trigger on phrases like "what parts do I need", "order components", "how much will this cost", "export for JLCPCB", "find parts for this board", "compare pricing", or "check stock".
How to use KubeSense MCP tools to query logs, traces, and metrics from Kubernetes clusters. Covers tool selection, the discovery-first workflow, and links to datasource-specific skills.
Embed a Factorial Code process's input-parameter form on a webpage — the three embed methods (data attributes, Fcode.initForm, the FcodeForm React component), version pinning to the stable alias, access restriction (authMode), driving behavior from the process return value, styling and themes (including the f0 theme inside Factorial), multi-step flows, pre-filling current values, and file uploads. Use when embedding, configuring, styling, restricting, version-pinning, pre-filling, or wiring up a Factorial Code (fcode) form.
Use this skill when managing the Android product catalog through the Play Console and the RevenueCat dashboard. Covers the two sided catalog flow (create in Play Console, import or map in RevenueCat), entitlement and offering maintenance, and why you do not call the Google Play Developer API directly.
Use when designing, reviewing, or decluttering a functional product, app, dashboard, or tool screen on any platform. Focal is the screen-local structure-and-attention lens—it decides what belongs, what waits, and what wins attention through Information Architecture, Progressive Disclosure, and Visual Hierarchy. Its methodology is One Screen, One Clear Intent—not one action per screen. It classifies task, hub, and exploration registers, chooses the matching action model, supports inherent binary-choice or dual-mode sets, and adjusts density for expertise. Triggers on clutter, "too much on screen", "simplify this screen", "what's the primary action", "too many choices", choice overload, manual selection, input parsing, contextual information, "show the consequence", one screen one purpose, one clear intent, IA, dashboard, admin, or onboarding/settings. Not for multi-screen flows or navigation (use Compass), visual styling, motion, research, code, marketing/landing pages, backend, or non-UI work.
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
Choose default fal.ai endpoint IDs for genmedia production skills. Use this with commercial, marketing, ugc, character-design, cinematography, storytelling, and workflow when the user has not named a specific model.
Create and export technical, product, architecture, and process illustrations in 27 formats—including architecture, IT current-state, flowchart, sequence, state machine, ER, timeline, swimlane, quadrant, radar, loop, nested, tree, org chart, layers, venn, pyramid, bar, line, Gantt, scatter, high-level, process, medallion, data flow, DP integration, and DP security matrix—as standalone HTML with inline SVG plus optional SVG/PNG/PDF exports. Use for diagram generation, architecture diagrams, process flows, workflow maps, visual variants, project-level light/dark theme and font initialization, brand onboarding, and diagram export. Incorporates the complete former architecture-diagram and process-flow-diagram skills as first-class technical-color families, alongside editorial light/dark/full/hand/terminal/consultant treatments and built-in Copy/PNG/PDF controls.
Find the perfect gaming monitor on Newegg by asking the user about their needs and returning the top matching monitors with parsed specs (size, resolution, refresh rate, panel type, response time) and direct purchase links. Use this skill whenever users want help choosing or finding a gaming monitor — even if they don't mention Newegg by name. Always trigger on phrases like: "help me find a gaming monitor", "what monitor should I buy for gaming", "recommend a 144Hz/240Hz monitor", "best monitor for FPS games", "I need a monitor under $X", "OLED gaming monitor recommendation", "curved ultrawide monitor for gaming", "我想买个电竞显示器", "推荐一个游戏显示器", "帮我找显示器", "144Hz显示器推荐", or any question about choosing or comparing gaming monitors for purchase. This skill handles the full flow: gathering requirements → searching Newegg → parsing specs → showing ranked results with clickable buy links.
Stand up (or extend) an operator-only in-app scratchpad / internal test-bed — a single gated internal page that reuses the project's real components and library functions so you can judge work-in-progress by eye: eyeball generated visuals (OG/social cards, emails, avatars, empty states), compare variants side by side or with live sliders, check config/env readiness, and exercise real side-effecting flows with fake data — without shipping any of it to users or clicking through the whole product. Boards and config panels get a "Copy as JSON" button so a tuned-by-eye result round-trips straight back into the code or to an agent to apply. Bootstraps into the user's existing stack: detects the framework, auth, and env conventions, writes a fail-closed access gate first, then a route with a section switcher seeded from their own code. Use when a user says "spin up a scratchpad", "internal test bed / dev playground / sandbox page", "an operator/admin preview page", "a page to eyeball my work", "preview my OG cards / emails / component variants", "add a test page for these components", or "an internal page to exercise a flow with fake data". NOT for public/user-facing features, NOT a replacement for tests (pass/fail machine-checkable → write a test), NOT Storybook (this lives inside the real app), and NOT a place to do load-bearing production operations.