VRTK V3 and/or SDK ?

With the Oculus integation asset, you have everything you need to start.

The VRTK asset helps simplifying more advanced interactions, but you probably do not need it immediatly.

The Oculus integration SDK includes several things :

- the base camera rigs: to track the headset and the hands. You can found an all set prefab in Oculus/VR/Prefabs/OVRCameraRig. If you want to move your character with the stick (raw movements, it is not what to use for the teleports), you can also use the OVRPlayerController

- OVRAvatar: if you want to display to your user the nice animated hands that you can see in many apps (or, if you also have a Rift, in the Rift home app), you can use OVRAvatar (Oculus/Avatar/Content/Prefabs/LocalAvatar). You also need the Ouclus Camera rig, in addition to this prefab. On the Quest, keep in mind to unchek "Show third person" on the OVRAvatar component. 

- a simple interaction system: in Oculus/SampleFramework, you will find lots of example of how to grab objets, teleport yourself, ... with simple and easy to understand/improve scripts. This part can replace VRTK for simple needs.

Please note also that since the last Oculus Quest updates, there is a few detection problems (the Quest could be detected as a go in your Unity builds). If you're starting to work on the Quest, you may think that you're doing something wrong, while it is a global problem ;)

It will probably be soon fixed, but in the meantime, you can see discussions about it there :

- https://forums.oculusvr.com/developer/discussion/79061/cant-record-only-one-hand-works-rebuild-your-manifest

- https://forums.oculusvr.com/developer/discussion/78926/bug-quest-shows-up-as-go-unityengine-xr-xrdevice-model#latest