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...
name: sysclaw-reporting
description: >
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, or
info-level issue for SysClaw triage, or request anything from SysClaw including
software installation, resource access, configuration changes, service management,
deployments, or system information. Triggers on phrases like report an issue,
report an error, request access, need software, install package, create database,
restart service, deploy, check status, escalate to sysclaw.
SysClaw Reporting (Client)
Report issues and submit requests to SysClaw. This is the client-side skill β it covers how to communicate with SysClaw, not how SysClaw processes requests.
Prerequisites
1. Install Python dependency
pip3 install psycopg2-binary
2. Set environment variables
Set these before running scripts. All scripts use a fallback chain: script-specific vars β SYSCLAW_DB_* β defaults.
# Shared connection settings (used by all scripts as fallback)
export SYSCLAW_DB_HOST="" # Ask your SysClaw operator
export SYSCLAW_DB_PORT="5432"
export SYSCLAW_DB_NAME="system_comm"
export SYSCLAW_DB_USER="" # e.g., jobagent, pmagent, researcher_agent
export SYSCLAW_DB_PASSWORD=""
You can also set per-script overrides (ISSUE_DB_*, REQUEST_DB_*) if different scripts need different credentials, but in most cases the shared SYSCLAW_DB_* vars are sufficient.
Ask your SysClaw operator for the correct host address and your agent credentials.
Report an Issue
For errors, warnings, and problems that need attention:
scripts/request-resource.sh jobhunter software install nginx '{"version":"latest"}' normal
scripts/request-resource.sh pmagent access grant /var/data/pm '{"level":"read"}'
scripts/request-resource.sh researcher info check disk_usage
What Happens Next
1. Your request is submitted and SysClaw is automatically notified
2. SysClaw assesses and processes the request (typically within 15 minutes)
3. SysClaw executes approved actions β you don't need to do anything after approval
4. You receive a notification with the result (e.g., "DONE: nginx installed and running")
Verdicts:
approved + DONE β SysClaw completed the work, see notification for details
denied β see notification for reason
escalated β human operator reviewing, you'll be notified when decided
Check Notifications
Check for responses from SysClaw:
scripts/check-notifications.sh # View unread
scripts/check-notifications.sh yes # View and mark as read
Workflow:
1. Run check-notifications.sh at session start or after submitting a request
2. Read the results β SysClaw has already done the work for approved requests
3. Mark as read when done
Automatic Notification Checking
Set up a cron job so responses are ready when your session starts:
-- Check responses
SELECT * FROM notifications WHERE recipient = 'pmagent' AND read = FALSE;
Do not set verdict, security_assessment, resolved_at, or resolved_by β SysClaw manages these.
Post-Install
1. TOOLS.md β Add DB host, user, and connection details
2. Set up notification cron job β See "Automatic Notification Checking" above
3. Test:
scripts/report-issue.sh info "SysClaw reporting skill installed - test"
Technical Notes
Scripts use Python psycopg2 with parameterized queries (no SQL injection risk)
JSON payloads are validated with json.loads() before database insertion
Connection retry: 3 attempts with exponential backoff (1s, 2s, 4s) on initial connection failure
Mid-session reconnect: If the connection drops between queries, scripts reconnect and retry once automatically
Connection timeout is 10 seconds per attempt (override with PGCONNECT_TIMEOUT)
All scripts exit non-zero on failure with descriptive error messages
π‘ Examples
scripts/request-resource.sh jobhunter software install nginx '{"version":"latest"}' normal
scripts/request-resource.sh pmagent access grant /var/data/pm '{"level":"read"}'
scripts/request-resource.sh researcher info check disk_usage
βοΈ Configuration
1. Install Python dependency
pip3 install psycopg2-binary
2. Set environment variables
Set these before running scripts. All scripts use a fallback chain: script-specific vars β SYSCLAW_DB_* β defaults.
# Shared connection settings (used by all scripts as fallback)
export SYSCLAW_DB_HOST="" # Ask your SysClaw operator
export SYSCLAW_DB_PORT="5432"
export SYSCLAW_DB_NAME="system_comm"
export SYSCLAW_DB_USER="" # e.g., jobagent, pmagent, researcher_agent
export SYSCLAW_DB_PASSWORD=""
You can also set per-script overrides (ISSUE_DB_*, REQUEST_DB_*) if different scripts need different credentials, but in most cases the shared SYSCLAW_DB_* vars are sufficient.
Ask your SysClaw operator for the correct host address and your agent credentials.