Agent skill · writing content · sickn33
hugo-to-markdown
Convert Hugo documentation sites and Hugo-managed content into standard Markdown.
Why this skill is useful
Adds a Python script that automates the conversion of Hugo sites to Markdown while respecting custom configurations and templates.
What it needs
Requires python3 installed locally. About 7k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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. Example invocation for the user's 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 shortcode usage across content files 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/hugo-to-markdown--56c7ee