ckl-search

Search code and navigate knowledge graphs across indexed projects.

Updated May 5, 2026
One-click install
npx skills add https://github.com/Alex980102/ckl-skill --skill ckl-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ckl-search
Source: https://github.com/Alex980102/ckl-skill/tree/main/skills/ckl-search
Command: npx skills add https://github.com/Alex980102/ckl-skill --skill ckl-search

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enables fast discovery of code and related knowledge across indexed projects by providing robust search and graph navigation capabilities.

Core Features & Use Cases

  • Hybrid search across code and knowledge graph to locate blocks, projects, and documents.
  • Scoped discovery by org/project/source/holder/kind/container with ID resolution.
  • Cross-entity discovery and relationship drill-down to understand dependencies and provenance.

Quick Start

Run a hybrid search over an indexed project to locate code and navigate the knowledge graph.

Frequently Asked Questions about ckl-search

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

FAQPage Schema
How do I search code and navigate the knowledge graph across indexed projects?

To search code and navigate the knowledge graph, use the ckl binary to perform a hybrid search across indexed projects, locating blocks, projects, and documents via scoped discovery by org, project, source, holder, kind, and container.

How does cross-entity discovery and relationship drill-down work for code dependencies?

Cross-entity discovery and relationship drill-down work by traversing the knowledge graph to map dependencies and provenance, allowing you to resolve entity names to IDs using project-query, org-query, or source-query flags for precise code navigation.

Do I need a specific ckl binary version to query the knowledge graph?

Yes, querying the knowledge graph requires the ckl binary version 0.5.7 or higher on your PATH, along with an actively indexed project to execute scoped searches and resolve entity IDs successfully.

Can I scope code searches by organization, source, or container?

Yes, you can scope code searches by org, project, source, holder, kind, and container. This scoped discovery supports cross-entity navigation and relationship drill-down across indexed projects within the knowledge graph.

What is the best way to resolve entity names to IDs when searching indexed projects?

The best way to resolve entity names to IDs during indexed project searches is using the --project-query, --org-query, and --source-query options, which map names to IDs for accurate knowledge graph traversal and code retrieval.

Why does knowledge graph search require an indexed project to function?

Knowledge graph search requires an indexed project because the ckl binary relies on the pre-built graph relationships and metadata within the index to locate code blocks, resolve entity IDs, and perform scoped cross-entity discovery.