doc-search

Search project documentation by tags, titles, and keywords using a pre-built index.

2|1|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/1ambda/dataops-platform --skill doc-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-search
Source: https://github.com/1ambda/dataops-platform/tree/main/.copilot/skills/doc-search
Command: npx skills add https://github.com/1ambda/dataops-platform --skill doc-search

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the inefficiency and token waste associated with manually searching through large documentation files by providing a token-efficient search mechanism.

Core Features & Use Cases

  • Token-Efficient Search: Significantly reduces token consumption compared to reading full files.
  • Targeted Retrieval: Allows searching by tags, titles, project, document type, or keywords.
  • Use Case: When needing to understand the "hexagonal architecture" pattern, instead of reading the entire PATTERNS.md file (which could cost thousands of tokens), you can use this Skill to pinpoint the exact relevant sections, costing only a few hundred tokens.

Quick Start

Search for documentation related to "hexagonal architecture" using the provided Python CLI command.

Frequently Asked Questions about doc-search

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

FAQPage Schema
How do I search project documentation without wasting tokens reading entire files?

Searching project documentation efficiently requires a pre-built index to pinpoint exact sections by tags, titles, or keywords, saving significant tokens compared to reading full files.

What is the best way to find specific architectural patterns in large markdown files?

Finding specific architectural patterns in large markdown files is best done by querying a pre-built index using keywords or tags, which retrieves only the precise relevant sections.

Can I retrieve documentation by document type and project scope?

Yes, you can retrieve documentation by document type and project scope, as the search mechanism supports targeted queries across tags, titles, projects, and keywords.

Do I need to build an index before searching for specific keywords?

Yes, you need a pre-built index to enable token-efficient searching, which allows the retrieval mechanism to locate specific keywords and sections without scanning full documents.

How does token-efficient documentation search compare to reading full files?

Token-efficient documentation search contrasts with reading full files by using a pre-built index to return exact sections, reducing token consumption from thousands to a few hundred.