Expert Unraid Community Apps template capability pack for source-backed XML metadata, safer defaults, and CA submission readiness.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
3 prerequisites to line up before setup.
Safety & privacy surface
3 safety and 2 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes.
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .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 |
# Trigger
"Apply the Unraid CA template authoring capability pack."
# Required output
1) Template XML with validated metadata fields
2) Beginner-safe default config and caveats
3) Support and documentation linkage
4) CA submission checklistThis capability pack is pinned to sources re-verified on 2026-06-19.
Verified on 2026-06-19:
<Repository> tag while plugin
entries need a <PluginURL> tag.ca_profile.xml,
raw TemplateURL pointers, license expectations, and the same Docker/plugin
minimum fields.This skill helps agents produce community-ready Unraid templates that are practical for beginners and maintainable for operators.
SKILL.md.SKILL.md content as reusable workflow instructions..gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported..cursor/rules/*.mdc adapter for project rules.Issue: Template rejected for weak metadata
Fix: complete Project, Support, TemplateURL, Icon, and Overview fields.
Issue: New users fail first boot
Fix: tighten defaults and add explicit setup prerequisites.
Issue: Support load spikes after release
Fix: publish FAQ + known limitations before submission.
Show that Unraid CA Template Authoring Capability Pack 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-ca-template-authoring-capability-pack)Unraid CA Template Authoring Capability Pack Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
| Field | Expert Unraid Community Apps template capability pack for source-backed XML metadata, safer defaults, and CA submission readiness. Open dossier | Deep, version-pinned Unraid API capability skill covering auth, schema patterns, safe mutations, and operational automation design. Open dossier | Expert Raycast extension maintainer capability pack for reviewing Raycast command structure, manifest metadata, API usage, store submission checks, and privacy-safe release notes aligned to official Raycast developer docs. Open dossier | Expert Claude Agent SDK custom tool authoring capability pack for designing typed in-process tools with createSdkMcpServer, allowedTools scoping, isError handling, and privacy-safe rollout checklists aligned to official custom-tools documentation. Open dossier |
|---|---|---|---|---|
| Next stepsDiffers | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified2026-04-11 | Package verified2026-04-10 | Package not verified | Package not verified |
| Source provenanceDiffers | Source-backed | No submission link | Submission linkedSource submission | Submission linkedSource submission |
| SubmitterDiffers | — | — | kiannidev | kiannidev |
| Install risk | Review first | Low risk | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | ||
| Category | skills | skills | skills | skills |
| Source | First-party | First-party | Source-backed | Source-backed |
| Author | JSONbored | JSONbored | kiannidev | kiannidev |
| Added | 2026-04-11 | 2026-04-10 | 2026-06-15 | 2026-06-16 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓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. | ✓This skill reviews extension behavior; it must not publish store updates or run untrusted extension code without maintainer approval. Extensions can invoke network APIs and local filesystem operations; verify least-privilege scopes before release. Do not embed long-lived API tokens in source; prefer Raycast preferences and secure storage patterns. Third-party dependencies in extensions inherit supply-chain risk; review updates before shipping. | ✓Tool descriptions and annotations are hints, not enforcement—validate destructive inputs in handlers. Wildcard mcp__server__* allowlists expand blast radius; prefer per-tool grants in production. Throwing from a handler stops the query; return isError for recoverable failures per custom-tools docs. In-process tools run inside your application whenever Claude calls them; gate writes explicitly. |
| Privacy notes | ✓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. | ✓Raycast extensions may read clipboard, local files, or user preferences depending on API usage. Network calls can transmit query text, auth tokens, and user identifiers to third-party services. Store release notes should not include internal API keys, employee data, or customer examples. Telemetry or analytics SDKs require explicit disclosure in extension README and store metadata. | ✓Tool schemas, inputs, and results enter model context each turn—never embed secrets in descriptions. Large tool sets increase context usage; defer rarely used tools via tool search when scaling. Structured outputs and logs may reach host telemetry—redact customer identifiers at handler boundaries. External APIs invoked by handlers may log request metadata governed by vendor retention policies. |
| Prerequisites |
|
|
|
|
| Install | | | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Expert Unraid API skill with endpoint behavior, auth flows, error patterns, and production-safe automation guardrails.
Maintain Raycast extensions with source-backed checks for commands, manifest metadata, API usage, and store submission readiness.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.