query-context

Retrieve relevant JSON knowledge resources from brand and knowledge base directories.

1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Largo2z9/phantomos --skill query-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: query-context
Source: https://github.com/Largo2z9/phantomos/tree/main/.skills/skills/query-context
Command: npx skills add https://github.com/Largo2z9/phantomos --skill query-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of scattered workspace knowledge by retrieving relevant brand, knowledge base, and cross-brand resources without manually searching files.

Core Features & Use Cases

  • Workspace Context Retrieval: Finds relevant JSON resources from shared knowledge bases and brand-specific workspaces based on natural language intent.
  • Multi-Scope Queries: Supports knowledge base lookups, individual brand context retrieval, and cross-brand comparisons with controlled read-only access.
  • Use Case: An operator can ask for frameworks, audience insights, brand positioning, or comparisons across brands and receive the relevant context resources for downstream agents.

Quick Start

Ask the query-context skill to find the relevant resources for a cold traffic Meta advertising angle strategy.

Frequently Asked Questions about query-context

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

FAQPage Schema
How do I retrieve relevant workspace knowledge resources without manually searching files?

Workspace knowledge retrieval is done by querying brand and knowledge base directories using natural language intent. The system locates relevant JSON resources across shared knowledge bases and brand-specific workspaces, returning structured JSON context with source metadata for downstream use.

Can I compare brand positioning and audience insights across multiple brands in my workspace?

Cross-brand comparisons are supported through multi-scope queries with controlled read-only access. You can request audience insights, brand positioning, or framework comparisons across brands, and the system returns the relevant context resources from your indexed workspace directories.

How does cross-brand context routing work for DTC operations scenarios?

Cross-brand context routing operates by applying natural language intent to indexed workspace resources, matching queries to brand-specific or shared knowledge base directories. It returns structured JSON context with source metadata, enabling framework discovery and routing decisions for DTC operations.

Do I need indexed workspace resources to use this knowledge base lookup?

Indexed workspace resources are required for knowledge base lookups. The system relies on pre-indexed brand and knowledge base directories to execute read-only access patterns, ensuring structured JSON context and source metadata are returned accurately for downstream agents.

What's the best way to find a cold traffic Meta advertising angle strategy in my brand knowledge base?

Finding a cold traffic Meta advertising angle strategy is done by asking the system to locate relevant resources using natural language. It retrieves the applicable framework and audience insight JSON resources from your brand knowledge base directories without manual file searching.

What are the limitations of using read-only access patterns for workspace context retrieval?

Read-only access patterns limit workspace context retrieval to querying and fetching existing indexed resources. The system cannot modify, write, or create new brand knowledge base files, meaning any updates to directories must be performed externally before retrieval.