Post Deployment Verifier

Verify deployments are healthy after release — check endpoints, compare response schemas, validate metrics, run smoke tests, verify database migrations, and...

This skill appears to implement useful post-deploy checks, but it performs broad environment and system scanning that is not declared. Before installing or letting an agent run it (especially autonomously or in production): - Inspect the full SKILL.md (and any truncated parts) line-by-line and confirm there are no unexpected network destinations or exfil paths. - Run the script manually in a safe staging environment to observe exactly what it reads (env, logs, files). - Remove or restrict the 'env | grep' discovery if you do not want all environment variables examined; prefer an explicit config (.deploy-verify.json) listing endpoints. - Ensure the agent runs with minimal privileges (non-root) so journalctl/docker logs are limited, or run checks that don't require elevated access. - Ask the publisher for source/homepage and to declare required env vars and tools (docker, journalctl, rg, python3, git) so you can make an informed consent decision. If you cannot review or confine its runtime, avoid running this skill in production where environment variables or logs may contain secrets.

Type: OpenClaw Skill Name: post-deployment-verifier Version: 1.0.0 The skill is a post-deployment verification utility designed to automate health checks, response schema validation, and resource monitoring. It uses standard system tools like curl, docker, and journalctl to inspect service status and logs (SKILL.md). While it scans environment variables for service URLs, it includes safety checks to ensure only HTTP/S endpoints are targeted, and its behavior remains strictly aligned with its stated purpose of deployment verification.