Polyhydra Skills / GitHub & Delivery
Use when the user wants to see GitHub issue progress rendered as a retro text-adventure screen instead of a status report — single-issue quest screens, a multi-issue "dungeon map" overview to answer "where do I need to focus," or optional local-LLM flavor narration layered over real, deterministic issue data.
Drop this in — save the block below as ~/.claude/skills/quest-log/SKILL.md, or run:
mkdir -p ~/.claude/skills/quest-log cat > ~/.claude/skills/quest-log/SKILL.md <<'EOF' # (paste the full source block below into this file) EOF
# Quest Log
Renders a GitHub issue's markdown checklist (`- [ ]` / `- [x]`) as a boxed,
retro text-adventure screen via `tools/quest_log.py`. Score, percent done,
and blocked-state are always computed 100% deterministically from the real
checklist — any flavor narration is a clearly separate, optional, best-effort
layer that never changes the real numbers.
## When to use
- The user wants a fun/gamified way to see how far along an issue is.
- The user asks "where do I need to focus" across several open issues.
- The user wants a terminal-friendly progress view instead of a wall of text.
## Single-issue quest screen
```bash
python3 tools/quest_log.py <issue-number> --repo <owner/repo>
```
Options:
- `--shape {zork,roguelike,mud}` — which renderer to use (default `zork`). All
three read the exact same underlying data; only the presentation differs.
- `--flavor` — ghostwrite 2-3 sentences of narration via the local Ollama
fanout (`skills/ollama-code-agents`). Best-effort: silently falls back to
no narration (with a stderr note) if no local Ollama agent is reachable.
Never touches the real score/percent/blocked values.
- `--color {auto,always,never}` — ANSI color (default `auto`, detects a TTY).
- `--points-per-item N` — XP awarded per checklist item (default 10).
## Multi-issue dungeon map
```bash
python3 tools/quest_log.py --map --repo <owner/repo> --limit 20
```
Scans open issues and renders them together, sorted blocked-first then
least-progressed-first — a disclosed heuristic over the two real signals a
checklist gives us (blocked, percent), not a claim of true priority.
Known limitation: an issue with **no checklist at all** shows `N/A`, not 0%
or 100% — do not read `N/A` rows as "nothing to do" or "fully done." They
just have no checklist to measure.
## Safety
- Read-only against GitHub (`gh issue view` / `gh issue list`) and the local
Ollama fanout script. Never writes to the issue, never applies changes.
- `--flavor` sends the issue title, percent, and a preview of remaining item
text to a local Ollama endpoint (not a cloud API) — do not use `--flavor`
on issues containing secrets or sensitive content in their title/checklist.