Validate CYPHER V3 API health, live data, latency, and UI consistency.
npx skills add https://github.com/0xjc65eth/CYPHER-V3 --skill qa-engineer-0xjc65eth
Please help me install this Agent Skill. Skill: qa-engineer Source: https://github.com/0xjc65eth/CYPHER-V3/tree/main/skills/qa-engineer Command: npx skills add https://github.com/0xjc65eth/CYPHER-V3 --skill qa-engineer-0xjc65eth
Validates CYPHER V3 from the perspective of a professional trader by checking that all market data, ordinals, runes, fees, and trading UX are real, timely, and actionable rather than mocked or broken, ensuring traders can rely on the terminal for real-money decisions.
Start the CYPHER V3 server locally and run the QA protocol to validate API health, live market endpoints, latency, visual UI checks, and generate the QA report.
High-intent search queries and answers about installing and using this skill.
To validate live trading data and detect mocked feeds, you can run a QA protocol that verifies BTC price ranges, checks rune naming formats, and confirms fee estimates are plausible. This ensures the terminal provides real, actionable data for traders.
Testing API latency and health involves measuring endpoint response times against defined thresholds and verifying core endpoints return expected schemas. A dedicated QA protocol can automate these checks to produce a report with latency metrics and API availability.
Performing a pre-release QA check on ordinals and runes data feeds requires verifying that the API returns real collection data rather than mocks. The validation protocol checks API health, real-time price feeds, and rune naming formats to ensure data integrity.
Yes, you can automate UI consistency checks by applying a QA protocol that reviews a visual checklist for loading states, errors, and images. It validates critical flows like wallet connection and trading indicators to ensure UX reliability.
Yes, you need HTTP access to local endpoints to run a trading terminal QA report. The validation protocol requires connecting to local or staging deployments to verify server status, test API health, and measure latency thresholds.
Incorrect fee estimates or broken market data occur when APIs return mocked data or fail schema validation. Running a QA protocol detects these issues by validating real-data integrity, checking fee plausibility, and measuring endpoint availability.
redactedmemeProvide headless REST API access to multi-chain crypto wallet operations, trading, and DeFi features.
bradtaylorsfAnalyze code coverage, defect, performance, and process metrics for software quality reporting.
distribucionesfayosmoreno-sysValidate UI modifications for visual regression, compliance, and accessibility.
0xjc65ethValidate CYPHER V3 API routes for schema compliance and latency.
