Smart Restaurant OS — Skill Layer (Domain Intelligence for AI Agents)

Validate SKILL.md frontmatter and extract metadata into structured YAML payloads.

Updated May 11, 2026
One-click install
npx skills add https://github.com/lochoangtran-510/smart-restaurant --skill smart-restaurant-os-skill-layer-domain-intelligence-for-ai-agents-lochoangtran-510
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Smart Restaurant OS — Skill Layer (Domain Intelligence for AI Agents)
Source: https://github.com/lochoangtran-510/smart-restaurant/tree/main
Command: npx skills add https://github.com/lochoangtran-510/smart-restaurant --skill smart-restaurant-os-skill-layer-domain-intelligence-for-ai-agents-lochoangtran-510

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SR-OS teams need a consistent way to discover, validate, and catalog AI governance Skill Units across a large codebase.

Core Features & Use Cases

  • Standardized frontmatter validation (name + description) for each Skill Unit.
  • Automated metadata extraction (dependencies, components, category, keywords) for centralized search.
  • Safety and compliance checks to flag missing or unsafe content before activation.

Quick Start

Scan the repository root to identify Skill Units, then run the metadata extractor to produce a structured YAML payload for each valid Skill Unit.

Frequently Asked Questions about Smart Restaurant OS — Skill Layer (Domain Intelligence for AI Agents)

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

FAQPage Schema
How do I validate YAML frontmatter in SKILL.md files for AI governance?

To validate YAML frontmatter in SKILL.md files, scan the repository root to identify Skill Units and verify the presence of required metadata fields like name and description. The extractor checks each file and flags invalid or unsafe content before activation.

What is the best way to extract metadata from Skill Units in a large codebase?

The best way to extract metadata from Skill Units is to scan the repository root and run an automated metadata extractor. This process reads YAML frontmatter to pull dependencies, components, category, and keywords, producing a structured YAML payload for centralized search.

How do I flag unsafe or missing frontmatter in AI agent Skill Units?

You can flag unsafe or missing frontmatter by verifying the SKILL.md file at the root of each Skill Unit. The validation process isolates invalid or unsafe Skill Units that lack proper frontmatter or contain risky content, preventing them from entering the discovery catalog.

Can I generate a structured YAML payload for downstream tooling from Skill Unit metadata?

Yes, you can generate a structured YAML payload for downstream tooling by scanning valid Skill Units. The extractor compiles extracted metadata such as name, description, dependencies, and category into a structured format ready for centralized search and discovery.

Does AI governance metadata extraction work for repositories without dependencies?

AI governance metadata extraction works for repositories without dependencies because the validator operates independently on SKILL.md files. It checks frontmatter presence and extracts available metadata fields, requiring no external dependencies to produce the structured YAML payload.