huaweicloud/huaweicloud-skills

huawei-cloud-openviking-agent-integration

Integrate and unbind OpenViking long-term memory with coding agents.

Voir la source
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Huawei Cloud Agent Integration (OpenViking Long-Term Memory)

Overview

Integrate and unbind OpenViking long-term memory with coding agents. Agents run in bwrap sandboxes under /root/job-envs/sandboxes/ and use their native mechanism — MCP (mcp__openviking__* tools) or HTTP memory provider — so integration survives agent upgrades.

Integration writes are template-level persistent: config is injected into the agent's start.sh / config templates under /root/template/<agent>/, so sandbox stop + start preserves the integration.

Supported Agents

AgentMechanismPersistence
CodeArts CLI@openviking/opencode-plugin.codeartsdoer/node_modules/Template + live
OpenCode@openviking/opencode-plugin (npm mirror → GitHub fallback)Template start.sh
OpenClawclawhub:@openviking/openclaw-plugin + contextEngine slotTemplate start.sh
Optimization: disables session-memory hook + denies memory_search tool (OpenViking handles recall; local memory degrades quality)
HermesBuilt-in memory.provider: openviking (HTTP REST, no MCP)Template + live
WorkSwarmDual-channel: native provider + MCP (13 tools) + code-mode patchTemplate + live + runtime patch
KimiCodeMCP via mcp.jsonTemplate + live
DeepSeek Harness@openviking/dsh-memory-plugin bundle (on-demand from GitHub)Template start.sh
Prime Agent@openviking/pi-coding-agent-extension (on-demand from GitHub)Template start.sh

Per-agent config details: references/agent-configs.md.

Prerequisites

  • OpenViking server running at http://127.0.0.1:1933 (curl -s http://127.0.0.1:1933/health).
  • Agent sandboxes exist under /root/job-envs/sandboxes/ (managed by job-env-manager).
  • Host tools: curl, python3, bash. OpenCode/OpenClaw additionally need npm.
  • No Huawei Cloud IAM policies required — this skill operates on local bwrap sandboxes only.

参数确认 (Required Inputs)

ParameterRequiredDescriptionExample
--agent <name>Yes (unless --all)Target agent (see table above)--agent opencode
--allYes (unless --agent)Operate on all 8 agents--all
--endpoint <url>NoOpenViking server URL (default http://127.0.0.1:1933)--endpoint http://192.168.1.100:1933
--api-key <key>NoOpenViking API key (dev mode needs none). Never echo in chat--api-key sk-xxx
--dry-runNoShow changes without applying--dry-run
--yes / -yNoSkip authorization prompt (automation only)--yes
--jsonNostatus.sh: machine-readable output--json

核心命令

功能命令
查看集成状态scripts/status.sh--json 机器可读,--agent <name> 指定)
验证 MCP 端点scripts/verify_mcp.sh
集成单个 Agentscripts/integrate.sh --agent <name> [--endpoint URL] [--api-key KEY] [--dry-run] [--yes]
集成全部 Agentscripts/integrate.sh --all
解绑单个 Agentscripts/unbind.sh --agent <name> [--dry-run] [--yes]
解绑全部 Agentscripts/unbind.sh --all

Workflow

bash
SKILL_DIR=/root/.agents/skills/huawei-cloud-openviking-agent-integration
  1. Check status: $SKILL_DIR/scripts/status.sh — per-agent state: template + live (active), template only (activates on restart), live only (lost on restart).
  2. Verify MCP: $SKILL_DIR/scripts/verify_mcp.sh — full MCP handshake (initialize → tools/list → health).
  3. Integrate: $SKILL_DIR/scripts/integrate.sh --agent <name> (or --all).
  4. Unbind: $SKILL_DIR/scripts/unbind.sh --agent <name> (or --all).
  5. Rebuild OpenClaw: stop + start via job-env-manager API re-runs start.sh. Scripts: references/related-commands.md.

Authorization & Safety

  • Authorization is mandatoryintegrate.sh and unbind.sh require explicit confirm (or --yes for automation). --dry-run previews without authorization.
  • Do not fabricate integration state — always run status.sh to verify before reporting.
  • Never edit agent configs directly — all changes go through the skill scripts.
  • No API keys in logs--api-key values must never appear in output.
  • Every config modification creates a .bak.<timestamp> backup for rollback.

Full rules: references/guardrails.md. Troubleshooting: references/troubleshooting.md.

