ClawHub

Self-Improving Analytics

v1.1.0

Captures data quality issues, metric drift, pipeline failures, misleading visualizations, metric definition mismatches, and data freshness problems to enable...

⭐ 0· 47·0 current·0 all-time
byJosé I. O.@jose-compu
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
The name/description match the provided artifacts: markdown templates, reminder scripts, a hook handler, and helpers to scaffold/promote analytics learnings. There are no unrelated required env vars, binaries, or external download/install steps that would be inconsistent with a logging/reminder skill.
ℹ
Instruction Scope
SKILL.md and scripts focus on creating/maintaining .learnings/ files and injecting reminders via OpenClaw hooks. The activator and error-detector are intended to be run as hooks and the error detector reads the CLAUDE_TOOL_OUTPUT environment variable to detect errors; SKILL.md also instructs copying hooks into ~/.openclaw/hooks and enabling them. These actions affect the agent workspace and hook configuration (expected for this skill) — review before enabling, and be cautious when enabling PostToolUse hooks since they run on tool output.
✓
Install Mechanism
There is no install spec that downloads or executes remote code. The package is instruction-plus-local-scripts and hook handlers that run locally. All files are present in the skill bundle; nothing pulls from arbitrary URLs or writes unexpected binaries.
ℹ
Credentials
The skill declares no required environment variables or credentials. Scripts do read CLAUDE_TOOL_OUTPUT (an agent-provided variable) to detect errors — this is reasonable for a PostToolUse detector but is not listed as a required env var. The README cautions not to log credentials or PII. Examples reference OpenClaw functions (sessions_send/sessions_spawn) which are platform features, not additional secrets.
✓
Persistence & Privilege
always:false and hooks are opt-in. The skill suggests copying hook files into ~/.openclaw/hooks and enabling them, which is expected for a hook; it does not demand forced always-on installation or modification of other skills' configuration beyond registering its own hook.
Assessment
This skill appears coherent and does what it says: it scaffolds .learnings/ logs and injects lightweight reminders via optional hooks. Before enabling: (1) review the scripts (scripts/activator.sh, scripts/error-detector.sh, scripts/extract-skill.sh) to confirm you’re comfortable with their behavior; (2) prefer enabling the UserPromptSubmit activator only (not PostToolUse) unless you want automatic error detection from tool output — PostToolUse reads CLAUDE_TOOL_OUTPUT and may run for many commands; (3) enable hooks per-project or add matcher filters so reminders only run for analytics-related sessions; (4) check file permissions and the paths where the hook is copied (~/.openclaw/hooks, ~/.openclaw/workspace) to avoid global changes you didn’t intend; (5) never copy unreviewed SQL or outputs containing credentials/PII into .learnings/ — the SKILL.md explicitly warns about this. If you want extra assurance, run the extract-skill.sh with --dry-run and test the activator locally before enabling hooks globally.

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

latestvk9733get6zfgyb6g1n5vxsh06s84sgxe

License

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

Comments