impeccable

Validate Skill Units by checking root SKILL.md metadata and optional directories.

Updated Dec 19, 2024
One-click install
npx skills add https://github.com/heyramzi/clickup-utils --skill impeccable-heyramzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impeccable
Source: https://github.com/heyramzi/clickup-utils/tree/main/.claude/skills/impeccable
Command: npx skills add https://github.com/heyramzi/clickup-utils --skill impeccable-heyramzi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps ensure that a Skill Unit is valid by requiring a root SKILL.md with a name and description, and by documenting optional resource directories for extended functionality.

Core Features & Use Cases

  • Validates Skill Units by checking for a root SKILL.md frontmatter containing name and description.
  • Detects and catalogs optional resources (scripts/, references/, assets/) that may be used by the skill to load deterministic tasks, in-depth references, or assets.
  • Supports export of structured metadata for indexing and discovery, enabling automation in tooling and pipelines.

Quick Start

Invoke /impeccable craft [feature description] to start shaping a distinctive frontend UI.

Frequently Asked Questions about impeccable

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

FAQPage Schema
How do I validate a Skill Unit's SKILL.md metadata for frontend UI generation?

To validate a Skill Unit, this tool scans the root SKILL.md to ensure it contains required name and description frontmatter. It outputs structured metadata including category, keywords, and dependencies for indexing.

What directories are scanned when validating frontend UI skill metadata?

The validation process scans for optional directories like scripts/, references/, and assets/ to support on-demand tasks and richer context. These directories provide deterministic tasks and in-depth references for UI generation.

Can I export structured metadata from a validated Skill Unit for pipeline automation?

Yes, you can export structured metadata for indexing and discovery, enabling automation in tooling and pipelines. The exported data includes name, tagline, description, request, complexity, category, keywords, dependencies, components, and toxicity.

How do I start crafting a distinctive frontend UI using a validated Skill Unit?

Invoke the craft command with your feature description to start shaping a distinctive frontend UI. The skill uses validated metadata and optional resource directories to support production-grade UI generation.

What happens if a root SKILL.md is missing a name or description during frontend UI validation?

If the root SKILL.md lacks a name or description, the Skill Unit fails validation. Both fields are required to ensure proper metadata extraction and structured output for frontend UI generation.

Why do I need to validate skill metadata before generating production-grade frontend UI?

Validating skill metadata ensures the SKILL.md contains essential name and description fields and catalogs optional resource directories. This structured metadata enables proper indexing, discovery, and automation for frontend UI workflows.