Plugin Sources

The skill ships no plugin code — plugins are installed on demand at integrate time via domestic-first mirrors (Huawei Cloud npm → npmmirror → npmjs; GitHub raw mirrors for non-npm plugins). All downloads are byte-verified against GitHub blob SHA. Installed copies under /root/runtime/ are reused if upstream is unreachable (3-tier cache: sandbox node_modules → runtime cache → online).

References

DocumentDescription
agent-configs.mdPer-agent config details, MCP tools, server info
guardrails.mdSafety, authorization, access permissions
troubleshooting.mdFailure scenarios and fixes
verification.mdVerification methods and acceptance criteria
related-commands.mdRestart/rebuild scripts, env vars

Scripts (OO Architecture)

Base class (lib/base.sh) + registry (lib/registry.sh) + per-agent subclasses (agents/*.sh). Entry points (integrate/unbind/status.sh) are thin CLI parsers. All scripts are idempotent with .bak.<timestamp> backups. Adding a new agent = one file in agents/.

du même dépôt

Autres Skills

Tous les Skills
huaweicloud
Communauté

huawei-cloud-publish-work-to-gallery

Publish user's work to the Huawei Cloud University Operations Platform (华为云高校运营平台/作品陈列馆). Use this skill whenever the user wants to publish, submit, or upload a project/work to the gallery or a training camp (训练营) on the platform — including casual phrasings like "把作品发布上去", "投稿到陈列馆", "传作品到平台", "提交作品/项目", "报名发布作品", as well as formal ones like "publish to work gallery", "submit to training camp", "upload work to the platform". Do NOT use for general dev questions, git push to GitCode alone, or platform browsing without publishing intent.

installations
5
GitHub Stars
50
Mis à jour
23 sept.
huaweicloud
Communauté

huawei-cloud-eip-cost-optimizer

Huawei Cloud EIP (Elastic IP) cost optimization skill using hcloud CLI (KooCLI). 1. List and query EIPs across regions with detailed status 2. Identify idle/unbound EIPs and generate cost optimization reports 3. Set up idle EIP monitoring with webhook/email alerts 4. Generate HTML/JSON cost analysis reports 5. Maintain operation audit logs for compliance Read-only analysis only - NO bandwidth adjustment, tag management, or EIP release/deletion. Triggers include: "EIP cost optimization", "idle EIP analysis", "EIP audit", "cost report", "EIP status query", "EIP list", "EIP monitoring", "EIP alert", "cost analysis", "idle monitoring", "operation audit", "EIP 成本优化", "闲置 EIP 分析", "EIP 审计", "成本报告", "EIP 状态查询", "EIP 查询", "EIP 列表", "EIP 监控", "EIP 告警", "成本分析", "闲置监控", "操作审计"

installations
1
GitHub Stars
50
Mis à jour
22 sept.
huaweicloud
Communauté

huawei-cloud-flexus-l-deploy-jiuwenswarm

One-click deployment of JiuwenSwarm multi-Agent collaboration platform on Huawei Cloud Flexus L instances. Usage scenarios: When users need to quickly deploy JiuwenSwarm/JiuwenClaw on Huawei Cloud Flexus L instances, when they need to automatically create cloud instances and deploy AI Agent platforms, when they need to configure model APIs and message channels (Xiaoyi/Feishu/DingTalk). Automatically create instances, deploy applications via COC, configure models and message channels. Trigger keywords: JiuwenSwarm deployment, JiuwenClaw deployment, 九问Swarm部署, 九问Claw部署, 一键部署JiuwenSwarm, AI智能体平台部署, 部署九问Swarm, 部署九问Claw,云服务器部署AI平台.

installations
1
GitHub Stars
50
Mis à jour
22 sept.
huaweicloud
Communauté

huawei-cloud-flexus-l-server-flexusagent-deployment

Deploy AI Agent development platform (Dify) on Huawei Cloud Flexus L instance, providing deployment operations, password management, MaaS model configuration, and workflow import capabilities. Trigger keywords: deploy flexusagent/一键部署Flexus AI Agent开发平台、change password/修改开发平台管理员密码、change dify password/修改dify平台密码、add maas provider/添加MaaS模型供应商、configure maas model/配置MaaS模型、view workflow/查看AI Agent工作流、import workflow/导入AI Agent工作流

installations
1
GitHub Stars
50
Mis à jour
22 sept.