OTIO Docs

Context: $ARGUMENTS

Quick start

• Find an OTIO class / function / adapter: → Step 2 (search --query <term>)
• Read the full API section: → Step 3 (section --page <page> --id <anchor>)
• Grab a whole tutorial / API page: → Step 4 (fetch --page <name>)
• Prime cache for offline use: → Step 5 (index)

When to use

• User asks "what does otio.schema.Clip take?" or "how do I subclass Track?"
• Need to confirm an adapter exists (EDL, FCP7-XML, FCPXML, AAF, ALE, XGES, SVG) before recommending.
• Need the otioconvert / otiotool / otiostat CLI surface (CLIs are documented via --help, not readthedocs — this skill pulls the tutorials + Python-API pages instead).
• Need to cite the canonical readthedocs URL or GitHub source of truth.
• Before writing OTIO Python code: verify API surface (classes, methods, serialization fields).