library-search

Search a local Prefab library for reusable assets using keywords, tags, and tracks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/moongci38-oss/forge --skill library-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: library-search
Source: https://github.com/moongci38-oss/forge/tree/main/.claude/skills/library-search
Command: npx skills add https://github.com/moongci38-oss/forge --skill library-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prefab Visual Library helps teams avoid recreating assets by first searching for reusable resources, reducing duplication and MCP overhead.

Core Features & Use Cases

  • Search by keywords, tags, and tracks to surface eligible assets in the local library.
  • Distinguish perfect matches from near-matches and decide to reuse, modify, or generate anew.
  • Update asset metadata after usage to improve future search quality and cost efficiency.
  • Use cases include rapid asset procurement, catalog browsing, and cost-conscious asset pipelines.

Quick Start

Search the local Prefab Visual Library for assets matching your query and decide whether to reuse, modify, or generate a new asset.

Frequently Asked Questions about library-search

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

FAQPage Schema
How do I find reusable visual assets to cut asset creation costs?

To find reusable visual assets and cut costs, search a local Prefab Visual Library using keyword, tag, and track filters to surface eligible candidates before creating new ones.

What do I need to set up before searching a local Prefab Visual Library?

Before searching a local Prefab Visual Library, you need to configure a PREFAB_LIBRARY_PATH and generate a _metadata.json file to drive keyword matching and rank results.

How does asset metadata matching work when searching for existing prefabs?

Asset metadata matching works by reading tags, track, and style_tags from a _metadata.json file to rank search results, distinguishing perfect matches from near-matches for reuse.

Can I update asset metadata after reusing a visual prefab to improve future searches?

Yes, you can update asset metadata after usage to improve future search quality and cost efficiency, ensuring the local library provides better matches over time.

What's the best way to avoid recreating visual assets and reduce MCP overhead?

The best way to avoid recreating visual assets and reduce MCP overhead is to search the local Prefab Visual Library first, evaluating existing candidates to reuse or modify before generating anew.

Why does my visual asset search return near-matches instead of exact prefab results?

Your visual asset search returns near-matches when exact keyword, tag, or style_tags alignments are absent, requiring you to evaluate candidates and decide whether to modify or generate a new asset.