# Query Templates

Start with the user's actual task, then map it to a small query set.

## By functionality

Use these when the user names a job directly:

- `repo`
- `codebase`
- `github`
- `browser`
- `file`
- `document`
- `search`
- `automation`
- `memory`
- `workflow`

## By practical outcome

Use these when the user describes a result instead of a category:

- `analyze repository`
- `read codebase`
- `manage github`
- `safe filesystem`
- `find skills`
- `summarize documents`
- `browser automation`
- `project planning`

## By provider or integration

Use these when the user already depends on a tool:

- `github`
- `feishu`
- `notion`
- `tavily`
- `chrome`
- `mcp`

## Query discipline

Run a narrow first pass with one to three direct queries.

Then expand only if needed:

1. direct task noun
2. workflow phrase
3. provider or integration name

Example for repo understanding:

- `repo`
- `codebase`
- `github`

Example for file workflows:

- `file`
- `filesystem`
- `document`

Example for discovery itself:

- `find skills`
- `search`
- `marketplace`