ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

ops-journal

v1.0.0

Automates logging of deployments, incidents, changes, and decisions into a searchable ops journal with incident timelines and postmortem generation.

⭐ 0· 475·0 current·0 all-time
by@mariusfit
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (ops-journal) match the contained code and CLI: the Python script implements logging, incident lifecycle, search, export, and writing markdown incident files. There are no unexpected external service credentials, packages, or binaries requested.
✓
Instruction Scope
SKILL.md instructs running the included scripts and using local commands (init, log, incident, search, export). The script reads/writes only local files (SQLite DB and incident markdowns) and CLI args; it does not perform network calls or access unrelated system paths. Behavior stays within the stated purpose.
✓
Install Mechanism
No install spec; this is instruction-only with an included Python script relying on the standard library. That is proportionate for a small CLI tool and keeps installation risk low.
ℹ
Credentials
The code honors an optional OPS_JOURNAL_DIR environment variable to override the default storage path, but the skill's metadata did not declare any required env vars. This is benign functional behavior but is an undeclared env var the user may want to know about because it controls where data is stored.
✓
Persistence & Privilege
The skill does not request permanent platform privileges (always: false) and does not modify other skills or global agent config. It creates files under the user's home workspace directory only.
Assessment
This skill appears to be a local ops journal and is internally consistent. Before installing or running: (1) review the script source (already included) and confirm you're comfortable with files being written to ~/.openclaw/workspace/ops-journal (or set OPS_JOURNAL_DIR to a different folder); (2) run it as a non-privileged user — it only needs file-system access to that directory; (3) if you plan integrations (infra-watchdog or others), verify hooks only post expected messages and do not expose sensitive data in entries; (4) if you require network isolation, note the tool itself performs no network operations but any integrations you add might. If you want stronger assurances, run it in a sandbox/container first.

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

devopsvk97cg2vr6jhjkywd8mh9167b6181smfbincidentsvk97cg2vr6jhjkywd8mh9167b6181smfblatestvk97cg2vr6jhjkywd8mh9167b6181smfbloggingvk97cg2vr6jhjkywd8mh9167b6181smfbopsvk97cg2vr6jhjkywd8mh9167b6181smfbpostmortemvk97cg2vr6jhjkywd8mh9167b6181smfbsrevk97cg2vr6jhjkywd8mh9167b6181smfb

License

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

Comments