Osop Report

Convert .osop and .osoplog.yaml into standalone HTML report with dark mode and expandable nodes

This skill appears to do what it claims: parse .osop and optional .osoplog.yaml files and emit a standalone HTML report using Python + PyYAML. The main inconsistency is that the registry metadata lists ~/.osop/config.yaml as a required config path even though neither the SKILL.md nor the visible code reads that file. Before installing or running: 1) Ask the publisher why ~/.osop/config.yaml is declared or remove that requirement if not needed. 2) Inspect the full osop-report.py (the provided portion looks benign: no network, subprocess, or secret-access calls). 3) Run the script on sample files in an isolated environment (or review the remainder of the source) to confirm it only reads the specified .osop/.osoplog.yaml and writes the -report.html file. 4) If you are concerned about privacy, run it locally (no network) — the code shown uses only standard libs + PyYAML. If the publisher cannot justify the declared config path or if additional files in the package reference external endpoints, treat the skill as risky and avoid installing it.

Type: OpenClaw Skill Name: osop-report Version: 1.2.0 The skill bundle is a legitimate utility for generating HTML reports from OSOP workflow and log files. The Python script (osop-report.py) uses safe practices such as yaml.safe_load and HTML escaping, and contains no network activity, obfuscation, or unauthorized file access.