franalgaba

Fetches Morpho Blue public deployment metadata using the Grimoire venue CLI. Use when you need contract addresses or adapter info.

Install and operate Grimoire, author .spell files with full syntax coverage (including advisory decision logic), and run compile/validate/simulate/cast safely. Use when users ask to create, edit, debug, validate, simulate, execute, or explain Grimoire strategies.

Fetches Aave V3 public market data using the Grimoire venue CLI. Use when you need Aave health checks, chain listings, market metadata, or reserve info.

Fetches Across Protocol bridge quotes, routes, and deposit status using the Grimoire venue CLI. Use when you need bridge quotes, route availability, or cross-chain deposit tracking.

Queries Hyperliquid market data using the Grimoire venue CLI. Use when you need mids, books, metadata, open orders, or a withdrawal call.

Fetches Pendle Hosted SDK metadata using the Grimoire venue CLI. Use when you need supported chains, aggregators, markets, assets, or market token details.

Queries Polymarket market data and CLOB state, and manages CLOB orders via the Grimoire venue CLI wrapper backed by the official Polymarket CLI.

Retrieves Uniswap router metadata using the Grimoire venue CLI. Use when you need router addresses, adapter information, or Uniswap V3/V4 details.

Compose programmable search pipelines with the Search as Code Python SDK.

Apply idiomatic Go best practices when reviewing, writing, or refactoring Go code. Covers naming, error handling, interfaces, concurrency/context, HTTP client/server production setup, receiver types, testing patterns, and project structure. Use this skill whenever the user is working with Go — writing new Go code, reviewing Go PRs or snippets, refactoring `.go` files, fixing Go style issues, or asking about idiomatic Go — even if they don't explicitly ask for "best practices." Also trigger on mentions of gofmt, goimports, go vet, effective Go, Go code review comments, goroutine leaks, context.Context usage, receiver types, or any Go-specific idiom question.

Review and refactor TypeScript code following Clean Code principles (Robert C. Martin's Clean Code, adapted for TypeScript). Produces a report listing every violation found — grouped by category — along with a fully refactored version of the code. Use this skill whenever the user asks to "review", "clean up", "refactor", "lint", "audit", or "improve" TypeScript or TSX code for readability, maintainability, or clean code compliance. Also trigger when the user pastes TypeScript code and asks for feedback, best practices, or code quality improvements — even if they don't explicitly say "clean code". Do NOT trigger for pure style/formatting-only requests (e.g. "run Prettier"), non-TypeScript languages, or runtime debugging/error-fixing that has nothing to do with code quality.