菜单
PiKVM HTTP API + Ansible collection development. This skill should be used when building Python clients, writing modules (argument_spec, check_mode), MSD uploads, ATX/HID/OCR, or REST calls.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Reviews code comments across languages before a PR opens. Use when finishing a development branch, before merging, or when a pr create was blocked pending comment review.
Create, promote, categorize, and validate skills for the kettleofskills marketplace. Use when syncing dotfiles skills into the marketplace, adding skills, assigning categories, or preparing a release.
Docker builds, Compose, and Docker-in-Docker for CI. Use when writing Dockerfiles, optimizing build times, multi-stage builds, BuildKit cache mounts, docker-compose.yml, or CI/CD pipelines (GitHub/GitLab/Forgejo Actions) — including docker-in-docker (dind) runners, rootless dind, bind-mount-vs-build-context confusion, and "mkdir <path>: permission denied" mount failures. Covers layer ordering, dependency caching, .dockerignore, multi-stage, BuildKit, Compose, and dind mount patterns.
Create or update Claude skills. Use for new skills, skill references, skill scripts, optimizing existing skills, extending Claude's capabilities.
Build Go terminal UIs (TUIs) and CLIs with charmbracelet — Bubble Tea runtime, Lip Gloss styling, Bubbles components, Glamour markdown, Harmonica animation, BubbleZone mouse. For any bubbletea TUI.
Bun SQL-first ORM for Go (uptrace/bun). Use for PostgreSQL/SQLite setup, bun.BaseModel struct tags, query builder CRUD, relations, migrations, fixtures, hooks, transactions, and soft deletes.
基于 SOC 职业分类
| name | pikvm |
| description | PiKVM HTTP API + Ansible collection development. This skill should be used when building Python clients, writing modules (argument_spec, check_mode), MSD uploads, ATX/HID/OCR, or REST calls. |
Python library and Ansible module for PiKVM KVM-over-IP device automation.
Base URL: https://<pikvm-ip>. All responses return {"ok": true/false, "result": {...}} unless noted. Self-signed TLS certificates are default.
| Subsystem | Reference | Key Endpoints |
|---|---|---|
| Authentication | api-auth.md | Login, session tokens, 2FA/TOTP, X-header auth |
| System | api-system.md | Device info, logs, Prometheus metrics |
| MSD (Mass Storage) | api-msd.md | ISO upload, virtual drive connect/disconnect, media type |
| ATX Power | api-atx.md | Power on/off, reset, button clicks |
| HID Input | api-hid.md | Keyboard/mouse events, text typing, shortcuts |
| GPIO | api-gpio.md | Switch/pulse GPIO channels |
| Streamer | api-streamer.md | Video state, snapshots, OCR |
| Switch | api-switch.md | Multi-port KVM switching, EDID, per-port ATX |
| Redfish | api-redfish.md | DMTF standard power control |
| WebSocket | api-websocket.md | Real-time state events, key/mouse input |
See python-library.md for implementation patterns.
Core design:
PiKVMClient class wrapping httpx.AsyncClient (async) with sync convenience wrappersclient.msd.upload(), client.atx.power(), client.hid.type_text()logging module with operation contextSee ansible-collection-setup.md for:
ansible-creator scaffolding (ansible-creator init collection, add plugin module)ansible-test (sanity, unit, integration)ansible-lint configuration and profile levelsSee ansible-module-best-practices.md for:
argument_spec keys and AnsibleModule constructor paramsextends_documentation_fragment)open_url from ansible.module_utils.urls (NOT httpx/requests)fail_json and optional dependency patternsSee ansible-module.md for PiKVM module implementations.
Core modules:
pikvm_msd — Upload ISO, set media type (cdrom/flash), connect/disconnect drivepikvm_atx — Power on/off/reset with state detectionpikvm_hid — Type text, send shortcuts, configure HID paramspikvm_info — Gather device facts (system, hardware, health)Key distinction: The standalone Python library uses httpx for async support. Ansible module_utils MUST use open_url from ansible.module_utils.urls for portability (no external dependencies).
The primary workflow for ISO management:
GET /api/msd to verify enabled, online, not busyPOST /api/msd/write?image=name.iso with binary body (or POST /api/msd/write_remote for URL-based download)POST /api/msd/set_params?image=name.iso&cdrom=1POST /api/msd/set_connected?connected=1GET /api/msd or subscribe via WebSocket for msd_state eventsTrack upload progress via WebSocket msd_state events (storage.uploading field). For large ISOs, use write_remote with URL to offload download to PiKVM.
All API errors follow: {"ok": false, "result": {"error": "ErrorType", "error_msg": "details"}}.
Common errors: 401 Unauthorized (no auth), 403 Forbidden (bad credentials), 409 Conflict (device busy), 503 Unavailable.