What makes Xz01 Dev Skill notable?

1.5K downloads. Trust evidence available

How should Xz01 Dev Skill be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Xz01 Dev Skill

Use when 用户提到“xz01规范”时必须命中本技能；xz01规范=xz01-dev-skill。用于 Hermes + Claude Code 围绕用户现有 OpenClaw/xz01 模板资料进行角色编排、开发学习范围、测试/规范分工，并严格将 /root/.openclaw 作为只读学习资料库；编码修...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.5k

Updated

Oct 10, 2026

Version

1.0.44

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.5K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.5K downloadsadoption · observed Oct 10, 2026
Latest release: 1.0.44release · observed May 18, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s1751ams93yq7ebhk4m0rj58f583gjdd:xz01-dev-skill

Install using `clawhub skill install s1751ams93yq7ebhk4m0rj58f583gjdd:xz01-dev-skill` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/amd5/xz01-dev-skill before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-amd5-xz01-dev-skill/snapshot"

Documentation

CLAWHUB

160,000 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: xz01-dev-skill
description: Use when 用户提到“xz01规范”时必须命中本技能；xz01规范=xz01-dev-skill。用于 Hermes + Claude Code 围绕用户现有 OpenClaw/xz01 模板资料进行角色编排、开发学习范围、测试/规范分工，并严格将 /root/.openclaw 作为只读学习资料库；编码修复交给 Claude dev，测试输出写入 /www/wwwroot/www.900az.com，彻底验证通过的模板按编号压缩到 /root/.hermes/workspace/xz01/；吸收 Karpathy 精准修改/目标驱动原则，并提供 xz01 专用 hook-style gate；包含 PC 与 m 移动端顶部导航必须成对按菜单数据渲染、多页列表必须按 xz01_demo 做双端翻页、所有详情页必须覆盖且右侧/底部必须混合游戏+应用+资讯/攻略模块、app/游戏/应用资源项必须图标化展示、视觉验收必须整页截图+分段AI检查的规则。
version: 1.0.44
author: Hermes Agent
license: MIT
metadata:
  hermes:
    tags: [xz01-dev-skill, xz01规范, xz01, openclaw, hermes, claude-code, role-orchestration, read-only, template-workflow, 角色分工, 学习范围, 只读, 测试输出, 模板打包, 验证通过]
    related_skills: [hermes-agent, claude-code, systematic-debugging, test-driven-development]
---

# xz01-dev-skill

## Trigger Alias / 命中别名

```text
xz01规范 = xz01-dev-skill
```

当用户提到以下中文触发词时，必须优先加载并遵循本技能：

- xz01规范
- xz01 规范
- xz01开发规范
- xz01学习范围
- xz01角色分工
- Hermes+Claude xz01
- OpenClaw xz01
- 谁是 dev / 谁是 test
- /root/.openclaw 只读
- 测试输出写到 /www/wwwroot/www.900az.com
- 验证通过模板打包到 /root/.hermes/workspace/xz01/
- 安装或接入 Lanhu MCP / 蓝湖 MCP
- PC/m 导航栏同步处理
- 双端顶部导航
- 移动端导航也要同步
- 导航栏按菜单数据渲染
- 整页截图验收
- full-page screenshot
- 资源项图标化展示
- app/game resource cards

## References

