asset-discovery

Asset discovery identifies existing skills and agents across project, user, and plugin layers to prevent duplicate scaffolding. It reads frontmatter fields and provides similarity heuristics to detect overlapping assets before you generate new ones.

The best way to prevent duplicate skill generation is to apply asset discovery to your setup and generator workflows. This surfaces overlaps, provenance, and potential conflicts by extracting frontmatter fields before you scaffold new assets.

Frontmatter extraction reads fields like name, description, domains, generated_by, and generated_at to perform similarity analysis. This mechanism maps existing definitions and labels their origin to detect overlaps and potential conflicts.

Yes, you can check skill provenance across project, user, and plugin layers. Asset discovery labels the origin of each SKILL.md and agent definition, providing a unified view that informs safe setup and refactoring decisions.

You need to run asset discovery before scaffolding new assets or during refactoring decisions. It provides a unified view of your asset ecosystem, applying similarity heuristics to maintain a clean environment and avoid overlapping definitions.