different-name

Compare SKILL.md frontmatter name against directory basename and report mismatches.

1.0k|92|Updated May 22, 2026
One-click install
npx skills add https://github.com/open-gsd/gsd-pi --skill different-name-open-gsd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: different-name
Source: https://github.com/open-gsd/gsd-pi/tree/main/packages/pi-coding-agent/test/fixtures/skills/name-mismatch
Command: npx skills add https://github.com/open-gsd/gsd-pi --skill different-name-open-gsd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mismatches between a Skill's directory name and its declared frontmatter name can cause discovery and automation failures. This skill detects such inconsistencies to keep the skill catalog trustworthy.

Core Features & Use Cases

  • Detects when the SKILL.md frontmatter 'name' value differs from the directory basename.
  • Produces a clear report of mismatches for audits and CI checks.
  • Helps enforce naming standards across the skill repository.

Quick Start

Compare the Skill's directory name to the frontmatter 'name' and report any mismatches.

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 its frontmatter?

Directory name and frontmatter mismatch validation works by reading the SKILL.md file, parsing the YAML 'name' field, and comparing it directly against the directory basename to report inconsistencies for repository audits.

Why do skill directory names need to match the YAML frontmatter name value?

Skill directory names must match the YAML frontmatter name value to prevent discovery and automation failures, ensuring the skill catalog remains trustworthy during automated CI checks and manual reviews.

Can I use frontmatter validation for CI checks in a skill repository?

Yes, frontmatter validation can be applied during CI checks to automatically detect mismatches between SKILL.md frontmatter 'name' values and directory basenames, producing clear reports of naming inconsistencies across the repository.

What is the best way to audit a skill catalog for naming consistency?

The best way to audit a skill catalog for naming consistency is to run a validation check that reads each SKILL.md frontmatter, extracts the 'name' value, and compares it against the directory basename to flag any mismatches.

Do I need any dependencies to validate SKILL.md frontmatter against directory names?

No dependencies are required to validate SKILL.md frontmatter against directory names, as the skill operates independently to parse YAML frontmatter and compare the 'name' field with the directory basename during repository audits.