checker

What This Skill Does

Checker is the final gatekeeper for the OpenClaw AI agent ecosystem. Its primary function is to conduct rigorous QA and peer reviews on deliverables generated by other agents—such as Scribe, Scout, or Pixel—before they are released to Honey B or published publicly. Checker ensures that everything passing through the system meets strict internal quality standards regarding brand voice, factual accuracy, and technical formatting.

Unlike content generation agents, Checker is strictly evaluative. It does not write, research, or edit; it reviews existing artifacts against a comprehensive checklist and issues a binary verdict: APPROVED or NEEDS REVISION. By enforcing this review layer, Checker prevents poor-quality, off-brand, or factually incorrect content from ever reaching production.

Installation

To add Checker to your OpenClaw agent instance, run the following command in your terminal:

clawhub install openclaw/skills/skills/honeybee1130/checker

Use Cases

Use Checker for high-stakes deliverables, including:

1. Content Verification: Checking Scribe-generated posts for brand voice, proper hook structure, and lack of emojis or em dashes.
2. Research Validation: Verifying that research from Scout contains valid, current, and unbiased sources before that information is integrated into a larger report.
3. Outreach Quality: Auditing personalized DMs and emails to ensure the tone is professional yet authentic, and that the call-to-action is optimized for low-friction responses.
4. Visual Consistency: Ensuring that assets created by Pixel feature the correct brand elements and are properly sized for their target platforms.

Example Prompts

1. "Checker, please review the latest blog post draft in artifacts/scribe/ and let me know if it meets the hook and voice guidelines for the Honey B brand."
2. "I need a QA report on the research summary from Scout regarding the latest market trends; check the links and verify that all claims are supported."
3. "Run a full peer review on this draft outreach email meant for potential collaborators. Use the outreach checklist and save the verdict to artifacts/checker/."

Tips & Limitations

• Be Specific: Always point to the artifact and the agent source to help Checker navigate the workspace effectively.
• Respect the Boundaries: Remember that Checker is not a writing assistant. Do not ask it to 'fix' errors; ask it to identify them so you can route the feedback back to the original authoring agent.
• Binary Verdicts: Do not expect Checker to provide 'maybe' feedback. It is designed to hold a high standard. If a deliverable fails, treat the NEEDS REVISION report as a direct set of instructions to improve the asset before the next submission.