---
title: "Search"
canonical: https://trickest.com/docs/developer-tools/cli/search
description: "Search across tools, modules, skills, workflows, memory, spaces, and solutions from the trickest CLI."
---

# Search

`trickest search <query>` runs a **cross-resource** search in one shot — useful
when you know a name fragment but not which command family owns it.

## Usage

```bash
trickest search amass
trickest search "api test" --type skill --limit 10
trickest --output table search httpx
```

| Flag | Description |
|---|---|
| `--limit <n>` | Max results **per resource type** (default 5) |
| `--type <type>` | Filter: `tool`, `module`, `skill`, `workflow`, `memory`, `spaces`, `solutions`, or `all` |

## Output shape

In default JSON mode, results are grouped by resource type. In `--output table`
mode the CLI prints sections such as:

```text
library (5)
  amass — The OWASP Amass Project … 44be711b
  …

Tools (5)
  amass — …
```

Each hit includes a short description and an ID fragment you can pass to the
matching `get` / `info` command (`library info`, `tool list`, `skill get`, etc.).

## When to use `search` vs family commands

| Goal | Command |
|---|---|
| Fuzzy find across everything | `trickest search <query>` |
| Browse public catalog | `trickest library ls <query>` |
| List your private tools | `trickest tool list` (paginated) |
| Find a workflow by name | `trickest workflow ls --all --filter <q>` |
| Semantic memory recall | `trickest memory search <query>` |

## Related

<CardGroup cols={2}>
  <Card title="Command Index" icon="list" href="/docs/developer-tools/cli/command-index">
    Full list of top-level commands.
  </Card>
  <Card title="Library, Tools & Modules" icon="cube" href="/docs/developer-tools/cli/library-tools-modules">
    Deep reference after you've found a tool name.
  </Card>
</CardGroup>

---
_Markdown source of https://trickest.com/docs/developer-tools/cli/search._