source-etl-query

Queries mirrored GitHub and NVIDIA forum data via REST ETL bridge for historical analysis.

86|42|Updated May 6, 2026
One-click install
npx skills add https://github.com/NVIDIA/nemoclaw-community --skill source-etl-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-etl-query
Source: https://github.com/NVIDIA/nemoclaw-community/tree/main/examples/recipes/nvidia/developer-community-chief-of-staff/agents/hermes/skills/source-etl-query
Command: npx skills add https://github.com/NVIDIA/nemoclaw-community --skill source-etl-query

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of accessing historical GitHub discussions, issues, pull requests, and NVIDIA forum topics when live API access is restricted or when historical context is required for analysis.

Core Features & Use Cases

  • Historical Data Access: Retrieve mirrored GitHub and forum data from the local ETL REST bridge.
  • Search and Filter: Narrow down large datasets using keyword searches across titles and bodies.
  • Use Case: Use this skill to build digests or perform research on past community discussions and forum topics without needing live internet egress to those platforms.

Quick Start

Use the source-etl-query skill to search for recent GitHub discussions containing the keyword NemoClaw.

Frequently Asked Questions about source-etl-query

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

FAQPage Schema
How do I query historical GitHub issues and NVIDIA forum data without live API access?

To query historical GitHub issues and NVIDIA forum data without live API access, use the source-etl-query skill to retrieve mirrored datasets from a local ETL REST bridge. This allows you to search and filter past community discussions within restricted sandbox environments.

Can I search mirrored GitHub pull requests by keyword in a sandbox environment?

Yes, you can search mirrored GitHub pull requests by keyword in a sandbox environment using the source-etl-query skill. It narrows down large datasets by filtering across titles and bodies through the local ETL REST bridge without requiring internet egress.

What is the best way to access past NVIDIA forum topics for community research?

The best way to access past NVIDIA forum topics for community research is by querying host-side REST mirrors. The source-etl-query skill facilitates this by retrieving mirrored topic data locally, bypassing the need for live platform access.

Do I need a specific API URL to retrieve mirrored GitHub discussions locally?

Yes, you need the SOURCE_ETL_API_URL or specific host and port configuration to retrieve mirrored GitHub discussions locally. This setup interfaces with the ETL bridge to allow the skill to access historical data within your constrained environment.

How does querying mirrored GitHub data differ from using live APIs?

Querying mirrored GitHub data differs from live APIs by accessing a local ETL REST bridge instead of live internet endpoints. This approach enables historical data analysis and community research within constrained sandbox environments where live egress is restricted.