Glossary
What Are Annotation Guidelines for Robot Training Data?
Last reviewed: October 2026
Short answer
Annotation guidelines are the written rules that tell labelers how to label a dataset: the vocabulary, where each label starts and ends, and which fields are required. For egocentric robot video they cover verb-noun action segments, hand pose, visibility flags and review. Firsthand sets them in the skill spec and ships them with the labels.
01
Why do robot training datasets need written labeling guidelines?
A label is only as consistent as the rule behind it. The site states that raw capture is labelled, keypointed, segmented or event-tagged as the spec requires, and that a generic taxonomy will not match a specific target task. Written guidelines fix the vocabulary and the boundaries before labeling starts, so a second reviewer can check a label against a rule instead of an opinion.
02
What goes into an annotation spec for egocentric video?
Firsthand states annotation level in the skill spec explicitly rather than leaving it implied. For skill-level labels, the spec names the verb-noun vocabulary and which sub-actions get their own segment boundary. For frame-level labels, it states the required fields, with hand_joints and hand_visible at minimum for any task involving grasping. Delivery is described as labelled, schema-conformant data with the annotation guidelines that produced it. The guideline document’s format, length and versioning are Not stated.
03
What are annotation guidelines?
Annotation guidelines, also called labeling guidelines, are the written instructions a labeler and a reviewer both follow: what each label means, where an action segment starts and ends, and which fields must be filled. An annotation spec for egocentric video is the same idea scoped to first-person footage with hands, objects and depth.
They are neither the labels nor the schema. The episode schema lists which fields exist; the guidelines say how a labeler fills them. The site states that a delivery carries the guidelines that produced its labels.
04
How do guidelines relate to skill specs and task taxonomies?
A skill spec is the written contract for one capture program: the named skill, the environments and conditions, the acceptance criteria and the target hours. Annotation level is set inside that same spec. A task taxonomy is different: it is the map of many tasks, from sector to environment to task to skill, used to plan coverage.
Because a generic taxonomy will not match a specific task, the spec names the verb-noun vocabulary the labels use. Action labels, the delivered label types, are what the guidelines govern. Whether the guidelines arrive as a standalone file is Not stated.
05
How are labels checked against the guidelines?
Labels are checked against a written acceptance test from the skill spec. The skill-spec guide’s worked example has a held-out reviewer name the verb and noun from the first 15 frames without reading the label. A second reviewer covers a sampled or full pass depending on the annotation’s density and stakes, and review depth is set per label type, since dense labels such as per-frame hand joints and instance masks are where errors compound.
Because hand pose carries a per-joint visibility flag, a reviewer can check that occluded joints are marked rather than invented. Items that fail are rejected, logged with a reason and recaptured at Firsthand’s cost, and are not billed. The reject log with reasons is visible to the buyer, and each episode’s meta.json carries reject_flags. Agreement scores, label accuracy rates and the second-pass sample rate are Not stated.
06
What do third-party papers say about annotation?
The EPIC-KITCHENS-100 paper (arXiv 2006.13256) reports that a new annotation pipeline gave denser annotations, 54% more actions per minute, and more complete ones, 128% more action segments, than the earlier version of the dataset. Ego4D (arXiv 2110.07058) describes itself as a massive annotated dataset and benchmark suite. Neither evaluates Firsthand data, so this page attributes no result to it.
07
How do you request a custom dataset?
Custom egocentric data collection starts from a written skill spec, usually proved by a Spec Pilot before volume scales. Where coverage is deep, a signed spec can reach a validated first batch in a median of 48 hours; where contributors must be recruited first, the site gives three to four weeks. Send the task, your verb-noun vocabulary, the label fields you need, your delivery format and your review bar, then ask to see the guidelines on the pilot batch.
08
Guideline components and where the site’s stated deliverables define them
| Component | Where the site states it | Status |
|---|---|---|
| Verb-noun vocabulary | Named in the skill spec; action_segments carry start_ns, end_ns, verb and noun | Stated |
| Segment boundaries | The spec names which sub-actions get their own segment | Stated |
| Required frame-level fields | The spec states them; hand_joints and hand_visible at minimum for grasping | Stated |
| Optional layers | Instance segmentation and de-identification when the program spec calls for them | Stated |
| Review rule | Written acceptance test; second reviewer on a sampled or full pass | Stated |
| Guideline file format and length | No detail given | Not stated |
| Guideline versioning | No detail given | Not stated |
10
Label types and delivered fields the site states
| Label | Delivered field | What the site states |
|---|---|---|
| Action segment | action_segments | Start, end, verb and noun for each sub-action |
| 3D hand pose | hand_joints | [T, 2, 21, 3] in metres, head frame |
| Joint visibility | hand_visible | Per-joint flag, so occluded joints are marked |
| Contact and grasp events | contact_events | Field name stated |
| Instance masks | instance_masks | Where the program spec calls for them |
| Body pose, objects, gaze | body_joints, objects, gaze_target | Field names stated |
| Inter-annotator agreement score | None | Not stated |
| Label accuracy rate | None | Not stated |
11
Frequently asked questions
- What are annotation guidelines?
- They are the written rules a labeler and reviewer follow: the vocabulary, where labels start and end, and which fields are required.
- Are annotation guidelines the same as a skill spec?
- No. A skill spec is the written contract for a capture program. Annotation level, including the verb-noun vocabulary and required fields, is set inside it.
- Does Firsthand deliver the guidelines with the data?
- The site describes delivery as labelled, schema-conformant data with the annotation guidelines that produced it. The file format is Not stated.
- How does Firsthand check labels?
- Against a written acceptance test, with a second reviewer on a sampled or full pass. Failures are rejected, logged with a reason and recaptured at Firsthand’s cost.
- Does Firsthand state an agreement score or accuracy rate?
- No. The egocentric pages state a second-reviewer pass but no inter-annotator agreement score, accuracy rate or sample rate.
- Can I set my own action vocabulary?
- Yes. The skill spec sets the action vocabulary, environment and label set before capture, so labels use the terms your training stack expects.
- Which label fields are in the episode schema?
- The annotations group lists hand_joints, hand_visible, body_joints, contact_events, instance_masks, objects, action_segments and gaze_target.