glean-extract

Trigger glean session extractions and monitor real-time progress via command line.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/vedantggwp/glean --skill glean-extract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: glean-extract
Source: https://github.com/vedantggwp/glean/tree/main/skills/glean-extract
Command: npx skills add https://github.com/vedantggwp/glean --skill glean-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Simplifies the process of manually initiating glean data extraction without navigating the full pipeline.

Core Features & Use Cases

  • Manual Trigger: Allows the user to directly start glean extraction for specific sessions or drain the pending queue.
  • Progress Monitoring: Streams real-time progress updates during extraction.
  • Use Case: A developer wants to reprocess a failed session or extract insights immediately for a particular session ID.

Quick Start

To manually start extraction for a specific session, run the skill with the session ID as an argument.

Frequently Asked Questions about glean-extract

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

FAQPage Schema
How do I manually trigger glean session extraction for a specific session ID?

To manually trigger glean session extraction, run the skill via command-line invocation with the target session ID as an argument. This initiates immediate processing for that specific session, bypassing the standard pipeline to retrieve targeted insights directly.

Can I monitor real-time progress of a manual glean extraction?

Yes, you can monitor real-time progress of manual glean extraction. Once triggered, the skill streams live progress updates during the processing phase, providing immediate feedback and summaries until the session extraction completes.

What is the best way to reprocess a failed glean session?

Reprocessing a failed glean session is handled by manually triggering extraction for that specific session ID. This targeted approach allows you to retry failed data processing without running the entire queued pipeline again.

Do I need a Python environment to run manual glean extraction?

Yes, you need a Python environment to run manual glean extraction. The skill requires the glean.worker module to be available within your Python setup to execute the command-line scripts and process session data.

How do I drain the pending queue for glean session extractions?

To drain the pending queue for glean session extractions, use the skill's manual trigger feature without specifying a single session ID. This processes all queued sessions sequentially, clearing the backlog.

Why trigger manual extraction instead of waiting for the automated pipeline?

Triggering manual extraction bypasses automated pipeline delays, allowing you to extract insights immediately or reprocess specific failed sessions. It provides direct control over when queued or targeted sessions are processed.