ljg-skill-map

Scan the skill directory and parse SKILL.md metadata to visualize installed skills.

Updated Feb 2, 2016
One-click install
npx skills add https://github.com/zjykzk/blog --skill ljg-skill-map-zjykzk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ljg-skill-map
Source: https://github.com/zjykzk/blog/tree/main/.agents/skills/ljg-skill-map
Command: npx skills add https://github.com/zjykzk/blog --skill ljg-skill-map-zjykzk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Visualize and inventory all installed skills by scanning the skill directory and rendering an at-a-glance map of name, version, invocability, and description.

Core Features & Use Cases

  • Scans ~/.claude/skills/ to discover installed skills and extract their metadata from SKILL.md.
  • Renders a structured ASCII map grouping skills by category and shows key details for quick decision making.
  • Supports quick auditing of capabilities and invocability for maintenance, onboarding, or capability planning.

Quick Start

Run the scan script to generate the JSON summary of all installed skills.

Frequently Asked Questions about ljg-skill-map

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

FAQPage Schema
How do I visualize installed skills and inventory their metadata at a glance?

To visualize installed skills, run the scan script to extract SKILL.md frontmatter metadata from the skill directory and render an ASCII map grouping capabilities by category for quick review.

What is the best way to audit skill versions and invocability for maintenance?

Auditing skill versions and invocability is done by scanning frontmatter fields like name, description, version, and user_invocable to generate a structured map for maintenance and capability planning.

Can I review my skill directory capabilities without manually opening each file?

You can review skill directory capabilities by running the scan script which parses SKILL.md metadata automatically and renders a searchable map showing names, versions, and descriptions grouped by category.

Does the skill inventory map rely on specific metadata fields to function correctly?

The skill inventory map relies on SKILL.md frontmatter fields including name, description, version, and user_invocable to accurately build and group the visualized skill map.

Why parse SKILL.md frontmatter when onboarding new skills to a project?

Parsing SKILL.md frontmatter when onboarding provides an at-a-glance structured ASCII map of available capabilities, versions, and invocability, enabling quick decisions without inspecting individual files.