debug-store

Debug vibe-seller store runtime via SQLite inspection, CDP proxy control, and unauthenticated API access.

40|8|Updated May 14, 2026
One-click install
npx skills add https://github.com/zpoint/vibe-seller --skill debug-store
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-store
Source: https://github.com/zpoint/vibe-seller/tree/main/.claude/skills/debug-store
Command: npx skills add https://github.com/zpoint/vibe-seller --skill debug-store

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of debugging broken or unresponsive vibe-seller store infrastructure when the standard task and agent workflow is unavailable or insufficient, giving developers direct access to the store's runtime components without needing to navigate the web UI or JWT authentication flows.

Core Features & Use Cases

  • Direct Store Runtime Access: Inspect the store's SQLite database to check store configurations, user accounts, browser session status, and recent task history without going through the HTTP API.
  • Browser Wrapper Control: Drive the store's browser-use wrapper directly via the CDP proxy to test page interactions, verify workflows, and access seller central pages without creating a formal task.
  • Daemon and Session Recovery: Fix wedged browser daemons, rotate VIBE_TASK_ID for stable sessions, and resolve session conflicts that cause browser automation to fail.
  • Unauthenticated API Access: Bypass JWT cookie authentication to call the vibe-seller HTTP API for debugging, using either a temporary admin user or direct wrapper calls.
  • Use Case: If a store's browser is stuck on a page, a task is failing with session errors, or you need to look up a seller SKU directly from Amazon Seller Central, use this Skill to directly interact with the store's runtime to isolate and fix the issue.

Quick Start

Use the debug-store skill to inspect the SQLite database for a broken store, restart its browser daemon, and test a seller central page interaction to resolve session issues.

Frequently Asked Questions about debug-store

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

FAQPage Schema
How do I debug a stuck vibe-seller store browser daemon without using the task workflow?

To debug a stuck vibe-seller store browser daemon, you can directly access the store's runtime infrastructure outside the standard task workflow to recover wedged sessions and restart browser automation.

How do I inspect a vibe-seller SQLite database to check store configuration and session status?

You can inspect the vibe-seller SQLite database directly to check store configurations, user accounts, browser session status, and recent task history without needing to go through the HTTP API.

Can I access the vibe-seller HTTP API without JWT cookie authentication for troubleshooting?

Yes, you can bypass JWT cookie authentication to call the vibe-seller HTTP API for debugging by using a temporary admin user or direct wrapper calls.

How do I control a browser-use wrapper via CDP proxy for store debugging?

You can drive the store's browser-use wrapper directly via the CDP proxy to test page interactions, verify workflows, and access seller central pages without creating a formal task.

What is the best way to rotate VIBE_TASK_ID for stable browser sessions?

Rotating VIBE_TASK_ID manually through direct store runtime access resolves session conflicts and stabilizes browser sessions when standard agent workflows are unavailable.

Why does my vibe-seller browser automation fail with session errors?

Vibe-seller browser automation fails with session errors when browser daemons become wedged or session conflicts occur, requiring direct daemon recovery and VIBE_TASK_ID rotation outside the standard workflow.