Pop Types

Validate Skill Units and extract structured metadata from SKILL.md files.

21|8|Updated Jun 23, 2025
One-click install
npx skills add https://github.com/mattia2110/tech-and-res --skill pop-types
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Pop Types
Source: https://github.com/mattia2110/tech-and-res/tree/main/.agents/skills/pop_types
Command: npx skills add https://github.com/mattia2110/tech-and-res --skill pop-types

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly identify valid Skill Units by ensuring each has a SKILL.md at its root with a mandatory name and description, enabling consistent discovery and metadata generation.

Core Features & Use Cases

  • Validates Skill Units by checking for a root SKILL.md and required frontmatter.
  • Extracts metadata (name, description) and detects optional resources (scripts/, references/, assets/) for downstream tooling.
  • Generates a structured metadata profile to feed downstream tooling and dashboards.

Quick Start

Open the repository, locate a Skill Unit with SKILL.md, and extract its metadata.

Frequently Asked Questions about Pop Types

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

FAQPage Schema
How do I validate a Skill Unit and check for required YAML frontmatter?

To validate a Skill Unit, check that its root directory contains a SKILL.md file with YAML frontmatter including at minimum a name and description. This ensures consistent discovery and structured metadata generation.

What is the best way to extract metadata from a repository with SKILL.md files?

Extract metadata by parsing the YAML frontmatter in a root SKILL.md file for name and description, then detect optional resources like scripts, references, and assets to populate dependencies and components.

How do I generate a structured metadata profile for downstream tooling and dashboards?

Generate a structured metadata profile by validating root SKILL.md files, extracting name and tagline fields, detecting optional components, and producing outputs including category, keywords, and toxicity assessment.

What optional components are detected during repository analysis for Skill discovery?

During repository analysis, optional components detected include scripts, references, and assets directories, which are parsed to populate the dependencies and components fields of the metadata profile.

Does Skill Unit validation require any external dependencies?

No external dependencies are required for Skill Unit validation. The process relies solely on checking for a root SKILL.md file and parsing its YAML frontmatter for mandatory name and description fields.

Why does my Skill Unit fail validation despite having a SKILL.md file?

Skill Unit validation fails when the SKILL.md file lacks required YAML frontmatter fields. Ensure the frontmatter contains at minimum a valid name and description to pass the metadata extraction check.