Loading...
Loading...
Found 736 Skills
Find dead code using parallel subagent analysis and optional CLI tools, treating code only referenced from tests as dead. Use when the user asks to "find dead code", "find unused code", "find unused exports", "find unreferenced functions", "clean up dead code", or "what code is unused". Analysis-only — does not modify or delete code.
Generate high-level overall design for large features. Produces database model overview, core flow diagrams, and phased iteration plan. Use when user needs overall architecture planning for a big feature, not detailed class-level design. Triggers on "总体设计", "初步设计", "方案设计", "overall design". Does NOT do detailed design — use detail-designer for class/method level. Does NOT implement code.
Use when declaring or initializing Go variables, constants, structs, or maps — including var vs :=, reducing scope with if-init, formatting composite literals, designing iota enums, and using any instead of interface{}. Also use when writing a new struct or const block, even if the user doesn't ask about declaration style. Does not cover naming conventions (see go-naming).
Use when deciding whether to use Go generics, writing generic functions or types, choosing constraints, or picking between type aliases and type definitions. Also use when a user is writing a utility function that could work with multiple types, even if they don't mention generics explicitly. Does not cover interface design without generics (see go-interfaces).
Use this skill when the user wants to debug, diagnose, or systematically iterate on an experiment that already exists, or when they need a structured experiment log for tracking runs, hypotheses, failures, results, and next steps during active research. Apply it to underperforming methods, training that will not converge, regressions after a change, inconsistent results across datasets, aimless experimentation without progress, and questions like 'why doesn't this work?', 'no progress after many attempts', or 'how should I investigate this failure?'. Also use it for setting up practical experiment logging/record-keeping that supports debugging and iteration. Do not use it for designing a brand-new experiment pipeline or full experiment program (use experiment-pipeline), generating research ideas, fixing isolated coding/syntax errors, or writing retrospective summaries into research memory/notes/knowledge bases.
What DeFi positions does a wallet hold? Protocol-by-protocol breakdown of assets, debts, and rewards across chains.
Fetches web pages and converts them to clean markdown using a robust 3-tier chain (Firecrawl → Jina Reader → Scrapling stealth browser). Use this skill instead of WebFetch whenever the user provides a URL and needs the page's text content — especially for sites that block direct access: medium.com articles (paywalled/metered), WeChat public accounts (mp.weixin.qq.com, geo-restricted), documentation sites with bot protection, or any page where simple HTTP fetching might return a CAPTCHA or empty page. Triggers for: "read this URL", "summarize this article/page", "grab the content from", "extract text from", "what does this page say", "fetch this link", or any request to access and process a specific web page. Do NOT trigger for: building scrapers, checking HTTP status codes, parsing already-downloaded HTML files, answering conceptual questions about scraping tools, or monitoring page changes.
The coupon management function of Gate Exchange: query available coupons, check coupon details, view usage rules, and trace coupon source. Use this skill whenever the user asks about their coupons, vouchers, or bonus cards on Gate Exchange. Trigger phrases include 'my coupons', 'do I have any coupons', 'coupon list', 'check my voucher', 'coupon details', 'when does my coupon expire', 'coupon rules', 'how did I get this coupon', 'coupon source'.
Read Twitter/X for financial research using the twitter-cli tool (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my bookmarks", "who follows", "look up @user", "what's trending about", "market sentiment on Twitter", "what are people saying about AAPL", "fintwit", any mention of Twitter/X in context of reading financial news or market research. This skill is READ-ONLY — it does NOT support posting, liking, retweeting, or any write operations.
Interactive guide to repository workflow system: agents, skills, routing, and execution patterns. Use when user asks how the system works, what commands are available, or how to use brainstorm/plan/execute phases. Use for "how does this work", "what can you do", "explain workflow", "help me understand", or "show me the process". Do NOT use for actually executing workflows (use workflow-orchestrator) or debugging (use systematic-debugging).
Apply when deciding, designing, or implementing FastStore theme customizations in src/themes/ or working with design tokens and SCSS variables. Covers global tokens, local component tokens, Sass variables, CSS custom properties, and Brandless architecture. Use for any visual customization of FastStore storefronts that does not require component overrides.
Recovery strategy when the Write tool fails to create a new file. Use this skill whenever a Write or Edit tool call fails with an error related to creating a new file — such as missing parent directories, permission issues, or "file not found" errors on files that don't exist yet. This skill does NOT apply to editing existing files that fail for other reasons. Trigger when you see Write/Edit errors on new file creation, when file creation fails unexpectedly, or when you get path-related errors trying to create files in nested directories.