Menu
Create, search, comment on, and manage issues in the canonical nixosconfig Forgejo tracker via its REST API.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | forgejo |
| description | Create, search, comment on, and manage issues in the canonical nixosconfig Forgejo tracker via its REST API. |
| version | 1.0.0 |
| metadata | {"hermes":{"tags":["homelab","forgejo","issues","nixosconfig"]}} |
Use this skill whenever the user asks to create or manage an issue for the
canonical abl030/nixosconfig Forgejo repository. GitHub is a read-only code
mirror; its issue tracker is not authoritative.
https://git.ablz.au/api/v1abl030/nixosconfig/run/secrets/forgejo/hermes-tokensecrets/hosts/proxmox-vm/forgejo-hermes-token.yaml with sops directly
into the same short-lived shell variable. Do not write plaintext to disk.write:issue only; Forgejo includes issue reads. It cannot push
source code.Never print, interpolate into a URL, or persist the token. Read it into a
short-lived shell variable and send it only in Forgejo's token-authentication
header. Use mode-0600 mktemp files for request/response bodies and remove them
with a trap.
GET /repos/abl030/nixosconfig/issues?state=all&limit=100 before creating a
new one. Compare both title and body for the named subsystem and intent.POST /repos/abl030/nixosconfig/issues and JSON fields title and body.html_url.GET /repos/abl030/nixosconfig/issues/{number}; comment
with POST .../comments; update title/body/state with PATCH .../{number}.
This Forgejo instance returns HTTP 201 for a successful issue PATCH (not only
200); accept either success code, parse the response, then GET the issue back
and verify the stored fields.message. Scope errors are a
token configuration problem, not evidence that issue operations require the
web UI.Issue bodies should capture motivation, current state, desired invariants, security boundaries, acceptance criteria, migration/rollback needs, and verification. Do not prescribe an architecture that has not been inspected; link to existing NixOS patterns when known.
Manage pfSense firewall - rules, NAT, VPN, DHCP, DNS, and system configuration
Spin up and manage Apollo/Sunshine gaming Windows VMs on the prom hypervisor — clones of the GTX-1080-passthrough golden template, one per game, streamed via Moonlight/Artemis. Use when the user wants a new gaming VM, another gaming VM, a VM "for <game>", or to start/switch/stop/list/destroy their gaming VMs. Single GPU = one runs at a time. Trigger phrases include "new gaming vm", "spin up a gaming vm", "gaming vm for <game>", "make me a windows gaming vm", "another gaming machine", "start the <game> vm", "switch to <game>", "list gaming vms", "stop the gaming vm", "destroy the <game> vm".
Add an MCP server to the project and sync to all AI tools
Detect configuration drift using hash-based verification.
Debug a NixOS service that is down, unhealthy, or misbehaving. Identifies which host runs the service, connects via SSH if remote, and investigates using journalctl. Trigger phrases include "debug X", "X is down", "why is X broken", "check X service", "X not working", "investigate X".
Use this skill when enabling, moving, or migrating a NixOS service between hosts (doc1/proxmox-vm, doc2, igpu, framework, etc.), or when verifying that a service is actually working after deployment. Trigger phrases include "move X to host Y", "enable X on Y", "deploy X", "is X working", "verify X is up", "X isn't accessible", "can't reach X".