Verified:GitHub

problem-analyzer

Analyze technical problems through database inspection and visual diagramming.

Updated Dec 5, 2025

Search Tags:#root cause analysis #technical analysis #architecture mapping #database troubleshooting #edge case management

Ready to run

npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill problem-analyzer-apothecaryman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: problem-analyzer
Source: https://github.com/ApothecaryMan/pharmaflow-ai/tree/main/.agent/skills/problem-analyzer
Command: npx skills add https://github.com/ApothecaryMan/pharmaflow-ai --skill problem-analyzer-apothecaryman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of thoroughly understanding complex issues before implementation, preventing costly mistakes and improving efficiency.

Core Features & Use Cases

Deep Technical Analysis: Maps problems, architectures, and edge cases with precision.
Read-Only Database Inspection: Uses mcp_supabase_list_tables and mcp_supabase_execute_sql for database analysis.
Architectural Mapping: Provides tools for visualizing and understanding data flow and relationships.
Root Cause Identification: Offers methods for identifying the source of technical issues.
Edge Case Investigation: Encourages considering 10+ edge cases to prevent unforeseen issues.
Implementation Strategy: Assists in creating a prioritized plan for implementing solutions.

Quick Start

Use the problem-analyzer skill to perform a deep dive on the 'database connection issue' by reviewing logs and inspecting the schema.

Frequently Asked Questions about problem-analyzer

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

FAQPage Schema

How do I perform root cause analysis for a complex database connection issue?▼

Root cause analysis for a database connection issue involves inspecting logs and reviewing the database schema. This Skill conducts read-only database inspection using Supabase tools to map architectures and identify the exact source of technical problems.

What is the best way to map system architecture before implementing a new feature?▼

Architecture mapping before implementation requires visualizing data flow and understanding system relationships. This Skill provides visual diagramming tools to map complex architectures precisely, preventing costly mistakes by thoroughly understanding the issue beforehand.

How do I investigate edge cases during technical troubleshooting?▼

Investigating edge cases during troubleshooting requires systematically considering potential failure scenarios. This Skill encourages identifying 10 or more edge cases to manage unforeseen issues and ensures comprehensive technical analysis for accurate decision-making.

Can I execute write operations or modify data during database troubleshooting?▼

Database troubleshooting with this Skill is strictly read-only. It uses Supabase tools to list tables and execute SQL queries for inspection purposes only, ensuring the analysis of your database schema and connection issues does not modify your data.

When do I need comprehensive technical analysis for debugging?▼

Comprehensive technical analysis for debugging is needed when facing complex systems troubleshooting or pre-implementation planning. It helps map problems, inspect databases, and identify root causes to prevent unforeseen issues and improve implementation efficiency.

Does this problem analysis approach work with Supabase for schema inspection?▼

Yes, this problem analysis approach integrates directly with Supabase for schema inspection. It utilizes specific Supabase tools to list database tables and execute SQL queries, enabling deep technical analysis and accurate root cause identification.