Qa Verify
Run scenario-based verification and regression checks for changed behavior, user flows, and bug fixes before delivery. Use after implementation or review whenever behavior changed or user-visible quality matters.
Install
$ agentstack add skill-keithhegit-ultra-orchestration-qa-verify ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-keithhegit-ultra-orchestration-qa-verify) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
QA Verify
Validate behavior, not just code shape.
Treat QA as two-mode verification:
- Static baseline: reason over code, diffs, existing tests, and available evidence
- Dynamic verification: run tests or commands when the host environment allows it
Do not assume browser automation exists unless the environment explicitly provides it.
Check
- Happy path
- Error path
- Regression risk
- User-visible behavior
- Follow-up tests that should exist even if they are not added now
Failure handling
- If behavior is wrong but the plan is still valid, send the work back to
Execute. - If QA reveals a deeper architecture or requirement flaw, send the work back to
Plan.
Output
Return:
- scenarios exercised
- evidence collected
- pass or fail status
- residual risks
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: keithhegit
- Source: keithhegit/ultra-orchestration
- License: Apache-2.0
- Homepage: https://keithhegit.github.io/ultra-orchestration/docs.html
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.