> For the complete documentation index, see [llms.txt](https://whitepaper.qorbiworld.com/qorbi-world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.qorbiworld.com/qorbi-world/one-tap-fps/weapon-skins.md).
# Weapon Skins
### Collection Details
This collection of new skins is called the “Color Series”. Inspired by One Tap’s 5 primary maps which are Scorch, Stonehalla, Corridor, Arctic, and Toxic. The rich and vibrant designs and color of these inspiring maps are used throughout the collection to celebrate the release of the game and its unique approach to competitive gameplay. There are 400 different unique variations of the skins, with each variation giving you a unique and enhanced skin experience.
| **Type** | **Rarity** | **Supply** | **Variation** |
| --------- | ---------- | ---------- | ------------- |
| Common | 63% | 120000 | 150 |
| Rare | 26% | 50000 | 100 |
| Epic | 7% | 12500 | 50 |
| Legendary | 3% | 5000 | 50 |
| Primal | 1% | 2500 | 50 |
### Collection Preview
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://whitepaper.qorbiworld.com/qorbi-world/one-tap-fps/weapon-skins.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.