- `references/session-2026-05-18-home-resource-iconized-cards.md` — durable homepage/resource-module correction: app/game/application resources must be iconized cards, icon grids, image-text lists, or icon ranking rows; no no-icon title-only horizontal rows for software/game/app resources. News/guide text lists are exempt when clearly article modules.
- `references/session-2026-05-18-karpathy-ecc-hook-adaptation.md` — user-approved adaptation notes: absorb Karpathy precise/goal-driven dev principles and xz01-specific hook gates; exclude generic security scanning and parallelization for now.
- `references/session-2026-05-18-skill-library-active-review.md` — skill-maintenance lesson: xz01 user corrections phrased as “这是规范” must be actively promoted into the class-level skill and references, not left only in chat or memory.
- `references/session-2026-05-18-all-detail-mixed-sidebar.md` — user correction that “详情页” means every active PC/mobile detail template, including collection/topic detail when present; PC right sidebars must not be only攻略 and must mix app/software, game, and news/guide modules with real data. Also covers the operational pattern that if a long dev worker times out after making file changes, do not assume failure or success: first inspect modified timestamps/content, then continue with smaller verification/fix tasks.
- `references/session-2026-05-18-dual-end-list-pagination.md` — hard pagination rule: every dual-end list page except ranking/rank-list pages must render pagination like `xz01_demo` when data exceeds one page; PC uses numeric page links, mobile uses `上一页` / `下一页` controls. The scope is route/database-list based, not limited to files named `list_soft/list_game/list_news/l

_meta.json

{
  "ownerId": "kn709ac4cea693g2hg2p4p3sgn82vk9z",
  "slug": "xz01-dev-skill",
  "version": "1.0.44",
  "publishedAt": 1779100324176
}

references/demo-xz01-may-2026-source-update.md

# demo_xz01 May 2026 source update learning

Context: user reported `/root/.openclaw/workspace/demo_xz01` source was updated and asked to learn differences from previous content. The analysis was read-only; do not modify `demo_xz01`.

## Compared materials

Updated archives observed around 2026-05-15:

- `www.277zy.com/public/themes/default_2GmaD.zip` compared against older `default_HrJZZ.zip`
- `www.400zyw.com/public/themes/default_6amTZ.zip` compared against older `default_KntTK.tar.gz`
- `www.988zyw.com/public/themes/default_7MikX.zip` compared against older `default_mCYYn.tar.gz`
- `www.866zyw.com/public/themes/default_L2GB4.zip` compared against current `public/themes/default`; no content delta found

## Durable learning

### Front-end dual-end search is canceled/weakened

The user explicitly confirmed the example: “其中前台双端搜索，已取消.” Treat this as a rule for future xz01-style template work:

- PC/mobile header search forms are no longer mandatory.
- Do not fail QA solely because a PC or mobile header lacks a complete `form action="...Search/index"` search submission flow.
- Search pages such as `cms/search.html` and `mobile/search.html` may still exist; their presence does not mean the front-end header must expose full search.
- Some updated templates retain only a search icon, placeholder input, hot tags, or static search entrance.

Observed examples:

- `www.277zy.com`: PC header form removed; mobile header form replaced by non-form `searchBox`/input/icon.
- `www.400zyw.com`: PC and mobile header forms removed/weakly represented.
- `www.988zyw.com`: no full header form baseline; search UI moved/reshaped.
- `www.866zyw.com`: no archive-to-current change; if a specific template still keeps search, respect that template.

### Template structure is no longer uniform

Updated templates diverge more strongly from each other:

- `www.277zy.com` removed `common_cms/common/zyxz_module/*` entirely in the new archive.
- `www.400zyw.com` and `www.988zyw.com` still have many `zyxz_module` files, but pages/partials changed substantially.
- Some templates add many mobile bottom/related partials; others reduce PC/mobile partials and inline sidebars/recommendation blocks directly in page templates.

Future dev/test work should not require a fixed `zyxz_module` inventory or a fixed set of `_side_*.html` includes.

### Page composition changes

Observed updated patterns:

- Home pages increasingly use page-local blocks and `getAllData()` calls for hot data, new data, recommendations, news, slides, videos, rankings, etc.
- List pages may replace sidebar includes with inline ranking/recommendation/news blocks.
- Game detail pages emphasize platform/download completeness: Android/iOS availability, QR scan download, screenshots/slider, related games, related news, and rankings.
- Rank pages may use `cms_appranking`, bind IDs, `$rank_channel_list`, and `$game_list` instead of plain appsoft list calls.

### Existing hard rules still apply

Do not blindly copy risky c

references/hermes-native-xz01-first-run.md

# Hermes-native xz01 factory first-run pattern

This reference captures the durable workflow learned from the first Hermes-native xz01 prototype run. It is not a one-off task log; use it as a starter pattern for future xz01 automation work.

## Context

The user corrected that OpenClaw runtime mechanisms (`sessions_send`, `agent:dev:main`, OpenClaw `flow-controller.js`) do not map to Hermes. For Hermes work, OpenClaw is a read-only standards/corpus source. New automation state and generated files belong under Hermes-owned paths.

## Correct first-run approach

When the user asks whether to keep discussing or “直接开发第一套给我看下”, act and produce a small end-to-end prototype rather than only listing caveats.

Recommended minimal first-run sequence:

1. Treat `/root/.openclaw` as read-only reference.
2. Create a Hermes factory run directory, e.g.:
   - `/root/.hermes/workspace/xz01-factory/runs/run-0001/`
   - generated template root: `generated/public/themes/default/`
   - reports: `reports/`
3. Write a minimal `state.json` and `requirement.json` for traceability.
4. Use `delegate_task` for a short dev-worker implementation task, or a long-running explicit `hermes` / `claude` worker if the implementation is large.
5. Generate only into the Hermes factory run directory; do not deploy or overwrite production themes in the prototype step.
6. Run deterministic static validation before reporting.
7. Report what exists, what was validated, and what remains before production deployment.

## Minimal output shape

```text
/root/.hermes/workspace/xz01-factory/runs/run-0001/
├── state.json
├── requirement.json
├── generated/public/themes/default/
│   ├── DEV_SUMMARY.md
│   ├── cms/index.html
│   ├── mobile/index.html
│   └── common_cms/
│       ├── common/_head.html
│       ├── pc/_header.html
│       ├── pc/_footer.html
│       ├── pc/assets/css/style.css
│       ├── pc/assets/js/style.js
│       ├── mobile/_header.html
│       ├── mobile/_footer.html
│       ├── mobile/assets/css/style.css
│       └── mobile/assets/js/style.js
└── reports/basic-validation.json
```

## Static validation checklist for prototype

Before telling the user the prototype is ready, verify at least:

- no writes under `/root/.openclaw`
- no production deploy unless explicitly requested
- no raw PHP template tags (`<?php`, `<?=`, `<?`)
- mobile templates contain no `target` / `_blank`
- no `href="#"`
- no `uk-cover` attributes
- no `limit="0"` / `getAllData({limit: 0})`
- CSS brace counts are balanced
- all `{include file="./themes/default/..."}` targets exist
- referenced local CSS/JS assets exist under the generated template root
- HTML class names used by the prototype have CSS definitions, or intentional exceptions are documented

## Prototype vs production boundary

A prototype-ready result is not production-ready. Before packaging/deployment, continue with:

1. renderer script: deploy to a safe test theme or staging path, clear cache, render PC/mobile
2. screenshot capture for both d

references/hermes-native-xz01-live-deploy-validation.md

# Hermes native xz01 live deployment and validation notes

Use this when the user asks to deploy a temporary xz01 template for live validation via:

- `https://www.900az.com/`
- `https://m.900az.com/`

## Key correction from the first live run

The prototype directory under `/root/.hermes/workspace/xz01-factory/runs/<run>/generated/` is safe for staging, but the user may explicitly want temporary template development to live under:

```text
/www/wwwroot/www.900az.com/public/themes/default/
```

When this happens, proceed directly but first make a timestamped backup of the current `default` theme.

## Safe live deployment sequence

1. Ensure generated source exists under the run directory.
2. Create backup:

```bash
BACKUP_DIR=/root/.hermes/workspace/xz01-factory/backups
mkdir -p "$BACKUP_DIR"
tar -czf "$BACKUP_DIR/default-before-<run_id>-$(date +%Y%m%d-%H%M%S).tar.gz" \
  -C /www/wwwroot/www.900az.com/public/themes default
```

3. Replace default theme:

```bash
rm -rf /www/wwwroot/www.900az.com/public/themes/default
mkdir -p /www/wwwroot/www.900az.com/public/themes/default
cp -a /root/.hermes/workspace/xz01-factory/runs/<run_id>/generated/public/themes/default/. \
  /www/wwwroot/www.900az.com/public/themes/default/
rm -rf /www/wwwroot/www.900az.com/runtime/*
```

4. Verify PC and mobile return HTTP 200.
5. Run PHP syntax checks on compiled runtime templates under `/www/wwwroot/www.900az.com/runtime/temp/*.php` after first render.
6. Run static checks:
   - mobile contains no `target="_blank"`
   - source templates contain no raw PHP tags
   - no `href="#"`
   - no `uk-cover`
   - no `limit="0"` / `getAllData({limit:0})`
   - CSS brace counts balanced
7. Use browser screenshots and AI vision on both URLs.
8. Save artifacts under:

```text
/www/wwwroot/www.900az.com/xz01-runs/screenshots/<run_id>/
/www/wwwroot/www.900az.com/xz01-runs/reports/
```

## Pitfalls found in run-0001

### Undefined template variables can cause 500

If the controller does not provide variables such as `$recommend_list`, `$latest_list`, `$rank_list`, `$category_list`, `$news_list`, or `$topic_list`, ThinkPHP may throw `未定义变量` during template compilation/rendering.

For live prototypes, wrap optional data blocks with `isset(...)` and provide static fallback content so the page can render before real DB binding exists:

```html
{if condition="isset($recommend_list)"}
  {foreach name="recommend_list" item="vo" key="key"}
  ...
  {/foreach}
{else/}
  <!-- static fallback cards for visual validation -->
{/if}
```

### Some `|default` forms may compile badly

Avoid complex `|default` expressions in live xz01 prototypes, especially inside `{:...}` expressions. Prefer explicit `isset(...) ? ... : ...` or static fallback blocks.

### ThinkPHP trace overlay can pollute screenshots

If debug trace is enabled, screenshots can show `#think_page_trace_open` with a small runtime number such as `0.070867s`. Hide it in temporary template CSS before visual validation:

```css
#think_page_tr

Github ReposUpdated 16h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.