Validating Inputs
Check all external inputs for validity - garbage in, nothing out, never garbage out
Install
npx skills add obra/clank --skill Validating Inputsgit clone --depth 1 https://github.com/obra/clank.git /tmp/clank
mkdir -p ~/.claude/skills
cp -r /tmp/clank/skills/coding/validating-inputs ~/.claude/skills/Validating-InputsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Validating Inputs ## Overview Professional-grade software never outputs garbage regardless of what it receives. "Garbage in, garbage out" is the mark of sloppy, insecure code. **Core principle:** Check all data from external sources. Validate all routine parameters from untrusted sources. Decide consciously how to handle invalid data. **Modern standard:** "Garbage in, nothing out" OR "Garbage in, error message out" OR "No garbage allowed in" **Violating the letter of this rule is violating the spirit of defensive programming.** ## When to Use **Always use when writing functions that receive:** - User input (forms, command-line args, uploaded files) - External API responses - Database query results - File contents - Network data - Configuration files - Any data from outside your direct control **Warning signs you need this:** - Function assumes inputs are valid - No validation beyond empty/null checks - No assertions documenting assumptions - Spec mentions constraints but code doesn't check them - Silent failures or wrong results with bad data - Security vulnerabilities (injection, overflow, etc.) - Functions accept any input without question **Don't skip when:** - "Inputs will always be valid" (they won't) - "Validation happens elsewhere" (defense in depth - check anyway) - "It's just internal code" (today's internal is tomorrow's API) - Under time pressure (validation prevents longer debugging) ## The Two-Level Defense
Details
- Skill name
Validating Inputs- Repository
- obra/clank
- Path
skills/coding/validating-inputs/SKILL.md- Repo updated
- 9 October 2025
FAQ
What does the Validating Inputs skill do?
Check all external inputs for validity - garbage in, nothing out, never garbage out
How do I install the Validating Inputs skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add obra/clank --skill Validating Inputs. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Validating Inputs popular?
It lives in obra/clank, which has 43 GitHub stars and 26 forks.
Related skills
Gardening Skills Wiki
43obra/clank
Maintain skills wiki health - check links, naming, cross-references, and coverage
Remembering Conversations
43obra/clank
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
Brainstorming Ideas Into Designs
43obra/clank
Interactive idea refinement using Socratic method to develop fully-formed designs
Zero in
62ElliotJLT/Claude-Skill-Potions
Before searching a codebase, forces you to zero in on the target: what exactly are you looking for, what would it look like, where would it live, what else might it be called. Activates on "find", "where is", "search for", or when exploration begins. Prevents grep-and-pray.
Trace It
62ElliotJLT/Claude-Skill-Potions
Before modifying shared code (utilities, types, configs, base classes), traces all callers and dependents first. Activates when editing files in shared/, utils/, lib/, or anything imported by 3+ files. Prevents "fixed one thing, broke three others.
Client Compatibility
45Azure-Samples/agent-skills-dotnet-demo
Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.