this-is-a-very-long-skill-name-that-exceeds-the-sixty-four-character-limit-set-by-the-standard

Validate skill names against the 64-character limit in SKILL.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imaginationeverywhere/clara-code --skill this-is-a-very-long-skill-name-that-exceeds-the-sixty-four-character-limit-set-by-the-standard-imaginationeverywhere
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: this-is-a-very-long-skill-name-that-exceeds-the-sixty-four-character-limit-set-by-the-standard
Source: https://github.com/imaginationeverywhere/clara-code/tree/main/packages/coding-agent/test/fixtures/skills/long-name
Command: npx skills add https://github.com/imaginationeverywhere/clara-code --skill this-is-a-very-long-skill-name-that-exceeds-the-sixty-four-character-limit-set-by-the-standard-imaginationeverywhere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce consistent naming for skills by validating that the 'name' in SKILL.md does not exceed the 64-character limit, preventing discovery and compatibility issues.

Core Features & Use Cases

  • Name-length validation: checks name field against the 64-character maximum.
  • Error signaling: reports violations with actionable remediation guidance.
  • Governance: supports linting and automated checks during skill creation or review.

Quick Start

Validate the skill name against the 64-character limit to ensure standard compliance.

Frequently Asked Questions about this-is-a-very-long-skill-name-that-exceeds-the-sixty-four-character-limit-set-by-the-standard

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

FAQPage Schema
How do I validate a skill name against the 64-character limit?

To validate a skill name, this tool checks the 'name' field in SKILL.md against the 64-character maximum, reporting violations with actionable remediation guidance to ensure standard compliance.

Why does my YAML frontmatter fail skill discovery checks?

YAML frontmatter fails skill discovery checks when the skill name exceeds the 64-character limit, violating frontmatter integrity constraints and causing compatibility issues across the repository.

What is the best way to lint skill names for standard compliance?

The best way to lint skill names for standard compliance is using automated validation checks during skill creation or review, which enforces name length constraints, uniqueness, and error signaling for violations.

How do I fix ultra-long skill name violations in my repository?

Fix ultra-long skill name violations by shortening the 'name' field in your SKILL.md YAML frontmatter to 64 characters or fewer, following the actionable remediation guidance provided by the validation error.

Can I use this validation for automated quality assurance in skill creation?

Yes, you can use this validation for automated quality assurance during skill creation and review, as it supports linting and automated checks to enforce frontmatter integrity and naming constraints.

What happens when a skill name exceeds the maximum length constraint?

When a skill name exceeds the maximum length constraint, the validation tool flags the violation and reports it with actionable remediation guidance to prevent discovery and compatibility issues.