Use Axon scrape to turn one or more known URLs into markdown, HTML, JSON, or saved artifacts.
Scanned 9/1/2026
Install to Claude Code
npx -y skills add dinglebear-ai/axon --skill scrape --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Scrape?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dinglebear-ai-scrape)More formats (shields.io, HTML) on the badges page.
---
name: scrape
description: Use Axon scrape to turn one or more known URLs into markdown, HTML, JSON, or saved artifacts.
---
# Axon Scrape
Use `axon scrape` when the user gives a URL and wants that page's content.
`scrape` is the retained one-page projection of the unified source pipeline —
same adapter, ledger, embedding, and publication path as `axon <url> --scope page`.
Reach for it rather than a bare `axon <url>`: the web family's default scope is
`site`, so an unscoped URL indexes the whole domain.
## Examples
```bash
mkdir -p .axon
axon scrape "https://example.com" --output .axon/example.md
axon scrape "https://example.com/pricing" --format json --output .axon/pricing.json
axon scrape "https://app.example.com" --render-mode chrome --output .axon/app.md
```
Multiple URLs:
```bash
axon scrape "https://example.com" "https://example.com/docs" --output-dir .axon/pages
```
## Guidance
- Quote URLs.
- Save output to `.axon/` for anything larger than a short answer.
- Use Chrome rendering when HTTP output is thin.
- Use `extract` when the desired output is structured fields rather than markdown.
- Use `axon <url> --scope site` when you need many linked pages — `scrape` is the one-page projection of the same source pipeline.
## See Also
- [search](../search/SKILL.md)
- [map](../map/SKILL.md)
- [crawl](../crawl/SKILL.md)
- [extract](../extract/SKILL.md)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.