💻

全能页面应用开发器

👤 zhyuzh 📦 v0.4.1 ⭐ 4.6 ⬇️ 319 下载
💻 开发编程 免费

📖 技能介绍

全能页面应用开发器

Use this skill in WorkBuddy when the user wants to create, develop, configure, preview, run, manage data/assets/resources, locally sync STS files, or publish XApps on x.10knet.com.

This is a standalone SkillHub package. A separately installed WorkBuddy custom connector is optional, not a prerequisite.

First Step

Before doing any XApp development work, load xapp_dev by the first available route:

  1. If native MCP tool xagent_skill_load is visible, call it with:
{ "skill": "xapp_dev" }
  1. If the native tool is not visible, immediately use the adapter included in this installed skill. Do not stop and do not ask the user or an organization administrator to install a connector:
node "{baseDir}/scripts/xagent_mcp.mjs" skill-load xapp_dev

Read result.content from the successful response, cache result.skill_version and the rules in this task/thread, and follow the returned server-side skill as the source of truth.

Calling XAgent Tools Without a Native Connector

After loading the dynamic skill, prefer any native XAgent MCP tool that is already visible. When a named XAgent tool is not visible, call the same tool through the bundled adapter:

node "{baseDir}/scripts/xagent_mcp.mjs" call xapp_list '{}'
node "{baseDir}/scripts/xagent_mcp.mjs" call <tool_name> '<json arguments>'

For complex JSON, pass the arguments through stdin:

printf '%s' '<json arguments>' | node "{baseDir}/scripts/xagent_mcp.mjs" call <tool_name> -

The adapter supports every remote tool exposed by XAgent MCP, including xagent_skill_load, xapp_list, XApp lifecycle/configuration tools, logic-table tools, STS issue tools, and commit/publish registration tools. It never prints the MCP token.

When the dynamic skill requires a local xagent-files operation and no native local tool is visible, use the file runtime bundled in this same SkillHub package:

node "{baseDir}/scripts/xagent_mcp.mjs" files workspace list --app-key <app_key>
node "{baseDir}/scripts/xagent_mcp.mjs" files workspace push --app-key <app_key> --local <local_path> --remote <remote_path>
node "{baseDir}/scripts/xagent_mcp.mjs" files asset <action> <arguments>
node "{baseDir}/scripts/xagent_mcp.mjs" files resource <action> <arguments>
node "{baseDir}/scripts/xagent_mcp.mjs" files publish <latest|version> --app-key <app_key> <arguments>

Follow the loaded server-side skill's file safety rules. Deletion-mirroring workspace, asset, and resource sync is disabled even when an older command name is attempted. Use non-deleting push; perform deletion only through explicit reviewed delete commands after confirmation.

For ordinary users, accept an app name and resolve its app_key internally. Do not expose raw tool JSON, credentials, OSS paths, manifests, or runtime tokens. Distinguish “已保存,可预览” from “已发布,可运行”, and turn failures into one concrete recovery action rather than connector jargon.

Mandatory Post-Change Surface

After every completed XApp modification, call WorkBuddy's preview_url tool to open the current app directly in the right-side in-app browser/panel before reporting completion. Use the parent platform container https://x.10knet.com/page/xapp/xapp.html?xapp_key=<app_key>&surface=preview when the current changes were not published in this task. Use the same parent container with surface=run only after this task successfully published the current changes.

Never open or report file://, local filesystem/editor/artifact previews, localhost, pub.10knet.com asset/release OSS URLs, raw/private/signed OSS URLs, xpreview.10knet.com, or /page/xapp/xapp.html without an explicit valid surface=preview|run. If preview_url is unavailable or opening fails, return the exact valid platform URL and state that limitation instead of substituting another target.

Absence of a WorkBuddy custom-connector entry is not an error condition for this skill. Only if the adapter itself returns auth_required should you ask the user to create/sign in with an XAgent MCP token. That is account authentication, not another plugin or connector installation. Never tell the user to ask an organization administrator merely because tool search cannot find xagent_skill_load.

Handoff

If the request is mainly wxoa/wxca/wxcw integration, plugin upgrade, goods, grants, resource objects, risk records, or tenant admin settings, use the admin skill instead. If the request is mainly charagent persona, behavior, FAQ, knowledge, media, or template design, use the charagent design skill instead.

本技能来自小葱技能站7w4.net。

🤖 AI 评测

这个Skill质量不错,核心功能齐全,操作流程清晰。它能帮助用户完整地开发和管理XApp页面应用,文档说明详细,错误提示明确。最值得肯定的是安全性设计——文件操作采用安全模式,能有效防止误删内容。不需要额外安装任何连接器就能使用这点也很友好。稍有不足的是,某些高级功能在复杂场景下的表现还需要进一步验证,整体上手需要一定时间。总体来说,这是一个成熟度较高的开发工具,值得信赖。

📊 多维度评分

适应性4.9
规范性4.4
有效性4.8
可靠性4.6
可信度4.3

📁 包含文件 (11 个)

📄 SKILL.md 5.3 KB
📄 runtime/hosts/shared/remote_mcp_proxy_core.mjs 7.3 KB
📄 runtime/hosts/shared/stdio_contract.mjs 1.4 KB
📄 runtime/hosts/shared/stdio_server.mjs 1.8 KB
📄 runtime/hosts/workbuddy/plugin/scripts/oss_client.mjs 6.1 KB
📄 runtime/hosts/workbuddy/plugin/scripts/oss_core.mjs 15.1 KB
📄 runtime/hosts/workbuddy/plugin/scripts/xapp_client.mjs 9 KB
📄 runtime/hosts/workbuddy/plugin/scripts/xapp_files.mjs 5.9 KB
📄 runtime/hosts/workbuddy/plugin/scripts/xapp_publish.mjs 5.2 KB
📄 runtime/hosts/workbuddy/plugin/scripts/xapp_workspace.mjs 4.4 KB
📄 scripts/xagent_mcp.mjs 11.2 KB