> For the complete documentation index, see [llms.txt](https://badgework.prepscouts.lk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://badgework.prepscouts.lk/junior-scouts/scout-award/signals.md).

# Signals

{% hint style="warning" %}
The Signals are mentioned in the NSM badge notes. Please refer to the section by clicking the below link
{% endhint %}

{% content-ref url="/pages/-MIrMJ4cHoQZJZOCkGDH" %}
[Scout Whistle & Hand Signals](https://badgework.prepscouts.lk/junior-scouts/national-scout-membership-badge/scout-whistle-and-hand-signals.md)
{% endcontent-ref %}

## Semaphore signals

### What is Semaphore?

&#x20;It’s a way of communicating across long distances, by holding flags in different positions to represent letters or numbers.

### Make a Semaphore flag

![](https://3619049534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MIozIAKaq918-cOtBC--3385112970%2Fuploads%2FzR1xcN5UPwoCuLceTZ3q%2Fimage.png?alt=media\&token=ca63cdd3-75b2-4100-959f-703752ddd8fe)

For this you will need either red and yellow A4 card or paper and some sticky tape.

1. Take one piece of red and one piece of yellow card or paper. You can make two flags from these.
2. Cut the card/paper diagonally from opposite corners as can be seen in the picture opposite.
3. Place the card/paper next to each other as seen in the picture and stick them together with the sticky tape on both sides.
4. You can add sticks to your flags if you want to. This can be done with lollipop sticks, kebab skewers or sticks from outside and attached using sticky tape

### Sending signals&#x20;

To send a Semaphore message correctly start by using the ‘Attention’ position and wait for the ‘Ready to receive’ position from the other team. When ready, start each word with the ‘Letters’ position and use the ‘Space’ position between each word. Finish the sentence with the ‘End of word’ position.&#x20;

### Receiving signals

To receive a message wait for the ‘Attention’ signal from the other team. When seen, reply with the ‘Ready to receive’ position. This is done by raising both flags straight above your head and then dropping them into the ‘Space’ position.

### Alphabet

<figure><img src="https://3619049534-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MIozIAKaq918-cOtBC--3385112970%2Fuploads%2FhfEKxNMTEzhVUPa25szG%2Fimage.png?alt=media&amp;token=cd5358a3-8fcd-464c-9380-b44e8da8bcaa" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://badgework.prepscouts.lk/junior-scouts/scout-award/signals.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
