> For the complete documentation index, see [llms.txt](https://docs.skullco.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skullco.in/overview.md). # Overview Skullcoin turns attention into repeatable, on-chain activity through **human-skill games** that are **provably fair** and **economically sustainable**.\ \ We combine three inventions: * **Find2Earn:** open hunts on digital maps where players race to pinpoint a real place before anyone else. * **Encrypted NFTs:** dual-layer NFTs (public art + owner-only secret) that enable honest **incomplete-information** gameplay on-chain. * **Strike:** a readable, real-time combat loop with mind-games, extended by stats and gear. Each module stands alone and composes with the others. The result is a game world where **information has value**, outcomes are **auditably fair**, and the **economy sustains itself through play, not speculation**. --- # 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.skullco.in/overview.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.