Bad_Frontmatter

Demonstrates invalid frontmatter conventions for skill validation testing.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/ricardolui/gcp-custom-agent-skills --skill bad-frontmatter-ricardolui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Bad_Frontmatter
Source: https://github.com/ricardolui/gcp-custom-agent-skills/tree/main/confluent-skill-reviewer/evals/mock-skills/bad-frontmatter
Command: npx skills add https://github.com/ricardolui/gcp-custom-agent-skills --skill bad-frontmatter-ricardolui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill serves as a negative test fixture for skill validation pipelines, providing an intentionally malformed frontmatter example that reviewers and linters must detect and reject. ## Core Features & Use Cases - Invalid Name Pattern: Uses uppercase letters and underscores in the name field, violating lowercase-hyphen naming conventions. - Vague Description: Contains a description too generic to function as a reliable activation trigger. - Use Case: A skill review harness loads this fixture to confirm its validator flags naming violations and weak descriptions before a skill is published. ## Quick Start Ask the validator to review this skill and report the frontmatter naming and description violations it contains.

Frequently Asked Questions about Bad_Frontmatter

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

FAQPage Schema
What makes a skill frontmatter name invalid?

A skill name is invalid when it uses uppercase letters, underscores, or spaces instead of lowercase hyphenated format. This fixture uses "Bad_Frontmatter" specifically to trigger that naming violation in validators.

How do I test a skill validation pipeline?

Test a skill validation pipeline by feeding it fixtures with known defects, such as invalid name patterns or vague descriptions, and confirming each defect is flagged. This mock skill provides exactly such a negative test case.

Why is a vague skill description a problem?

A vague description like "Helps with stuff" fails as a discovery trigger because it gives no concrete signal about when the skill should activate. Validators should reject descriptions lacking specific actions or domains.

Can this skill be used in production workflows?

No, this skill is a broken-on-purpose mock fixture for evaluation suites, not a functional tool. It exists only to verify that review tooling correctly identifies malformed frontmatter.