SysClaw Reporting

Report system issues and submit resource requests to SysClaw via the cross-agent communication system. Use when an agent needs to report an error, warning, o...

This skill appears to do what it says (submit reports/requests by writing to a PostgreSQL database), but there are important warnings to consider before installing or using it: - Metadata mismatch: The registry declares no required environment variables, but the scripts and SKILL.md require SYSCLAW_DB_HOST/PORT/NAME/USER/PASSWORD (or per-script equivalents). Treat that omission as a red flag and ask the publisher to correct the manifest before use. - Credential safety: The scripts require a DB user + password. Do NOT store high-privilege credentials in plaintext wrapper scripts or crontab entries. If you must run periodic checks, prefer a least-privileged DB account, secure storage for secrets (OS keyring, vault), and avoid embedding passwords in files under /usr/local/bin or crontab lines. - Network security: The scripts connect to a DB host without explicit TLS/sslmode configuration. Ensure connections to the DB are restricted to trusted networks or use SSL/TLS and network-level access controls to protect credentials in transit. - Least privilege: Create a dedicated DB role for reporting with only the necessary INSERT/SELECT/UPDATE privileges on the specific tables used (issues, agent_requests, notifications). Do not reuse admin or broad-privilege DB credentials. - Audit and review the DB schema: Because these scripts write directly to the database, verify the schema, triggers, and any downstream automation that acts on inserted rows (SysClaw may execute approved actions). Ensure you trust the operator(s) who have access to that automation. - Ask the maintainer for clarification: Request an updated registry manifest listing required environment variables and a justification for any suggested persistent cron-install steps. If you cannot verify the SysClaw operator and DB host, do not provide credentials. If you want to proceed, only provide a tightly-scoped DB user with minimal privileges and avoid the suggested plaintext cron wrapper; instead use credential management tooling and secure scheduling mechanisms.

Type: OpenClaw Skill Name: sysclaw-reporting Version: 4.0.0 The sysclaw-reporting skill bundle provides a legitimate interface for an AI agent to communicate with a central management system (SysClaw) via a PostgreSQL database. The scripts (check-notifications.sh, report-issue.sh, request-resource.sh) are well-structured, utilize parameterized queries to prevent SQL injection, and include robust error handling with exponential backoff. While the documentation suggests setting up a cron job for automated notification checking, this is a transparently documented feature for polling and does not constitute a stealthy persistence mechanism.