The normal way to ‘pass’ a parameter in a web application is to use a ‘?’ question mark followed by the parameter name, an equal sign, and the parameter value. This part is-> ‘?id=a2Xf10000000ZS1LEAW’.
I added the ‘/Marker’ to the URL since this is the ‘name’ of your Site in Salesforce. This is how you get to the pages in your Site. You enter the custom domain address for your Salesforce org. followed by the ‘/Marker’. In your case your custom Site address is https://dorothy.secure.force.com/Marker and the full address to open your Skuid page and pass in the ‘id’ of the Salesforce record to load is-> https://dorothy.secure.force.com/Marker?id=a2Xf1000000ZS1LEAW
Note that the parameter name can be anything. ‘id’ is used throughout Salesforce to represent the Salesforce Id for a given record. It could just as easily be ‘recordId’ or ‘mycustomboject’ or ‘ID’. It depends upon what your Skuid page is expecting. You will normally setup the name of the parameter in your Skuid model. Here is an example where the page parameter that the model will use is ‘id’.
I could change the Skuid model to use a parameter name ‘recordid’ (as below).
If you change your model to use ‘recordid’ as the paramter (as seen above), then your URL would be: https://dorothy.secure.force.com/Marker?recordid=a2Xf1000000ZS1LEAW
If your second object ‘CR_Path__c’ is on the same page, then I think you will need to modify the parameter name on the condition for the ‘CR_Path__c’ model. It is probably set to ‘id’. Change it to ‘crpathid’ (or whatever you want as long as it is not ‘id’). Then update your URL to include both parameters-> https://dorothy.secure.force.com/Marker?id=a2Xf1000000ZS1LEAW&crpathid=a0Tc10000000AB3XRW