Loading...
Loading...
Found 5,627 Skills
Expert skill for using OpenViking, the open-source context database for AI Agents that manages memory, resources, and skills via a filesystem paradigm.
AI-native open knowledge base about Taiwan built with Astro v5, featuring bilingual content (zh-TW/en), D3.js knowledge graph, and structured Markdown SSOT architecture.
Analyze codebases from the bottom up and generate a hierarchical README.md document tree. Start analysis from leaf directories, generate README.md files for each directory containing one-sentence descriptions of files, classes, and functions, and summarize layer by layer upwards to form a complete codebase documentation system. Supports state persistence and resumable analysis, suitable for scenarios such as understanding new projects, generating technical documentation, and analyzing code structures. Use this skill when you need to understand codebase structures, analyze function implementations, or generate code documentation.
Migrates apps from @coinbase/onchainkit to standalone wagmi/viem components. Handles provider replacement (OnchainKitProvider to WagmiProvider), wallet component replacement (Wallet/ConnectWallet to custom WalletConnect), and transaction component replacement. Use when the user says "migrate my onchainkit", "replace onchainkit provider", "migrate my wallet component", "replace my onchainkit wallet", "migrate my transaction component", "remove onchainkit dependency", or "move off onchainkit".
Converts Farcaster miniapp SDK projects into regular Base/web apps. Starts with an interactive quiz to choose between the default regular-app conversion and a narrowly isolated Farcaster surface when something truly needs to remain separate. Handles wagmi connectors, providers, auth, SDK actions, manifest routes, meta tags, dependencies, and read-only preservation.
Use this skill when designing database schemas, optimizing queries, creating indexes, planning migrations, or choosing between database technologies. Triggers on schema design, normalization, indexing strategies, query optimization, EXPLAIN plans, migrations, partitioning, replication, connection pooling, and any task requiring database architecture or performance decisions.
Use when facing complex reasoning tasks - multi-step math, logic puzzles, decisions with tradeoffs, problems where direct answers fail, or when you need to show your work. Triggers on arithmetic errors, shallow analysis, or "I'm not sure" hedging.
Condition-based polling and retry patterns: exponential backoff, health checks, rate limit recovery, circuit breakers. Use when replacing arbitrary sleeps with condition checks, implementing retry logic, waiting for service availability, or handling API rate limits. Use for "wait for", "poll until", "retry with backoff", "health check", or "rate limit". Do NOT use for async event-driven architectures, distributed locking, or real-time guarantees.
Systematic 4-phase codebase exploration: Detect, Explore, Map, Summarize. Use when starting work on an unfamiliar codebase, onboarding to a new project, reviewing a repository for the first time, or building context before debugging or code review. Use for "explore codebase", "what does this project do", "understand architecture", or "onboard me". Do NOT use for modifying files, running applications, performance optimization, or deep domain analysis.
Expert knowledge for Azure Database for MySQL development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when deploying MySQL Flexible Server, tuning performance, configuring HA/networking, securing access, or integrating apps, and other Azure Database for MySQL related development tasks. Not for Azure Database for MariaDB (use azure-database-mariadb), Azure Database for PostgreSQL (use azure-database-postgresql), Azure SQL Database (use azure-sql-database), Azure SQL Managed Instance (use azure-sql-managed-instance).
Select an installation method, install NocoBase, and start it locally or on a server. Use when users ask how to install NocoBase, initialize a project, or start a running instance.
Create and manage NocoBase data models via MCP. Use when users want to inspect or change collections, fields, relations, or view-backed schemas in a NocoBase app.