invalid-compatibility-too-long
Scannednpx machina-cli add skill sven1103-agent/sklint/invalid-compatibility-too-long --openclawFiles (1)
SKILL.md
604 B
Body
Source
git clone https://github.com/sven1103-agent/sklint/blob/main/testdata/invalid-compatibility-too-long/SKILL.mdView on GitHub Overview
This skill entry models a submission where the compatibility field is too long and invalid. It highlights how length validation blocks imports that exceed allowed limits, preventing bad data from entering the registry.
How This Skill Works
A validation step checks the length of the compatibility field during skill submission. If the value is longer than the permitted limit, the system rejects the skill and returns a validation error.
When to Use It
- When a skill submission triggers a compatibility length validation error.
- During data migrations or test data generation when compatibility values may overflow limits.
- While debugging the validation pipeline or registry integration for skills.
- When auditing data quality and enforcing field length constraints.
- When creating documentation or samples that demonstrate invalid input.
Quick Start
- Step 1: Identify the compatibility field's max length from docs or schema.
- Step 2: Shorten or truncate the value to fit within the limit and consider concise encoding.
- Step 3: Re-submit and verify the skill is accepted or provide a meaningful error message if still invalid.
Best Practices
- Enforce a defined max length on the compatibility field in UI and API.
- Validate length on both client and server sides before submission.
- Provide clear error messages that indicate the max allowed length.
- Use concise compatibility values or encode data to fit the limit.
- Write tests that cover boundary conditions around the max length.
Example Use Cases
- Submitting a skill with a 1,000+ character compatibility field fails with a length-validation error.
- Migrating legacy data where compatibility text exceeded current limits requires truncation.
- An automated data generator creates oversized compatibility strings that get rejected.
- A regression test flags long compatibility strings not properly truncated in imports.
- An import pipeline logs a 'compatibility too long' validation message during ingest.
Frequently Asked Questions
Add this skill to your agents