qa-gate
Final quality validation gate for any artifact before human review. Run this skill on documents, skills, PRDs, blog posts, or code artifacts to validate factual accuracy, tone consistency, completeness, structural integrity, operational soundness, and sensitive data handling. Use when you need to "QA gate this", "validate before publish", run a "final check", perform "quality validation", proofread this, fact-check this, or otherwise validate, QA, or quality-gate an artifact before review, release, or publication.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/bloodandeath/keats-qa-gateWhat This Skill Does
The qa-gate skill serves as the ultimate quality assurance layer for the OpenClaw agent ecosystem. Designed as a non-negotiable release gate, it ensures that any artifact—ranging from complex PRDs and code implementations to blog posts and technical documentation—is rigorously vetted before reaching human eyes. Rather than acting as a code review tool, qa-gate operates as a final, high-fidelity checkpoint that evaluates content across six critical dimensions: Factual Accuracy, Tone Consistency, Completeness, Structural Integrity, Operational Soundness, and Sensitive Data Handling. By enforcing these standards, it guarantees that all outputs presented to the principal are professional, secure, and ready for publication.
Installation
To integrate this skill into your workflow, execute the following command in your terminal:
clawhub install openclaw/skills/skills/bloodandeath/keats-qa-gate
Use Cases
- Pre-Publication Review: Use this before pushing content to ClawHub or Gumroad to ensure high quality.
- PRD Validation: Automatically run this after any PRD generation loop to catch missing sections or placeholders.
- Technical Documentation: Verify that code blocks, command sequences, and API references are valid and error-free.
- Sensitive Content Scrubbing: Use the sensitive data check feature to ensure no private keys, tokens, or personal identifiers are accidentally included in public-facing artifacts.
- High-Stakes Projects: Utilize the optional
--dualflag to perform a redundant, cross-model verification for critical business documents.
Example Prompts
- "QA gate this draft PRD for the new marketing engine and let me know if it's ready to share with the team."
- "Run a final quality validation on this blog post. Make sure the tone is consistent and check for any placeholder text."
- "Please perform a quality gate on these technical instructions. I need to be 100% sure the API commands are correct and no sensitive data is present before I release this to our users."
Tips & Limitations
- Do not skim: The skill requires the full document to function effectively; ensure the agent has access to the complete file content.
- Use
--dualwisely: While highly accurate, the dual-model mode increases token latency and cost. Reserve it for high-stakes content. - Not a Code Reviewer: While it validates the operational soundness of commands, it does not replace a deep-dive security or performance audit for complex codebases.
- Iterate: If the gate returns a FAIL, treat the output as a checklist. Fix all CRITICAL and MAJOR issues before attempting to present the work to the principal.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-bloodandeath-keats-qa-gate": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read
Related Skills
design-engineering
Orchestrate iterative design and frontend engineering work through research, planning, sub-agent execution, and validation loops. Use when a visual/UI task requires multiple iterations, when the first implementation needs refinement based on feedback, when choosing between competing technical approaches (Canvas vs SVG vs CSS), or when coordinating sub-agents on design-heavy work. Covers animation architecture decisions, progressive enhancement patterns, performance-aware rendering choices, and the research→plan→execute→validate workflow. Complements frontend-design (which handles aesthetics) by adding engineering discipline, iteration management, and technical decision-making.
agent-cost-monitor
Real-time token usage and cost tracking across all your OpenClaw agents — alerts, budgets, and optimization tips
web-monitor
Monitor web pages for content changes and get alerts. Track URLs, detect updates, view diffs. Use when asked to watch a website, track changes on a page, monitor for new posts/content, set up page change alerts, or check if a site has been updated. Supports CSS selectors for targeted monitoring.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
code-reviewer
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Default behavior is a single-model adversarial review that identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Supports an optional `--dual` mode for heavier cross-model iterative review when deeper scrutiny is worth the added cost and latency. Use when users ask to "critically review my code", "critically review" code or a PR, "critique my code", "find issues in my code", "find issues" in code, ask "what's wrong with this code", ask to "review this code", "critique my PR", say "double review this", or request a "cross-model review". Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required Changes, Suggestions, Noted) and specific, actionable recommendations.