html-to-markdown-extracting-tables
Skill888 starsChanged 3 months agoMITView on GitHub
Use when extracting tabular data from HTML. Covers GFM Markdown tables, the structured tables array (grid cells plus pre-rendered markdown), and HTML line breaks in table cells.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Use this when the user wants tabular data out of HTML — pricing tables, data grids, spec sheets.
- Distinctive: line 42
When you only care about tables (not the Markdown body):
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!--
AI-RULEZ :: GENERATED FILE — DO NOT EDIT
Content-Hash: blake3:d581ed76f6325d95c7906b89a227dabe3598860edfd1a5b4a22e4fbbb085f140
Source-Hash: blake3:25aff2d6495f85f31e43d878c418221ab6d2edce946baaa4716510a2c8633f5b
Schema-Version: v1
-->Extracting tables
Use this when the user wants tabular data out of HTML — pricing tables, data
grids, spec sheets. html-to-markdown parses <table> elements into two
surfaces: inline GFM Markdown tables in the content stream, and a
structured tables array when document structure extraction is enabled.
Two surfaces
# Inline GFM tables appear in the Markdown body
html-to-markdown input.html
# Structured table data appears under .tables in CLI JSON
html-to-markdown --json --include-structure input.html | jq '.tables'- Markdown tables in
content—| col | col |blocks, good for LLM ingestion and human reading. - Structured
tablesarray — each entry has amarkdownfield (pre-rendered) and agridof structured cells (rows × cols). Use this when downstream code needs exact cell access.
Inline Markdown tables are rendered by default. Structured tables require
--include-structure in the CLI, include_document_structure=True in Python,
or includeDocumentStructure: true in Node.js.
Extraction-only
When you only care about tables (not the Markdown body):
html-to-markdown --json --include-structure --no-content input.html | jq '.tables'Inspecting tables
# How many tables, and the row count of each
html-to-markdown --json --include-structure input.html \
| jq '.tables | to_entries | map({index: .key, rows: .value.grid.rows, cols: .value.grid.cols})'
# Just the rendered markdown of the first table
html-to-markdown --json --include-structure input.html | jq -r '.tables[0].markdown'Line breaks in cells
By default <br> inside a cell is converted to a space. Keep hard breaks:
html-to-markdown input.html --br-in-tablesProgrammatic access
from html_to_markdown import convert, ConversionOptions
html = "<table><tr><th>A</th><th>B</th></tr><tr><td>1</td><td>2</td></tr></table>"
# result.tables is only populated when include_document_structure=True
result = convert(html, ConversionOptions(include_document_structure=True))
for table in result.tables:
print(table.markdown) # rendered GFM markdown
print(table.grid.cells[0].content) # first cell (grid is a TableGrid)import { convert } from "@xberg-io/html-to-markdown";
// Node's convert() returns a ConversionResult object directly.
const result = convert(html, { includeDocumentStructure: true });
for (const table of result.tables ?? []) {
console.log(table.markdown); // rendered table
// table.grid is a TableGrid: { rows, cols, cells: GridCell[] }
}Notes and limits
- Nested tables are flattened — the inner table is rendered inline within the parent cell.
- Merged / spanning cells preserve
row_spanandcol_spanon each grid cell. Inspect both cell positions and span dimensions when reconstructing a layout. - Malformed tables still parse on a best-effort basis; check
result.warnings(or--show-warnings) for non-fatal issues.
See references/cli-reference.md (Tables section) for the
full flag set.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- kreuzberg-dev/html-to-markdown★ 88199% same
Wrote their own version · 0
None found.
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 repository14 other files it gives its agents.
- apiSkill
- cliSkill
- mcpSkill
- apiSkill
- cliSkill
- mcpSkill
- apiSkill
- cliSkill
- mcpSkill
- html-to-markdown-converting-htmlSkill
- html-to-markdown-extracting-metadataSkill
- html-to-markdown-fetching-and-converting-urlsSkill
- html-to-markdownSkill
- html-to-markdown-using-the-mcp-serverSkill
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.

