skills-monitor

What to check before installing or running this skill: - Metadata mismatch: The registry lists no required env vars, but the code expects WECOM_* variables (enterprise WeCom credentials), NGROK token, and uses keyring. Do not assume 'no credentials required' — inspect and set these intentionally. - Review external endpoints: The code can push reports via a hard-coded WEBHOOK_URL and supports uploading data to arbitrary servers (upload --server). Verify the webhook target is one you control and understand where 'upload' will send data. Consider running in offline/mock mode first. - Inspect deploy scripts: deploy/setup_ssh_key.sh and deploy/pack_and_upload.sh exist and can create SSH keys / push artifacts. Do not run those scripts unless you trust the destination and have reviewed their contents. - Data collection scope: This tool is designed to run other Skills and collect inputs/outputs and metrics. If you install it, it will have access to whatever skills it runs and their I/O. Limit its permissions, run in a sandbox, or restrict the skills directory if you are concerned about sensitive data being captured. - WeCom configuration: ALLOWED_USERS defaults to allow-all (empty list means no restriction). If you enable the WeCom callbacks/server, set ALLOWED_USERS properly and validate CALLBACK tokens. Also replace or confirm any hard-coded webhook keys. - Network exposure: Running 'server' or the web dashboard exposes endpoints (PWA, callbacks). Avoid binding to public interfaces or use firewall / localhost-only binding until configured securely. - Review adapters/uploader: Audit adapters (clawhub_client, DataUploader, skill_registry, runners) to see what external services are called and what data they transmit. If you plan to use 'live' benchmarking (real API calls) check how API keys are handled. - Source verification: The skill.json references a GitHub repo. If you need higher confidence, fetch and compare the upstream repository, confirm author identity, and check for recent commits/issues. Summary recommendation: treat this package as a powerful tool that legitimately needs broader permissions, but the manifest underreports them and the distributed files include scripts that can change system state or transmit data. If you decide to install, run it first in an isolated environment (VM/container) and audit/replace webhook keys and deploy scripts before enabling networked features.