kcp-navigate

To find specific documentation in a project with a knowledge.yaml file, use targeted knowledge retrieval to query KCP structures with natural language. This selectively loads only the relevant knowledge units for your task, eliminating blind exploration across the repository.

Targeted knowledge retrieval in KCP structures is the process of navigating a knowledge.yaml file to locate specific information units. It supports natural language queries and metadata-based filtering to find and load only the necessary documentation for a given task.

Yes, you can use natural language queries for project navigation within KCP-structured repositories. The navigation skill accepts natural language and triggers to find relevant knowledge units without requiring manual browsing or complex search syntax.

Yes, you need a knowledge.yaml file at the root of your project or documentation site. This file provides the necessary KCP knowledge structure that enables the selective loading and metadata-based filtering required for information discovery.

The best way to navigate large repositories without browsing all content is querying the KCP knowledge structure via a knowledge.yaml file. This approach handles selective loading and metadata-based filtering to quickly locate only the required knowledge units.

You should avoid metadata-based filtering for document search when a project lacks a knowledge.yaml file at its root. Without this KCP structure, the selective loading and knowledge unit retrieval mechanisms cannot function properly to locate relevant information.