Agent skill · Documentation

hugo-to-markdown

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...

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorships scriptsMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill hugo-to-markdown --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 8
SKILL.md size: 13 KB
Bundled scripts: yes
Path: skills/hugo-to-markdown/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 provid

What's inside
Steps it walks through
  1. When to Use
  2. Overview
  3. Official Basis
  4. Workflow
  5. 1. Inventory the site before converting files
  6. 2. Convert with repository rules, not generic heuristics
  7. 3. Preserve semantics during conversion
  8. 4. Apply Hugo-specific body rules carefully
  9. 5. Validate the output
  10. 6. Downgrade explicitly when full materialization is not safe
  11. Common Hugo Docs Site Patterns
  12. Safety Rules
  13. Resources
  14. Limitations
Ships with 7 files
  • agents/openai.yaml
  • references/conversion-workflow.md
  • references/front-matter-and-content.md
  • references/links-assets-and-validation.md
  • references/shortcodes-and-render-hooks.md
  • scripts/check_standard_markdown.py
  • scripts/inventory_hugo_rules.py
Commands it runs
python3 scripts/inventory_hugo_rules.py --site-root /path/to/hugo-site
python3 skills/hugo-to-markdown/scripts/inventory_hugo_rules.py \
python3 skills/hugo-to-markdown/scripts/check_standard_markdown.py \
More from agentic-awesome-skills
All skills →
About this skill
What does the hugo-to-markdown skill do?

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...

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill hugo-to-markdown --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going