Token导航 LogoToken导航

Agent Skill · 研究检索

helpcenter(helpcenter 搜索)

helpcenter 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

helpcenter 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 10,898。

总安装 11,971周安装 489GitHub Stars 公开资料未说明下载 3,873核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:helpcenter(helpcenter 搜索)
来源仓库:https://github.com/shyjal/helpcenter
安装命令:
openclaw skills install helpcenter
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install helpcenter

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

通过 Help.Center API 管理帮助中心文章创建与更新。支持内容版本控制与多语言发布流程管理。helpcenter 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适用于产品文档维护与客户自助服务体系建设。操作前应确认 API 密钥权限与内容审核机制。建议定期同步文档变更以确保信息一致性。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install helpcenter;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

helpcenter 怎么安装?

在终端执行 openclaw skills install helpcenter。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

helpcenter 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

helpcenter 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

helpcenter 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

helpcenter 用的人多吗?

公开数据是累计安装 11,971 次,近一周安装 489 次,下载 3,873 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

helpcenter 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
helpcenter

helpcenter 搜索 · 本页

11,971—接触敏感数据MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
helpcenter
description
>
metadata
version
1.0.0
author
Microdot Company

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:

  1. API Key - Created in Help.Center dashboard under Settings > General > API

- The key must have appropriate scopes: - content.read - Required for searching/reading articles - content.write - Required for creating/updating articles and categories - content.publish - Required for publishing/unpublishing articles - content.delete - Required for deleting articles or categories

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

  1. 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"
  1. 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"
  1. 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": "<h1>Updated full HTML content with changes merged in</h1>"
     }' \
     "https://api.help.center/v0/centers/$HC_CENTER_ID/articles/ARTICLE_ID/draft"
  1. 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

  1. 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"
  1. Write the article content as clean, well-structured HTML. Follow these content guidelines:

- Use semantic HTML: <h1> for main title, <h2> for sections, <h3> for subsections - Use <p> tags for paragraphs - Use <ul>/<ol> for lists - Use <code> for inline code and <pre><code> for code blocks - Use <strong> for emphasis on key terms - Use <a href="..."> for links - Keep the tone clear, helpful, and concise - Structure content so users can scan and find what they need quickly

  1. Create the article:
   curl -s -X POST \
     -H "Authorization: Bearer $HC_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "title": "Article Title",
       "content": {
         "html": "<h1>Title</h1><p>Content here...</p>"
       },
       "category_id": "category-slug"
     }' \
     "https://api.help.center/v0/centers/$HC_CENTER_ID/articles"
  1. 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

  1. 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.
  1. 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.
  1. Always ask before publishing. Default to creating as draft. Only publish when the user explicitly asks for it.
  1. 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)

  1. Use pagination for large result sets. The API returns max 100 articles per request. Use starting_after with the last article's ID to fetch more.

API Quick Reference

ActionMethodEndpoint
List articlesGET/v0/centers/:centerId/articles
Search articlesGET/v0/centers/:centerId/articles?search=query
Get articleGET/v0/centers/:centerId/articles/:articleId
Create articlePOST/v0/centers/:centerId/articles
Update draftPATCH/v0/centers/:centerId/articles/:articleId/draft
Update metadataPATCH/v0/centers/:centerId/articles/:articleId/metadata
PublishPOST/v0/centers/:centerId/articles/:articleId/publish
UnpublishPOST/v0/centers/:centerId/articles/:articleId/unpublish
DeleteDELETE/v0/centers/:centerId/articles/:articleId
DuplicatePOST/v0/centers/:centerId/articles/:articleId/duplicate
List draftsGET/v0/centers/:centerId/articles/drafts
Get draftGET/v0/centers/:centerId/articles/:articleId/draft
Discard draftPOST/v0/centers/:centerId/articles/:articleId/draft/discard
List categoriesGET/v0/centers/:centerId/articles/categories
Create categoryPOST/v0/centers/:centerId/articles/categories
Update categoryPATCH/v0/centers/:centerId/articles/categories/:categoryId
Delete categoryDELETE/v0/centers/:centerId/articles/categories/:categoryId
Upload imagePOST/v0/centers/:centerId/articles/images
Get center infoGET/v0/centers/:centerId
Count articlesGET/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": "<svg>...</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": "<svg>...</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-data with field name image

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

78.05%
按下载量换算3,023

安全审计

VirusTotal

可疑

ClawScan

可疑

Static analysis

未展示

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills