tavily-map
Discover and list all URLs on a website without extracting content, via the Tavily CLI. Use this skill when the user wants to find a specific page on a large site, list all URLs, see the site structure, find where something is on a domain, or says "map the site", "find the URL for", "what pages are on", "list all pages", or "site structure". Faster than crawling — returns URLs only. Essential when you know the site but not the exact page. Combine with extract for targeted content retrieval.
What this skill does
# tavily map Discover URLs on a website without extracting content. Faster than crawling. ## Before running any command If `tvly` is not found on PATH, install it first: ```bash curl -fsSL https://cli.tavily.com/install.sh | bash && tvly login ``` Do not skip this step or fall back to other tools. See [tavily-cli](../tavily-cli/SKILL.md) for alternative install methods and auth options. ## When to use - You need to find a specific subpage on a large site - You want a list of all URLs before deciding what to extract or crawl - Step 3 in the [workflow](../tavily-cli/SKILL.md): search → extract → **map** → crawl → research ## Quick start ```bash # Discover all URLs tvly map "https://docs.example.com" --json # With natural language filtering tvly map "https://docs.example.com" --instructions "Find API docs and guides" --json # Filter by path tvly map "https://example.com" --select-paths "/blog/.*" --limit 500 --json # Deep map tvly map "https://example.com" --max-depth 3 --limit 200 --json ``` ## Options | Option | Description | |--------|-------------| | `--max-depth` | Levels deep (1-5, default: 1) | | `--max-breadth` | Links per page (default: 20) | | `--limit` | Max URLs to discover (default: 50) | | `--instructions` | Natural language guidance for URL filtering | | `--select-paths` | Comma-separated regex patterns to include | | `--exclude-paths` | Comma-separated regex patterns to exclude | | `--select-domains` | Comma-separated regex for domains to include | | `--exclude-domains` | Comma-separated regex for domains to exclude | | `--allow-external / --no-external` | Include external links | | `--timeout` | Max wait (10-150 seconds) | | `-o, --output` | Save output to file | | `--json` | Structured JSON output | ## Map + Extract pattern Use `map` to find the right page, then `extract` it. This is often more efficient than crawling an entire site: ```bash # Step 1: Find the authentication docs tvly map "https://docs.example.com" --instructions "authentication" --json # Step 2: Extract the specific page you found tvly extract "https://docs.example.com/api/authentication" --json ``` ## Tips - **Map is URL discovery only** — no content extraction. Use `extract` or `crawl` for content. - **Map + extract beats crawl** when you only need a few specific pages from a large site. - **Use `--instructions`** for semantic filtering when path patterns aren't enough. ## See also - [tavily-extract](../tavily-extract/SKILL.md) — extract content from URLs you discover - [tavily-crawl](../tavily-crawl/SKILL.md) — bulk extract when you need many pages
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.