# Introduction **Welcome to the Skydel Custom Signal documentation!** The Custom Signal feature allows users to create their own personalized signals and attach them to GNSS satellites, so that they are streamed alongside regular GNSS signals. The purpose of this feature is to provide advanced users a tool that allows them to design GNSS or non-GNSS (such as LEO constellation signals) and evaluate their performance. It avoids the burden of designing an engine that will simulate the satellite and/or vehicle dynamics, and all the environmental effects (atmospheric effects, multipath, jamming, spoofing, etc.). Users can then focus all their efforts on the design and architecture of the signal itself. **How can you begin working on your Skydel Custom Signal?** The first step is to follow the instructions on setting up the development environment on either [Ubuntu](/skydel-custom-signal-documentation/development-environment/ubuntu-22.04.md) or [Windows](/skydel-custom-signal-documentation/development-environment/windows.md). Are you having trouble figuring out how Custom Signals are integrated in Skydel? This [page](/skydel-custom-signal-documentation/usage.md) explains it all. ## SDK and Examples on GitHub The source code located on [GitHub](https://github.com/learn-orolia/skydel-custom-signal) includes the software development kit (SDK) and multiple custom signal examples. ## Support Do you have questions? Let us know on the [Skydel User Forum](https://learn.safran-navigation-timing.com/)! --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://skydel.gitbook.io/skydel-custom-signal-documentation/introduction.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.