workos

Validate SKILL.md frontmatter and extract metadata into a structured YAML block.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/iqbal125/typescript_projects --skill workos-iqbal125
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workos
Source: https://github.com/iqbal125/typescript_projects/tree/main/nestjs-react-monorepo-nx/.agents/skills/workos
Command: npx skills add https://github.com/iqbal125/typescript_projects --skill workos-iqbal125

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill unit identifies and documents valid WorkOS skill units within a repository by enforcing the mandatory SKILL.md frontmatter. It ensures discoverability by extracting core metadata such as name and description and by recognizing optional resources like references, assets, or scripts to support on-demand loading.

Core Features & Use Cases

  • Validate Skill units by confirming a SKILL.md frontmatter exists at the root and contains required fields.
  • Extract and consolidate metadata (name, description) for indexing and routing.
  • Detect and catalog optional resources (scripts/, references/, assets/) for on-demand usage as described by SKILL.md.
  • Produce a standardized metadata block suitable for downstream tooling and discovery pipelines.

Quick Start

Identify and output the Skill unit metadata for all valid Skill units in the repository.

Frequently Asked Questions about workos

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

FAQPage Schema
How do I extract frontmatter metadata from SKILL.md files for repository analysis?

Extract frontmatter metadata from SKILL.md files by verifying required fields and consolidating name, description, and resource references into a structured YAML block for automatic indexer ingestion.

How do I validate Skill units in a repository using frontmatter?

Validate Skill units by confirming a SKILL.md frontmatter exists at the root directory and contains essential fields, ensuring proper repository analysis and documentation routing.

What's the best way to route WorkOS documentation topics to the correct docs?

Route WorkOS documentation topics by extracting metadata such as name and description from valid Skill units, enabling fast discovery and routing through a standardized metadata block output.

Can I catalog optional resources like scripts and references during skill discovery?

Yes, skill discovery can detect and catalog optional resources like scripts, references, and assets directories for on-demand usage as described by the SKILL.md frontmatter.

Does documentation routing require dependencies to process repository metadata?

No, documentation routing processes repository metadata independently without dependencies, validating SKILL.md frontmatter fields and outputting structured YAML blocks for downstream tooling.

Why is my skill discovery not finding valid Skill units in the repository?

Skill discovery fails when directories lack a SKILL.md file with mandatory frontmatter fields, preventing metadata extraction and blocking the validation required for documentation routing.