Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions., Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
Privacy notes
Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots., Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
Current risk score 0/100. Use staged verification before broader rollout.
Risk 0
Pre-adoption checks
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Done
Confirm metadata review state
Listing has review metadata.
Done
Verify install payload
Install/config payload exists and can be inspected.
Done
Security checks
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Done
Review privacy notesRequired
Privacy notes are present.
Done
Verify package integrity metadata
Package verification/checksum metadata is available.
Done
Rollout
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Pending
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Pending
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Pending
Evidence readiness
Evidence readiness matrix · balanced
Required evidence gates are covered (6/6 signals complete).
Risk 0
Source provenance
Present
Source repository/provenance is listed.
Required in this preset
Metadata review
Present
Review metadata is present.
Required in this preset
Safety notes
Present
Safety notes are present.
Required in this preset
Privacy notes
Present
Privacy notes are present.
Optional in this preset
Package integrity
Present
Package integrity metadata is present.
Optional in this preset
Install payload
Present
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
Decision timeline · balanced
6/6 steps complete with no blocking gaps for this preset.
Risk 0
triage
Confirm source provenanceRequired
Source/provenance metadata is available.
Done
triage
Check metadata review statusRequired
Review metadata is available.
Done
verify
Review safety notesRequired
Safety notes are available.
Done
verify
Review privacy notes
Privacy notes are available.
Done
verify
Validate package integrity metadata
Package integrity metadata is available.
Done
rollout
Verify install payload and commandsRequired
Install payload is available.
Done
No required blockers for this timeline preset.
Prerequisite readiness
Prerequisite readiness
3 prerequisites to line up before setup. Have accounts and credentials ready first.
0/3 ready
Account & credentials1Configuration1General1
Safety & privacy surface
Safety & privacy surface
2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens.
3 areas
SafetyExecution & processesCan design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
SafetyCredentials & tokensKeep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
PrivacyData retentionInputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
PrivacyCredentials & tokensRedact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
Safety notes
Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
Privacy notes
Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursor
Adapter
.cursor/rules/<skill-name>.mdc
cli
Manual
AGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Use the Unraid API automation operator skill for this operation workflow."
# Required output
1) Automation scope and guardrails
2) API operation plan
3) Idempotency and rollback handling
4) Alerting/reporting output
About this resource
Overview
This skill helps AI agents create safe and repeatable Unraid automations. It focuses on real operational tasks such as health checks, backup verification, container lifecycle actions, and maintenance windows.
Compatibility
Native
Claude Code / Claude: native skill usage via SKILL.md.
Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.
Manual Adaptation
Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.
Prerequisites
Operational policy for when automation may modify host state
Backup and restore baseline
Alert channel for actionable failures
What This Skill Delivers
Task-level automation design with execution boundaries
API request sequencing with safety checks
Retry/backoff and rollback considerations
Human-readable run summary and escalation guidance
How to Use This Skill
Define allowed operations and protected resources.
Map API calls to deterministic execution steps.
Add pre-checks and post-checks for each action.
Add failure handling and rollback branches.
Emit concise run report for ops visibility.
Troubleshooting
Issue: Automation retries create duplicate side effects Fix: Add idempotency keys and state checks before write operations.
Issue: API calls fail intermittently Fix: Add bounded retries with backoff and explicit timeout policy.
Issue: Hard to trust autonomous changes Fix: Add human approval for destructive or high-risk operations.
Knowledge Freshness
Treat tooling details as time-sensitive. Re-validate APIs, limits, pricing, auth models, and deployment flags immediately before implementation. If docs conflict with prior memory, follow current official docs and release notes.
Show that Unraid API Automation Operator Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/unraid-api-automation-operator)
How it compares
Unraid API Automation Operator Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
2 trust signals differ across this comparison (Package trust, Source provenance).
✓Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
✓Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
✓Treat generated templates as review drafts; validate XML fields, image names, support links, ports, volumes, and first-boot behavior before submission.
Keep defaults beginner-safe and document resource, network, socket, and permission tradeoffs clearly.
Do not submit templates for images or support paths you cannot maintain.
✓Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions.
Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution.
Privacy notes
✓Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
✓Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.
✓Docker template XML and appdata paths can reveal environment names, paths, credentials, or application-specific secrets.
Redact private registry credentials, passwords, tokens, tunnel URLs, and user-specific paths before using real templates as examples.
✓Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots.
Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts.