library-lookup

Query keyword indices and flat-file greps to retrieve domain definitions from the garden library.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill library-lookup-kriscendobot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: library-lookup
Source: https://github.com/kriscendobot/garden/tree/main/skills/library-lookup
Command: npx skills add https://github.com/kriscendobot/garden --skill library-lookup-kriscendobot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of fragmented domain knowledge by providing a standardized way to locate canonical definitions and section files across the garden's library, while simultaneously improving the index for future users.

Core Features & Use Cases

  • Unified Search: Quickly find domain terms, code symbols, or proper names across the entire library structure.
  • Index Maintenance: Automatically suggests or performs writebacks to add shortcuts, prune misleading search results, or draft new concept pages.
  • Use Case: A developer encountering an unfamiliar term like formulaGraph can use this skill to find its definition, see related sections, and ensure the term is properly indexed for the next person who searches for it.

Quick Start

Use the library-lookup skill to find the canonical definition for the term retention-accumulator and update the index if necessary.

Frequently Asked Questions about library-lookup

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

FAQPage Schema
How do I search for canonical definitions across a knowledge management library?

You can search a knowledge management library by querying keyword indices and performing flat-file greps across conceptual, topical, and source-based axes. This unified search approach retrieves canonical definitions and section files while maintaining index integrity through automated writebacks.

How does keyword indexing work for domain-specific documentation?

Keyword indexing for domain-specific documentation works by implementing mandatory index-on-the-fly procedures during retrieval. It queries keyword indices across conceptual, topical, and source-based axes, then performs automated writebacks to maintain search integrity and documentation quality for future queries.

What is the best way to maintain search integrity when updating a documentation index?

The best way to maintain search integrity is implementing index-on-the-fly procedures that automatically suggest or perform writebacks. This adds shortcuts, prunes misleading search results, and drafts new concept pages to ensure domain-specific documentation remains accurate for future users.

Can I use flat-file greps to find code symbols and proper names in a library structure?

Yes, you can use flat-file greps to find code symbols, proper names, and domain terms across an entire library structure. Querying keyword indices retrieves canonical definitions while ensuring unfamiliar terms are properly indexed for subsequent searches.

Why does my domain knowledge search return fragmented or misleading results?

Domain knowledge searches return fragmented results when indices lack proper maintenance. Without mandatory index-on-the-fly procedures and automated writebacks, missing shortcuts and unpruned misleading entries prevent consistent retrieval of canonical definitions across conceptual, topical, and source-based axes.

Do I need existing concept pages to perform a library lookup?

No, you do not need existing concept pages to perform a library lookup. The skill can draft new concept pages through automated writebacks when encountering unfamiliar terms, ensuring domain-specific definitions are indexed for future retrieval.