Loading...
Loading...
Found 9,298 Skills
Size and structure an emergency fund based on individual circumstances, income stability, and expense profile. Use when the user asks about emergency fund sizing, how many months of expenses to save, where to keep emergency savings, or tiered fund structures. Also trigger when users mention 'rainy day fund', 'how much cash should I keep', 'high-yield savings account', 'money market fund', 'freelancer cash reserve', 'variable income buffer', or ask what counts as an emergency expense.
Draft or update requirement documents under `easysdd/requirements/` for the project — describe a capability's "reason for existence, solution approach, and boundaries" using **user stories + plain language**, so non-technical readers can quickly grasp the key highlights of the system. Layered with architecture: requirement is the "problem space" (why this capability is needed), while architecture is the "solution space" (what structure is used to implement it). Two modes: new (draft a new requirement doc from scratch), update (refresh an existing doc based on new materials or implementation changes). Single-target rule — only modify one document at a time. Trigger scenarios: when the user says "fill in a requirement doc", "write down the requirements for this capability", "update the requirements directory", or when it is found during the feature-design phase that there is no corresponding requirement for the capability to be implemented this time.
CRITICAL: Use for Makepad 2.0 DSL syntax and property system. Triggers on: makepad dsl, script_mod!, makepad syntax, makepad property, makepad 2.0 syntax, colon syntax, merge operator, named instance, let binding, mod.widgets, register_widget, script_component, type_default, widgets_internal
Juicebro Content Aggregation Skill. Enables Agents to query, aggregate, and navigate public content from "Juicebro" across 13 platforms including Weibo, Xiaohongshu, Douyin, Bilibili, Xueqiu, Toutiao, WeChat Official Account, Xiaoyuzhou, etc. Supports full-platform search, single-platform query, topic filtering, content type screening, summary report generation, and platform navigation recommendation. Note: This Skill is in the specification-first phase, and content acquisition depends on the Agent's own public access capabilities.
Issue Workflow Stage 1 — Convert the user's problem into a reproducible, traceable {slug}-report.md through conversation. The AI only asks "what you saw, how to reproduce it, what should happen" here, and does not guess the root cause for the user (that's Stage 2's responsibility). Meanwhile, this stage is the only official decision point for choosing between the fast track and standard path: Based on the user's description, first review the relevant code; if the root cause can be identified at a glance and the required changes are minor, directly inform the user to take the fast track. Trigger scenarios: The user says "file an issue", "record this bug", "I found a problem". This is the starting point of the issue workflow with no pre-dependencies.
Enter this sub-process when conducting code optimization — handle tasks where 'behavior remains unchanged, structure changes' (structure / performance / readability). Shift single-module internal optimization from 'AI random refactoring' to 'first scan to generate a checklist, confirm each item with the user, execute step-by-step according to the method library, and require manual approval for each step'. Trigger scenarios: Users mention phrases like 'optimize it / refactor / rewrite / split it / poor performance / code is too long' without any accompanying behavior changes. Do not handle new requirements (route to feature), bugs (route to issue), or cross-module architecture restructuring (route to architecture + decisions).
Use whenever writing or reviewing Laravel PHP code (Laravel 13+). Prefer PHP attributes over class properties for models, jobs, commands, controllers, form requests, tests, factories, API resources, and container bindings. Trigger on $fillable, $table, $queue, $tries, $signature, $redirect, $errorBag, $seeder, constructor middleware, singleton registration, and any new Laravel class.
Build standalone custom pages using Amis low-code framework, independent of object records. Pages are defined as paired .page.yml (metadata) and .page.amis.json (UI schema) files in main/default/pages/. Covers page types (app, list, record), render_engine configuration, pageAssignments for desktop/mobile, and Amis schema with components like service, crud, chart, form, wizard, tabs. Includes examples for dashboards, reports, and custom forms.
Use The Graph Token API MCP through UXC for token metadata, wallet balances, transfers, holders, pools, and market data with help-first inspection and Token API specific JWT bearer auth binding.
Use Dune MCP through UXC for blockchain table discovery, SQL query creation/execution, execution result retrieval, and visualization with help-first schema inspection, explicit auth binding, and guarded credit-consuming operations.
Build token swap functionality with Circle App Kit or standalone Swap Kit SDKs. App Kit (`@circle-fin/app-kit`) is an all-inclusive SDK covering swap, bridge, and send -- recommended for extensibility. Swap Kit (`@circle-fin/swap-kit`) is a standalone package for swap-only use cases. Both require a kit key and run server-side only. Swap is mainnet-only (no testnet support). Supports same-chain swaps. For cross-chain token movement, combine separate swap and bridge calls using App Kit (swap tokenA to USDC, bridge USDC, swap USDC to tokenB). Use when: swapping tokens, exchanging stablecoins, converting USDT to USDC, setting up swap adapters (Viem, Solana Kit, Circle Wallets), estimating swap rates, configuring slippage or stop limits, collecting custom swap fees, or combining swap and bridge for cross-chain token movement. Triggers on: swap tokens, token exchange, App Kit, Swap Kit, @circle-fin/app-kit, @circle-fin/swap-kit, USDT to USDC, swap USDC, swap stablecoin, estimateSwap, slippage, stop limit, kit key, swap fees.
MaxIQ platform help — AI-native revenue intelligence with EchoIQ conversation intelligence, InspectIQ pipeline visibility, ForecastIQ AI-driven forecasting, 9 AI agents (NoteTaker, Radar, Summarizer, Coach, Taskmaster, Watchdog, Forecaster, Revenue Planner, Deal Mapper), usage-based pricing (no per-seat), Salesforce/HubSpot CRM sync. Use when EchoIQ not capturing all meeting types, AI Coach scoring criteria not matching your sales process, CRM fields not auto-populating from calls, InspectIQ deal signals seem inaccurate, ForecastIQ predictions not matching reality, comparing MaxIQ vs Gong vs Clari for revenue intelligence, setting up AI Radar keyword tracking, or evaluating usage-based CI pricing vs per-seat alternatives. Do NOT use for designing outbound cadences (use /sales-cadence) or cross-platform coaching programs (use /sales-coaching).