KPI for clawbot
v1.0.1基于 KPI 体系管理智能体关键绩效指标与执行任务。当用户提到 KPI、指标管理、达成率、绩效复盘、评分、经验沉淀时使用，并将信息维护到 memory/kpi.md。
⭐ 0· 273·0 current·0 all-time
byInfiniEcho@dawnlck
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description describe KPI management and the SKILL.md contains detailed rules for creating, tracking, and reviewing KPIs and tasks. There are no unexpected env vars, binaries, or external services requested — the requested capabilities align with the stated purpose.
Instruction Scope
Instructions explicitly require reading and writing a local memory file (~/.openclaw/workspace/memory/kpi.md) and define structured persistence and update rules. This is within scope for a KPI assistant, but be aware the skill will persistently modify a workspace file and will update it when the user mentions KPI-related items. Minor inconsistency: top-level description refers to memory/kpi.md (relative) while the doc uses the absolute ~/.openclaw/workspace/memory/kpi.md path.
Install Mechanism
No install spec and no code files — instruction-only. Nothing is downloaded or written to disk by an installer beyond the normal memory file updates defined in the instructions.
Credentials
The skill requires no environment variables, credentials, or external config paths. It also explicitly states not to record sensitive info (passwords, keys). The requested access (local workspace file) is proportional to its purpose.
Persistence & Privilege
The skill persists KPI data to the agent workspace (memory file) and will read/modify that file as part of normal operation. It is not marked always:true and requests no elevated privileges — this persistent write access is expected for a memory-based KPI assistant but is the primary consequence users should understand.
Assessment
This skill is coherent and appears to do what it says: it will read and update a persistent KPI file at ~/.openclaw/workspace/memory/kpi.md to track goals, tasks, and periodic reviews. Before enabling, confirm you are comfortable storing KPI content in that location (back it up if needed) and that the workspace file does not contain other sensitive information. The skill requests no credentials or external installs. If you want stricter control, consider restricting write permissions to the workspace or reviewing the memory file periodically; also note the small path wording inconsistency (relative vs. absolute) and confirm the exact file location in your environment.Like a lobster shell, security has layers — review code before you run it.
latestvk97857672m1xzy5ae14fye9cms82k8cp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.