EO Blog Dev
v1.0.0Build a complete blog system using Everything Openclaw (EO) multi-expert collaboration - full workflow demo
⭐ 1· 73·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description describe a multi-expert demo for building a blog and the SKILL.md contains only high-level orchestration instructions and a prerequisite to install the Everything Openclaw (EO) plugin. The skill itself does not request unrelated credentials, binaries, or config paths, so its declared purpose aligns with its requests.
Instruction Scope
Instructions are high-level workflow steps (planner, architect, dev, QA, deploy) and do not directly read files, access env vars, or run commands beyond recommending installing the EO plugin. However the instructions are vague and delegate execution to the eo-collaboration plugin; that delegation gives the plugin wide discretion to perform actions (create repos, run builds, connect to deployment targets) not specified here.
Install Mechanism
The skill is instruction-only and has no install spec. It only suggests running 'openclaw plugins install eo-collaboration' which is a standard plugin install command; nothing in the skill would write arbitrary code to disk on its own.
Credentials
The skill declares no required environment variables or credentials itself. Be aware that the EO plugin (which this skill requires) may later request cloud, Git, or CI/CD credentials to implement deployment and repo creation. Those external credential requests are not visible in this SKILL.md and should be evaluated when the plugin is installed.
Persistence & Privilege
The skill does not request 'always: true' and is user-invocable only. Autonomous model invocation is allowed by default (platform behavior) but the skill does not request elevated persistence or to modify other skills' configurations.
Assessment
This skill itself is just a high-level orchestration script and is internally consistent with its stated purpose, but it depends on the external eo-collaboration plugin to do real work. Before installing or running this skill: 1) Inspect and verify the eo-collaboration plugin (source, maintainer, permissions) because it will perform actions the skill delegates; 2) Be cautious about providing any cloud/Git/CI credentials to the plugin — only supply minimal scoped tokens and use throwaway/test accounts if possible; 3) Expect the workflow to generate, run, and possibly deploy code — plan to review generated code and any automated pushes to repositories before they are published; 4) Run the demo in an isolated/test environment first and monitor network activity and credential usage. If you want a stricter assessment, provide the eo-collaboration plugin manifest or its SKILL.md so those behaviors can be evaluated directly.Like a lobster shell, security has layers — review code before you run it.
latestvk97dc3zqc6qmvyb9qt12thy2j584471c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.