Workflow Guardian

• Verdict: Pass
• Confidence: High
• Analyzed: Apr 14, 2026, 2:34 PM
• Findings: 0
• Version: 1.0.0

Overview

The skill's files, runtime instructions, and requested capabilities are internally consistent with a local workflow-enforcement tool and do not ask for extra credentials, network endpoints, or install steps.

This skill appears coherent and local-only: it manages workflows by reading/writing files in a contained folder structure and does not request credentials or network access. Before installing, consider: 1) Back up any existing workspace files you care about (WORKFLOW_LOG.md, memory/index.json, SOUL.md) because the skill expects to append/update them. 2) Review the global rules/docs (AGENT.md, rules/global/*.md) to confirm you accept the strict gate semantics and the claim that some rules 'cannot be overridden by owner instruction' — if you need manual bypasses, plan how you'll signal overrides. 3) Test in a non-production workspace to verify behavior and that the agent's file writes match your expectations. If you need the skill to call external services or require fewer persistent writes, request a variant that limits persistence or exposes explicit owner-controlled override mechanisms.