Skills type-safety-validation
๐Ÿ“ฆ

type-safety-validation

v1.0.0 Content revision r2 Medium Risk โš™๏ธ External commands๐ŸŒ Network access๐Ÿ“ Filesystem access

Build Type-Safe TypeScript Applications

Static types alone cannot verify data arriving at application boundaries. This skill shows how Zod, tRPC, Prisma, and TypeScript connect compile-time types with runtime validation.

Supports: Claude Codex Code(CC)
๐Ÿ“Š 72 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "type-safety-validation" from https://skillstore.io/skills/ariegoldkin-type-safety-validation.md and its manifest at https://skillstore.io/api/skills/ariegoldkin-type-safety-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.

Test it

Using "type-safety-validation". Validate a registration form with email, age, and role fields.

Expected outcome:

A Zod schema validates email format, age limits, and allowed roles. The result includes an inferred form type and field-level error guidance.

Using "type-safety-validation". Design a typed endpoint that loads a user by identifier.

Expected outcome:

The proposed procedure validates the identifier before querying. It explains nullable results, client inference, authorization requirements, and safe error handling.

Using "type-safety-validation". Review a JavaScript service before a strict TypeScript migration.

Expected outcome:

The review prioritizes external inputs, database results, unchecked indexes, and broad any types. It proposes phased compiler changes and boundary validation.

Security Audit

Medium Risk
v10 โ€ข 7/23/2026 Open versioned report

All 36 static findings are false positives caused by Markdown syntax, TypeScript examples, sample URLs, relative imports, validation chains, and ordinary identifiers. One medium semantic issue remains: the examples expose database reads and writes without authentication or authorization.

1
Files scanned
326
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Medium
Unauthenticated Read and Write Procedures
The examples expose user lookup and post creation through procedures with no authentication or authorization checks. Adoption as shown can permit unauthorized reads and writes.
The first example uses a direct t.procedure, and the second explicitly uses publicProcedure for a database write. Neither example includes access control.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/ariegoldkin-type-safety-validation/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/ariegoldkin-type-safety-validation/security.svg)](https://skillstore.io/skills/ariegoldkin-type-safety-validation?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/ariegoldkin-type-safety-validation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/ariegoldkin-type-safety-validation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/ariegoldkin-type-safety-validation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

AI Agent Hub. (2026). type-safety-validation security audit report (audit version 10) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/ariegoldkin-type-safety-validation/audits/10

BibTeX citation

@techreport{ai-agent-hub-ariegoldkin-type-safety-validation-2026, author = {AI Agent Hub}, title = {type-safety-validation security audit report (audit version 10)}, institution = {Skillstore}, year = {2026}, number = {10}, url = {https://skillstore.io/skills/ariegoldkin-type-safety-validation/audits/10}, note = {Author version 1.0.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "type-safety-validation security audit report (audit version 10)" version: "1.0.0" type: report authors: - name: "AI Agent Hub" date-released: "2026-07-23" url: "https://skillstore.io/skills/ariegoldkin-type-safety-validation/audits/10" identifiers: - type: other value: "skillstore:ariegoldkin-type-safety-validation:audit:10" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
100
Maintainability
87
Content
70
Community
83
Spec Compliance

What You Can Build

Validate API Boundaries

Design typed request schemas and predictable validation errors for new backend procedures.

Share Types Across the Stack

Connect server procedures to typed React clients without duplicating request and response interfaces.

Strengthen an Existing TypeScript Project

Identify unsafe boundaries and plan stricter validation, compiler settings, and database access patterns.

Try These Prompts

Create a Validation Schema
Create a Zod schema for {data shape}. Include validation rules, an inferred TypeScript type, and safeParse error handling.
Design a Typed Procedure
Design a tRPC procedure for {operation}. Validate its input with Zod and describe the inferred client types and expected errors.
Review a Type-Safety Boundary
Review {boundary or workflow} for unsafe inputs, any usage, missing checks, and type duplication. Recommend focused Zod and TypeScript improvements.
Plan End-to-End Type Safety
Plan a migration of {application} to strict TypeScript, Zod, tRPC, and Prisma. Prioritize boundaries, compatibility risks, tests, and incremental delivery.

Best Practices

  • Validate untrusted data at every external boundary and return clear, structured errors.
  • Infer types from shared schemas to reduce duplicated declarations and drift.
  • Enable strict compiler checks gradually and protect each migration step with tests.

Avoid

  • Do not treat compile-time types as proof that runtime data is valid.
  • Do not expose database procedures without authentication, authorization, and ownership checks.
  • Do not use broad any types or unchecked casts to silence migration errors.

Frequently Asked Questions

Does this skill run type checks on my project?
No. It provides implementation guidance and examples, but it does not execute compilers or inspect files automatically.
Can I use Zod without tRPC or Prisma?
Yes. Each library can be used independently, although the examples show how they support one typed application flow.
Does TypeScript replace runtime validation?
No. TypeScript checks source code, while runtime validation verifies values from users, networks, files, and other external systems.
Are the examples production ready?
No. Add authentication, authorization, logging controls, error handling, tests, rate limits, and environment-specific configuration.
Which TypeScript settings are recommended?
Start with strict mode and consider noUncheckedIndexedAccess. Adopt additional checks according to project compatibility and migration cost.
How should validation errors reach users?
Map schema issues to stable field or request errors. Avoid exposing internal database details, stack traces, or sensitive input values.

Developer Details

License

MIT

Author version

v1.0.0

Skillstore revision

r2

Ref

89edfdc710d0846129dcee6a929477b04f08052c

Maintenance freshness

7/24/2026

Usage

8 downloads ยท 175 views

File structure

๐Ÿ“„ SKILL.md