help

Creates a centralized help center from your own uploaded files and metadata, accessible 24/7 via chat.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/charlieclark/skill-help --skill help-charlieclark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: help
Source: https://github.com/charlieclark/skill-help/tree/main/skills/help
Command: npx skills add https://github.com/charlieclark/skill-help --skill help-charlieclark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates project documentation into a centralized help center so teams can access and manage articles without duplicating content.

Core Features & Use Cases

  • Init: scaffold a help center config, article directories, and templates.
  • Generate: AI-assisted creation of articles from codebases and resources.
  • Update: refresh existing articles when code changes.
  • Import: crawl external help centers and convert pages to Markdown.
  • Dashboard & Preview: launch a local dashboard for exploration and validation.

Quick Start

Use the /help commands to initialize, generate, and preview your help center. Start with /help init to scaffold the structure, then /help generate to populate articles, and finally /help dashboard to view the UI.

Frequently Asked Questions about help

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I consolidate project documentation into a centralized help center?

Consolidate project documentation into a centralized help center by initializing directory structures, generating articles from codebases, and launching a local dashboard for preview and navigation.

Can I import existing external help center pages into Markdown?

Import external help center pages into Markdown by crawling target help centers and converting the crawled pages directly into frontmatter-driven Markdown articles.

How does AI-assisted article generation from codebases work?

AI-assisted article generation from codebases works by analyzing project resources and templates to automatically populate help center articles, which you can then preview in a local dashboard.

What's the best way to update existing documentation articles when code changes?

Update existing documentation articles by refreshing the generated content to reflect code changes, maintaining frontmatter-driven metadata and optional assets for navigable help interface organization.

Do I need specific templates to scaffold a help center config?

Scaffolding a help center config requires templates and frontmatter-driven metadata to organize article directories, initialize the structure, and expose a navigable help interface.

Can I preview the help center dashboard locally before publishing?

Preview the help center dashboard locally to explore articles and validate the navigable help interface before publishing, using the dashboard command to launch the local UI.