skills/web-search-tools/nimble-web-expert/references/nimble-map/SKILL.md
Reference for nimble map command. Load when discovering URLs on a site before bulk extraction. Contains: all flags (limit 1-100000, sitemap include/only/skip, domain_filter), response structure {links[].url/title/description}, map→filter→extract pattern, map vs crawl comparison.
npx skillsauth add nimbleway/agent-skills nimble-map-referenceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Discovers all URLs on a site in seconds. Returns URL metadata (url, title, description) — run extract on results to get page content. Single synchronous call — no polling required.
| Parameter | CLI flag | Type | Default | Description |
| --------------- | ----------------- | ------ | --------- | ------------------------------------------------------------------------------------ |
| url | --url | string | required | Starting URL |
| limit | --limit | int | 100 | Max URLs returned (1–100,000) |
| sitemap | --sitemap | string | include | include (sitemap + crawl) | only (sitemap only, fastest) | skip (crawl only) |
| domain_filter | --domain-filter | string | — | domain (exact) | subdomain (include subdomains) | all (follow all links) |
| country | --country | string | ALL | ISO Alpha-2 proxy location (e.g. US) |
| locale | --locale | string | — | LCID locale (e.g. en-US) or auto |
nimble map --url "https://docs.example.com" --limit 100
# Sitemap only (fastest)
nimble map --url "https://example.com" --sitemap only --limit 500
# Extract just the URL list
nimble --transform "links.#.url" map --url "https://docs.example.com" --limit 100
from nimble_python import Nimble
nimble = Nimble(api_key=os.environ["NIMBLE_API_KEY"])
resp = nimble.map(url="https://docs.example.com", limit=100, sitemap="include")
links = resp.links # list of link objects
urls = [l.url for l in links]
| Field | Type | Description |
| --------------------- | ------- | ------------------------------------ |
| task_id | string | Request identifier |
| success | boolean | Whether the request succeeded |
| links | array | Discovered URLs |
| links[].url | string | The discovered URL |
| links[].title | string | Page title (if available) |
| links[].description | string | Page meta description (if available) |
# Map → filter → extract
nimble --transform "links.#.url" map --url "https://docs.stripe.com" --limit 200 > .nimble/urls.txt
grep "charges\|refund" .nimble/urls.txt
# Specific path section
nimble map --url "https://shop.example.com/products/" --limit 200
| | map | crawl |
| -------- | ------------------------------------------- | ------------------------- |
| Speed | Seconds (sync) | Minutes (async) |
| Output | URL list with metadata | Full page content per URL |
| Best for | Discover URLs, then selectively extract | Archive all pages at once |
| LLM use | ✅ Combine with extract --format markdown | ⚠️ Returns raw HTML |
development
Builds Databricks data products from live web data, end to end: discovers the right Nimble web-data agents, scrapes into Delta tables, and produces an AI/BI dashboard and/or a deployed Databricks App — a table → dashboard → app workflow, for production data products or quick demos. Use whenever a request pairs live or scraped web data WITH a Databricks destination — e.g. "scrape Amazon/Walmart prices into a Delta table and build a dashboard", "load Zillow/Instagram/Maps/search results into Databricks and build a dashboard or app", "showcase Nimble + Databricks to a prospect". Prefer it over nimble-web-expert or competitor-intel when the data lands in Databricks. Do NOT use for one-off web fetches or CSV exports with no Databricks destination — use nimble-web-expert instead. Do NOT use for competitor or company research briefings — use competitor-intel or company-deep-dive instead. Do NOT use for generic Databricks work with no Nimble/web-data angle — use the official databricks-* skills instead.
development
Finds qualified candidates for a role by searching LinkedIn, Indeed, GitHub, and other professional platforms using Nimble Web Search Agents. Accepts a job description, role title, or freeform request and returns a ranked candidate list with profiles, skills, and contact signals. Use this skill when the user wants to find, source, or recruit candidates for a role. Common triggers: "find candidates for", "source engineers in", "who can I hire for", "find me a [role]", "recruiting for", "talent search", "find a [role] in [city]", "build a candidate list", "sourcing for [role]", "who's available for", "find potential hires". Also triggers on a pasted job description followed by a sourcing request. Do NOT use for job market research or salary benchmarking — use market-finder instead. Do NOT use for researching a single known person — use company-deep-dive or meeting-prep instead.
development
Get web data now — fast, incremental, immediately responsive to what the user needs. The only way Claude can access live websites. USE FOR: - Fetching any URL or reading any webpage - Scraping prices, listings, reviews, jobs, stats, docs from any site - Discovering URLs on a site before bulk extraction - Calling public REST/XHR API endpoints - Web search and research (8 focus modes) - Bulk crawling website sections Must be pre-installed and authenticated. Run `nimble --version` to verify. For building reusable extraction workflows to run at scale over time, use nimble-agent-builder instead.
development
A building experience: create, test, validate, refine, and publish extraction workflows based on existing or new Nimble agents. For users who want to invest in a durable, reusable workflow for a specific domain — not get data immediately. Trigger phrases: "set up extraction for X site", "I need to extract from this site regularly", "build an agent for", "create a reusable scraper", "generate a Nimble agent", "refine my agent", "add a field to my agent", or when the user wants to run extraction at scale. For getting data immediately, use nimble-web-expert instead.