# OSINT Navigator Skill

Use OSINT Navigator when a user needs to find, compare, or verify open-source intelligence tools for an investigation task.

## Use When

- The user asks how to perform an OSINT task and needs tool recommendations.
- The user wants to compare tools for a specific investigation workflow.
- The user has a known tool and needs documentation or usage context from OSINT Navigator.
- The user asks for categories of OSINT tooling, such as domains, social media, imagery, geolocation, transport, or companies.

## Connection Options

- MCP: use the remote Streamable HTTP MCP server at `https://navigator.indicator.media/mcp`. OAuth handles authentication. MCP access requires a Pro account.
- REST API: use `https://navigator.indicator.media/api/openapi.json` for the OpenAPI schema. Authenticate with `Authorization: Bearer on_...`.

## Tool Choice

- Use MCP `query` or REST `POST /api/query` for natural-language questions such as "How do I find who registered a domain?"
- Use MCP `search_tools` or REST `POST /api/tools/search` for direct keyword/category searches.
- Use MCP `search_tool_documentation` when you already have a `tool_id` and need richer documentation.
- Use REST `GET /api/categories` when building a UI, filter, or category picker.

## Category Hints

Common categories include:

- `domains_websites`
- `social_media`
- `image_video_analysis`
- `geolocation_mapping`
- `transport`
- `companies`

If a category search is too narrow, retry without a category and explain that the broader query may return adjacent tools.

## Response Rules

- Include tool names and URLs when available.
- Explain briefly why each recommended tool fits the investigation task.
- Do not invent tools or URLs. If the database does not contain a good match, say so and suggest a broader query.
- Prefer verified tool records from OSINT Navigator over general web memory.
- Keep recommendations practical: mention what the user should do with the tool, not just that it exists.
- For multiple tools, order the strongest fit first and include alternatives only when they add distinct value.
- Avoid legal advice. If appropriate, remind the user to follow applicable law, platform rules, and organizational policy.

## Output Pattern

Use this structure unless the user asks for something else:

1. Start with the best-matching tool and its URL.
2. Add one concise sentence explaining why it fits.
3. Add up to three alternatives when they cover meaningfully different workflows.
4. Note any important limitation, such as paid access, API requirement, or stale documentation, if known.

## Example Requests

- "Find tools for checking who registered a domain."
- "Search for image verification tools."
- "What can I use to archive a webpage?"
- "Show me transport or vessel-tracking tools."
- "Get documentation for a known OSINT Navigator tool ID."

## Limits

- Natural-language `query` calls are rate-limited by user tier.
- Direct tool search and documentation lookup are intended for lookup workflows and may not count against the same query quota.
- MCP access requires a Pro account. Use the REST API path when MCP authentication is unavailable.

## Minimal Prompt

Use this prompt when configuring an agent:

```text
Use OSINT Navigator for OSINT tool recommendations. Prefer its MCP tools or REST API over web memory. Return tool names, URLs, and concise reasons. Do not invent tools or URLs; if OSINT Navigator does not contain a good match, say so and suggest a broader query.
```