/install helpcenter
Help.Center Article Management
Manage help center articles through the Help.Center API. Supports creating new articles, reading and updating existing ones, publishing/unpublishing, and organizing by category.
Prerequisites
Before making any API calls, you need two pieces of information from the user:
- API Key - Created in Help.Center dashboard under Settings > General > API
- The key must have appropriate scopes:
content.read- Required for searching/reading articlescontent.write- Required for creating/updating articles and categoriescontent.publish- Required for publishing/unpublishing articlescontent.delete- Required for deleting articles or categories
- The key must have appropriate scopes:
- Center ID - Found on the same page
If the user hasn't provided these, ask for them before proceeding. Store them as environment variables for the session:
export HC_API_KEY="the_api_key"
export HC_CENTER_ID="the_center_id"
Base URL
https://api.help.center
Authentication
All requests require the API key in the Authorization header:
Authorization: Bearer $HC_API_KEY
Workflow
When the user wants to UPDATE an existing article
-
Search for the article first to find its ID and current content:
curl -s -X GET \ -H "Authorization: Bearer $HC_API_KEY" \ -H "Content-Type: application/json" \ "https://api.help.center/v0/centers/$HC_CENTER_ID/articles?search=SEARCH_TERM&expand[]=content" -
Read the full article using the article ID from search results:
curl -s -X GET \ -H "Authorization: Bearer $HC_API_KEY" \ -H "Content-Type: application/json" \ "https://api.help.center/v0/centers/$HC_CENTER_ID/articles/ARTICLE_ID?expand[]=content" -
Update only the specific part the user wants changed. Merge the user's changes into the existing HTML content, preserving everything else. Update via the draft endpoint:
curl -s -X PATCH \ -H "Authorization: Bearer $HC_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "title": "Updated Title", "html": "\x3Ch1>Updated full HTML content with changes merged in\x3C/h1>" }' \ "https://api.help.center/v0/centers/$HC_CENTER_ID/articles/ARTICLE_ID/draft" -
Publish the updated article (ask the user first if they want to publish or keep as draft):
curl -s -X POST \ -H "Authorization: Bearer $HC_API_KEY" \ "https://api.help.center/v0/centers/$HC_CENTER_ID/articles/ARTICLE_ID/publish"
When the user wants to CREATE a new article
-
List categories so the article can be assigned properly:
curl -s -X GET \ -H "Authorization: Bearer $HC_API_KEY" \ -H "Content-Type: application/json" \ "https://api.help.center/v0/centers/$HC_CENTER_ID/articles/categories" -
Write the article content as clean, well-structured HTML. Follow these content guidelines:
- Use semantic HTML:
\x3Ch1>for main title,\x3Ch2>for sections,\x3Ch3>for subsections - Use
\x3Cp>tags for paragraphs - Use
\x3Cul>/\x3Col>for lists - Use
\x3Ccode>for inline code and\x3Cpre>\x3Ccode>for code blocks - Use
\x3Cstrong>for emphasis on key terms - Use
\x3Ca href="...">for links - Keep the tone clear, helpful, and concise
- Structure content so users can scan and find what they need quickly
- Use semantic HTML:
-
Create the article:
curl -s -X POST \ -H "Authorization: Bearer $HC_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "title": "Article Title", "content": { "html": "\x3Ch1>Title\x3C/h1>\x3Cp>Content here...\x3C/p>" }, "category_id": "category-slug" }' \ "https://api.help.center/v0/centers/$HC_CENTER_ID/articles" -
Publish if requested:
curl -s -X POST \ -H "Authorization: Bearer $HC_API_KEY" \ "https://api.help.center/v0/centers/$HC_CENTER_ID/articles/ARTICLE_ID/publish"
Important Rules
-
Always search before creating. If the user says "write an article about X", search for existing articles on that topic first. If one exists, confirm with the user whether they want to update it or create a new one.
-
Preserve existing content when updating. Never overwrite an entire article when only a section needs changing. Fetch the current content, modify the relevant part, and send back the full updated HTML.
-
Always ask before publishing. Default to creating as draft. Only publish when the user explicitly asks for it.
-
Handle errors gracefully. Check HTTP status codes. Common issues:
- 401: API key is invalid or missing
- 403: Insufficient permissions (missing required scope)
- 404: Article or center not found
- 400: Missing required fields (title is always required)
- 429: Rate limited (wait and retry)
-
Use pagination for large result sets. The API returns max 100 articles per request. Use
starting_afterwith the last article's ID to fetch more.
API Quick Reference
| Action | Method | Endpoint |
|---|---|---|
| List articles | GET | /v0/centers/:centerId/articles |
| Search articles | GET | /v0/centers/:centerId/articles?search=query |
| Get article | GET | /v0/centers/:centerId/articles/:articleId |
| Create article | POST | /v0/centers/:centerId/articles |
| Update draft | PATCH | /v0/centers/:centerId/articles/:articleId/draft |
| Update metadata | PATCH | /v0/centers/:centerId/articles/:articleId/metadata |
| Publish | POST | /v0/centers/:centerId/articles/:articleId/publish |
| Unpublish | POST | /v0/centers/:centerId/articles/:articleId/unpublish |
| Delete | DELETE | /v0/centers/:centerId/articles/:articleId |
| Duplicate | POST | /v0/centers/:centerId/articles/:articleId/duplicate |
| List drafts | GET | /v0/centers/:centerId/articles/drafts |
| Get draft | GET | /v0/centers/:centerId/articles/:articleId/draft |
| Discard draft | POST | /v0/centers/:centerId/articles/:articleId/draft/discard |
| List categories | GET | /v0/centers/:centerId/articles/categories |
| Create category | POST | /v0/centers/:centerId/articles/categories |
| Update category | PATCH | /v0/centers/:centerId/articles/categories/:categoryId |
| Delete category | DELETE | /v0/centers/:centerId/articles/categories/:categoryId |
| Upload image | POST | /v0/centers/:centerId/articles/images |
| Get center info | GET | /v0/centers/:centerId |
| Count articles | GET | /v0/centers/:centerId/articles/count |
Content Writing Guidelines
When writing help center articles:
- Lead with the outcome. Start by telling the user what they'll be able to do after reading.
- Use short paragraphs. 2-3 sentences max per paragraph.
- Add step-by-step instructions with numbered lists for procedures.
- Include examples wherever possible to make abstract concepts concrete.
- Use screenshots or visuals references where helpful (use the image upload endpoint to host images, then reference the returned URL in your HTML).
- End with next steps or related articles when relevant.
- Write for scanning. Use descriptive headings so users can jump to what they need.
Category Management
Categories help organize your articles. You can create hierarchical categories with one level of subcategories.
Creating a category:
curl -s -X POST \
-H "Authorization: Bearer $HC_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Getting Started",
"description": "Articles for new users",
"icon": "\x3Csvg>...\x3C/svg>", // Optional custom SVG icon
"parent_id": "parent-cat-id" // Optional, for subcategories
}' \
"https://api.help.center/v0/centers/$HC_CENTER_ID/articles/categories"
Updating a category:
curl -s -X PATCH \
-H "Authorization: Bearer $HC_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Updated Name",
"description": "Updated description",
"icon": "\x3Csvg>...\x3C/svg>"
}' \
"https://api.help.center/v0/centers/$HC_CENTER_ID/articles/categories/CATEGORY_ID"
Deleting a category:
Categories can only be deleted if no articles are using them.
curl -s -X DELETE \
-H "Authorization: Bearer $HC_API_KEY" \
"https://api.help.center/v0/centers/$HC_CENTER_ID/articles/categories/CATEGORY_ID"
Image Upload
Upload images for use in your articles:
curl -s -X POST \
-H "Authorization: Bearer $HC_API_KEY" \
-F "image=@/path/to/image.jpg" \
"https://api.help.center/v0/centers/$HC_CENTER_ID/articles/images"
Constraints:
- Maximum size: 10MB
- Supported formats: JPEG, PNG, GIF, WebP, SVG
- Use
multipart/form-datawith field nameimage
The response will include the image URL to use in your article HTML:
{
"success": true,
"data": {
"url": "https://cdn.help.center/images/...",
"filename": "image.jpg",
"size": 1024576
}
}
SEO Metadata
When creating articles, optionally include SEO metadata:
{
"metadata": {
"seo": {
"title": "Concise, keyword-rich title (50-60 chars)",
"description": "Clear summary of the article (150-160 chars)"
}
}
}
You can also update SEO metadata on existing articles via the metadata endpoint:
curl -s -X PATCH \
-H "Authorization: Bearer $HC_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"seo": {
"title": "SEO Title",
"description": "SEO Description"
}
}' \
"https://api.help.center/v0/centers/$HC_CENTER_ID/articles/ARTICLE_ID/metadata"
- 确保已安装 OpenClaw(本地或 Docker 部署)
- 在对话框中输入安装命令:
/install helpcenter - 安装完成后,直接呼叫该 Skill 的名称或使用
/helpcenter触发 - 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
Help.Center Article Management 是什么?
When the user wants to create, update, read, or manage help center articles via the Help.Center API. Use when the user says "write a help article", "update t... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 385 次。
如何安装 Help.Center Article Management?
在 OpenClaw 或 Claude Code 对话框中运行命令「/install helpcenter」即可一键安装,无需额外配置。
Help.Center Article Management 是免费的吗?
是的,Help.Center Article Management 完全免费(开源免费),可自由下载、安装和使用。
Help.Center Article Management 支持哪些平台?
Help.Center Article Management 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。
谁开发了 Help.Center Article Management?
由 shyjal(@shyjal)开发并维护,当前版本 v1.0.0。