From tidewave-tools-usage
CRITICAL for ALL Elixir/Phoenix/Ash development work. Invoke when working with Elixir code, Ecto schemas, Ash resources, Phoenix applications, or databases in Elixir projects. Provides MCP tools for live code evaluation (via IEx), instant module navigation, direct SQL execution, schema introspection, and documentation access. Tidewave provides superior alternatives to bash/grep/read for Elixir tasks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tidewave-tools-usage:tidewave-tools-usageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When working with this Elixir/Phoenix/Ash codebase, **ALWAYS prioritize Tidewave MCP tools** over traditional file system operations. Tidewave provides deep integration with the Elixir runtime and superior code intelligence.
When working with this Elixir/Phoenix/Ash codebase, ALWAYS prioritize Tidewave MCP tools over traditional file system operations. Tidewave provides deep integration with the Elixir runtime and superior code intelligence.
NEVER use Bash to run Elixir code! Instead use mcp__tidewave__project_eval:
exports(Module), h(Module.function))arguments parameterExample:
bash: mix run -e "IO.inspect(MyModule.function())"mcp__tidewave__project_eval: code: "IO.inspect(MyModule.function())"Before using Grep, Glob, or Read for Elixir code:
mcp__tidewave__get_source_location - Find exact file locations instantly
Module, Module.function, Module.function/arity"dep:package_name"mcp__tidewave__get_docs - Get documentation without reading files
"MyModule""MyModule.function/2""c:GenServer.init/1"Example:
grep: pattern: "defmodule Worker"mcp__tidewave__get_source_location: reference: "MyApp.Worker"mcp__tidewave__execute_sql_query - Run SQL directly against Ecto repos
mcp__tidewave__get_ecto_schemas - List all schemas and their locations
Example:
bash: psql -c "SELECT * FROM users"mcp__tidewave__execute_sql_query: query: "SELECT * FROM users LIMIT 10"mcp__tidewave__search_package_docs - Search Hex documentation
mcp__tidewave__get_logs - Get application logs
mcp__tidewave__get_docs - Get documentationmcp__tidewave__get_source_location - Find the filemcp__tidewave__project_eval with exports(Module) - List functionsmcp__tidewave__project_eval before writingcode: "MyModule.new_function(:test_input) |> IO.inspect()"mcp__tidewave__get_ecto_schemas - Understand data modelsmcp__tidewave__execute_sql_query - Inspect actual datamcp__tidewave__project_eval - Test Ecto queriesmcp__tidewave__get_logs - Recent errorsmcp__tidewave__get_source_location - Find problem codemcp__tidewave__project_eval - Reproduce issueh(Module) - Get help for a moduleexports(Module) - List all exported functionsi(value) - Inspect data structure infot(Module) - Show types defined in moduleb(Module) - Show behaviours module implementsarguments - Access passed arguments arrayWhen using execute_sql_query:
::text (PostgreSQL)query: "SELECT * FROM users WHERE id = $1", arguments: [123]❌ DON'T:
bash to run mix commands for code evaluationgrep to find module definitions when you know the module nameiex in bash instead of using project_evalget_ecto_schemas✅ DO:
project_eval for ALL Elixir code executionget_source_location for known modulesget_docs for documentationget_ecto_schemas first for schema discoveryThe Tidewave MCP server gives you:
Every time you reach for Bash, Grep, or Read for Elixir code, ask yourself: "Can Tidewave MCP do this better?" The answer is almost always YES.
npx claudepluginhub forest/agent-skills --plugin tidewave-tools-usageExposes MCP tools for Phoenix apps: execute Elixir code, run SQL queries, list Ecto schemas, fetch docs/logs/source. Use for AI assistant integration, runtime debugging, Tidewave setup.
Connects AI coding assistants to running Phoenix apps via MCP for runtime introspection: Ecto schemas, code execution, docs, logs, SQL queries. Prefer MCP tools over web fetches for version-pinned results.
Provides Tidewave MCP runtime tools for debugging, smoke testing, live state inspection, SQL queries, and Hex docs in running Phoenix apps. Use when evaluating code.