Loading...
Loading...
Found 150 Skills
Guides the agent through migrating an existing Ionic/Capacitor project from Ionic Appflow to Capawesome Cloud. Detects which Appflow features are in use (Live Updates, Native Builds, App Store Publishing) and provides step-by-step migration for each feature to its Capawesome Cloud equivalent. Covers SDK replacement, configuration mapping, API migration, CI/CD pipeline updates, and verification. References the capawesome-cloud skill for detailed Capawesome Cloud setup procedures. Do not use for setting up Capawesome Cloud from scratch without an existing Appflow project, for non-Capacitor mobile frameworks, or for migrating Ionic Enterprise plugins.
MSVC cl.exe and clang-cl skill for Windows C/C++ projects. Use when configuring Visual Studio builds, MSBuild, or clang-cl as a drop-in MSVC replacement. Covers translating GCC/Clang flags to MSVC equivalents, runtime library selection, Windows SDK setup, and diagnosing MSVC-specific errors. Activates on queries about cl.exe, clang-cl, /O flags, /MT vs /MD, PDB files, Windows ABI, or MSVC project settings.
Ctrip Flight Query Skill based on browser automation tools, supporting one-way and round-trip flight queries, capable of handling parameter inputs such as departure location, destination, date, etc., and equipped with error recovery mechanisms. Suitable for scenarios where flight information, flight prices, and schedules need to be queried from Ctrip.
Strategic account planning and execution for enterprise deals. Use when planning complex sales cycles, managing multiple stakeholders, applying MEDDICC qualification, tracking deal health, or building mutual action plans. Includes the "stale MAP equals dead deal" pattern.
Build self-serve acquisition and expansion motions. Use when deciding PLG vs sales-led, optimizing activation, driving freemium conversion, building growth equations, or recognizing when product complexity demands human touch. Includes the parallel test where sales-led won 10x on revenue.
Decompose Return on Equity into component ratios to identify performance drivers. Use for financial analysis, performance benchmarking, and identifying improvement opportunities.
US stock market sentiment monitoring and position recommendation system. Evaluates market sentiment by tracking 5 core indicators (NAAIM Exposure Index, Institutional Equity Allocation, Retail Net Buying, S&P 500 Forward P/E Ratio, Hedge Fund Leverage) and outputs sentiment ratings and position recommendations. This skill should be used when the user mentions topics such as US stock sentiment, market overheating, greed/fear indicators, NAAIM, institutional positioning, retail sentiment, P/E valuation bubbles, hedge fund leverage, whether to reduce positions, market risk assessment, position management advice, market top/bottom signals, etc. Even if the user simply asks "Is the US stock market risky right now?" or "Should I reduce my positions?", this skill should be triggered to provide a structured analytical framework.
Query and manage Gate multi-collateral loan. Use this skill whenever the user asks about collateral loan, current loan, fixed loan, repay, add collateral, or redeem collateral. Trigger phrases include "collateral loan", "current loan", "fixed loan", "repay", "add collateral", "redeem collateral", or equivalent in other languages.
Gate Exchange affiliate program data query and management skill. Use this skill when users ask about their affiliate/partner commission, trading volume, net fees, customer count, trading users, or want to apply for the affiliate program. Supports queries for up to 180 days (API limited to 30 days per request, agent should split longer queries). IMPORTANT: user_id parameter in APIs refers to 'trader' not 'commission receiver' - avoid using unless explicitly specified. Aggregated data from API lists should be calculated using custom scripts, not simple summation. CRITICAL TIME CONSTRAINT: All query times are calculated based on user's system current date in UTC+8 timezone. For relative time descriptions (e.g., 'last 7 days', 'last 30 days', 'this week', 'last month'), calculate start date by subtracting days from current date, then convert both start and end dates to UTC+8 00:00:00 and 23:59:59 respectively, then convert to Unix timestamps. NEVER use future timestamps as query conditions. When timestamps are needed, obtain them via system functions, never generate manually. The 'to' parameter must always be less than or equal to the current Unix timestamp. Trigger phrases include 'my affiliate data', 'commission this week', 'partner earnings', 'team performance', 'customer trading volume', 'rebate income', 'apply for affiliate', 'can I apply', 'am I eligible', 'my application status', 'recent application', 'partner application status'.
Short-term and swing trading assistant for the Indian stock market (NSE/BSE). Helps with stock screening, technical analysis, trade planning, and watchlist generation focused on breakout/breakdown patterns, support-resistance levels, and volume-price action. Use this skill whenever the user mentions Indian stocks, NSE, BSE, Nifty, swing trades, short-term trades, positional trades, breakout setups, stock screening for Indian markets, trade plans for Indian equities, or asks for watchlists with entry/exit/SL levels. Also trigger when the user uploads Indian market data (CSV exports, screenshots of charts), mentions specific NSE/BSE stock names or tickers, or asks questions like "find me good setups", "scan for breakouts", "give me a trade plan for TATAMOTORS", "what looks good in Nifty 50 right now", or "build me a watchlist". Do NOT trigger for intraday/scalping, options strategies, mutual fund analysis, long-term investing (6+ months), or non-Indian markets.
This skill should be used when the user asks about 'TRON energy', 'TRON bandwidth', 'how much energy do I need', 'energy cost on TRON', 'bandwidth insufficient', 'resource delegation on TRON', 'rent energy on TRON', 'TRON transaction fee', 'why is my TRON transaction expensive', 'optimize TRON costs', or mentions Energy, Bandwidth, resource management, fee estimation, or cost optimization on the TRON network. This is a TRON-specific concept with no direct equivalent on EVM chains. Do NOT use for staking/voting — use tron-staking. Do NOT use for balance queries — use tron-wallet.
Model Kotlin persistence code correctly for Spring Data JPA and Hibernate. Covers entity design, identity and equality, uniqueness constraints, relationships, fetch plans, and common ORM (Object-Relational Mapping) traps specific to Kotlin. Use when creating or reviewing JPA (Java Persistence API) entities, diagnosing N+1 or LazyInitializationException, placing indexes and uniqueness rules, or preventing Kotlin-specific bugs such as data class entities and broken equals/hashCode.