agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/IsaacCapture/src/python/isaaccapture/cts/hand/checker/AGENTS.md

IsaacCapture / checker

AGENTS.md438 starsChanged 31 days agoApache-2.0View on GitHub

CRITICAL: complete the mandatory AGENTS.md preflight in ../../../../../../AGENTS.md before editing here, and read ../AGENTS.md and ../../common/AGENTS.md. - Per-hand checks subclass HandCheck(side) and are registered through per_hand(), which copies the policy fields and merges the two sides: any fail fails, else any insufficient is insufficient. A check that compares the hands subclasses _PairCheck, which pairs opposite-side records within PAIR_TOLERANCE_NS and leaves a check with no pairs unanswered. - A cross-hand check gates on the pose before judging the device. Not palm…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    A cross-hand vector compared across windows keeps one sign: Write it right minus left everywhere.

    line 29
  2. Very specific:

    Unanswered is not failed: When PALM and the metacarpals are all invalid, optional_joints.geometry_consistent has nothing to judge and says …

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 -->

Agent notes — cts/hand/checker/

CRITICAL: complete the mandatory AGENTS.md preflight in ../../../../../../AGENTS.md before editing here, and read ../AGENTS.md and ../../common/AGENTS.md.

  • Per-hand checks subclass HandCheck(side) and are registered through per_hand(), which copies the policy fields and merges the two sides: any fail fails, else any insufficient is insufficient. A check that compares the hands subclasses _PairCheck, which pairs opposite-side records within PAIR_TOLERANCE_NS and leaves a check with no pairs unanswered.
  • A cross-hand check gates on the pose before judging the device. Not palm down, not facing, not rolled far enough is a PERFORMANCE outcome (Outcome.attribution), so a missed pose asks for a retake instead of failing the glove.
  • Structural questions use the OpenXR joint frame, not a threshold: −Z along the bone toward the tip, +Y dorsal. Handedness depends on quaternion.component_order, because a wxyz stream makes every axis read wrong.
  • Shape measurements are in the wrist frame (Frame.local), so they survive any placement of the hand in the world.
  • A window is not held for its whole length. Performers lift a hand partway through a flat window. Gate each frame on the pose itself (still, palm down, at table height) and take the median of per-frame measures; a joint-wise mean over a window averages two placements into a hand that never existed.
  • A cross-hand vector compared across windows keeps one sign. Write it right minus left everywhere; a roll reference taken as one difference and judged against the other doubles the reference gap, and a small synthetic gap hides it.
  • Nearest-neighbour is only structural when the neighbours are far. Thumb to fingertip works; fingertip to fingertip across pressed palms does not, since the neighbours are 2 cm apart and any offset over 1 cm reads as a wrong finger.
  • Window checks are required = False. Whether a step was performed attributes to PERFORMANCE, so a missed pose asks for a retake rather than blaming the device.
  • Unanswered is not failed. When PALM and the metacarpals are all invalid, optional_joints.geometry_consistent has nothing to judge and says so.
  • Oracle check names are the vocabulary. Renaming a check means updating ../oracle/fixtures_index.json through the generator, never by hand.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free