Overview

This is a test fixture focused on validating the 64 character limit for skill names. It ensures that names exceeding the limit fail validation, preventing inconsistent catalogs and broken displays.

How This Skill Works

The skill metadata includes a name field. Validation checks the length against the 64 character limit and rejects any entry that exceeds it, returning an error to guide correction.

When to Use It

• Submitting a new skill to verify the 64 character name limit is enforced.
• Running automated validation tests in CI to catch regressions on long names.
• Debugging errors related to skill name length in the catalog UI or API.
• Performing batch imports to ensure long names are consistently rejected.
• Documenting the naming policy for contributors and skill creators.

Quick Start

1. Step 1: Create a test skill whose name exceeds 64 characters.
2. Step 2: Run the skill validation workflow to observe the failure.
3. Step 3: Shorten the name to 64 characters or fewer and resubmit.

Best Practices

• Enforce the 64 character limit at both client and server layers.
• Return a clear, actionable error message when the limit is exceeded.
• Include edge case tests with names just under and just over the limit.
• Define a recommended strategy for long names, such as concise aliasing.
• Keep the limit visible in UI hints and in your contribution guidelines.

Example Use Cases

• A new skill with a 70 character name fails validation and is rejected.
• API response contains a name_too_long error code and message.
• After shortening, the skill is accepted and shown in the catalog.
• Batch import reports mixed results with long names filtered out.
• User sees a tooltip indicating the 64 character limit when typing.

Frequently Asked Questions