メニュー
Use for Taskfile and operations workflow work under Taskfile.yml and operations/**, including local validation, wrappers, diagnostics, and CI entrypoints.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Hovirix/homelab --skill taskfileコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Diagnose HX Lab data incidents, determine the last known-good time, and advise the smallest safe recovery using local Proxmox snapshots, TrueNAS disaster recovery, or PostgreSQL-aware recovery.
Use for Ansible work under infrastructure/ansible/**, especially Proxmox host and datacenter configuration.
Use for Docker and Docker Swarm work under platform/** and operations workflows that render, validate, or manage containers, stacks, services, networks, volumes, secrets, configs, ingress, and health checks.
SOC 職業分類に基づく
SKILL.md を表示中
| name | taskfile |
| description | Use for Taskfile and operations workflow work under Taskfile.yml and operations/**, including local validation, wrappers, diagnostics, and CI entrypoints. |
Use this for changes to Taskfile.yml, operations/**, workflow wrappers, local validation, diagnostics, and CI orchestration.
Read the relevant included taskfile, script, workflow, and root Taskfile.yml before changing behavior. Keep tasks thin and predictable. Move complex shell logic into scripts only when Taskfile syntax becomes unclear. Always follow the Task Style guide.
Use upstream docs when Taskfile behavior, variable expansion, includes, loops, status checks, or command execution semantics matter:
Taskfile is the operational interface. It should wrap desired-state tools safely; it should not hide destructive behavior or imply runtime success from local checks.
Treat remote execution, apply/destroy/import/state movement, Swarm mutation, service restarts, secret decryption, and backup/restore execution as explicit-authorization workflows.
Validation should use current task entrypoints when they exist. Inspect task --list when task availability is unclear. Report exactly what ran and what was skipped.
Watch for failure modes such as masked shell-loop failures, unsafe variable interpolation, missing fail-fast behavior, remote drift, and tasks whose names make mutating operations look read-only.