# Validate Inputs Across Entry Points

Input validation often becomes inconsistent across forms, APIs, and business rules. This skill guides Claude, Codex, and Claude Code toward secure validation patterns.

## Install

```bash
npx skillstore add eis-its/global-validation
```

## Metadata

- Status: approved
- Slug: eis-its-global-validation
- Skillstore revision: r1
- Version status: missing
- Tree hash: 62f39705bdf516cbdfce66409b24ba91941e93aba603bda1695047558e380062
- Author: EIS-ITS
- GitHub username: EIS-ITS
- License: MIT
- Repository: https://github.com/EIS-ITS/vss-cli/tree/main/.claude/skills/global-validation
- Ref: 30c73eac2afe762f6aa9c4553158769369d47351
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/eis-its-global-validation
- Manifest: https://skillstore.pages.dev/api/skills/eis-its-global-validation/manifest

## Capabilities

- Guides server-side validation for forms, APIs, and external input.
- Promotes allowlist checks for accepted values, formats, and ranges.
- Encourages type checking and required-field validation before business logic.
- Covers input sanitization for SQL, XSS, and command injection prevention.
- Supports consistent validation errors for clear user feedback.
- Distinguishes security validation from client-side user experience checks.

## Use Cases

- Secure API Requests: Define validation checks for request parameters and payloads before endpoint logic runs.
- Improve Form Validation: Align client-side feedback with server-side enforcement for form submissions.
- Review Validation Coverage: Check whether validation is applied consistently across entry points and business rules.

## Prompt Templates

### Identify Validation Needs

```
Review this feature and list every input that needs validation. Separate security checks from user experience checks.
```

### Design Validation Rules

```
Create validation rules for these fields. Include required fields, type checks, ranges, formats, allowlists, and user-facing errors.
```

### Implement Consistent Validation

```
Update this code so validation runs server-side before business logic. Keep client-side validation for immediate feedback only.
```

### Audit Validation Security

```
Audit this workflow for missing validation, unsafe input handling, weak sanitization, and inconsistent error behavior across entry points.
```

## Limitations

- Does not include the referenced detailed validation standard inside the packaged skill.
- Does not provide framework-specific validation library code by itself.
- Requires project context to choose exact schemas, rules, and error formats.
- Does not replace security testing or penetration testing.

## Best Practices

- Validate on the server before business logic or persistence.
- Use allowlists for formats, ranges, enum values, and accepted identifiers.
- Keep validation errors clear without exposing internal implementation details.

## Anti Patterns

- Relying on client-side validation as the only enforcement layer.
- Using blocklists as the main defense against malicious input.
- Returning raw parser, database, or stack errors to users.

## Security Audit

- Audited at: 2026-07-05T15:39:25.08\+00:00
- Summary: The two static findings were determined to be false positives. The path traversal pattern appears only in a fixed Markdown reference, not executable file access. The system reconnaissance alert is a business-rule validation example and shows no system inspection behavior.

## Stats

- Views: 209
- Downloads: 10
- Favorites: 0
- Popularity score: 0