Overview

compatibility-too-long is a test fixture designed to reproduce a skill with a compatibility field that exceeds the 500-character limit. It helps verify that the validation layer rejects overlong metadata and surfaces clear errors. This ensures the platform enforces length constraints consistently.

How This Skill Works

The skill includes a compatibility attribute populated with a lengthy string. A maximum-length validator (500 characters) triggers a failure when the value goes beyond the limit, allowing test suites to confirm proper error handling and messaging.

When to Use It

• Validating the length limit of compatibility fields in skills
• Testing import/creation of skills with long metadata
• Ensuring error handling for invalid skill definitions
• Assessing UI or API behavior when field values are too long
• Verifying regression coverage for edge-case metadata length

Quick Start

1. Step 1: Load the compatibility-too-long skill fixture
2. Step 2: Run the validation/test suite enforcing the 500-character limit
3. Step 3: Verify a validation error is raised for the overlong compatibility value

Best Practices

• Validate all skill metadata length constraints, starting with compatibility
• Use this fixture in regression tests to catch regressions on length checks
• Prefer truncation or normalization only if your policy allows, otherwise reject
• Ensure error messages clearly indicate the field and limit breached
• Document the 500-character limit in contribution guidelines and tests

Example Use Cases

• A CI job fails with a message that the compatibility field is too long
• An import workflow rejects a skill due to a compatibility value exceeding the limit
• A test suite exercises edge cases for long metadata values
• A marketplace submission is blocked by an overlong compatibility field
• Admins review logs showing a length violation on the compatibility attribute

Frequently Asked Questions