ClawHub

L76 Core Arch

v1.0.1

Demonstration skill showcasing complete AgentSkills core architecture. Includes SKILL.md structure, main entry logic, tool integration patterns, error handli...

⭐ 0· 80·1 current·1 all-time
by@wyblhl
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description claim a template/demonstration skill and the manifest, docs, example code, and a small Node index.js are consistent with that purpose. Required binary is only 'node', which is appropriate for a Node-based template.
ℹ
Instruction Scope
SKILL.md and the code stay within template/documentation scope and provide patterns/examples. The docs contain examples that run shell commands (curl, copy, iconv, exec, read/write examples) and reference local Windows paths (D:\...) — these are illustrative, not active behaviors. Users should still review any example command before executing in their environment because examples can perform file or network operations if run as-is.
✓
Install Mechanism
No external downloads or installers are included; the only install spec references the Node runtime as 'built-in'. No archive downloads, remote URLs, or extract steps observed.
✓
Credentials
The skill declares no required environment variables, no credentials, and no config paths. That matches the stated role as a template and demo. Example snippets mention tooling (clawhub, curl) but those are examples and not required env secrets.
ℹ
Persistence & Privilege
The index.js implements a StateManager that reads/writes a state.json in the skill directory and updates runCount/errors. The skill does not request elevated privileges nor set always:true; persistence is limited to its own state file (expected for a template).
Assessment
This skill is primarily documentation and a Node.js template. It does not ask for credentials and only writes a small state.json in the skill directory. Before running anything: (1) inspect index.js and scripts/validate.sh locally, (2) run commands in a sandbox or with --dry-run/--verbose first, (3) be cautious with example shell commands (curl, copy, exec, iconv) as they can read/write files or access the network if you execute them, and (4) if you plan to publish or run automated validation, ensure 'clawhub' commands and any platform-specific paths are appropriate for your environment.

Like a lobster shell, security has layers — review code before you run it.

latestvk973yr33tb524wwd04a89fxw0h83chj0

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

Binsnode

Install

Node.js runtime (built-in)
Bins: node

Comments