smart-query

Translate natural-language tracking questions into Trekker queries for status, history, blockers, and related work.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/obsfx/trekker-codex --skill smart-query-obsfx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-query
Source: https://github.com/obsfx/trekker-codex/tree/main/skills/smart-query
Command: npx skills add https://github.com/obsfx/trekker-codex --skill smart-query-obsfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate natural-language questions about project work into Trekker queries that fetch status, history, blockers, and related work.

Core Features & Use Cases

  • Query translations for common prompts like status, history, blockers, and related work.
  • Quick access to commands such as trekker task list --status in_progress, trekker history --limit 10, trekker dep list TREK-12, trekker search "topic".
  • Use case: a user asks what's in progress, and the AI returns the corresponding Trekker command without exposing internal queries.

Quick Start

Ask for the current in-progress work to see live status.

Frequently Asked Questions about smart-query

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

FAQPage Schema
How do I convert natural language questions into Trekker queries?

You can translate natural-language tracking questions into Trekker queries to fetch status, history, blockers, and related work. The AI returns the corresponding Trekker command without exposing internal query syntax.

What is the best way to check task status and blockers using Trekker?

Checking task status and blockers is done by translating prompts into Trekker commands like trekker task list --status in_progress or trekker dep list TREK-12 to retrieve relevant project data.

Can I use natural language to search project history in Trekker?

Yes, you can use natural language to search project history. It translates prompts into commands such as trekker history --limit 10 or trekker search "topic" to retrieve history records.

Does this natural language query translation work for project inquiries and task-tracking scenarios?

Yes, it applies specifically to project inquiries and task-tracking scenarios. It enables quick status checks and history reviews by converting tracking questions into executable Trekker commands.

What are the limitations of translating natural questions into Trekker commands?

The translation focuses on common prompts like status, history, blockers, and related work. Complex queries outside these core task-tracking scenarios may not be supported by the generated Trekker commands.