Self-Evolving Harness

Self-Evolving Harness — 聚焦增强 OpenClaw 的自主性与可控性。从领域意图理解、自主知识沉淀到自主评测与本地 Agent 架构的端到端自主进化，拒绝在 Skill 层面无序熵增。搭配自动化软件研发流水线；反脆弱，即便记忆丢失，Agent 依然有序运行和进化。

Security Scan

The skill's description promises complex autonomous evolution features but the skill contains no implementation, runtime instructions, or required resources — it is incoherent and likely a placeholder or incomplete upload.

Purpose & Capability

The README/description claims end-to-end autonomous evolution, knowledge consolidation, evaluation, and CI integration, but there are no code files, no install steps, no required binaries, and no environment variables. The requested surface (nothing) does not match the claimed functionality (significant system and network interactions).

Instruction Scope

SKILL.md contains only metadata and a title with no runtime instructions, commands, or guidance for the agent. This makes the skill non-functional as described and prevents verifying what it would actually do at runtime.

Install Mechanism

There is no install spec (instruction-only). That minimizes direct install risk but also means there is no implementation to inspect.

Credentials

The skill requests no credentials or config paths, which superficially reduces risk. However, given the ambitious description, the absence of any required credentials or integrations is unexpected and suggests the package is incomplete or misrepresented.

Persistence & Privilege

always is false and no special persistence or system-wide config changes are requested. The skill is user-invocable only and does not request elevated presence.

What to consider before installing

This package looks like a stub or marketing copy rather than a working skill. Before installing or enabling it: (1) treat it as non-functional — it contains no runtime code or instructions; (2) ask the publisher for a full implementation, a README describing runtime steps, and a trustworthy source/homepage; (3) if they provide an implementation later, review the SKILL.md for exact commands, any install URLs, and required environment variables before enabling autonomous invocation; (4) avoid trusting this skill with sensitive credentials or making it always-enabled until its behavior and dependencies are explicit and auditable.