syncfusion-react-list-box

Validate SKILL.md frontmatter and extract structured metadata for Skill Units.

3|8|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/syncfusion/react-ui-components-skills --skill syncfusion-react-list-box
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: syncfusion-react-list-box
Source: https://github.com/syncfusion/react-ui-components-skills/tree/main/skills/syncfusion-react-listbox
Command: npx skills add https://github.com/syncfusion/react-ui-components-skills --skill syncfusion-react-list-box

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill Unit helps teams maintain a consistent catalog of Skill Units by validating the root SKILL.md and parsing its frontmatter to produce discoverable metadata.

Core Features & Use Cases

  • Validates the presence of SKILL.md at the root of each Skill directory (case-insensitive) and ensures the frontmatter includes required fields like name and description.
  • Extracts a standardized metadata profile (name, description, tagline, request, complexity, category, keywords, dependencies, and components) for discovery, search, and tooling.
  • Detects optional resources (scripts/, references/, assets/) and performs a toxicity check to flag potential risks.

Quick Start

Identify Skill Units, validate SKILL.md frontmatter, and generate structured metadata for review.

Frequently Asked Questions about syncfusion-react-list-box

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

FAQPage Schema
How do I validate SKILL.md frontmatter and extract structured metadata for discovery?

To validate SKILL.md frontmatter and extract structured metadata, parse the YAML frontmatter at the root of each directory to confirm required fields like name and description, generating a discoverable metadata profile for tooling and search.

What is the best way to scan a repository for valid Skill Units and generate a metadata catalog?

Scanning a repository for valid Skill Units involves checking each directory for a case-insensitive SKILL.md file, parsing its YAML frontmatter, and extracting structured metadata like category, keywords, and dependencies to produce a standardized catalog.

How does the toxicity check work when evaluating script directories for dependencies?

The toxicity check evaluates script directories for dependencies and risky content, flagging potential safety issues to ensure that extracted Skill Unit metadata remains standards-compliant and safe for discovery and tooling.

Can I use this metadata extraction approach to detect optional resources like scripts and references?

Yes, you can use this metadata extraction approach to detect optional resources. It evaluates directories for scripts, references, and assets, confirming component presence and checking for risky content during the validation process.

What metadata fields are required to parse from YAML frontmatter for a valid Skill Unit?

Required metadata fields parsed from YAML frontmatter include name and description, alongside extracted fields like tagline, request, complexity, category, keywords, dependencies, and components to ensure complete discovery metadata.