insights

Aggregate structured reports and manifests into a queryable lineage graph and metrics store.

17|8|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/nebius/nebius-physical-ai --skill insights-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: insights
Source: https://github.com/nebius/nebius-physical-ai/tree/main/skills/tools/insights
Command: npx skills add https://github.com/nebius/nebius-physical-ai --skill insights-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the fragmentation of workflow data by aggregating disparate reports and manifests into a unified, queryable lineage graph and metrics store, ensuring that complex physical AI experiments remain legible and reproducible.

Core Features & Use Cases

  • Lineage Tracking: Automatically reconstructs the provenance of artifacts, showing how datasets, models, and evaluations relate to one another.
  • Metric Aggregation: Provides a centralized store for performance metrics, enabling cross-run comparisons and automated dashboard generation.
  • Use Case: A researcher can use this tool to compare the performance delta between two different model training runs, identifying regressions in latency or accuracy across the entire lineage of the experiment.

Quick Start

Use the insights skill to ingest all run data from the specified S3 prefix and generate a summary dashboard.

Frequently Asked Questions about insights

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

FAQPage Schema
How do I track artifact provenance and lineage for physical AI workflows?

Track artifact provenance by aggregating structured reports and manifests into a queryable lineage graph. This automatically reconstructs how datasets, models, and evaluations relate to one another across distributed GPU clusters.

What is the best way to compare performance metrics across distributed GPU clusters?

Compare performance metrics across distributed GPU clusters by aggregating run data into a centralized metrics store. This enables cross-run comparisons to identify regressions in latency or accuracy across the entire experiment lineage.

How do I generate dashboards for physical AI experiments without a dedicated database?

Generate dashboards without a dedicated database by using an append-only S3-based index with optional LanceDB integration. This ensures consistent data access for dashboard generation across distributed physical AI workflows.

Can I use LanceDB integration with S3 storage for physical AI observability?

Yes, LanceDB integration is supported alongside an append-only S3-based index to ensure consistent data access. This combination provides queryable lineage and metrics storage for physical AI observability.

Why does my physical AI experiment lineage become fragmented across multiple runs?

Lineage becomes fragmented when disparate reports and manifests are not aggregated into a unified graph. Aggregating this workflow data ensures complex physical AI experiments remain legible and reproducible.

Does the insights skill support cross-run comparison for model training regressions?

Yes, cross-run comparison is supported to identify regressions in latency or accuracy. Researchers can compare performance deltas between different model training runs across the entire experiment lineage.