data-validate

What This Skill Does

The data-validate skill provides a robust framework for verifying data integrity within your OpenClaw agent workflows. It focuses on syntactic validation for four critical data types: URLs, JSON structures against draft-07 schemas, email addresses per RFC 5322, and international phone numbers in E.164 format. By offloading these checks to the validate.agentutil.net service, you ensure that the inputs passed to your subsequent agent actions are clean, correctly formatted, and compliant with expected specifications. This reduces runtime errors and helps prevent malformed data from causing failures in downstream processes. Note that the service performs strictly structural analysis; it does not ping websites, verify the existence of email inboxes, or connect to telephone networks, ensuring a lightweight and privacy-conscious operation.

Installation

To integrate this utility into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/cutthemustard/data-validate Ensure you have the latest version of the ClawHub CLI installed to maintain compatibility with the API endpoints.

Use Cases

• Form Input Sanitization: Automatically validate user-submitted contact forms before forwarding the data to a CRM or database.
• Configuration Checks: Ensure that environment variables or configuration files provided as JSON meet specific schema requirements before the agent attempts to apply them.
• Link Verification: Check if provided URLs are well-formed before an agent attempts to crawl or summarize the content of the linked page.
• Communication Prep: Ensure that customer contact details meet international standards before initiating outreach sequences.

Example Prompts

1. "I have a list of email addresses from a survey; please check if they are formatted correctly before I import them."
2. "Validate this JSON object against the following schema: { "type": "object", "required": ["user_id"] } and let me know if it passes."
3. "Is this phone number +1 415 555 0199 in the correct E.164 format for my international API call?"

Tips & Limitations

• Consent is Mandatory: The tool processes data externally. Always confirm with the user before sending PII. The agent will prompt for consent, but as a best practice, initiate the request by stating: 'I am going to check this data using an external validation tool, do you consent?'
• Syntax Only: Remember that 'valid' does not mean 'existing'. A valid email syntax check does not mean the user actually owns that email address. It only confirms the characters follow the proper RFC standards.
• Usage Limits: Keep an eye on your usage; the free tier is capped at 10 queries per day. For higher volumes, ensure you are set up with the x402 protocol for paid tier access via USDC on Base.