# Step1: Clone Repo

Make a [fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of the [Repo](https://github.com/js-kingdata/indicators_factory). Including cloning locally and adding an upstream.

Review Github’s [instructions](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork) on how to make a pull request from a fork.

After that, you will get the following directory structure：

![](/files/6Pf78KphiZRLcwCjUZ0D)     

### crawlers/indicators/spiders

One indicator corresponds to one file, and the original files of all indicators are placed in it.

### crawlers/utils

Many public methods that crawlers need to use are placed here. Such as data formatting, Redis tools, etc.

## Create new indicator

We need create a new folder in `crawlers/indicators/spiders`

For Example: `mainstream_coin_long_short_ratio.`

This folder needs to contain thress basic files:

* Definition.md - This file contains background information about the indicator.
* indicator\_name.py - This file contains indicator logic code.
* \_\_init\_\_.py - This file is to config your inidicator spider.


---

# 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://open.kingdata.com/how-to-develop-an-indicator/step1-clone-repo.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.