> ## Documentation Index
> Fetch the complete documentation index at: https://docs.entire.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Search from Your Agent
> Use the `search` Skill so your agent can find previous Entire history before or during work.
Use the `search` Skill when you want your agent to look up previous checkpoints, sessions, or commits before it starts changing code.
## Before You Start
Make sure you have [Skills installed](/learn/skills) and that `entire login` works in the environment where your agent runs.
The `search` Skill uses [`entire search`](/cli-reference/search), summarizes likely matches, and helps the agent decide which checkpoint or session to inspect next.
## See Search in action
The recording above comes from [Bring Your Entire Context to Your Agents with Skills](https://entire.io/blog/bring-your-entire-context-to-your-agents-with-skills), which introduces the core Skills workflows.
## Run the Skill
Use the `search` Skill directly:
```text theme={null}
/search where did we move old missions out of the main list
```
You can also ask in natural language:
```text theme={null}
search past work for duplicate validation
```
## Tips for Writing Search Prompts
Good prompts include the feature, behavior, bug, file, or decision you want the agent to find:
```text theme={null}
search past work for duplicate validation in the checkout form
```
```text theme={null}
search previous sessions about retry logic for failed mirror pushes
```
```text theme={null}
find the checkpoint where we changed auth token refresh behavior
```
Avoid vague prompts like:
```text theme={null}
search the old thing
```
## Continue with
Run `entire search` yourself.
Learn how Skills help agents use Entire.