Use OrbitSmith with Your AI

Start at the following OrbitSmith public directory and follow its links to retrieve the data for “adras J”.
https://orbitsmith.net/data/orbitsmith/catalog/directory/index.html

Briefly explain the name, NORAD ID, launch date if recorded, and data timestamps in plain English, with sources. If there are multiple candidates, let me choose. Do not add general knowledge. If retrieval fails, tell me where it stopped.

Also report the recorded classification, perigee and apogee altitudes, and period when available, with units and a brief explanation. Distinguish the snapshot time from the orbital reference time, retain warnings, and leave missing values unknown. These records do not show current position or operational status.

After the first answer, you can continue in the same chat. For example, ask about HST instead.

Using the same OrbitSmith directory, now look up “HST” and explain the same fields in plain English, with sources and dates.
https://orbitsmith.net/data/orbitsmith/catalog/directory/index.html

Let me choose if there are multiple candidates. Do not add general knowledge; if retrieval fails, tell me where it stopped.

Read the guide below, then start at the OrbitSmith public directory and follow its links to retrieve the actual records for both “ADRAS-J” and “HST”.
https://orbitsmith.net/llms.txt
https://orbitsmith.net/data/orbitsmith/catalog/directory/index.html

If either name fits more than one object, show the candidates, stop, and ask me to choose a NORAD ID. Check that the NORAD ID in each record you retrieved is the object it is meant to be; never use a sample or example object's record instead.

Then put the two records side by side, briefly: name, NORAD ID, object type, launch date if supplied, perigee and apogee altitudes in km, inclination in degrees, period in minutes. Keep the names, IDs and values as OrbitSmith returned them.

State the data snapshot time, the response generation time (generated_at) returned by OrbitSmith, and the orbital element epoch (and the TLE epoch when it differs) separately, and keep any epoch-mismatch warning OrbitSmith returned. Do not present the two records as where the objects are at the same moment.

Leave missing values unknown; if a field is supplied for only one object, show unknown for the other and give no difference for that field. You may subtract the same field between the two objects (for example apogee minus apogee) if you say you calculated it and give the unit. Do not estimate the distance between the objects, how close they pass, collision or reentry risk, safety, or which one is better.

Cite each record URL and its upstream sources. Explain briefly in plain English. Do not fill anything in from general knowledge. If either record cannot be retrieved, tell me which one and where it stopped, and do not present the comparison as complete.

Use OrbitSmith to calculate HST's position at a time I choose. First ask me for the full date, time and time zone; do not choose a time for me.
Read this guide and follow its position-calculation instructions:
https://orbitsmith.net/llms.txt

Find the object in the public directory below. If there are several candidates, stop and let me choose a NORAD ID.
https://orbitsmith.net/data/orbitsmith/catalog/directory/index.html

After the object and time are agreed, fetch the position calculation URL for that NORAD ID and UTC. Check the returned ID and time. Briefly explain the latitude, longitude and WGS84 ellipsoid height in plain English, with the orbital data's reference time, sources and warnings. This is a calculated position at the requested time, not an observed current location or a pass prediction. If retrieval fails or no result is returned, explain where it stopped; do not substitute another object, time or calculation.

Use browser controls to operate OrbitSmith Passes, not just fetch the page text:
https://orbitsmith.net/passes

First ask me for the city, period (Tonight, Next 24h or Next 3 days) and display time zone. Confirm the actual dates and interval for that choice. Do not reuse a saved location, obtain my current location or choose another period without asking.

Search for the city on the page and let me choose if the place name is ambiguous. Let Passes calculate, then select ISS (NORAD ID 25544) and open its details. Report the selected coordinates, period and filters. Stop if you cannot operate the browser, the calculation fails, or the requested conditions are unsupported; do not substitute another object, time or your own calculation.

