crawl
Skill1 starsChanged 9 months agoMITView on GitHub
Crawl any website and save pages as local markdown files. Use when you need to download documentation, knowledge bases, or web content for offline access or analysis. No code required - just provide a URL.
- Reads credentials
5 other projects use a version of this.
Adopted by
Most recently taken up by
- ZenRows/clitheir own version, first seen Nov 1, 2026
- eprouveze/claude-skillstheir own version, first seen Oct 20, 2026
- datalayer/agent-codemodetheir own version, first seen Oct 13, 2026
- cline/autoqatheir own version, first seen Sep 29, 2026
- xiaoshuai1024/skillstheir own version, first seen Aug 16, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- ZenRows/cli★ 16same name
- datalayer/agent-codemode★ 7same name
- xiaoshuai1024/skills★ 1same name
- cline/autoqa★ 0same name
- eprouveze/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- extractSkill
- inspiro-best-practicesSkill
- researchSkill
- searchSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Create an account at inspiro.top
- Very specific: line 16
Add it to ~/.claude/settings.json:
- Distinctive: line 25
Only API key authentication is supported.
- Very specific: line 53
When output_dir is provided, each crawled page is saved as a separate markdown file.
- Very specific: line 144
For agentic use (feeding results into context): Always use instructions + chunks_per_source.
- Distinctive: line 152
Use when feeding crawl results into an LLM context:
- Distinctive: line 187
Use when saving content to files for later processing:
- Very specific: line 207
Use map instead of crawl when you only need URLs, not content:
- Very specific: line 236
Omit
chunks_per_sourceonly for data collection: - when saving full pages to files
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Crawl Skill
Crawl websites to extract content from multiple pages. Ideal for documentation, knowledge bases, and site-wide content extraction.
Authentication
This skill only supports API key authentication.
- Create an account at inspiro.top
- Generate your API key
- Add it to
~/.claude/settings.json:
{
"env": {
"INSPIRO_API_KEY": "inspiro-your-api-key-here"
}
}Only API key authentication is supported.
Quick Start
Using the Script
./scripts/crawl.sh '<json>' [output_dir]Examples:
# Basic crawl
./scripts/crawl.sh '{"url": "https://docs.example.com"}'
# Deeper crawl with limits
./scripts/crawl.sh '{"url": "https://docs.example.com", "max_depth": 2, "limit": 50}'
# Save to files
./scripts/crawl.sh '{"url": "https://docs.example.com", "max_depth": 2}' ./docs
# Focused crawl with path filters
./scripts/crawl.sh '{"url": "https://example.com", "max_depth": 2, "select_paths": ["/docs/.*", "/api/.*"], "exclude_paths": ["/blog/.*"]}'
# With semantic instructions (for agentic use)
./scripts/crawl.sh '{"url": "https://docs.example.com", "instructions": "Find API documentation", "chunks_per_source": 3}'When output_dir is provided, each crawled page is saved as a separate markdown file.
Basic Crawl
curl --request POST \
--url https://api.inspiro.top/crawl \
--header "Authorization: Bearer $INSPIRO_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"url": "https://docs.example.com",
"max_depth": 1,
"limit": 20
}'Focused Crawl with Instructions
curl --request POST \
--url https://api.inspiro.top/crawl \
--header "Authorization: Bearer $INSPIRO_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"url": "https://docs.example.com",
"max_depth": 2,
"instructions": "Find API documentation and code examples",
"chunks_per_source": 3,
"select_paths": ["/docs/.*", "/api/.*"]
}'API Reference
Endpoint
POST https://api.inspiro.top/crawlHeaders
| Header | Value |
Authorization | Bearer <INSPIRO_API_KEY> |
Content-Type | application/json |
Request Body
| Field | Type | Default | Description |
url | string | Required | Root URL to begin crawling |
max_depth | integer | 1 | Levels deep to crawl (1-5) |
max_breadth | integer | 20 | Links per page |
limit | integer | 50 | Total pages cap |
instructions | string | null | Natural language guidance for focus |
chunks_per_source | integer | 3 | Chunks per page (1-5, requires instructions) |
extract_depth | string | "basic" | basic or advanced |
format | string | "markdown" | markdown or text |
select_paths | array | null | Regex patterns to include |
exclude_paths | array | null | Regex patterns to exclude |
allow_external | boolean | true | Include external domain links |
timeout | float | 150 | Max wait (10-150 seconds) |
Response Format
{
"base_url": "https://docs.example.com",
"results": [
{
"url": "https://docs.example.com/page",
"raw_content": "# Page Title\n\nContent..."
}
],
"response_time": 12.5
}Depth vs Performance
| Depth | Typical Pages | Time |
| 1 | 10-50 | Seconds |
| 2 | 50-500 | Minutes |
| 3 | 500-5000 | Many minutes |
Start with max_depth=1 and increase only if needed.
Crawl for Context vs Data Collection
For agentic use (feeding results into context): Always use instructions + chunks_per_source. This returns only relevant chunks instead of full pages, preventing context window explosion.
For data collection (saving to files): Omit chunks_per_source to get full page content.
Examples
For Context: Agentic Research (Recommended)
Use when feeding crawl results into an LLM context:
curl --request POST \
--url https://api.inspiro.top/crawl \
--header "Authorization: Bearer $INSPIRO_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"url": "https://docs.example.com",
"max_depth": 2,
"instructions": "Find API documentation and authentication guides",
"chunks_per_source": 3
}'Returns only the most relevant chunks (max 500 chars each) per page - fits in context without overwhelming it.
For Context: Targeted Technical Docs
curl --request POST \
--url https://api.inspiro.top/crawl \
--header "Authorization: Bearer $INSPIRO_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"url": "https://example.com",
"max_depth": 2,
"instructions": "Find all documentation about authentication and security",
"chunks_per_source": 3,
"select_paths": ["/docs/.*", "/api/.*"]
}'For Data Collection: Full Page Archive
Use when saving content to files for later processing:
curl --request POST \
--url https://api.inspiro.top/crawl \
--header "Authorization: Bearer $INSPIRO_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"url": "https://example.com/blog",
"max_depth": 2,
"max_breadth": 50,
"select_paths": ["/blog/.*"],
"exclude_paths": ["/blog/tag/.*", "/blog/category/.*"]
}'Returns full page content - use the script with output_dir to save as markdown files.
Map API (URL Discovery)
Use map instead of crawl when you only need URLs, not content:
curl --request POST \
--url https://api.inspiro.top/map \
--header "Authorization: Bearer $INSPIRO_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"url": "https://docs.example.com",
"max_depth": 2,
"instructions": "Find all API docs and guides"
}'Returns URLs only (faster than crawl):
{
"base_url": "https://docs.example.com",
"results": [
"https://docs.example.com/api/auth",
"https://docs.example.com/guides/quickstart"
]
}Tips
- Always use
chunks_per_sourcefor agentic workflows - prevents context explosion when feeding results to LLMs - Omit
chunks_per_sourceonly for data collection - when saving full pages to files - Start conservative (
max_depth=1,limit=20) and scale up - Use path patterns to focus on relevant sections
- Use Map first to understand site structure before full crawl
- Always set a
limitto prevent runaway crawls
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

