strykr-qa-bot

What This Skill Does

The strykr-qa-bot is a specialized AI-powered quality assurance automation tool designed specifically for the Strykr finance dashboard. It bridges the gap between manual testing and automated deployment cycles, providing a robust testing framework for complex, data-heavy web interfaces. The skill comes pre-packaged with distinct test suites covering the entire Strykr ecosystem: homepage functionality, cryptocurrency signals, stock market analytics, real-time news feeds, economic events, and the core AI chat module. It is engineered to perform deep assertions, such as validating the presence of price charts within signal cards or checking the minimum character length of AI-generated financial analysis. By automating regression testing and site health monitoring, it ensures that every deployment to https://app.strykr.ai maintains strict quality standards.

Installation

To integrate this skill into your OpenClaw environment, use the following command in your terminal:

clawhub install openclaw/skills/skills/nextfrontierbuilds/strykr-qa-bot

Ensure that you have the web-qa-bot dependency installed, as the strykr-qa-bot relies on this foundational framework for browser orchestration. Configuration is handled via a simple strykr-qa.yaml file where you can define your base URL, browser execution preferences (headless vs. headed), and global timeouts.

Use Cases

This skill is ideal for DevOps engineers and frontend developers who need rapid feedback after pushing code changes. Key use cases include:

• Post-Deployment Validation: Running the full test suite immediately after a CI/CD build to ensure no regression in signal card rendering or API responsiveness.
• PRISM API Monitoring: Automated health checks for the PRISM infrastructure to ensure data feeds remain active.
• AI Response Auditing: Validating that the integrated financial AI consistently returns valid, high-quality responses during long-running stress tests.
• Regression Testing: Automated regression suites that run overnight to catch breaking changes in UI components.

Example Prompts

1. "OpenClaw, run the complete strykr-qa-bot test suite and provide me with a summary of any failures encountered."
2. "Use the QA bot to validate that the stock signals page is rendering correctly and check if the PRISM API is currently responding within normal latency limits."
3. "Strykr-qa-bot, perform a smoke test on the production build and generate a markdown report detailing any known issues with the signal modals."

Tips & Limitations

• Known Issues: The skill currently tracks specific bugs, such as the details-modal-empty issue and direct navigation failures for news and events. Be sure to check your logs against these known issues to avoid false alarms.
• Vibe-coding: This skill is compatible with modern AI coding assistants like Cursor and Claude; use it to iterate on test scripts by asking for new test cases for specific UI updates.
• Performance: For high-load testing, keep headless: true enabled in your configuration to maximize resource efficiency on your CI server.