Briefly explain the displayed pass candidates in plain English: date and time zone, start, peak and end times, directions and maximum elevation. Preserve warnings and cite the page and its stated sources. If available, distinguish the result generation time from the TLE epoch; otherwise say they are unavailable. The page assumes WGS84 ellipsoid height 0 m and displays times in the device time zone. Read only relevant result fields, not the entire large JSON. No candidate under the selected filters does not mean no geometric pass. Brightness is not assessed and visibility is not guaranteed; do not infer operational safety.

Use browser controls to operate OrbitSmith Mission Engineering Workbench and help me check the radio-link margin for my design:
https://orbitsmith.net/mission-engineering?group=ground_comms&module=link_budget

First ask whether this is my actual design or an educational scenario, and which concept to use. Before editing, confirm what may be changed; do not overwrite a saved design or adopt default values without my permission. Ask for the orbit and its source/reference time, full dates/time zone (convert to UTC with me), ground station, coordinates, WGS84 ellipsoid height and minimum elevation. Do not obtain my location. Treat any planning orbit or assumed station as an assumption, not an observed satellite record or verified station specification.

Follow the page's prerequisites in the same concept and revision: Visibility → Ground-station geometry and distance → Link budget. Ask for frequency, transmit power, transmit/receive antenna gains, receiver noise temperature, data rate, required Eb/N0, required margin and all nine losses, with units and sources or explicit assumptions. If a value is missing, stop and list what is needed; do not replace it with zero or invent a specification. Only use an educational assumption after I explicitly agree to it. Leave human input-confirmation checkboxes to me; do not mark them confirmed on my behalf. Once I have confirmed the inputs, run each calculation on the page.

Read only relevant displayed results. Briefly explain in plain English the inputs used, near/far distances, best/worst radio-link margins in dB and how they compare with my required margin. Use only valid results for the selected concept and revision, and distinguish detailed results from the simplified check. Cite OrbitSmith, the page URL and sources actually shown. Distinguish the result generation time from the orbital reference time when available; otherwise say unknown. Preserve missing information, assumptions and warnings.

If browser operation, inputs or prerequisites are unavailable, or calculation fails, stop and explain where; do not substitute a different design, orbit, time or your own calculation. This is an educational/initial design calculation, not a guarantee of actual communication, frequency authorization, ground-station availability, booking or operational safety. Do not infer transferable MB or treat geometric visibility time as usable transmission time. Do not upload or send my design to another service.

Use browser controls to operate OrbitSmith Mission Engineering Workbench and compare the radio-link margin before and after changing one communication input:
https://orbitsmith.net/mission-engineering?group=ground_comms&module=link_budget

First ask which concept to use, whether it is an actual design or an educational scenario, what I want to change, and the before/after values and units. Lowering the data rate is only an example: do not choose values for me. Confirm permission to edit the chosen Workbench input; do not overwrite a saved design without permission or change the Guided concept. Keep the other inputs fixed. Do not obtain my location.

Before calculating, confirm the orbit, its source/reference time, full UTC interval (confirm any time-zone conversion with me), station coordinates, WGS84 ellipsoid height and minimum elevation. Also confirm frequency, transmit power, both antenna gains, receiver noise temperature, data rate, required Eb/N0, required margin and all nine losses, with units and sources or explicitly agreed assumptions. Fictional or assumed values are not observed satellite data or verified equipment specifications. Stop if inputs are missing; do not invent them or replace them with zero. Leave human input-confirmation checkboxes to me.

Before editing, obtain valid detailed results for the selected concept and revision, following the page's Visibility → Ground-station geometry and distance → Link budget prerequisites. I will confirm the inputs before you run each calculation. Keep the before inputs, distances, best/worst margins and required margin in this conversation, with units, concept/revision when visible, sources, warnings and assumptions. Editing can remove the earlier result; do not claim the app automatically stores its history.

Change only the agreed Workbench input. Follow the page's invalidation and prerequisite requirements, wait for my confirmation again and then recalculate. Do not mark checkboxes on my behalf. Avoid unnecessary reloads or concept switches. Check that the after result matches the new input and selected concept/revision; do not reuse an invalid old result.

