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.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "global-validation" from https://skillstore.io/skills/eis-its-global-validation.md and its manifest at https://skillstore.io/api/skills/eis-its-global-validation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "global-validation". A payment endpoint accepts amount, currency, and account identifier.
Expected outcome:
Validate amount as a positive decimal within allowed limits. Allowlist supported currencies. Verify account identifier format before balance checks.
Using "global-validation". A signup form validates email only in the browser.
Expected outcome:
Move email format and required-field checks to the server. Keep browser validation for faster feedback, but do not trust it.
Using "global-validation". A search field is passed into a database query.
Expected outcome:
Limit length, normalize expected characters, and use safe query parameters. Return a clear validation error for unsupported input.
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.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/eis-its-global-validation/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/eis-its-global-validation?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/eis-its-global-validation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/eis-its-global-validation/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/eis-its-global-validation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>EIS-ITS. (2026). global-validation security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/eis-its-global-validation/audits/9@techreport{eis-its-eis-its-global-validation-2026,
author = {EIS-ITS},
title = {global-validation security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/eis-its-global-validation/audits/9},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "global-validation security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "EIS-ITS"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/eis-its-global-validation/audits/9"
identifiers:
- type: other
value: "skillstore:eis-its-global-validation:audit:9"
description: "Skillstore immutable audit report identifier"
Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
eis-its-global-validation
2026-08-21
devanb-global-validation
2026-08-21
Define validation checks for request parameters and payloads before endpoint logic runs.
Align client-side feedback with server-side enforcement for form submissions.
Check whether validation is applied consistently across entry points and business rules.
Review this feature and list every input that needs validation. Separate security checks from user experience checks.
Create validation rules for these fields. Include required fields, type checks, ranges, formats, allowlists, and user-facing errors.
Update this code so validation runs server-side before business logic. Keep client-side validation for immediate feedback only.
Audit this workflow for missing validation, unsafe input handling, weak sanitization, and inconsistent error behavior across entry points.
Author
EIS-ITSLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
30c73eac2afe762f6aa9c4553158769369d47351
Maintenance freshness
7/18/2026
Usage
6 downloads · 209 views
File structure
📄 SKILL.md
Build Reusable Frontend Components
Frontend teams need consistent component structure across frameworks. This skill guides Claude, Codex, and Claude Code to design focused, reusable UI components.
Improve Frontend Accessibility
Frontend teams often miss keyboard, semantic, and screen reader requirements during routine UI work. This skill guides Claude, Codex, and Claude Code to apply accessibility checks while creating or editing interfaces.
Apply Consistent Coding Style
Inconsistent code slows reviews and makes maintenance harder. This skill gives Claude, Codex, and Claude Code clear rules for readable, consistent code.
Write Focused Behavior Tests
Teams often add brittle tests that mirror implementation details instead of user behavior. This skill guides Claude, Codex, and Claude Code to write focused tests for critical workflows.
Build Consistent Frontend CSS
Frontend styling often drifts across files, components, and frameworks. This skill guides Claude, Codex, and Claude Code toward consistent CSS methods and design tokens.
Improve Application Error Handling
Inconsistent error handling can hide failures and confuse users. This skill guides Claude, Codex, and Claude Code toward clear exceptions, validation, cleanup, and recovery paths.
Protect Next.js Auth Routes
by AayushBaniya2006
Authentication changes often fail when teams mix session APIs and route guards. This skill guides Claude, Codex, and Claude Code toward the project helpers for secure access control.
Build Secure Backend Services
by sickn33
Backend flaws can expose data, accounts, and infrastructure. This skill guides secure implementation and review using established defensive patterns.
Review Web App Security Before Release
by sickn33
Security issues often appear when teams add authentication, APIs, payments, uploads, or sensitive data flows. This skill provides a focused checklist and review prompts for finding common web application risks before deployment.
Plan API Security Testing
by sickn33
API reviews can miss authorization flaws, unsafe inputs, weak rate limits, and exposed errors. This skill organizes authorized REST and GraphQL testing into seven focused phases.
Build Claude Code Agents
by C0ntr0lledCha0s
Creating reliable AI agents requires clear schemas, safe tools, and repeatable review steps. This skill guides agent design, validation, migration, and maintenance for Claude Code workflows.
Create Effective AI Skills
by 89jobrien
Building reusable AI skills is hard when structure, resources, and validation rules are unclear. This skill provides a practical workflow for designing, writing, validating, and packaging skills.