skills

Discover available skills by parsing SKILL.md YAML frontmatter.

Updated Sep 12, 2021
One-click install
npx skills add https://github.com/cerico/macfair --skill skills-cerico
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skills
Source: https://github.com/cerico/macfair/tree/main/files/claude/skills/skills
Command: npx skills add https://github.com/cerico/macfair --skill skills-cerico

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill Unit helps users identify what skills exist and what they do by listing available skills and their purposes, enabling quick recall or discovery.

Core Features & Use Cases

  • Discover all defined skills by reading each SKILL.md frontmatter at the skill root.
  • Compare skills to determine which is best suited for a task or learning goal.
  • Provide a concise reference to guide prompt design and capability exploration.

Quick Start

Ask for the list of defined skills or request a summary of all skills currently defined in this repository.

Frequently Asked Questions about skills

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

FAQPage Schema
How do I discover available skills in a repository?

Discover available skills by reading the SKILL.md YAML frontmatter at each skill's root to extract the name, description, and metadata. This provides a concise reference to help you choose the right tool for a task.

What is the best way to list all defined skills and their purposes?

Listing all defined skills involves parsing the SKILL.md frontmatter at each skill root to surface relevant metadata. This enables quick recall or discovery of capability descriptions to guide prompt design.

How do I compare skills to determine which is best suited for a task?

Compare skills by reviewing the extracted name and description metadata from the SKILL.md frontmatter. This allows you to evaluate capability descriptions to determine which tool fits your learning goal or task.

Does skill discovery consider optional directories like scripts or references?

Skill discovery optionally considers optional directories such as scripts/, references/, and assets/ when present. It primarily parses the SKILL.md frontmatter to extract the core name and description metadata.

Can I use this approach for repository-wide skill discovery and capability exploration?

Repository-wide skill discovery and capability exploration apply directly to this approach. It reads the SKILL.md frontmatter at each skill root to surface relevant metadata, helping users choose the right tool for a task.