Briefly compare the before/after displayed results in plain English. Label any subtraction as your arithmetic, with units. Keep the simplified check separate from detailed results and distinguish result generation times from the orbital reference time; unreadable values remain unknown. Cite OrbitSmith, the page URL and displayed sources. Retain warnings, assumptions and unassessed items. A model-derived distance under a fictional orbit is not measured distance. Do not infer effects on power consumption, cost, schedule, transferable MB, actual communication, station availability, operational safety or the best overall mission.

If browser controls, inputs, previous results or the calculation are unavailable, stop and explain where; do not substitute a different design or your own calculation. Do not upload or send my design to another service. This is for education and initial design exploration, not an operational guarantee.

Use browser controls to operate OrbitSmith Mission Engineering Workbench and compare the mass budgets of two saved concepts:
https://orbitsmith.net/mission-engineering?group=spacecraft&module=mass_budget

Use the same browser tab that contains my saved concepts. First ask which two concepts to compare, whether this is an actual design or an educational scenario, and what differences I want to examine. This example covers mass only. Ask permission before editing. If concepts need to be created, ask me first and use Mission Designer (https://orbitsmith.net/designer); do not delete or overwrite existing concepts to make room. Do not obtain my location or upload my design to another service.

Before creating anything, inspect the current mission type and saved list. Permission to create concepts is not permission to reset the current design. Selecting a mission-type card (template) again clears the saved list; do not assume those concepts remain elsewhere. For two alternatives within the same mission type, agree on inputs, save the first, change only agreed settings without selecting a mission-type card again, and save the second. Confirm both names appear before entering Workbench. If I want different mission types (such as optical versus SAR), or a saved concept disappears, explain the limitation and stop. Do not reset, recreate or replace the requested comparison on your own. Do not change an actual design into an educational scenario without my explicit agreement.

Use the detailed Mass budget in Workbench, not Mission Designer’s simplified mass breakdown as a substitute. Confirm that the design limit, growth allowances, overall reserve and all other agreed conditions are actually reflected in the detailed inputs and result. If a condition is not reflected, list it and stop before comparison. Permission to run a simplified check is not permission to treat it as completion of the detailed comparison.

For each concept, show its name and readable ID/revision. Confirm every mass entry including propulsion hardware, growth percentages, overall reserve, design limit and payload screening range, with units and sources or explicitly agreed educational assumptions. Identify shared conditions and differences. Do not adopt defaults silently, invent missing inputs or fill them with zero. Leave confirmation checks to me unless I explicitly authorize you for the specific inputs and calculation.

For the first concept, confirm the inputs and run Mass budget on the page. Immediately record the input values, current mass estimate, growth allowance, planned mass excluding fuel, remaining design allowance, units, sources and warnings in this conversation, before switching. Keep the simplified check separate from the detailed result. Switching concepts resets edited inputs and checks, while an earlier result may remain; do not treat restored fields as that result's inputs or claim permanent history is saved.

Select the second concept, confirm its own inputs and calculate. Record the same items immediately. Check each input/result pair belongs to the selected concept and its relevant revision. Avoid unnecessary reloads. After a reload or unexpected state change, reconfirm conditions; if the records cannot be matched, stop instead of mixing results. Report any readable result generation time and keep it separate from an orbital epoch; otherwise leave it unknown. Do not open unrelated modules or read a large JSON record in full.

Briefly compare the recorded results in plain English with common conditions, differences, units, OrbitSmith, page URLs, displayed sources and warnings. Label any subtraction as the AI's arithmetic. Do not call planned mass a measured or fuel-inclusive mass, or infer the best overall mission, cost, schedule, structural/launch suitability or operational safety. If browser controls, required inputs or results are unavailable, explain where you stopped without substituting your own calculation. This is educational/initial design analysis, not an operational guarantee.