wrong-name-here

Name: wrong-name-here
Availability: InStock
Author: Chancetop

Compare SKILL.md frontmatter name against the containing directory name.

18|1|Updated Nov 7, 2024

Search Tags:#testing #yaml #metadata #lint #ci #skill-validation

Ready to run

npx skills add https://github.com/chancetop-com/core-ai --skill wrong-name-here

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wrong-name-here
Source: https://github.com/chancetop-com/core-ai/tree/main/core-ai/src/test/resources/skills/invalid-name
Command: npx skills add https://github.com/chancetop-com/core-ai --skill wrong-name-here

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures the declared skill name in SKILL.md matches its containing directory to prevent discovery, indexing, and deployment errors in skill registries and CI pipelines.

Core Features & Use Cases

Name Consistency Validation: Compares the SKILL.md frontmatter name field against the directory name and flags discrepancies.
CI and Pre-commit Integration: Runs as a lightweight check during continuous integration or as a pre-commit hook to catch naming issues early.
Developer QA: Helps maintainers and contributors avoid broken references and documentation mismatches in multi-skill repositories.

Quick Start

Run a skill validation that compares the SKILL.md name field with its containing directory and reports any mismatches.

Frequently Asked Questions about wrong-name-here

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

FAQPage Schema

How do I validate that a SKILL.md name matches its directory during CI?▼

To validate skill name consistency in CI, you compare the declared name field in the SKILL.md YAML frontmatter against the containing directory path to flag any discrepancies.

Why do skill metadata and directory name mismatches cause deployment errors?▼

Metadata and directory name mismatches cause deployment errors because skill registries and CI pipelines rely on exact path-to-name mapping for indexing and discovery.

What is the best way to automate skill validation for multi-skill repositories?▼

Automating skill validation for multi-skill repositories is best achieved by running a lightweight pre-commit hook or CI check that flags broken references and documentation mismatches.

Does skill validation require specific dependencies or components?▼

Skill validation requires no external dependencies or components, only a SKILL.md file containing YAML frontmatter with the name and description fields to perform the comparison.

Can I use this name consistency check as a pre-commit hook?▼

Yes, you can use this name consistency check as a pre-commit hook to help maintainers and contributors catch naming issues and avoid broken references early in development.

What happens when the YAML frontmatter name differs from the folder path?▼

When the YAML frontmatter name differs from the folder path, the validation check reports the mismatch to prevent discovery, indexing, and deployment errors in skill registries.