Metrics
v1.0.0Capture, normalize, and report metrics across any domain with reusable dimensions, programmable formulas, and scalable reporting workflows.
⭐ 0· 408·8 current·8 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name and description (capture, normalize, report metrics) align with the instructions and included docs. It asks the user to create and use ~/metrics/ for registry, formulas, reports, and automations; no unrelated binaries, credentials, or external services are requested.
Instruction Scope
SKILL.md and the supporting docs stay within the stated purpose: defining metrics, formulas, reports, and local memory. The only scope item to note is the 'Integration First' setup choices which ask whether the skill should 'activate whenever the user discusses KPIs...' — this could enable proactive suggestions or broader invocation if the user opts in, so confirm that behavior at setup.
Install Mechanism
Instruction-only skill with no install spec and no code files. Nothing is downloaded or written except files the skill itself will create under ~/metrics/ (per its persistence rules). This is the lowest-risk install profile.
Credentials
The skill requires no environment variables, no credentials, and no config paths beyond its own ~/metrics/ memory. It explicitly states it will not store secrets or access files outside ~/metrics/.
Persistence & Privilege
always:false and no persistent install actions are requested. The only persistence is creating and maintaining ~/metrics/memory.md. The remaining note is that if the user enables the 'activate whenever...' integration option, the skill may be more proactive in conversations — ensure that opt-in is explicit and understand how/when it triggers.
Assessment
This skill appears coherent and low-risk because it is instruction-only, stores data locally under ~/metrics/, and requests no credentials. Before installing: 1) Confirm you understand and approve the 'activate whenever the user discusses KPIs...' setup option (decline if you don't want proactive monitoring/suggestions). 2) Expect the skill to create and update ~/metrics/ files — review those files for any sensitive content and do not store secrets there. 3) If you later install the related skills (analytics, dashboard, sql, etc.), review those skills separately because they may request external credentials or installs. 4) If you need stricter guarantees, test in a disposable account or environment and inspect the created ~/metrics/ files after first use.Like a lobster shell, security has layers — review code before you run it.
latestvk97arg2keh5n99y67hr6xrabmx82012p
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📊 Clawdis
OSLinux · macOS · Windows