bad-bool-skill

Validate boolean inputs and reject non-boolean types when coercion is disabled.

376|31|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/avifenesh/agnix --skill bad-bool-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bad-bool-skill
Source: https://github.com/avifenesh/agnix/tree/main/tests/fixtures/invalid/skills/string-boolean-disable
Command: npx skills add https://github.com/avifenesh/agnix --skill bad-bool-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables reliable testing of boolean validation logic to ensure inputs are correctly accepted or rejected and to prevent incorrect guarantees in software behavior.

Core Features & Use Cases

  • Boolean input validation: Verify that true/false values are handled correctly across modules.
  • Error handling: Provide clear feedback for invalid types (e.g., strings, numbers) when coercion is not desired.
  • Use Case: Validate API payloads or form data to ensure booleans are preserved and mis-typed data is rejected.

Quick Start

Provide a boolean value to test and run the validator to verify correct handling of true and false.

Frequently Asked Questions about bad-bool-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate boolean inputs in an API payload without coercing strings or numbers?

Boolean input validation rejects non-boolean types when coercion is disabled, ensuring API payloads preserve true/false values and reject mis-typed data like strings or numbers. This prevents incorrect guarantees in software behavior.

What is the best way to test boolean validation logic for edge cases in data processing pipelines?

Testing boolean validation logic involves providing true and false values to a validator to verify correct handling. It ensures inputs are correctly accepted or rejected, preventing incorrect guarantees in data processing pipelines.

How does type safety validation handle invalid boolean inputs in form data?

Type safety validation for boolean inputs provides clear error messages for invalid types in form data. It ensures true/false values are handled correctly across modules and rejects non-boolean types when coercion is not desired.

Can I use boolean validation to check edge cases where API schemas receive mis-typed data?

Yes, boolean validation checks edge cases by verifying that API schemas correctly handle true and false values. It rejects mis-typed data such as strings or numbers and provides clear feedback for invalid inputs.

Why should I disable type coercion when validating boolean values for software quality?

Disabling type coercion during boolean validation ensures strings or numbers are rejected rather than converted, maintaining software quality. It provides clear error reporting for invalid inputs and prevents incorrect behavioral guarantees.