when-to-query

Determines whether to query Bluera Knowledge or use grep for given scenarios.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/blueraai/bluera-knowledge --skill when-to-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: when-to-query
Source: https://github.com/blueraai/bluera-knowledge/tree/main/skills/when-to-query
Command: npx skills add https://github.com/blueraai/bluera-knowledge --skill when-to-query

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you decide whether to use Bluera Knowledge (BK) for querying external code and documentation, or to use traditional tools like grep and read for your current project's codebase. It prevents inefficient searches and ensures you're using the right tool for the job.

Core Features & Use Cases

  • Decision Guidance: Provides clear rules on when to query BK versus other methods.
  • Use Case Scenarios: Helps you determine the best approach for library implementation questions, API specifics, error handling in dependencies, and configuration options.
  • Quick Reference: Offers a table summarizing when to use BK, Grep/Read, training data, or web search based on the question type.

Quick Start

Use the when-to-query skill to understand when to use Bluera Knowledge for library questions.

Frequently Asked Questions about when-to-query

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

FAQPage Schema
When should I query external library documentation versus grep my codebase?

Query external library documentation when investigating library implementation, API usage, error handling, or configuration options. Use grep or read for searching internal project codebase. Differentiating external dependency queries from internal code searches prevents inefficient lookup.

What is the best way to search for API specifics in external dependencies?

The best way to search for API specifics in external dependencies is querying Bluera Knowledge rather than grep or read, as traditional code search tools are designed for internal project codebase navigation and lack external documentation context.

How do I know if I should use grep or read for code search?

Use grep or read for code search when querying your current project's codebase for internal implementation details. Switch to querying Bluera Knowledge when you need to understand external library implementation, API usage, or dependency configuration.

Does querying Bluera Knowledge work for internal project codebase searches?

Querying Bluera Knowledge does not work efficiently for internal project codebase searches. It is designed for external library and dependency documentation queries, while grep and read handle internal codebase navigation and implementation searches.

Why does grep not return results for external library implementation questions?

Grep does not return results for external library implementation questions because it only searches your current local project codebase. External dependency code and documentation require querying Bluera Knowledge to retrieve relevant API usage and error handling information.

Can I use code search tools for dependency configuration and error handling queries?

You cannot effectively use local code search tools like grep for dependency configuration and error handling queries. These external library questions require querying Bluera Knowledge to access documentation beyond your current project's internal codebase.