Loading...
Loading...
Found 1,934 Skills
Guide for implementing Syncfusion WPF OLAP Gauge control for displaying Key Performance Indicators (KPI) from OLAP data sources. Use this when working with OLAP KPI visualization, business intelligence dashboards, or XML/A data binding in WPF. This skill covers connecting to OLAP cubes, SQL Server Analysis Services, Mondrian servers, and configuring KPI displays for executive dashboards and BI applications.
Generate Google Ads creatives using each::sense AI. Create display ads, YouTube thumbnails, Discovery ads, Performance Max assets, and responsive display ads optimized for Google's ad formats and best practices.
Diagnose MSBuild build performance bottlenecks using binary log analysis. Only activate in MSBuild/.NET build context. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization below 80%, excessive Copy tasks, NuGet restore running every build. Covers timeline analysis, Target/Task Performance Summary interpretation, and 7 common bottleneck categories. Use after build-perf-baseline has established measurements. DO NOT USE FOR: establishing initial baselines (use build-perf-baseline first), fixing incremental build issues (use incremental-build), parallelism tuning (use build-parallelism), non-MSBuild build systems. INVOKES: dotnet msbuild binlog replay with performancesummary, grep for analysis.
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. Only activate in MSBuild/.NET build context. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ / .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead). INVOKES: shell commands (dotnet build /bl:{}).
Analyze MSBuild binary logs to diagnose build failures by replaying binlogs to searchable text logs. Only activate in MSBuild/.NET build context. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, investigating common errors like CS0246 (type not found), MSB4019 (imported project not found), NU1605 (package downgrade), MSB3277 (version conflicts), and ResolveProjectReferences failures. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), build performance analysis (use build-perf-diagnostics), non-MSBuild build systems. INVOKES: dotnet msbuild binlog replay, grep, cat, head, tail for log analysis.
Execute a comprehensive React Project Health Audit. Analyzes tech stack, architecture, state management, testing, code quality, performance, CI/CD, and documentation. Produces a Google Docs-ready report with section scores and weighted overall score. Use when the user asks to audit a React project, run a health check, evaluate frontend quality, or assess technical debt. Triggers on: 'react audit', 'health audit', 'react health', 'frontend audit', 'next.js audit', 'vite audit', 'project quality check'.
WordPress performance code review and optimization analysis. Use when reviewing WordPress PHP code for performance issues, auditing themes/plugins for scalability, optimizing WP_Query, analyzing caching strategies, checking code before launch, or detecting anti-patterns, or when user mentions "performance review", "optimization audit", "slow WordPress", "slow queries", "high-traffic", "scale WordPress", "code review", "timeout", "500 error", "out of memory", or "site won't load". Detects anti-patterns in database queries, hooks, object caching, AJAX, and template loading.
Comprehensive SAC scripting skill for SAP Analytics Cloud Analytics Designer and Optimized Story Experience. This skill should be used when the user asks to "create SAC script", "debug Analytics Designer", "optimize SAC performance", "planning operations in SAC", "filter data in SAC", "use DataSource API", "chart scripting", "table manipulation", "SAC event handlers", "version management", "data locking", "Optimized Story Experience API", "OSE scripting", "OSE widget API", "OSE DataSource", "story scripting API", "OSE planning API", "OSE method", "optimized story", "SAC story scripting", "story script", "SAC scripting", or works with SAC widgets, planning models, or analytics applications.
Discover trending tokens and newly listed tokens across supported blockchains: view trending token rankings by chain and time window, find newly launched tokens, filter by launchpad platform, sort by volume/price change/market cap, and search within rankings by keywords. Trigger words: trending, trending tokens, hot tokens, top tokens, top gainers, top losers, market overview, market trends, what's hot, what's trending, popular tokens, most traded, highest volume, biggest gainers, biggest movers, new tokens, new listings, newly listed, just launched, new coins, recent launches, launchpad, pump.fun, pump fun, new launch, discovery, discover tokens, explore, market scan, market watch, ranking, rankings, leaderboard, top chart, heat map, token rankings, performance ranking, best performing. Chinese: 趋势, 热门代币, 排行, 排行榜, 涨幅榜, 跌幅榜, 市场趋势, 什么在涨, 热门, 最热, 新币, 新上线, 刚上线, 新发行, 最近上线, 市场概览, 市场扫描, 发现代币, 探索. CRITICAL: Always use `--json` flag for structured output. CRITICAL: When showing rankings, display at least token name, symbol, price, and 24h change. Do NOT use this skill for: - Specific token details, security audit, holders, or K-line → use liberfi-token - Wallet holdings or portfolio analysis → use liberfi-portfolio - Swap quotes, trading, or transaction execution → use liberfi-swap Do NOT activate on vague inputs like "market" alone without context indicating the user wants rankings or new token discovery.
Analyze wallet portfolios on supported blockchains: view token holdings with current values, track transaction activity and history, check PnL (profit and loss) statistics over different time windows, and query total wallet net worth. Also supports querying the authenticated user's own LiberFi TEE wallet portfolio without needing to provide a wallet address — use the `me` commands when the user wants to check their own LiberFi account's holdings, activity, stats, or net worth. Trigger words: wallet, portfolio, holdings, my tokens, my coins, my balance, what do I hold, what tokens do I have, wallet balance, wallet holdings, wallet activity, transaction history, recent transactions, transfers, swaps, trade history, wallet stats, PnL, profit and loss, profit, loss, gains, returns, performance, how much did I make, how much did I lose, win rate, net worth, total value, portfolio value, total balance, how much is my wallet, wallet overview, wallet summary, wallet analysis, check wallet, view wallet, my portfolio, account balance, my LiberFi wallet, my TEE wallet, my account portfolio, check my account, my holdings without address. Chinese: 钱包, 持仓, 我的代币, 我持有什么, 余额, 钱包余额, 交易记录, 交易历史, 最近交易, 转账记录, 钱包统计, 盈亏, 利润, 亏损, 收益, 收益率, 胜率, 净值, 总价值, 钱包总价值, 钱包概览, 钱包分析, 查看钱包, 我的LiberFi钱包, 我的TEE钱包, 我的账户持仓, 不知道地址查我的钱包. CRITICAL: Always use `--json` flag for structured output. CRITICAL: Public `wallet` commands require both chain and wallet address — always ask the user for these if not provided. CRITICAL: `me` commands do NOT require a wallet address — they use the authenticated user's TEE wallet automatically. They DO require authentication (run `lfi status` first, then `lfi login key` if needed). Do NOT use this skill for: - Token search, info, security audit, K-line → use liberfi-token - Trending tokens or new token rankings → use liberfi-market - Swap quotes, trade execution, or transaction broadcast → use liberfi-swap - Token holder analysis (for a specific token) → use liberfi-token Do NOT activate on vague inputs like "wallet" alone without a wallet address or clear intent to check portfolio data.
Guides the agent through Angular-specific patterns for Ionic app development. Covers project structure, standalone vs NgModule architecture detection, Angular Router integration with Ionic navigation (tabs, side menu, modals), lazy loading, Ionic page lifecycle hooks, reactive forms with Ionic input components, Angular services for state management, route guards, performance optimization, and testing. Do not use for creating a new Ionic app from scratch, upgrading Ionic versions, general Ionic component usage unrelated to Angular, Capacitor plugin integration, or non-Angular frameworks (React, Vue).
Generate comprehensive issue reports from HyperPod clusters (EKS and Slurm) by collecting diagnostic logs and configurations for troubleshooting and AWS Support cases. Use when users need to collect diagnostics from HyperPod cluster nodes, generate issue reports for AWS Support, investigate node failures or performance problems, document cluster state, or create diagnostic snapshots. Triggers on requests involving issue reports, diagnostic collection, support case preparation, or cluster troubleshooting that requires gathering logs and system information from multiple nodes.