home / skills / pproenca / dot-skills / invalid-name-uppercase

invalid-name-uppercase skill

safe

/tests/fixtures/invalid-name-uppercase

This skill detects invalid names containing uppercase letters and guides corrective naming to meet validation rules.

This is most likely a fork of the invalid-name-uppercase skill from pluk-inc

npx playbooks add skill pproenca/dot-skills --skill invalid-name-uppercase

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

188 B

---
name: Invalid-Name
description: This skill has an uppercase letter in the name which should fail validation.
---

# Invalid Name Skill

This skill has an uppercase letter in the name.

Overview

This skill is a small demonstration tool that highlights naming-validation rules for agent skills. It intentionally uses an uppercase character in its identifier to show how tooling and registries detect and report invalid names. The skill is lightweight and intended for testing validation pipelines and documentation examples.

How this skill works

The skill contains a minimal manifest and a single shell-based artifact that represents a skill package. Validation tooling inspects the skill name, compares it against allowed naming conventions (lowercase, hyphens, no spaces), and produces a clear failure if the name contains disallowed characters or uppercase letters. It can be used in CI to ensure name-format checks run consistently across submissions.

When to use it

To test continuous-integration name validation rules for agent skills.
When demonstrating how registries enforce lowercase, hyphenated naming conventions.
As an example in documentation or training about common packaging mistakes.
To verify tooling correctly reports invalid identifiers and returns actionable messages.
During code reviews to reproduce and clarify a reported validation failure.

Best practices

Keep skill names lowercase and use hyphens to separate words; avoid spaces and special characters.
Include validation checks in CI to catch naming issues early before publishing.
Provide clear error messages that state the naming rule and show a corrected example.
Use minimal example artifacts when testing validators to isolate naming errors from other failures.
Document the naming convention in contributor guides and templates.

Example use cases

A CI job that runs a name-format linter and needs a failing case to assert the linter works.
A tutorial showing contributors common mistakes and how to correct skill manifests.
A registry migration test that ensures older packages are flagged if they break current naming rules.
An automated report generator that samples packages and demonstrates validator output for errors.

FAQ

Why intentionally include an invalid name?

Including a deliberate invalid case helps validate tooling, ensures CI rules catch regressions, and provides a concrete example for contributors.

How should I fix the invalid name?

Rename the skill to all lowercase and use hyphens instead of spaces or uppercase letters, for example: invalid-name.