investigations

Execute SQL and Ecto queries to inspect database states and logs.

Updated Aug 27, 2026

Search Tags:#debugging #investigation #database #logs #sql #ecto

Ready to run

npx skills add https://github.com/ityonemo/pepper --skill investigations

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigations
Source: https://github.com/ityonemo/pepper/tree/main/.claude/skills/investigations
Command: npx skills add https://github.com/ityonemo/pepper --skill investigations

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides tools and techniques to investigate database states, debug pipeline issues, and explore data for troubleshooting.

Core Features & Use Cases

Direct SQL Queries: Execute arbitrary SQL queries against the database using mcp__tidewave__execute_sql_query.
Ecto Queries: Run Ecto queries for more structured data access using mcp__tidewave__project_eval.
Log Analysis: Inspect application logs for errors and warnings using mcp__tidewave__get_logs.
Use Case: When a user reports an issue, use this Skill to query the users table for their record and check the events table for recent activity related to their account.

Quick Start

Use the investigations skill to check the last 20 error logs.

Frequently Asked Questions about investigations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug database issues using SQL queries?▼

Database debugging through SQL queries allows you to execute arbitrary statements directly against the database to inspect table states. You can analyze user records, event sourcing data, and background job queues to pinpoint pipeline issues.

Can I run Ecto queries to investigate application data?▼

Yes, running Ecto queries provides structured data access for application investigation. This approach enables you to evaluate project-specific query logic to explore database states and troubleshoot reported user issues more safely than raw SQL.

What's the best way to inspect application logs for errors and warnings?▼

Inspecting application logs for errors and warnings is best handled through a dedicated log retrieval function. This allows you to quickly pull recent error logs to identify pipeline failures and correlate them with database states during troubleshooting.

How do I troubleshoot a reported user issue by checking recent activity?▼

Troubleshooting a reported user issue involves querying the users table for their specific record and checking the events table for recent activity. This database investigation approach links user accounts to their latest event sourcing data.

Does this database investigation approach support analyzing background job queues?▼

Yes, database investigation supports analyzing background job queues. You can execute direct SQL queries against the database to inspect the queue tables, helping you debug pipeline issues and identify stalled or failed background jobs.

When do I need to use direct SQL over Ecto queries for database debugging?▼

Direct SQL is needed for database debugging when you require arbitrary, ad-hoc queries without framework constraints. Ecto queries offer structured data access, while raw SQL provides flexible exploration for complex event sourcing data analysis and troubleshooting.