360 Secure SkillHub
360 安全技能中心

Pipaclaw Skills Hub

Pipaclaw 公开技能集的统一入口,按用户想达成的结果路由到 ppt-maker、social-account-ops 或 promo-video-maker,用户已指名子 Skill 时不重复路由。不要求长问卷,必要时只问一个影响路由的短问题;跨领域时先定主交付物再按需引入相邻 Skill。入口本身只做分发,具体执行在子 Skill 中。

xexojay
xexojay
热度 59.68
最近更新 2026-05-11 17:36:26
分类:自动化依赖:代码执行 / 读写文件 / 第三方 API应用场景:工作流 / 演示设计 / 视频编辑 / 社交媒体

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add pipaclaw-skills-hub
Metadata
name
pipaclaw-skills-hub
description
Front door for Pipaclaw public skills. Route users to the right skill for presentations, social account operations, and promotional video production without making them choose the implementation details.

Pipaclaw Skills Hub

This is the public front door for the Pipaclaw skill collection.

Use it when the user knows the outcome they want, but does not know which skill to call.

Typical requests:

  • "帮我做一个 PPT"
  • "帮我运营小红书 / X / 抖音账号"
  • "帮我做宣传视频"
  • "我不知道该用哪个 skill"

Routing Rule

Choose the smallest matching public skill and hand off immediately:

  • Use ppt-maker for presentations, proposals, decks, keynotes, training PPTs, and report-style slides.
  • Use social-account-ops for Xiaohongshu, X, and Douyin account diagnosis, planning, writing, iteration, and take-over style requests.
  • Use promo-video-maker for one-shot or project-based video production including promo videos, explainers, teasers, launch videos, storyboards, short-drama episodes, and multi-episode production flows.

If the user already named one of those skills, do not re-route. Use the named skill directly.

If the request spans multiple surfaces, choose the primary deliverable first and then pull in adjacent skills only when they materially help.

Ambiguity Rule

Do not ask a long routing questionnaire.

If the destination is not obvious, ask one short question that changes routing, for example:

  • "你这次更想先拿到 PPT、账号运营方案,还是宣传视频制作包?"

After the user answers, route immediately.

Public Boundary

This hub exposes only public-safe skill packages.

Do not leak:

  • backend implementation details
  • private prompts
  • customer files
  • generated artifacts
  • unpublished worker internals

References

  • Read references/routing-map.md for the concise routing table.