list-search

Search project documentation for keywords with type filters and JSON output.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill list-search-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list-search
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/list-search
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill list-search-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Поиск по всей документации проекта — инструкции, скиллы, агенты, правила, README и скрипты. Ускоряет навигацию, предотвращает дублирование и упрощает поиск материалов перед созданием нового объекта.

Core Features & Use Cases

  • Поиск по ключевым словам во всей документации проекта (инструкции, скиллы, агенты, правила и скрипты).
  • Фильтры по типу (--type) и возможность вывода результатов в JSON.
  • Поддержка быстрого поиска для проверки наличия дубликатов и быстрой ориентации в репозитории.

Quick Start

Search the entire project documentation for a given keyword.

Frequently Asked Questions about list-search

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

FAQPage Schema
How do I search across all project documentation to find specific instructions or rules?

You can search project documentation by running keyword-based queries to instantly locate instructions, skills, agents, rules, and scripts across the repository. This documentation search supports navigation and discovery without manual browsing.

Can I filter repository search results by type and output them as JSON?

Yes, repository search results can be filtered by type using the --type flag and returned in JSON format using the --json flag. This allows structured parsing of discovered documentation files for downstream processing.

What is the best way to check for duplicate skills or scripts before creating a new one?

Checking for duplicates is done by running a keyword text search across the entire project documentation using the --search flag. This discovers existing instructions, scripts, or skills to prevent duplication before creating new repository objects.

Does the documentation search require any external dependencies or components to run?

No external dependencies or components are required to run the documentation search. It is implemented via a standalone Python script located at .instructions/.scripts/search-docs.py within the repository.

How do I search READMEs and code references for specific keywords in my repository?

You can search READMEs and code references by executing keyword-based queries across the entire project documentation. This scans all repository materials including READMEs to locate exact text matches and navigation points.

When should I use type filters instead of a general text search for repository navigation?

Type filters should be used when you need to narrow navigation results to specific categories like scripts or agents, while general text search is better for broad keyword discovery across all documentation types in the repository.