> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/getting-started/learn-80-of-shade-in-2-minutes.md).
# Learn 80% of Shade in 2 minutes
Most of the ways you will use Shade on a day-to-day can be learned in [2 minutes](https://www.youtube.com/watch?v=qiTMrJkC40Q).
{% stepper %}
{% step %}
## Use natural language in your AI search
Our neural search works best when you use natural language instead of tags. You can also search an individual folder instead of the current drive with **`cmd/ctrl+f`**. Alternatively, you can access the AI Search via our Command Pallete with **`cmd/ctrl+k`**
{% endstep %}
{% step %}
## Filter for specific attributes
Get granular with filters on file level attributes or custom metadata.
{% endstep %}
{% step %}
## Share externally with invites or published links
Right click on any folder or asset to invite collaborators via email or send out published links with optional passwords, expiration dates, and view limits.
{% endstep %}
{% step %}
## Manage your ShadeFS mount
ShadeFS works by allotting cache space on your computer or an external directory. After you set up ShadeFS, you can adjust these settings and get to work by hitting “mount” on any drive on the left panel. Right-click any file or folder and select "Pin to Cache" to keep important assets available offline for instant access.
{% endstep %}
{% step %}
## Put it all together
Start with an AI search to find what you are looking for, review the comments, and open the file locally to start working.
{% endstep %}
{% endstepper %}
---
# 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://academy.shade.inc/getting-started/learn-80-of-shade-in-2-minutes.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.
