> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/spikemark-6/navigating-spikemark/tags.md). # Tags Tags allow you to organize and find your Stagehands quickly. When you click on a tag, Spikemark will show you only the Stagehands with that tag. If you want to see all the Stagehands in your show. Click the "All" tag. ## Using Tags In The Jogging Workspace ### Create A New Tag
Create a new tag
1. From the Identification pane click the + button. 2. Give the tag a name. 3. Select a color for the tag. 4. Click "OK". ### Delete A Tag
Create a new tag
1. From the Identification pane select the tag. 2. Click the "X" button. ### Assign A Tag
Create a new tag
1. Select the Stagehands you want to tag. 2. Select the tag in the all tags box. 3. Click the right pointing arrow to assign the tag to the Stagehands. ### Un-Assign A Tag
Create a new tag
1. Select the tag in the assigned box. 2. Click the left pointing arrow to un-assign the tag from the Stagehands. ## Using Tags From The Tags Bar ### Create A New Tag
Create a new tag
1. Right-click on a tag. 2. Click "Add Tag". 3. Give the tag a name. 4. Select a color for the tag. 5. Click "OK". ### Edit A Tag
Create a new tag
1. Right-click on a tag. 2. Click "Edit Tag". 3. Change the name of the tag. 4. Change the color of the tag. 5. Click "OK". ### Delete A Tag
Create a new tag
1. Right-click on a tag. 2. Click "Delete Tag". --- # 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://docs.creativeconners.com/docs/spikemark-6/navigating-spikemark/tags.md?ask=&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.