Effect Boundary Validation

Decode untrusted data once at ingress with Effect Schema (v4) and pass typed values downstream. Use for HTTP bodies, params and query strings, webhooks, RPC and message payloads, MCP tool arguments, env and config, JSON.parse, stored JSON or rows, third-party API responses, unsafe casts, or porting Zod/Valibot schemas.

23 stars 1 forksAI, LLMs & Agents

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jpoehnelt/skills --skill effect-boundary-validation
Manual install
git clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/effect-boundary-validation ~/.claude/skills/effect-boundary-validation

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Boundary validation

Decode untrusted data once, at the ingress, then pass the decoded type downstream. TypeScript types, `satisfies`, and `as` casts are not runtime validation. Assumes Effect v4 `Schema`, imported the way the repo's import policy says (the `effect` root or `effect/Schema`); see `effect` for errors and runners.

Repo facts (from AGENTS.md): where shared wire schemas live, retired schema libraries, safe-decode helpers, ast-grep boundary rules, the public error shape, and check and test commands.

## Inventory the boundary

Run `scripts/boundary-audit.sh [--ban MODULE]... [--rule RULE_ID]... [paths]` on the changed paths. It lists parse and cast sites, signature checks, and decode sites, fails on imports of any `--ban` module (for example `--ban zod --ban valibot`; a text search, so enforce a ban structurally with an ast-grep rule), and runs the named ast-grep rules when the repo has `sgconfig.yml`. For each change, name:

1. The ingress point (route, webhook, message or topic handler, RPC method, upstream response, env read, stored row).
2. The owning schema: shared wire schemas live in the contract package when several packages consume them; local-only shapes stay beside their consumer.
3. Checks that run before decoding: signature or MAC, bearer token or session, origin.
4. The decoded internal type.
5. What the caller sees on failure and what is logged.

## Policy: requests strict, responses tolerant
Read the full skill on GitHub

Details

Skill name
effect-boundary-validation
Path
effect-boundary-validation/SKILL.md
License
MIT
Repo updated
12 November 2026

FAQ

What does the Effect Boundary Validation skill do?

Decode untrusted data once at ingress with Effect Schema (v4) and pass typed values downstream. Use for HTTP bodies, params and query strings, webhooks, RPC and message payloads, MCP tool arguments, env and config, JSON.parse, stored JSON or rows, third-party API responses, unsafe casts, or porting Zod/Valibot schemas.

How do I install the Effect Boundary Validation skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill effect-boundary-validation. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Effect Boundary Validation popular?

It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.

Related skills

Agents Correct

23

jpoehnelt/skills

Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.

AI, LLMs & Agents

Agents Create Verification Skill

23

jpoehnelt/skills

Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.

AI, LLMs & Agents

Agents Reflect

23

jpoehnelt/skills

After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.

AI, LLMs & Agents

Eng Agent Dx CLI Scale

23

jpoehnelt/skills

A scoring scale for evaluating how well a CLI is designed for AI agents, based on the "Rewrite Your CLI for AI Agents" principles. Use when reviewing, designing, or comparing a CLI for agent use, or scoring its agent readiness.

AI, LLMs & Agents

Design Mobile Apps with Daisy

9

daisy-now/agent-skills

Design native mobile app screens with Daisy (daisy.now), an AI design agent with a canvas. Use when the user wants mobile screens or flows designed or mocked up (onboarding, settings, feeds, checkout), wants changes to screens in a Daisy project, or wants a Daisy screen as a PNG or as HTML. Mobile only, not web pages.

AI, LLMs & Agents

Jeffdean Mind

9

closedsi-engineering/JeffDean-Mind

Jeff Dean의 엔지니어링 사고방식으로 설계·코딩·리뷰를 수행한다. 시스템 설계, 아키텍처 결정, 성능 최적화, 분산 시스템, 확장성(스케일링), 지연시간(latency) 분석, 인프라 설계, 기술 선택, 코드 리뷰, 병목 분석, AI/ML 시스템 설계, 스타트업 기술 전략 관련 작업 시 사용한다. Triggers: "설계해줘", "아키텍처", "성능", "최적화", "확장", "스케일", "병목", "지연시간", "latency", "분산", "distributed", "design review", "백오브엔벨로프", "back-of-envelope", "제프 딘", "jeff dean", "capacity planning", "SLO", "p99".

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.