modes-of-reasoning

Parse SKILL.md YAML frontmatter to validate and index Skill Units in guardian-core.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/guardian-intelligence/guardian-core --skill modes-of-reasoning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: modes-of-reasoning
Source: https://github.com/guardian-intelligence/guardian-core/tree/main/.claude/skills/modes-of-reasoning
Command: npx skills add https://github.com/guardian-intelligence/guardian-core --skill modes-of-reasoning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill unit provides a standardized mechanism to discover, validate and metadata-index Skill units defined within guardian-core by requiring a SKILL.md at the root and a YAML frontmatter with name and description.

Core Features & Use Cases

  • Identifies Skill Units by the mandatory SKILL.md at their root and uses the YAML frontmatter as the discovery entry.
  • Supports optional resources (scripts/, references/, assets/) to be loaded on demand as directed by SKILL.md.
  • Produces machine-readable metadata (name, description, categories, keywords, dependencies, components) suitable for indexing, auditing, and activation.

Quick Start

Review the Modes-of-Reasoning Skill Unit in guardian-core to confirm it conforms to the SKILL.md frontmatter schema and extract its metadata into the discovery index.

Frequently Asked Questions about modes-of-reasoning

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

FAQPage Schema
How do I extract YAML frontmatter metadata from SKILL.md files for discovery indexing?

To extract YAML frontmatter metadata for discovery indexing, locate SKILL.md files at the root of Skill Units and parse required fields like name and description to generate a structured YAML document for auditing and activation.

What is the best way to validate Skill Units and index their optional resources like scripts and references?

Validating Skill Units and indexing optional resources requires checking for a root SKILL.md file, parsing its YAML frontmatter, and appending available scripts, references, or assets directories into machine-readable discovery metadata.

Can I use structured metadata extraction to audit dependencies and keywords across multiple Skill Units?

Yes, structured metadata extraction audits dependencies and keywords by validating each Skill Unit's SKILL.md frontmatter and returning a unified YAML document containing category, keywords, dependencies, and components fields.

How does model-theoretic taxonomy discovery work when parsing SKILL.md files?

Model-theoretic taxonomy discovery works by identifying SKILL.md files at Skill Unit roots, validating their YAML frontmatter schema, and generating structured discovery metadata that maps taxonomy fields like name, tagline, and category.

What fields are required when composing machine-readable metadata for CAC assets?

Composing machine-readable metadata for CAC assets requires extracting the mandatory name and description fields from YAML frontmatter, alongside optional resources, to produce a structured document with safety metadata.

Do I need a YAML frontmatter schema to perform metadata extraction on guardian-core Skill Units?

Yes, metadata extraction on guardian-core Skill Units requires a YAML frontmatter schema containing at minimum the name and description fields to validate the unit and compose its discovery metadata index.