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
- northraystudio/marudatheir own version, first seen Oct 22, 2026
- ymd38/dev-skillstheir own version, first seen Oct 22, 2026
- TJM-NZ/claude-skillstheir own version, first seen Oct 11, 2026
- edu6565/claude-skillstheir own version, first seen Oct 11, 2026
- ChloeQcc/skillstheir own version, first seen Aug 20, 2026
- albertdobmeyer/openskill-forgetheir own version, first seen Apr 2, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- northraystudio/maruda★ 7same name
- ymd38/dev-skills★ 7same name
- ChloeQcc/skills★ 2same name
- albertdobmeyer/openskill-forge★ 1same name
- edu6565/claude-skills★ 0same name
- TJM-NZ/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- api-syncSkill
- archive-changeSkill
- auto-flowSkill
- build-reportSkill
- change-impact-reviewSkill
- code-review-auditSkill
- code-reviewSkill
- coverage-reportSkill
- data-logic-validationSkill
- data-risk-auditSkill
- dingtalk-notifySkill
- git-reviewSkill
- knowledge-opsSkill
- learning-engineSkill
- learning-feedbackSkill
- log-auditSkill
- offline-design-analysisSkill
- project-reviewSkill
- release-inspectionSkill
- report-insightsSkill
- requirement-analystSkill
- resource-bindSkill
- service-governance-auditSkill
- service-governance-changeSkill
- service-governance-diagnosisSkill
- service-management-log-analysisSkill
- sls-log-auditSkill
- test-reportSkill
- yapi-sync-interfaceSkill
- yuque-sync-designSkill
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
- Distinctive: line 12
Verify business logic, data integrity, and processing correctness.
“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.
Files
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
| Check | Description |
| Type Match | Field types match schema |
| Required Fields | All required fields present |
| Length Limits | String lengths within limits |
| Format | Dates, emails, phones valid |
Business Rules
| Check | Description |
| Calculations | Totals, averages correct |
| State Transitions | Valid state changes |
| Dependencies | Required relationships exist |
| Constraints | Business 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"
}
]
}
}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
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.

