How do I install the Okf Hugo Site skill?

Run npx skillmds@latest add dceoy/okf-hugo-site in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Okf Hugo Site safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Okf Hugo Site?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Okf Hugo Site free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Okf Hugo Site?

dceoy (@dceoy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Okf Hugo Site by dceoy — Agent Skill

Name: Okf Hugo Site
Author: dceoy

Okf Hugo Site

Build, preview, troubleshoot, search, and publish HOKF's static Hugo presentation. Use when changing the OKF-to-Hugo adapter, site layouts or assets, Pagefind integration, GitHub Pages workflow, or diagnosing generated-content and deployment failures.

dceoy Updated Sep 17, 2026

File contents

Operate the HOKF Hugo site

Build in dependency order

Install Python and Node dependencies, then validate, generate, render, and index:

python3 -m pip install --only-binary=:all: -r requirements.txt
npm ci --ignore-scripts
python3 tools/okf_validate.py --src okf
python3 tools/okf_hugo_adapter.py --src okf --dst site/content --clean
hugo --source site --destination public --cleanDestinationDir
npm run pagefind

Treat okf/ as canonical. Never hand-edit or commit site/content/; it is disposable shadow content. Do not commit site/public/ or node_modules/.

For a plain local preview, generate content and run:

hugo server --source site

The pages remain usable before Pagefind runs; the search control explains that the index is unavailable. Build and index first when testing search.

Preserve presentation boundaries

Keep templates theme-free and framework-free. Render optional metadata only when present, tolerate unknown types and fields, and read the canonical type from Hugo's native page type. Keep internal URLs base-path aware through the link render hook and Hugo RelPermalink/relURL.

Test project-path behavior with an explicit base URL:

hugo --source site --destination public --cleanDestinationDir \
  --baseURL https://example.github.io/hokf/

Confirm generated links include /hokf/, Pagefind indexes titles, descriptions, tags, and body text, and navigation is excluded where marked.

Diagnose by stage

Validation failure: fix canonical YAML or reserved-document structure.
Generation failure: inspect safe YAML parsing and source/destination paths.
Missing or stale page: regenerate with --clean.
Template failure: check optional values before dereferencing nested metadata.
Broken project-path link: use the render hook or Hugo URL functions, not a domain-root literal.
Empty search: rebuild Hugo, run npm run pagefind, and confirm site/public/pagefind/pagefind-ui.js exists.
CI or deploy failure: compare local commands with .github/workflows/pages.yml; keep tool versions and the lockfile pinned.

Publishing occurs only through the successful default-branch build and the separate least-privilege GitHub Pages deploy job.

---name: okf-hugo-sitedescription: Build, preview, troubleshoot, search, and publish HOKF's static Hugo presentation. Use when changing the OKF-to-Hugo adapter, site layouts or assets, Pagefind integration, GitHub Pages workflow, or diagnosing generated-content and deployment failures.---# Operate the HOKF Hugo site## Build in dependency orderInstall Python and Node dependencies, then validate, generate, render, and index:```shpython3 -m pip install --only-binary=:all: -r requirements.txtnpm ci --ignore-scriptspython3 tools/okf_validate.py --src okfpython3 tools/okf_hugo_adapter.py --src okf --dst site/content --cleanhugo --source site --destination public --cleanDestinationDirnpm run pagefind```Treat `okf/` as canonical. Never hand-edit or commit `site/content/`; it isdisposable shadow content. Do not commit `site/public/` or `node_modules/`.For a plain local preview, generate content and run:```shhugo server --source site```The pages remain usable before Pagefind runs; the search control explains thatthe index is unavailable. Build and index first when testing search.## Preserve presentation boundariesKeep templates theme-free and framework-free. Render optional metadata onlywhen present, tolerate unknown types and fields, and read the canonical typefrom Hugo's native page type. Keep internal URLs base-path aware through thelink render hook and Hugo `RelPermalink`/`relURL`.Test project-path behavior with an explicit base URL:```shhugo --source site --destination public --cleanDestinationDir \ --baseURL https://example.github.io/hokf/```Confirm generated links include `/hokf/`, Pagefind indexes titles,descriptions, tags, and body text, and navigation is excluded where marked.## Diagnose by stage- Validation failure: fix canonical YAML or reserved-document structure.- Generation failure: inspect safe YAML parsing and source/destination paths.- Missing or stale page: regenerate with `--clean`.- Template failure: check optional values before dereferencing nested metadata.- Broken project-path link: use the render hook or Hugo URL functions, not a domain-root literal.- Empty search: rebuild Hugo, run `npm run pagefind`, and confirm `site/public/pagefind/pagefind-ui.js` exists.- CI or deploy failure: compare local commands with `.github/workflows/pages.yml`; keep tool versions and the lockfile pinned.Publishing occurs only through the successful default-branch build and theseparate least-privilege GitHub Pages deploy job.

Frequently asked questions