Loading...
Loading...
Found 10,562 Skills
Design customer service operations including tiered support (L1/L2/L3), response templates, SLA definitions, escalation procedures, and complaint handling. Use this skill when the user needs to set up a CS team, create service standards, design escalation flows, or improve response quality — even if they say 'our CS is a mess', 'how should we handle complaints', 'set up support tiers', or 'create CS SOPs'.
Use when app feels slow, memory grows, battery drains, or diagnosing ANY performance issue. Covers memory leaks, profiling, Instruments workflows, retain cycles, performance optimization.
Builds multi-layer features as vertical end-to-end slices instead of horizontal layers. Each slice is verified before the next begins. Use when: starting any task that spans 2+ layers (DB, API, UI, tests), building CRUD features, implementing multi-step flows, decomposing features into subtasks, or planning implementation order.
Pulumi integration. Manage data, records, and automate workflows. Use when the user wants to interact with Pulumi data.
Emulated Stripe API for local development and testing. Use when the user needs to process payments locally, test checkout flows, create customers, manage products and prices, handle payment intents, work with webhooks, or use the Stripe SDK without hitting real Stripe servers. Triggers include "Stripe API", "emulate Stripe", "test payments locally", "checkout flow", "payment intent", "Stripe webhook", "Stripe SDK", "STRIPE_API_KEY", or any task requiring a local Stripe API.
Perform common Git operations safely with sandbox-aware failure handling. Use whenever the user wants to inspect or modify git state, especially for cherry-pick, merge, rebase, commit, branch, stash, or worktree workflows. Always use this skill when the user mentions a Git failure, conflict, cherry-pick, merge issue, worktree, branch checkout problem, lock file, permission denied, operation not permitted, or any case where a sandboxed agent might confuse an environment restriction with a real code conflict. Be proactive: if the task smells like Git state or Git write behavior, use this skill even if the user did not explicitly ask for a 'Git' workflow.
Eva-skill: A Thinking Coaching & Viral Short Video Toolkit for Creators. It helps creators organize their desire to express, aids thinking with creator thinking tools, thinking lenses and MBTI lenses, reframes superficial problems, deconstructs concepts, expands content directions, and completes the production of voiceover short videos for platforms like Xiaohongshu, Douyin, and Video Account. It covers modules including Thinking Assistant, Creator Thinking Tool Library, Thinking Lenses, MBTI Lens, Superficial Problem Reframing, Viral Topic Selection, Viral Case Deconstruction, Title Anchor, User Question Validation, Title & Cover, Voiceover Script, Material Retrieval, Voiceover Performance, Post-Publishing Review, Sedimentation Mechanism, Fallback Mechanism, and Interactive Tone & Rhythm. Trigger Methods: /eva, /thinking-flow, /viral-short-video, /eva-think, /eva-lens, /eva-lenses, /eva-mbti, /eva-mbti-lens, /eva-reframe, /eva-shortvideo, /eva-topic, /eva-deconstruct, /eva-title-cover, /eva-script, /eva-performance, /eva-review, /eva-sediment, "Help me think", "My mind is messy", "Thinking Lens", "Scholar's Perspective", "MBTI Lens", "MBTI Lens", "MBTI", "Personality Type", "Reframe Problem", "Deconstruct Concept", "Help me make a voiceover video", "How to make this Xiaohongshu video", "Help me write a video script", "Help me review data", "Sediment", "Save", "Archive", "Continue next time"
MUST be used whenever fixing performance issues in a Flows app. This skill finds AND fixes performance problems — re-renders, inefficient queries, missing pagination, unbounded fetches, large bundles, and memory leaks. It does not just report them. Always measure before and after. Triggers: performance, slow, laggy, optimize, re-render, bundle size, load time, CDF query, large list, memory leak, debounce, virtualize, lazy load, code split.
Reverse import existing novels. Parse written novels (unfinished or completed) into a standard project directory structure, compatible with the subsequent writing workflow of story-long-write. Internally reuse the deep analysis pipeline of story-long-analyze. Trigger methods: /story-import, "Import Novel", "Reverse Parse", "Import", "Import My Book"
NeoData Financial Search — A universal natural language financial data search service. Query full-category financial data such as stocks, funds, indices, sectors, macroeconomics, foreign exchange, and commodities using natural language, covering market quotes, financial statements, capital flows, research report ratings, event announcements, etc. It supports two recall modes: structured API data and financial articles, providing instant answers. Use when the user asks about financial data, stock quotes, financial statements, earnings reports, market data, fund info, macroeconomics, forex, commodities, or needs to query the NeoData API.
Best practices for contributing code to TensorRT-LLM. Covers the official contribution process (issue tracking, fork workflow, DCO signing), coding guidelines, implementation workflow, common mistakes, testing strategy, commit hygiene, and review readiness. Incorporates rules from CONTRIBUTING.md and CODING_GUIDELINES.md plus lessons distilled from real PR retrospectives. Use when implementing new features, optimizations, or bug fixes in the TensorRT-LLM codebase.
Implement Syncfusion ASP.NET Core Diagram component (EJ2 Tag Helper `ejs-diagram`) for building interactive diagrams in Razor Pages or MVC applications. Use this skill when working with org charts, flowcharts, BPMN process diagrams, UML diagrams, or swimlane charts. This skill covers node and connector configuration, layout options, shape styling, data binding, drawing tools, export/print functionality, and other diagram features.