timerise-ai

Help Center Markdown — Documentation skill for Claude Code

Documentation community

Agent Skill: build a markdown-backed help center — category folders of frontmatter articles, static landing/category/tag/article pages, ranked client-side search, tags with slug identity, locale fallb.

How to install Help Center Markdown

This entry records only its repository, not the path inside it, so there is no exact command to give. Open timerise-ai/help-center-markdown and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Help Center Markdown does

Agent Skill: build a markdown-backed help center — category folders of frontmatter articles, static landing/category/tag/article pages, ranked client-side search, tags with slug identity, locale fallback with hreflang, JSON-LD and sitemap, CI content validator — in Next.js App Router, no CMS

Alternatives in Documentation

  • Wiki Build — Regenerate the static HTML site for the llmwiki 375 ★
  • Create Command — by scopecraft - Guides Claude through creating new custom commands with proper structure by analyzing requirem 172 ★
  • Split View Editor — Give the Inkwell editor a side-by-side markdown view — edit on the left, live preview on the 143 ★

README

help-center-markdown

[![Agent Skills](https://img.shields.io/badge/Agent_Skills-open_format-059669)](https://agentskills.io) [![skills.sh](https://img.shields.io/badge/skills.sh-npx_skills_add-059669)](https://www.skills.sh) [![Claude Code](https://img.shields.io/badge/Claude_Code-compatible-059669)](https://docs.claude.com/en/docs/claude-code/skills) [![Codex CLI](https://img.shields.io/badge/Codex_CLI-compatible-059669)](https://developers.openai.com/codex/skills) [![Gemini CLI](https://img.shields.io/badge/Gemini_CLI-compatible-059669)](https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/skills.md)

An [Agent Skill](https://agentskills.io) that teaches an agent to build a markdown-backed help center in a **Next.js App Router** app: category folders of frontmatter articles, statically rendered landing, category, tag and article pages, client-side search with ranking and keyboard navigation, locale-aware routing with default-locale fallback, tags with slug identity and their own pages, related articles, breadcrumbs, JSON-LD and sitemap entries, and a content validator for CI. Content lives in the repository; there is no CMS.

A help center is a small static site with one hard requirement: **every article must be reachable**: from the sidebar, from search, from a locale that has not been translated yet. This skill was written by the engineer who has shipped this module; the earlier implementation it was audited against was a marketing-site help center. The templates hold that requirement as verified properties: the sidebar shows every article of every category, the parser reads every frontmatter shape the corpus uses and the validator fails the build on the ones it cannot, tags group by slug so one label reaches one page however it is spelled, and search ranks a query however it is typed, trailing space and diacritics included. The loader, search and tag suites cover each of those; [references/provenance.md](references/provenance.md) carries the record