sqlmesh-expert
Use when working with SQLMesh projects - creating models, reviewing plans, validating changes, debugging failures, or deploying to production environments.
Browse published AI skills maintained by vrazdalovschi. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
10Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Use when working with SQLMesh projects - creating models, reviewing plans, validating changes, debugging failures, or deploying to production environments.
Use when writing or reviewing React useEffect, useState for derived values, data fetching, or synchronizing state with external systems.
Use when delegating coding tasks to Gemini CLI agent, when you need parallel AI execution, or when tasks benefit from Gemini's 1M+ context window.
Use when you need validation, analysis, or research from multiple AI agents before implementing. Gathers perspectives from Gemini and Codex, synthesizes feedback.
Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing
Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
Use when something works unusually well during agentic coding - fast completion, first-try success, elegant solution, minimal intervention needed, or new technique paid off.
Use when something goes wrong during agentic coding - hallucination, bug, ignored instruction, anti-pattern, context loss, or Claude getting stuck in a loop.
Use when asked about library/framework APIs, version-specific features, or when user mentions outdated docs. Requires Context7 MCP server.
Use when editing .sql files, reviewing SQL in Python/JavaScript/TypeScript code, writing database queries, or when user mentions PostgreSQL, SQL validation, query optimization, or database schema.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.