qmd-cli

Search indexed text corpora using qmd commands instead of grep.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/mpsuesser/workspace --skill qmd-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qmd-cli
Source: https://github.com/mpsuesser/workspace/tree/main/dotconfig/pi/agent/skills/__techs__/.unused/qmd-cli
Command: npx skills add https://github.com/mpsuesser/workspace --skill qmd-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm install -g @tobilu/qmd, qmd, session-view, grep, find, sed, awk, sort, uniq, mktemp, python3, and includes scripts (resource) components.

What problem does it solve?

Searching large, indexed text corpora with grep-style techniques is slow, noisy, and error-prone because indexed files (especially JSONL session logs) are difficult to interpret without the right retrieval layer.

Core Features & Use Cases

  • Ranked discovery with qmd: Use qmd status and discovery commands to search and retrieve relevant indexed passages across session logs, notes, docs, and other corpora.
  • Correct command selection: Prefer qmd search for exact clues, qmd query for conceptual/weak lexical matches, and qmd vsearch only for pure semantic similarity.
  • Guided session inspection workflow: Locate candidate sessions in the sessions collection, inspect transcripts with qmd get, and recover exact raw details using original_session plus session-view tools when needed.

Quick Start

Tell the AI: use qmd search in the sessions collection to find the top matches for the phrase apply_edits error, return compact file paths, then inspect the best transcript.

Frequently Asked Questions about qmd-cli

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

FAQPage Schema
How do I search indexed text corpora without slow grep commands?

Searching indexed text corpora without slow grep commands requires using qmd-based search and retrieval. This approach uses ranked discovery across session logs and documents, avoiding the noise and errors of raw grep on difficult-to-interpret indexed files.

What is the best way to locate agent session transcripts for debugging tool usage failures?

Locating agent session transcripts for debugging tool failures is best done by searching the sessions collection with qmd. You can inspect the best transcript with qmd get, and recover exact raw details using original_session plus session-view tools when needed.

When should I use qmd search, query, or vsearch for session discovery?

You should use qmd search for exact clues, qmd query for conceptual or weak lexical matches, and qmd vsearch solely for pure semantic similarity. Choosing the correct command based on clue strength ensures efficient and accurate session discovery.

How do I confirm which collections and contexts are indexed before searching?

Confirming which collections and contexts are indexed before searching is done using qmd status and discovery commands. This preliminary step verifies the available indexed text corpora so you can target your search and retrieval accurately.

Can I use shell filtering tools like awk and sed on indexed JSONL session logs?

You can use safe shell filtering with tools like awk, sed, sort, and uniq on indexed JSONL session logs. However, you must not directly grep indexed files for meaning, relying instead on qmd for the actual search and retrieval layer.

Do I need npm and python3 to use qmd for transcript inspection?

You need npm to install the qmd package globally and python3 for associated script execution. These dependencies provide the environment necessary to run the qmd-based search and retrieval workflow for inspecting session transcripts.