home / skills / pproenca / dot-skills / invalid-name-consecutive-hyphens

invalid-name-consecutive-hyphens skill

safe

/tests/fixtures/invalid-name-consecutive-hyphens

This skill detects invalid skill names containing consecutive hyphens and enforces proper naming conventions to ensure robust repository validation.

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

npx playbooks add skill pproenca/dot-skills --skill invalid-name-consecutive-hyphens

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

Files (1)

SKILL.md

189 B

---
name: invalid--name
description: This skill has consecutive hyphens in the name which should fail validation.
---

# Invalid Name Skill

This skill has consecutive hyphens in the name.

Overview

This skill demonstrates a naming validation failure: its identifier contains consecutive hyphens. It is intentionally crafted to fail schema or registry checks that enforce name format rules. The skill exists to help test tooling and CI pipelines that validate agent skill metadata.

How this skill works

The skill metadata uses an invalid name with consecutive hyphens, which violates common name-format rules (e.g., allowed characters, no repeated separators). Validation tools will detect the malformed identifier and return an error or reject the package. It does not provide runtime logic beyond serving as a test artifact for name-validation flows.

When to use it

Testing registry or schema validation that enforces name format rules
Simulating error handling in CI pipelines that publish or lint skills
Demonstrating best-practice naming rules in documentation or training
Verifying automated tooling reports and developer feedback for metadata issues
Including in QA suites that ensure consistent metadata across many skills

Best practices

Choose names with single separators (use single hyphens or underscores, not consecutive ones)
Follow the registry or schema naming conventions exactly (allowed characters, length limits)
Run metadata linting locally and in CI before publishing
Provide clear, actionable error messages when validation fails
Keep identifiers readable, stable, and descriptive of the skill purpose

Example use cases

A CI job that verifies skill metadata rejects this package and surfaces the name-format error
A documentation example showing what a validation failure looks like and how to fix it
A teaching exercise for new contributors on how to craft valid skill identifiers
A test case for a registry UI that highlights invalid fields in metadata

FAQ

Why does the name fail validation?

The name contains consecutive hyphens which most schemas treat as an invalid pattern or repeated separator; registries typically require single separators and restrict certain characters.

How do I fix this issue?

Rename the skill to remove consecutive hyphens (e.g., replace "invalid--name" with "invalid-name" or another valid identifier) and re-run validation.