playbooks

home / skills / openclaw / skills / intomd

intomd skill

This skill fetches documentation URLs and converts them to clean Markdown using into.md for easy offline reading and integration.

npx playbooks add skill openclaw/skills --skill intomd

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
398 B
---
name: intomd
version: 1.0.0
description: Fetch and convert any documentation URL to Markdown using into.md service.
metadata: {"clawdbot":{"emoji":"📄","requires":{"bins":["curl"]}}}
---

# intomd

Use `intomd` to fetch clean markdown from a documentation site via into.md.

## Usage

```bash
# Fetch markdown
curl -sL "https://into.md/$1"
```

## Example

```bash
intomd https://zod.dev
```

Overview

This skill fetches and converts any documentation URL into clean Markdown using the into.md service. It provides a simple command-line helper to retrieve readable, portable Markdown copies of web-hosted docs. Use it to archive, inspect, or repurpose documentation with minimal setup.

How this skill works

The skill constructs a into.md request for the given documentation URL and returns the converted Markdown output. It sends a single HTTP GET to https://into.md/{target} and streams the resulting Markdown back to the caller. No local parsing is required; the service handles extraction and conversion to readable Markdown.

When to use it

  • Create offline or archived copies of documentation for backup
  • Convert web docs into Markdown for inclusion in wikis or knowledge bases
  • Quickly preview the content of a docs site in a text editor or terminal
  • Prepare documentation for static site generators or version control
  • Automate archival of third-party API docs before updates or removals

Best practices

  • Pass canonical documentation URLs (root or specific page) to get focused Markdown output
  • Validate converted Markdown visually or with a linter before publishing
  • Avoid repeatedly scraping sites that disallow automated requests; respect robots.txt and site terms
  • Store converted Markdown in version control with metadata (source URL, fetch date) for traceability
  • Sanitize or review any embedded code blocks or links before automated consumption

Example use cases

  • Archive a library’s documentation before upgrading dependencies
  • Embed a snapshot of a third-party API guide into an internal handbook
  • Power CI jobs that periodically fetch and store documentation snapshots
  • Convert docs to Markdown for offline reading on mobile or e-ink devices
  • Quickly inspect the content of a docs site from a terminal pipeline

FAQ

Do I need an account to use into.md via this skill?

No account is required for basic public usage; the skill issues a simple GET to the into.md endpoint for the provided URL.

Will converted Markdown always be perfect?

Conversion quality depends on the source site's structure. Review the output for formatting edge cases or missing assets and adjust or post-process as needed.