Practicing README Driven Development • now: intermission • prev: VP product @cloudflare • earlier still: maintained the @gorilla web toolkit.
Is this your GitHub account?
Sign in as @elithrar with GitHub.
Your indexed skills will appear on your curator profile.
skilld will also check your public repositories for other SKILL.md files.
SKILL.md
dotfiles for my macOS & Linux environments ⌨️
npx skilld add elithrar/dotfiles
/anti-slop
Edit formulaic or AI-sounding prose while preserving the author's voice. Use for an anti-slop pass, editorial review, or requests to make writing sound more human; ordinary drafting does not require this skill.
/code-reviewer
Review a specified code change for actionable defects. Use for uncommitted changes, base-branch diffs, commits, PRs or MRs; review alone is read-only, and requested fixes follow the review. Not a repository-wide security or complexity audit.
/create-readme
Write or improve concise, reader-focused README.md files for open source projects. Use for new READMEs, README rewrites, installation and usage examples, or README reviews. Do not use for API references, tutorials, changelogs, contributing guides, or unrelated prose editing.
/cut-ready
Prepare or review CAD and vector artwork for physical fabrication, cutting, printing, or machining. Use for production files, scale, contours, fit, bends, and vendor handoff; not digital-only graphics, 3D-print meshes, or CAD explanation without a production artifact.
/logging-sucks
Design or review structured application logging, canonical request events, correlation, redaction, and sampling. Use when changing logging instrumentation or auditing log quality, not for every debugging task.
/motronic
Diagnose Porsche Carrera 3.2 Bosch Motronic faults and interpret DME ROMs or calibration changes. Use for 1984-1989 3.2 DME systems, including swaps into earlier cars; not generic 911, CIS, or other ECU advice.
/neo-industrial-design
Design or restyle web interfaces in the user's neo-industrial or editorial-brutalist style. Use when that visual direction is requested; not for generic dashboards, dark themes, or copywriting.
/prompt-engineer
Audit and revise system prompts, developer instructions, tool descriptions, and reusable LLM prompt templates. Use for behavioral failures such as over-searching, format drift, weak tool use, instruction conflicts, or unsupported claims. Use for prompt behavior, not ordinary prose editing or skill packaging alone.
/summarize-work
Summarize OpenCode session history into work recaps, commit messages, or PR descriptions. Use when a summary needs past sessions or cross-project history; ordinary commits and summaries fully supported by the current conversation do not need this skill.
/web-perf
Diagnose page-load and interaction performance using browser traces, network evidence, and source code. Use for site-speed, Lighthouse, Core Web Vitals, or layout-shift investigations; a general accessibility audit is separate.
/wow-addon-development
Build, improve, debug, port, or review World of Warcraft Midnight/Retail and official Forever add-ons. Use for addon Lua/XML, packaging, settings, profiles, performance, and UI layout. Not for gameplay advice, addon recommendations, or WoW-themed websites.
Curated skills from @elithrar. Checked GitHub just now