OpenParable
Skip to content
← Back to skills

Agent Bom Troubleshoot

Testing & Quality
agent-bom-troubleshoot

Agent Bom Troubleshoot is an Agent Skill for testing & quality published in the LeoYeAI/openclaw-master-skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Diagnose issues, check prerequisites, and validate configurations. Use when: "doctor", "debug", "why failing", "validate config", "check prerequisites", "something is broken", "db status", "fix my setup".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/LeoYeAI/openclaw-master-skills/blob/HEAD/skills/agent-bom/troubleshoot/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/agent-bom-troubleshoot, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

agent-bom-troubleshoot — Diagnostics & Configuration Validator

Diagnoses issues, checks prerequisites, validates configurations, and reports on the health of the agent-bom installation and connected database.

Install

pipx install agent-bom
agent-bom doctor             # check prerequisites and installation health
agent-bom validate           # validate configuration files
agent-bom db status          # check database connection status

When to Use

  • "doctor" / "run doctor"
  • "debug" / "help me debug"
  • "why failing" / "something's broken"
  • "validate config" / "check configuration"
  • "check prerequisites"
  • "db status" / "database status"
  • "fix my setup"

Commands

# Run full diagnostic check
agent-bom doctor

# Validate configuration
agent-bom validate

# Check database status
agent-bom db status

Examples

# Run diagnostics
doctor()

# Validate config
validate()

# Check DB
db_status()

Example doctor output:

agent-bom doctor

  Python        3.12.2   OK
  agent-bom     0.75.9   OK
  pip           24.0     OK
  semgrep       not found  (optional — SAST scanning unavailable)
  kubectl       not found  (optional — K8s context unavailable)

  Config files found:
    Claude Desktop  ~/.config/Claude/claude_desktop_config.json  OK
    Cursor          ~/.cursor/mcp.json                           OK

  Database:      SQLite  ~/.agent-bom/db.sqlite  OK
  Last scan:     2 hours ago

  Status: Ready

Guardrails

  • Diagnostics are read-only — no configuration files are modified.
  • Doctor checks do not transmit any data externally.
  • If the user is experiencing an error, show the full diagnostic output before suggesting fixes.
  • Validate configuration files before recommending changes.