invalid-version-type

Version field validation enforces string-type requirements through schema checks. Non-string values like numbers (123) are rejected with actionable error reporting during skill metadata loading and validation.

Non-string version values trigger validation failure. The schema detects type mismatches and produces clear error messages, preventing skill loading until the version field is corrected to a string type.

Version fields require string type to ensure consistent metadata parsing and prevent type-mismatch errors during skill validation. String format enables proper version comparison and semantic versioning support.

No, version must be a string type. Numeric values fail validation with type-check errors. Use quoted strings like "1.0.0" instead of unquoted numbers.

Use this test skill with intentionally non-string version values to verify validators detect type mismatches. It confirms schema strictness and error reporting during skill loading.