khasky/awesome-agent-skills
Skills for AI coding agents: code review, test writing, design docs, debugging, security and dependency audits, git history surgery, refactoring, copywriting, and cleaning up AI-written code and text. Every skill is a plain SKILL.md folder under the open Agent Skills standard, stack-agnostic, and ends with the check that proves its claim.
Read-only WCAG audit of UI and markup with a concrete fix per finding. Use when asked to check accessibility, a11y, keyboard or screen-reader support, or contrast.
Mines a codebase's real commands, conventions and boundaries into an agent-agnostic AGENTS.md, nested per package in monorepos, every rule backed by counted evidence. Use when asked to write, generate or refresh AGENTS.md or agent instructions for a repo.
Designs or reviews an HTTP API's shape before code: resources, versioning, pagination, idempotency, filtering. Use when asked to design an API or an endpoint.
Read-only audit of a whole codebase's design: module boundaries, dependency direction, docs-vs-code drift, extensibility, with a verdict. Use when asked to audit the architecture.
Fixes a bug by building a runnable reproduction and finding the root cause before any fix. Use for errors, crashes, failing tests or builds, flaky behavior, or repeated failed fixes.
Checks public claims (site, README, store listing, privacy policy, structured data) against the code and config that decide them, then fixes drift. Use when asked whether the site still matches the product.
Behavior-preserving cleanup of AI-like code noise: narrating comments, dead code, vague names, over-abstraction; applies a slop-audit report. Use when asked to clean up code or comments, or to de-slop.
Generates a full technical documentation set for a codebase, from a local folder or a clone of any git host URL: architecture, per-module and API reference, data model, flows, config, operations, how-to guides, written bottom-up along the dependency graph, cited. Use when asked to document a repo.
Explains how a codebase works, from a local folder or a clone of any git host URL, as one illustrated page: purpose, stack, structure, entry points, main flow, patterns, where to start reading, every claim cited. Use when asked to explain a repo or get up to speed on one.
Reviews a diff, patch or pull request for correctness, security and team standards, with severity-ranked findings. Use when asked to review a change or PR, or before merging.
Responds to code review feedback: verifies each point before changing code, clarifies unclear items, pushes back with reasons when a point is wrong. Use when asked to address reviewer or bot comments.
Reviews a code change with a jury: independent read-only subagents on different models review blind, a separate judge cross-examines them and returns one verdict. Use when asked for a second opinion, a multi-model or panel review, or a high-stakes review.
Coding conventions that fill the gaps a project's own rules leave: naming, structure, immutability, types, error handling, layering. Use when starting a module, setting lint rules, refactoring to conventions, or onboarding.
Plans a scheduled batch of platform-fit posts about a product from repos, sites or files, every claim traced to evidence; also writes one post for named platforms. Use when asked for a content plan or product posts.
Adapts one finished image into a horizontal 16:9 and a vertical 9:16 version for social platforms without redrawing the artwork. Use when asked to resize a picture for posts.
Publishes prepared posts to the user's own accounts through their live browser, on schedule, with login checks, a no-duplicates ledger and a confirmation gate before anything goes public. Use when asked to publish posts.
Turns one source (article, guide, notes) into three posts for all platforms: a long read, a regular and a short post, in the language the user picks. Use when asked to adapt a text for social posts.
Builds a reusable profile of the user's own writing voice from their posts, files, samples or an interview, for other skills to read. Use when asked to learn the user's voice.
Writes short product copy: headlines, titles, meta and store descriptions, buttons, empty states, error messages, subject lines, CTAs. Use when asked for such copy.
Read-only audit of a database layer: schema anti-patterns, query and index fit, integrity, concurrency, migrations, tenancy, with a verdict. Use when asked to review a schema, migrations or data model.
Read-only supply-chain audit of packages and agent extensions: lockfiles, typosquats, dependency confusion, install scripts, licenses, CVEs. Use when asked if a package, manifest change or bot bump is safe.
Plans and executes dependency upgrades: batches by risk, changelog-driven majors, CVE overrides, one revertable commit per batch. Use when asked to upgrade packages, merge bot update PRs, or act on an audit report.
Writes a design doc or ADR: requirements and scale first, real alternatives with trade-offs, a grounded recommendation, non-goals, migration path; also runs a pre-mortem on a plan. Use when choosing an approach.
Line-edits Markdown documents into clear, specific, publication-ready prose: cuts bloat and template structure, fixes vague wording and number style. Use when asked to edit, tighten or polish a document.
Applies consistent error handling: typed errors, operational vs programmer errors, API error envelopes, HTTP status mapping, user-facing messages. Use when adding or refactoring error handling or designing an error contract.
Rewrites the author and committer on commits with a wrong identity, then force-pushes after access checks, a mirror backup and a confirmation gate. Use when a commit has the wrong name or email.
Plans a codebase as a bisectable commit series: a module map, then commits that each build and test alone, verified in a scratch clone, as one plan file. Use when asked to split a project into commits.
Erases a repository's history and rebuilds it as a curated commit series over the same tree, with a backup, confirmation gates and a tree-hash proof. Use when asked to rewrite history as readable commits.
Erases a repository's entire history into one fresh commit and force-pushes, after access checks, a mirror backup, a secret scan and a confirmation gate. Use when asked to wipe history.
Read-only recovery of every commit a repository ever held, force-pushed history included, from refs, PR refs, backups and the host's activity log. Use when asked what a repo held before a rewrite.
Proofreads prose and reports grammar, logic and flow issues as suggestions without rewriting the text. Use when asked to proofread or copy-edit an article, email, doc or post while keeping the author's wording.
Removes signs of AI writing from English text: cliches, filler, jargon, sycophancy, em-dash habits, fake sources, chatbot markers like ':contentReference'. Use when text reads like a chatbot.
Read-only audit of a landing page's conversion structure: primary CTA, form friction, message match, trust elements, above-the-fold value. Use when a page is not converting.
Audits a public client (extension, app, SPA, CLI, SDK) for what it reveals about the private backend (limits, anti-abuse, backdoors, infra) and client hardening. Use before open-sourcing or a store submission.
Applies structured logging: levels, PII redaction, request logging, wide events (canonical log lines). Use when adding or reviewing logs, choosing levels, or after logs failed or leaked data in an incident.
Runs a penetration test (web app, API, network, cloud, mobile) per PTES and OWASP: scoping, recon, testing, proof, CWE/CVSS findings, retest; every active probe needs written authorization. Use for a pentest or red team engagement.
Read-only performance and reliability audit: event loop, backpressure, memory and CPU, timeouts, retries, queues, Core Web Vitals, bundles, with a verdict. Use when something is slow, memory climbs or latency spikes.
Read-only sweep for regressions against a recorded baseline: typecheck, lint, test suites, wire contracts, generated-file drift, downstream builds, deploy drift. Use to verify everything before or after a deploy.
Root-cause analysis for incidents, recurring failures and process problems with no failing test: 5 Whys, fishbone, PDCA, A3. Use for a postmortem or why something keeps happening.
Read-only security audit of code: injection, secrets, auth and authorization, dependency CVEs, CI/CD exposure, crypto misuse, with CWE-mapped fixes. Use for a security review, before a release, or after adding auth or payments.
Read-only SEO audit of a site or web codebase: crawling, indexing, on-page, structured data, rendering, hreflang, links, visibility to LLMs and agents, baseline diffs. Use when asked to audit SEO, titles or meta.
Removes installed agent skills from every AI agent on the machine (Claude Code, Codex, Gemini CLI, Cursor...) behind a keep list, an archive and a confirmation gate. Use when asked to uninstall installed skills.
Read-only audit of a repository for AI-slop markers in code, comments, tests, docs and CI, each verified against the code and ranked for awesome-code-cleanup. Use when asked to find AI slop or machine-written code.
Learns a website's writing style by crawling it in a live browser, writes a reusable style guide, then rewrites documents in that voice. Use when asked to learn a site's style or write in its voice.
Designs and writes tests that catch real regressions: unit, integration or E2E placement, fixtures, behavior-first assertions, characterization and property tests. Use when asked to write tests, add coverage or a regression test.
Translates Russian text of any genre into natural English, keeping structure, formatting, links, identifiers and the author's voice; can mirror a folder. Use when asked to translate Russian into English.