Osop Optimize

Analyze .osoplog execution history to optimize workflows — finds slow steps and parallelization opportunities

This skill appears to do what it claims, but it asks for access to ~/.osop/config.yaml without explaining why. Before installing or running it: 1) Ask the publisher why the config file is required and what data from it is used. 2) Inspect ~/.osop/config.yaml yourself (or provide a copy of it stripped of secrets) to see if it contains API keys, tokens, or endpoints. 3) Run the skill first on a copy of your .osop file and logs (not production files) and confirm the diff before applying changes. 4) If you don't want the skill to read your home config, see if the skill author will remove that requirement or allow providing any needed settings explicitly. 5) Because this is an instruction-only skill with no code to inspect, prefer running it in a safe/test environment until the author clarifies the config usage.

Type: OpenClaw Skill Name: osop-optimize Version: 1.2.0 The osop-optimize skill is designed to analyze workflow execution logs (.osoplog.yaml) and suggest performance or reliability improvements to the corresponding workflow files (.osop). The instructions in SKILL.md are focused on data aggregation, issue identification (e.g., slow steps, failure rates), and applying user-approved optimizations. There are no indicators of data exfiltration, malicious execution, or prompt injection attacks.