velkalisted
Install: claude install-skill sgtlaugh/skills
# /velka - observe the cycle, name the recurring sin
Velka, Goddess of Sin: she *observes and records transgressions* across the whole cycle. Sibling to `darkmoon` (which judges **one** answer) - velka watches **many sessions** and names the habit you keep repeating. The "sin" here is a workflow inefficiency: a file you thrash, a tool you keep skipping, a 3-step dance you redo by hand every time.
**Why it exists.** Inside a single session you already lived it - telling you "you edited `auth.ts` 12 times today" is no news. What you *cannot* see is the pattern **across** sessions: that you thrash frontend files every time, that you've run `occam` in 8 of 441 sessions, that the same grep→read→edit dance recurs and should be a skill. velka aggregates the mechanical footprints your transcripts leave and surfaces the cross-session habit.
**Honest ceiling - read this.**
- **velka sees ONLY what ran through Claude Code's tools.** Tests in your IDE/terminal/CI, edits in vim, commits from another shell - **invisible.** A "you never test" finding means "no test command ran *through Claude*," NOT "you don't test." This caveat is **mandatory** on any testing/coverage finding (see Guard rails) - omitting it is a false accusation.
- **Mechanical footprints only.** velka proves *what happened* (counts, files, tools). It does **not** prove *what you should have done* - "you should've used darkmoon" is an inference the transcript can't ground. Those are **low-confidence flags for your revie