agentleFS
Eleven-MEleven-M/flowmind/skills/data-validation/SKILL.md

data-validation

Skill1 starsChanged 3 months agoMITView on GitHub

Data validation and logic verification skill for FlowMind. Verify business logic, data integrity, and processing correctness.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify business logic, data integrity, and processing correctness.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Data Validation Skill

Verify business logic, data integrity, and processing correctness.

Features

📊 Data Integrity

  • Referential integrity checks
  • Data type validation
  • Range and constraint validation
  • Null/required field checks

🔄 Business Logic

  • Workflow validation
  • Calculation verification
  • State machine validation
  • Rule engine checks

📈 Data Quality

  • Duplicate detection
  • Consistency checks
  • Completeness analysis
  • Accuracy verification

Trigger Patterns

"数据验证", "data validation", "validate"
"逻辑验证", "logic verification"
"数据检查", "data check"
"业务逻辑", "business logic"
"数据质量", "data quality"

Output Format

┌─────────────────────────────────────────────────────┐
│ Data Validation Report                              │
├─────────────────────────────────────────────────────┤
│ Table: {table_name}                                 │
│ Records: {count}                                    │
├─────────────────────────────────────────────────────┤
│ ✓ Passed: {pass_count}                              │
│ ✗ Failed: {fail_count}                              │
│ ⚠ Warnings: {warn_count}                           │
├─────────────────────────────────────────────────────┤
│ Issues:                                             │
│ • {issue_description}                               │
│ • {issue_description}                               │
└─────────────────────────────────────────────────────┘

Validation Types

Schema Validation

CheckDescription
Type MatchField types match schema
Required FieldsAll required fields present
Length LimitsString lengths within limits
FormatDates, emails, phones valid

Business Rules

CheckDescription
CalculationsTotals, averages correct
State TransitionsValid state changes
DependenciesRequired relationships exist
ConstraintsBusiness rules satisfied

Learning Integration

This skill supports FlowMind learning:

  • Validation Rules: Learns your business rules
  • Error Tolerance: Learns acceptable error rates
  • Output Format: Learns preferred report format
User: "金额不能为负数"
FlowMind: ✓ Learned: Amount must be non-negative

User: [Next validation]
FlowMind: [Checks for negative amounts]

Examples

Example 1: Order Validation

User: 验证订单数据的正确性

FlowMind:
┌─────────────────────────────────────────────────────┐
│ Order Validation Report                             │
├─────────────────────────────────────────────────────┤
│ Table: orders                                       │
│ Records: 1,000                                      │
├─────────────────────────────────────────────────────┤
│ ✓ Passed: 985                                       │
│ ✗ Failed: 15                                        │
│ ⚠ Warnings: 5                                       │
├─────────────────────────────────────────────────────┤
│ Critical Issues:                                    │
│ • 10 orders with negative total                     │
│ • 5 orders with missing customer_id                 │
├─────────────────────────────────────────────────────┤
│ Warnings:                                           │
│ • 5 orders with future dates                        │
└─────────────────────────────────────────────────────┘

Example 2: Calculation Verification

User: 验证订单金额计算是否正确

FlowMind:
┌─────────────────────────────────────────────────────┐
│ Calculation Verification                            │
├─────────────────────────────────────────────────────┤
│ Formula: subtotal + tax = total                     │
│ Records Checked: 500                                │
├─────────────────────────────────────────────────────┤
│ ✓ Correct: 498 (99.6%)                              │
│ ✗ Incorrect: 2 (0.4%)                               │
├─────────────────────────────────────────────────────┤
│ Errors:                                             │
│ • Order #1234: Expected 110.00, Got 100.00          │
│ • Order #5678: Expected 55.50, Got 55.00            │
└─────────────────────────────────────────────────────┘

Configuration

{
  "data-validation": {
    "rules": {
      "required": ["id", "created_at", "status"],
      "types": {
        "id": "integer",
        "email": "email",
        "phone": "phone"
      },
      "ranges": {
        "age": { "min": 0, "max": 150 },
        "amount": { "min": 0 }
      }
    },
    "business": {
      "calculations": [
        {
          "name": "order_total",
          "formula": "subtotal + tax = total",
          "tolerance": 0.01
        }
      ]
    }
  }
}

Custom Rules

Define Custom Validation

{
  "data-validation": {
    "customRules": [
      {
        "name": "valid_email",
        "field": "email",
        "pattern": "^[\\w.-]+@[\\w.-]+\\.\\w+$",
        "message": "Invalid email format"
      }
    ]
  }
}

Business Rule Validation

{
  "data-validation": {
    "businessRules": [
      {
        "name": "order_amount",
        "condition": "amount > 0",
        "message": "Order amount must be positive"
      }
    ]
  }
}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.