Pilot Sla

Service-level agreement enforcement with automatic penalties. Use this skill when: 1. You need guaranteed performance levels for critical tasks 2. You want a...

Before installing, confirm the following: 1) Who provides the AGENT environment variable and add it to the skill's declared requirements (or change the scripts to accept an explicit parameter) — the skill currently uses $AGENT but does not declare it. 2) Verify you have the pilot-protocol companion skill available (SKILL.md says it's required) and that the registry metadata is updated to reflect that dependency. 3) Inspect your local pilotctl configuration and daemon credentials — pilotctl calls will access your task/agent data and may use stored tokens; ensure those credentials are appropriate for this skill's access. 4) Test the scripts in a safe environment — some snippets assume a task lifecycle and may loop/poll indefinitely or divide by zero if no tasks exist. 5) Consider license implications (AGPL-3.0) for your usage. If these points are addressed (declared env vars and clear dependency), the skill appears coherent for its purpose; until then, treat it cautiously.

Type: OpenClaw Skill Name: pilot-sla Version: 1.0.0 The pilot-sla skill provides standard logic for monitoring service-level agreements (SLAs) by calculating task response times and success rates. It utilizes the pilotctl utility alongside common shell tools like jq and bc to track task status and performance metrics. The instructions in SKILL.md are strictly aligned with the stated purpose of performance enforcement and contain no indicators of malicious intent, data exfiltration, or prompt injection.