Track a body of claims and questions through a human-gated lifecycle — DRAFT → UNVERIFIED → VERIFIED (or CANCELLED), open → answered — where a claim is a validatable statement about code, libraries, or data, and "verified" means a HUMAN judged it, never that…
avidrucker/claude-config
SkillsMP has collected 14 skills from avidrucker/claude-config. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 14
- GitHub stars
- 0
- GitHub forks
- 0
Skills in this repository
Showing 14 of 14 collected skills.
Audit a software project for WASTE using Sedano, Ralph & Péraire's empirical nine-waste taxonomy (ICSE 2017) — building the wrong feature, mismanaging the backlog, rework, unnecessarily complex solutions, extraneous cognitive load, psychological distress,…
Triage all open issues for the current project and produce a prioritized work plan. Config-driven (.claude/orchestrate.json) — in fleet mode it emits copy-pasteable plain-paragraph assignments per agent (APPLE, BANANA, CHERRY, DRAGONFRUIT, ELDERBERRY, FIG,…
Protocol for recording agent errors into the project's errors store — when to log, what fields to populate, the resolved command, and when to skip. Use whenever a tool call fails, a hook blocks, a claim fails, or any non-trivial error occurs during puzzle…
Pre-close checklist that catches findings that should be filed as tickets before the close commit. Surface it at every close on a substantive puzzle, but run it only with explicit user go-ahead — it is a token-heavy pass, not an auto-run step.
Track wall-clock time per puzzle/ticket with dual H/C estimates and a logged row so forecasts can be calibrated over time. Use when picking up or closing a puzzle, starting work on a ticket, or logging velocity. Pairs with the yegor-* family.
Guide an agent through writing, filing, and closing a TIL (Today I Learned) entry in docs/learnings/. Use when the user says "write a TIL", "write up what you learned", "add to learnings", or requests a session retrospective.
Rank the open issues/puzzles by ICE score (Impact×Confidence×Ease) then severity, and render them with severity-color emoji, splitting out blocked and iceboxed work. Use ONLY when the user explicitly asks "what's next", "what should I work on", "triage the…
Download native-speaker pronunciation audio from Forvo (and optionally top Wikipedia images) for personal study. Use when the user asks for "forvo" audio, "pronunciation audio", "native audio for my cards", a Wikipedia image for vocab cards, to grab a…
Review a GitHub issue for quality and clarity before work begins. Use this skill whenever a user asks to review, improve, critique, score, or quality-check a GitHub issue or ticket. Also triggers on: "is this issue ready?", "review my ticket", "improve this…
Run Avi's code-quality-analysis tool against a project. Reads or authors an EDN config of checks (deterministic shell commands, AI-assisted prompts, human sign-offs), runs assess.bb, and prints a per-concern scorecard. Use when the user says "run code…
Re-explain Claude's most recent substantive answer in plain, jargon-free English — same content, accessible words. Use when the user invokes /eli5, or says "explain that simply", "ELI5 that", "in plain English", "re-explain your last answer", "I didn't follow…
Walk the user through a human-required decision ticket — pull issue context (including pre-existing options analyses in comments), surface each discrete decision point with options, a recommendation, and evidence, receive user choices, then translate choices…
Relocate a handoff document into the project's orphan `handoffs` branch so it persists in version control rather than living only in /tmp. Use after `/handoff` has written the doc, when you want a durable archive that survives reboot and is shareable via the…