Convert any public web page into clean, structured Markdown. Preserves headings, links, images, code blocks, and tables while removing ads, navigation, and clutter. Perfect for content archival, knowledge base building, and research note-taking.
Installs into .claude/skills of the current project.
Are you the author of Url To Markdown?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sandbaseai-url-to-markdown)
---
name: url-to-markdown
description: "Convert any public web page into clean, structured Markdown. Preserves headings, links, images, code blocks, and tables while removing ads, navigation, and clutter. Perfect for content archival, knowledge base building, and research note-taking."
---
# URL to Markdown
Convert any public web page into clean, structured Markdown. Preserves headings, links, images, code blocks, and tables while removing ads, navigation, and clutter. Perfect for content archival, knowledge base building, and research note-taking. Read [the API map](references/sandbase-api-map.md) before selecting a capability.
## Call SandBase capabilities
Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with `sandbase_discover(q: "<provider and capability>")`; use its returned `name` in `sandbase_inspect(name: "<returned name>")`. Read `inputSchema`, pricing, and `execute_as`, then call `sandbase_run` using `execute_as.arguments.name` and schema-defined `arguments`. If a `run_id` is returned, poll `sandbase_run_get(run_id: "<returned run_id>")` within the task budget until `completed` or `failed`; report pending or failed runs without resubmitting them automatically.
## Capability identifiers
- `strale_url_to_markdown`
- `context_dev_scrape_markdown`
## Workflow
1. Understand the user's research question, target, and context.
2. Resolve each selected capability with `sandbase_discover`, then inspect the returned `name` with `sandbase_inspect` to confirm the schema and pricing.
3. Follow `execute_as` with `sandbase_run`; collect async results with `sandbase_run_get` as described above.
4. Synthesize findings into a clear, evidence-backed answer.
5. Cite sources, note evidence gaps, and separate observations from interpretations.
## Guidelines
- Always call `sandbase_inspect` before using any capability.
- Cite sources and preserve attribution (URLs, usernames, dates, metrics).
- Separate factual observations from analysis and recommendations.
- If data is unavailable, note the gap and continue with available evidence.
- Read-only research only. Never take actions on platforms.
