esond

Create or audit a repo's README.md, CLAUDE.md, and REVIEW.md docs.

Remove unused PackageVersion entries from `Directory.Packages.props` files in a .NET repo using Central Package Management (CPM). Scans every `.csproj`, `.props`, and `.targets` file for PackageReference includes, computes which PackageVersion IDs aren't referenced anywhere, removes the unused entries with line-targeted edits that preserve formatting and comments, then verifies with `dotnet restore`. Use this skill whenever the user wants to clean up, prune, or remove unused entries from `Directory.Packages.props`, or says things like "clean up CPM", "remove unused packages from central package management", "the props file has stale entries", "prune Directory.Packages.props", or "dead packages in the central versions file" — even if they don't literally say "CPM". Trigger proactively when the user mentions `Directory.Packages.props` alongside cleanup, removal, dead, stale, or unused. Refuses to run on repos without a `Directory.Packages.props` (CPM not in use).

Make any message look AI-generated — the mirror image of the humanizer skill. Rewrites text to pile on the tells of LLM slop (em dashes, rule of three, "it's not just X, it's Y," words like delve / tapestry / testament / underscore, inflated significance, sycophantic openers, emoji bold headers) while keeping the original meaning fully intact. Has an intensity dial — subtle (the default, plausibly deniable), heavy (unmistakably AI), and unhinged (maximum slop). Use this skill whenever the user wants to make writing look AI-written, robotic, botted, or ChatGPT-flavored — phrasings like "dehumanize this," "make this look AI-generated," "make it sound like a bot wrote it," "AI-ify this," "add some slop," "give it the ChatGPT treatment," "dial up the AI," or "make this more obviously AI" — even if they never say the word "dehumanize." Mostly used for trolling and parody. If the text already looks AI-ish, dial it up rather than tone it down.

Review and consolidate Claude Code permission entries in settings.json files. Use this skill whenever the user wants to clean up, consolidate, review, audit, or prune their Claude Code permissions, or says things like "my allow list is huge", "too many permission entries", "the permissions file is a mess", "consolidate my permissions", or "look at settings.local.json". Also trigger proactively when the user mentions "permissions", "settings.local.json", "settings.json", "allow list", or complains about repeatedly approving similar commands — even if they don't literally ask to "consolidate".

Experimental HTML variant of `plan-repl`. Same research → plan → annotate → implement workflow, but each phase produces an interactive HTML page instead of a markdown file — with an in-browser annotation widget that exports notes back to a JSON file Claude reads on the next turn. Use this skill whenever the user explicitly asks for the HTML version of plan-repl, wants to prototype or evaluate the HTML output format, says things like "let's try the HTML plan thing", "use plan-repl-html", "render the plan as HTML", "I want the experimental HTML workflow", "do the plan thing but in HTML", "annotate this in the browser instead of in markdown", or references Thariq's "HTML is the new markdown" post in the context of planning. Do NOT auto-suggest this for general planning tasks — `plan-repl` is the default; `plan-repl-html` is an opt-in experiment. Trigger only when the user has explicitly asked for the HTML variant.

Resume an in-progress `plan-repl` task from its persisted files. Reads `tasks/{task-name}/research.md`, `plan.md`, and `todo.md`, cross-references them against the current branch's git state to figure out where the previous session actually left off, then continues from that phase. Use this skill whenever the user wants to pick a `plan-repl` task back up — even if they phrase it as "resume the X task", "continue where we left off", "I cleared my context, let's keep going", "pick up the webhook-retries task", "what were we doing on X", or just "let's continue X" with a name that matches a directory under `tasks/`. The two main scenarios: (1) the user cleared their context mid-workflow because research and planning bloated the conversation and wants a fresh slate without losing the work on disk, and (2) the user is returning to a task in a new session after exiting earlier. Trigger proactively when the user references a task name that exists under `tasks/` and hasn't been part of the current conversation yet.