# How Skylark Works

## Problem

<figure><img src="/files/riU78Sd3KJggPivGxs6u" alt=""><figcaption></figcaption></figure>

Let's Elaborate!

* Consumers have much more to earn from their data being monetized by centralized entities.
* Brands/communities ability to discovery and associate their consumers is heavily dependent on what platform you are aiming towards.
  * It is oversaturated and  marketing efforts are compounded trying to build your community tribes.

## Solution

<figure><img src="/files/4FuD4VBx7eIOFuDuQpCm" alt=""><figcaption></figcaption></figure>

## Multi-Modal Engagement System

<figure><img src="/files/wyW12satBNQ38kVHk8NH" alt=""><figcaption></figcaption></figure>

### Other Modules

<figure><img src="/files/sflI7CqDpPtPhAYOjvi6" alt=""><figcaption></figcaption></figure>

## The ARC of Participation

<figure><img src="/files/IUzO4Xge2XjszaiukhkE" alt=""><figcaption></figcaption></figure>


---

# 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://skylark.gitbook.io/skylark/skylark/how-skylark-works.md?ask=<question>
```

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.