home / skills / pluk-inc / skills / invalid-name-uppercase

invalid-name-uppercase skill

safe

This skill enforces consistent naming conventions by validating identifiers and rejecting names with uppercase letters to prevent validation failures.

npx playbooks add skill pluk-inc/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 intentionally uses an invalid name that includes an uppercase letter to demonstrate and test name validation behavior. It serves as a minimal, deterministic case that triggers repository or package name validation errors. Use it to observe how systems react to naming rule violations and to verify tooling that enforces naming policies.

How this skill works

The skill contains a simple shell-based project with a name that violates lowercase-only naming rules. It does not rely on complex logic; instead it exists to be scanned by validators, linters, CI pipelines, or cataloging tools. When run through a validation step, the uppercase character causes the project to fail automated name checks, producing reproducible failure output for debugging and tests.

When to use it

Test name-validation rules in catalogs, package registries, or CI pipelines
Demonstrate how tooling reports and surfaces naming errors
Validate automated publishing or deployment safeguards that block invalid names
Train developers or reviewers on repository naming conventions
Simulate failure cases in release automation and error-handling flows

Best practices

Enforce lowercase, hyphen-separated names in automation and pre-commit hooks
Add a validation step to CI to catch naming issues before publishing
Provide clear error messages that explain the naming rule and how to fix it
Include linting and name checks in developer onboarding and templates
Document naming conventions in contributing guides and templates

Example use cases

CI test that ensures name validation rejects this project and logs the expected error
Tooling demo showing how a registry or catalog blocks uploads with invalid names
Developer training exercise: find and fix the naming issue, then re-run validation
Build and verify a pre-commit hook that flags uppercase letters in project names
Integrate with a release pipeline to ensure invalid names prevent accidental publishing

FAQ

Why does this skill intentionally have an invalid name?

I created it to provide a guaranteed, reproducible failure for testing validators, CI rules, and training scenarios that expect naming errors.

How do I fix the name so it passes validation?

Rename the project to use only lowercase letters, digits, and allowed separators (typically hyphens). Update any references in metadata and CI configuration accordingly.