wrong-name

Compare SKILL.md frontmatter names to parent folder names and output structured reports.

33|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/lvlup-sw/exarchos --skill wrong-name
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrong-name
Source: https://github.com/lvlup-sw/exarchos/tree/main/skills/test-fixtures/name-mismatch
Command: npx skills add https://github.com/lvlup-sw/exarchos --skill wrong-name

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures the skill's declared identifier in SKILL.md matches its filesystem folder name to prevent discovery, routing, and installation failures caused by inconsistent naming.

Core Features & Use Cases

  • Validation: Parse SKILL.md YAML frontmatter and compare the name value to the immediate parent directory name.
  • Reporting: Produce human-readable and machine-consumable reports for CI, pre-commit hooks, or repository audits.
  • Fix Guidance: Recommend the minimal corrective action (update frontmatter or rename folder) and include examples for automated fixes.
  • Use Case: Integrate into a repository linter that blocks merges when skills are misidentified by agent installers.

Quick Start

Compare the SKILL.md name field with the containing folder name and return a clear pass/fail report with suggested fixes.

Frequently Asked Questions about wrong-name

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

FAQPage Schema
How do I validate a skill's frontmatter name against its folder name in CI?

To validate a skill's frontmatter name against its folder name in CI, parse the SKILL.md YAML frontmatter and compare the name value to the immediate parent directory. This produces a structured pass/fail report suitable for automated pipelines to block misidentified merges.

Why does my skill discovery or routing fail after installation?

Skill discovery and routing fail when the declared identifier in SKILL.md YAML frontmatter does not match the filesystem folder name. Comparing the frontmatter name string to the parent directory name identifies these mismatches to prevent installation failures.

What's the best way to lint repository skills for name mismatches locally?

The best way to lint repository skills for name mismatches locally is to read the SKILL.md YAML frontmatter, compare the name string to the immediate parent directory name, and output a human-readable report with minimal corrective actions.

Can I automate fixes for SKILL.md name and folder mismatches?

Yes, you can automate fixes for SKILL.md name and folder mismatches. The validation process recommends the minimal corrective action, such as updating the frontmatter or renaming the folder, and includes examples suitable for automated pipeline fixes.

Does skill validation work with pre-commit hooks for repository audits?

Skill validation works with pre-commit hooks for repository audits by reading the SKILL.md YAML frontmatter, comparing the name to the containing folder, and generating machine-consumable reports that block invalid commits before they reach CI.