finyx-insurance

Scan repositories for valid Skill units and generate structured metadata blocks.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/italolelis/finyx --skill finyx-insurance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finyx-insurance
Source: https://github.com/italolelis/finyx/tree/main/skills/insurance
Command: npx skills add https://github.com/italolelis/finyx --skill finyx-insurance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes and standardizes metadata for Skill units within a repository, enabling reliable discovery, indexing, and automated activation of skills. This description guides users and systems to understand each Skill's scope, entry points, and resource organization.

Core Features & Use Cases

  • Validates Skill units by enforcing the mandatory SKILL.md at root and YAML frontmatter with name and description.
  • Extracts and consolidates mandatory discovery fields (name, description) and optional resources (scripts/, references/, assets/).
  • Computes and emits a consistent metadata schema for each Skill unit to support search, cataloging, and automated tooling.
  • Enables auditing and gap analysis across repository Skill units to identify missing frontmatter, missing resources, or misconfigurations.

Quick Start

Execute a repository-wide scan to identify valid Skill units and generate their metadata.

Frequently Asked Questions about finyx-insurance

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

FAQPage Schema
How do I generate structured metadata for Skill units in a repository?

To generate structured metadata for Skill units, you execute a repository-wide scan that identifies valid units requiring a SKILL.md file and YAML frontmatter. This process outputs a machine-parseable metadata block for each valid Skill unit to support automated tooling.

What is required to validate a Skill unit for indexing?

Validating a Skill unit for indexing requires a mandatory SKILL.md file at the root directory and YAML frontmatter containing both name and description fields. Optional resources like scripts, references, and assets are consolidated during the scan.

How does automated skill discovery handle missing YAML frontmatter?

Automated skill discovery identifies missing YAML frontmatter during repository auditing and gap analysis. The scan evaluates each Skill unit's configuration, flagging missing mandatory fields or misconfigurations to ensure reliable cataloging and activation.

Can I use this metadata schema for automated activation pipelines?

Yes, you can use this metadata schema for automated activation pipelines because the outputs are specifically computed to be machine-parseable. The standardized metadata blocks ensure reliable indexing and activation of skills across tooling systems.

What is the best way to audit Skill units for missing resources?

The best way to audit Skill units for missing resources is executing a repository-wide scan. This computes a consistent metadata schema for each unit, identifying missing frontmatter, absent optional resources like scripts or references, and configuration gaps.