nimble-crawl-reference
Reference for nimble crawl command. Load when bulk-crawling many pages asynchronously. Contains: async workflow (create → status → tasks results), all flags, polling guidelines, CRITICAL: use task_id (not crawl_id) for results, crawl vs map comparison.
What this skill does
# nimble crawl — reference
Async bulk crawling — starts a crawl job, returns a `crawl_id`, then you poll for status and retrieve per-page content via individual `task_id`s.
> **Tip:** For LLM use, prefer `nimble map` + `nimble extract --format markdown` (faster, cleaner). Use crawl when you need raw HTML archives of many pages at once.
## Table of Contents
- [1. Create crawl (async)](#1-create-crawl-async)
- [2. Get crawl status](#2-get-crawl-status)
- [3. List crawls](#3-list-crawls)
- [4. Cancel crawl](#4-cancel-crawl)
- [Polling guidelines](#polling-guidelines)
- [Retrieving page content](#retrieving-page-content)
- [Crawl vs Map](#crawl-vs-map)
---
## 1. Create crawl (async)
**Parameters:**
| Parameter | CLI flag | Type | Default | Description |
| ------------------------- | --------------------------- | -------- | --------- | -------------------------------------------- |
| `url` | `--url` | string | required | Starting URL |
| `limit` | `--limit` | int | `5000` | Max pages (1–10,000) — always set this |
| `name` | `--name` | string | — | Label for tracking |
| `sitemap` | `--sitemap` | string | `include` | `include` \| `only` \| `skip` |
| `include_path` | `--include-path` | string[] | — | URL path regex to include (repeatable) |
| `exclude_path` | `--exclude-path` | string[] | — | URL path regex to exclude (repeatable) |
| `max_discovery_depth` | `--max-discovery-depth` | int | `5` | Max link depth from start (1–20) |
| `crawl_entire_domain` | `--crawl-entire-domain` | bool | `false` | Follow sibling/parent paths |
| `allow_subdomains` | `--allow-subdomains` | bool | `false` | Follow links to subdomains |
| `allow_external_links` | `--allow-external-links` | bool | `false` | Follow links to external domains |
| `ignore_query_parameters` | `--ignore-query-parameters` | bool | `false` | Deduplicate query-param variants |
| `callback` | `--callback` | string | — | Webhook URL for real-time page notifications |
| `extract_options` | `--extract-options` | object | — | Extraction config applied to each page |
**CLI:**
```bash
nimble crawl run --url "https://docs.example.com" --limit 50 --name "docs-crawl"
```
**Python SDK:**
```python
from nimble_python import Nimble
nimble = Nimble(api_key=os.environ["NIMBLE_API_KEY"])
resp = nimble.crawl.run(url="https://docs.example.com", limit=50, name="docs-crawl")
crawl_id = resp.crawl_id
```
**Response fields:** `crawl_id`, `status` (initial: `queued`), `url`, `name`, `crawl_options`, `created_at`
**Crawl status values:** `queued` → `running` → `succeeded` / `failed` / `canceled`
---
## 2. Get crawl status
**Parameters:**
| Parameter | CLI flag | Type | Description |
| --------- | -------- | ------ | --------------------- |
| `id` | `--id` | string | `crawl_id` (required) |
**CLI:**
```bash
nimble crawl status --id "abc-123"
```
**Python SDK:**
```python
crawl = nimble.crawl.status(id=crawl_id)
print(crawl.status, crawl.completed, crawl.total)
```
**Response adds:** `total`, `pending`, `completed`, `failed`, `tasks[]`
| Field | Description |
| ----------------- | ----------------------------------------------------- |
| `tasks[].task_id` | Use with `nimble tasks results` to fetch page content |
| `tasks[].status` | `pending` / `processing` / `completed` / `failed` |
> **CRITICAL:** Use `tasks[].task_id` — NOT `crawl_id` — to fetch page content. Using `crawl_id` with tasks returns 404.
---
## 3. List crawls
**Parameters:**
| Parameter | CLI flag | Type | Description |
| --------- | ---------- | ------ | ---------------------------------------------------------------------- |
| `status` | `--status` | string | Filter: `queued` \| `running` \| `completed` \| `failed` \| `canceled` |
| `limit` | `--limit` | int | Results per page |
| `cursor` | `--cursor` | string | Pagination cursor |
**CLI:**
```bash
nimble crawl list --status running
```
**Python SDK:**
```python
result = nimble.crawl.list()
# result.data = list of crawl objects
# result.pagination = { has_next, next_cursor, total }
```
---
## 4. Cancel crawl
**Parameters:**
| Parameter | CLI flag | Type | Description |
| --------- | -------- | ------ | --------------------- |
| `id` | `--id` | string | `crawl_id` (required) |
**CLI:**
```bash
nimble crawl terminate --id "abc-123"
```
**Python SDK:**
```python
nimble.crawl.terminate(id=crawl_id)
# Returns: {"status": "canceled"}
```
---
## Polling guidelines
```bash
CRAWL_ID=$(nimble crawl run --url "https://example.com" --limit 100 --name "my-crawl" \
| python3 -c "import json,sys; print(json.load(sys.stdin)['crawl_id'])")
while true; do
STATUS=$(nimble crawl status --id "$CRAWL_ID" \
| python3 -c "import json,sys; print(json.load(sys.stdin).get('status',''))")
echo "Status: $STATUS"
[ "$STATUS" = "succeeded" ] || [ "$STATUS" = "failed" ] || [ "$STATUS" = "canceled" ] && break
sleep 30
done
```
| Crawl size | Poll interval |
| ------------ | ------------- |
| < 50 pages | every 15–30s |
| 50–500 pages | every 30–60s |
| 500+ pages | every 60–120s |
---
## Retrieving page content
After crawl `succeeded`, fetch each completed task — see `nimble-tasks` reference:
```bash
nimble tasks results --task-id "task-456"
```
---
## Crawl vs Map
| | `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 |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.