different-name

Detect mismatches between a skill directory name and its SKILL.md frontmatter name.

484|76|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/bastani-inc/atomic --skill different-name-bastani-inc
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: different-name
Source: https://github.com/bastani-inc/atomic/tree/main/packages/coding-agent/test/fixtures/skills/name-mismatch
Command: npx skills add https://github.com/bastani-inc/atomic --skill different-name-bastani-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps detect when a skill directory and its SKILL.md metadata do not agree, preventing discovery errors and mislabeled packages.

Core Features & Use Cases

  • Name consistency checks: Compare the directory identity with the frontmatter name field.
  • Fixture validation: Useful for testing skill loaders, packaging pipelines, and repository audits.
  • Mismatched metadata review: Helps spot naming issues before publishing or distributing a skill.

Quick Start

Ask the assistant to inspect this skill folder and report any mismatch between the directory name and the SKILL.md frontmatter name.

Frequently Asked Questions about different-name

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

FAQPage Schema
How do I check if a skill directory name matches the YAML frontmatter in SKILL.md?ā–¼

To check if a skill directory matches its YAML frontmatter, compare the folder name against the name field in the root SKILL.md to detect any naming inconsistencies before publishing.

Why does my skill discovery audit fail because of mismatched metadata?ā–¼

Skill discovery audits fail due to mismatched metadata when the directory name and the SKILL.md frontmatter name field do not align, causing loaders to misidentify the intended skill package.

How do I validate skill fixtures for packaging checks and repository audits?ā–¼

You validate skill fixtures for packaging checks by inspecting the root SKILL.md file and verifying that its declared YAML frontmatter name exactly matches the enclosing directory name structure.

What is the best way to catch skill name mismatches before distributing a package?ā–¼

The best way to catch skill name mismatches before distribution is to run a consistency check that compares the enclosing folder identity against the YAML frontmatter name field in SKILL.md.

Do I need a root SKILL.md with YAML frontmatter to perform a directory name validation?ā–¼

Yes, you need a root SKILL.md file containing YAML frontmatter to perform directory name validation, as the check compares the declared name field against the folder structure.