hugo-to-markdown

name	hugo-to-markdown
description	Convert Hugo documentation sites and Hugo-managed content into standard Markdown. Use when Agent needs to inspect a local Hugo repository, read hugo.toml or config files, content/, archetypes/, layouts/_shortcodes/, layouts/_markup/, and related docs content, then produce Markdown...
risk	unknown
source	https://github.com/chaunsin/agent-skills/tree/master/skills/hugo-to-markdown
source_repo	chaunsin/agent-skills
source_type	community
date_added	2026-07-01T00:00:00.000Z
license	Apache-2.0
license_source	https://github.com/chaunsin/agent-skills/blob/master/LICENSE

Hugo To Markdown

When to Use

Use this skill when you need convert Hugo documentation sites and Hugo-managed content into standard Markdown. Use when Agent needs to inspect a local Hugo repository, read hugo.toml or config files, content/, archetypes/, layouts/_shortcodes/, layouts/_markup/, and related docs content, then produce Markdown...

Overview

Use this skill when Markdown output must be derived from the local Hugo site, not guessed from generic Hugo knowledge. The conversion rules are the combination of Hugo's official behavior and the repository's own configuration, shortcode templates, render hooks, archetypes, and content conventions.

The target output is standard Markdown:

• Keep plain Markdown and YAML front matter.
• Replace or materialize Hugo-only constructs.
• Preserve meaning when exact rendering is not safely reproducible.
• Prefer explicit Markdown text over live Hugo template syntax.
• Distinguish literal Hugo syntax examples from active Hugo features before rewriting anything.

Official Basis

Treat the repository's own Hugo configuration and templates as the primary ruleset. For any site under conversion, inspect these rule sources in the user's provided site root:

• hugo.toml (or hugo.yaml, hugo.yml, hugo.json, or config/*)
• archetypes/*
• data/*
• layouts/_shortcodes/* or layouts/shortcodes/*
• layouts/_markup/*
• content/**

Also read any local docs that define shortcode, front matter, bundle, resource, and render-hook behavior.

Do not assume built-in Hugo defaults if the repository overrides them locally.

Workflow

1. Inventory the site before converting files

Always inspect the site-level rules first.

python3 scripts/inventory_hugo_rules.py --site-root /path/to/hugo-site

Example invocation for the user's site:

python3 skills/hugo-to-markdown/scripts/inventory_hugo_rules.py \
  --site-root /path/to/your-hugo-site

This inventory step is mandatory for batch work. It identifies:

• active config files
• module mounts and content roots
• custom shortcodes
• custom render hooks
• front matter keys seen in content