verify

Verify trading bot activity and trade execution after deployments.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Liquilab/Bottie --skill verify-liquilab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/Liquilab/Bottie/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/Liquilab/Bottie --skill verify-liquilab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deployment verification ensures the bot actually trades and that changes are effective, preventing silent failures after deploys.

Core Features & Use Cases

  • Post-deploy checks: confirm services are active, trades are executed (FILLED), and config reloads happen as expected.
  • Regressions & reporting: detect anomalies, log issues, and produce a concise verification report.
  • Real-world use case: after any deployment or config change, run /verify to validate bot activity and surface actionable next steps.

Quick Start

Run the verification workflow after deployment to confirm the bot is trading and the configuration reloaded correctly.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify my trading bot is active after a deployment?

To verify your trading bot after a deployment, run a post-deploy check to confirm services are active, trades reach FILLED status, and configuration reloads occur. This produces a structured PASS/FAIL report with remediation steps.

Why does my trading bot stop trading after a config tweak?

Trading bots can stop trading after a config tweak if signals are filtered or silent errors occur during configuration reloads. Running a verification check surfaces these anomalies and logs issues in a concise report.

How do I troubleshoot silent failures in a deployed trading bot?

Troubleshoot silent failures in a deployed trading bot by running a verification workflow to detect anomalies, log issues, and confirm if trades are executed. It reports whether signals are filtered or errors occur.

Can I check if my bot trades are FILLED without manual log monitoring?

Yes, you can check if bot trades are FILLED without manual log monitoring by running an automated verification workflow. It validates bot activity, detects anomalies, and produces a concise verification report with actionable next steps.

What's the best way to confirm configuration reloads happen as expected in a trading bot?

The best way to confirm configuration reloads happen as expected is to run a post-deployment verification check. This validates that the bot is trading, applies after each config tweak, and reports if signals are filtered.

Do I need a specific healthcheck tool to validate bot activity post-deploy?

No specific external healthcheck tool is required. You can validate bot activity post-deploy by running the verification workflow, which checks service status, trade execution, and config reloads to produce a structured PASS/FAIL verdict.