CodingMeta

Aria Knowledge

Encoded knowledge for Project Aria Gen 2 and the Aria Research Kit (ARK) - hardware, profiles, calibration, coordinate systems, VRS format, time domains, on-device perception, MPS outputs (SLAM, point cloud, hand…

ariakitknowledgeproject

Read exactly what Claude will be told

SKILL.md

View source on GitHub →

---
name: aria-knowledge
description: Encoded knowledge for Project Aria Gen 2 and the Aria Research Kit (ARK) — hardware, profiles, calibration, coordinate systems, VRS format, time domains, on-device perception, MPS outputs (SLAM, point cloud, hand tracking), plus pointers to the source-of-truth docs for specifics. Use whenever the user asks ANY conceptual question about Aria Gen 2 / ARK and you need to either answer from encoded knowledge or know where to look next. This skill is the single index that tells an agent how to fetch official Aria knowledge — encoded stable concepts for what does not drift, explicit public-doc pointers for hardware specs / schemas / numerical values that do, and "go read the code" or "run --help" for things owned by source. Pair with the domain skills in this plugin (`projectaria-tools`, `client-sdk`, `mps`, `vrs-health-check`, `pilot-dataset`, `web-app-creator`, `custom-profile`, `vrs-cli`, `client-sdk-ros2-integration`, `cloud-streaming`) for hands-on work.
---

# Aria Knowledge

This skill is the **knowledge index** for Project Aria Gen 2 and the Aria Research Kit (ARK). It encodes the high-level concepts that are stable across releases, and for specifics that drift (sensor specs, CSV column lists, exact API signatures, CLI flags) it tells you where the source-of-truth lives so you can fetch a current answer rather than guess.

## How to use this skill

```text
Question type                         → Action
─────────────────────────────────────────────────────────────────────────
What is X? / How does Y work?         → Answer from this skill
Specific numeric value / schema       → Read the public doc page this skill
                                        names (under `DOCS_BASE` below)
Exact API call / API signature        → Read the code (see corresponding
                                        skill for header locations)
Exact CLI flag                        → Run `<cmd> --help`
Hands-on workflow                     → Defer to the matching plugin skill
                                        (listed at the end of each section)
```

**Source-of-truth rule.** Anything that may change with a release — sample rates, profile JSON, stream IDs, calibration model parameters, MPS service versions, API names, CSV columns — lives in the docs or the source code. This skill repeats only the conceptual definitions that are unlikely to evolve.