khasky
UserSkills for AI coding agents: code review, debugging, security audits, refactoring, cleaning up AI-written code and text, and more.
Categories
Indexed Skills (59)
awesome-content-publisher
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.
awesome-content-image-adapter
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.
awesome-git-author-rewrite
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.
awesome-style-mimic
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.
awesome-git-history-salvage
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.
awesome-git-history-rebuild
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.
awesome-git-history-reset
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.
awesome-content-graphics
Draws the image a post ships with and picks one with the user. The agent itself composes every picture — no image service, no MCP generator, no key, nothing uploaded, and no template either. A reference goes in: text, images, a URL, or several of them, read for what the picture is actually about before anything is drawn. The user names the count: 10, 20, 50 or 100. The set opens as a folder and the user answers with a number or a name; another round rebuilds the set from different ideas rather than shaking the same one. The pick is saved into a folder of its own and that folder is opened. Use when asked to make an image or graphic for a post or campaign, 'сделай картинку для поста', or whenever awesome-content-campaign or awesome-content-repurpose reach a platform that needs media. Do not use to fit a finished picture to each platform's frame (awesome-content-image-adapter), or to write the posts themselves.
awesome-post-publisher
Publishes a prepared batch of scheduled posts to the user's own accounts through their live browser (Playwright MCP --extension bridge to Chrome): bridge preflight, post-source scan with hard-stop format validation, per-platform login checks with a wait-or-skip choice (login itself is never automated), a persistent ledger that survives restarts and prevents duplicate posts, timezone-mapped scheduling that can idle for days between posts, and strictly sequential, human-paced posting with read-back verification of every post and a confirmation gate before anything goes public. Use when asked to 'publish the campaign', 'post these files to my accounts', 'post on schedule', or in Russian 'опубликуй посты', 'публикуй по расписанию', 'запости в соцсети'. Do not use to write the posts — use awesome-content-campaign; not to crawl or learn a site — use awesome-style-mimic.
awesome-db-audit
Read-only audit of a database layer — schema design against a catalog of SQL anti-patterns (EAV, generic keys, imprecise types), query patterns (SELECT *, N+1, unindexable predicates), integrity and concurrency (constraints in the DB, transactions, locking), and migration/operations hygiene (forward-only, expand/contract, restore path, tenancy model) — producing evidence-backed findings and a SHIP / FIX / BLOCK verdict. Use when the user asks to 'audit the database', 'review the schema', 'check our migrations', 'is this data model sound', 'why are queries slow' (static analysis), or 'проверь схему базы'. It audits and reports; it never edits schema or data. Do not use for runtime latency profiling (use awesome-performance-audit), SQL injection and access control (use awesome-security-audit), or app-layer data-access style (use awesome-code-standards).
awesome-commit-plan
Turns a codebase into a commit plan: a navigation map of its modules and their dependency direction, then a split where every commit builds and tests on its own, so the series is bisectable end to end. Each commit is verified by replaying the ladder in a scratch clone against the repository's own gates, never asserted. Messages follow a strict ruleset that keeps machine-written prose out of the log. The only output is a plan file numbered #1 to #N, no dates, no preamble. Use when asked to 'split this project into commits', 'plan the commit history for this repo', 'how should I break this into commits', 'prepare a bisectable commit series', or in Russian 'разбей проект на коммиты', 'составь план коммитов', 'как разбить это на коммиты'. Takes a repository URL or a local path: '/awesome-commit-plan <url-or-path>'. Do not use to execute the plan against git history — that is awesome-git-history-rebuild; not to squash an existing history — awesome-git-history-reset; not to review a diff — awesome-code-review.
awesome-content-repurpose
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.
awesome-code-cleanup
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.
awesome-slop-audit
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.
awesome-code-standards
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.
awesome-content-campaign
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.
awesome-claims-audit
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.
awesome-regression-sweep
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.
awesome-dependency-audit
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.
awesome-code-review
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.
awesome-leak-audit
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.
awesome-root-cause
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.
awesome-architecture-audit
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.
awesome-humanize-en
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.
awesome-document-style
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.
awesome-landing-audit
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.
awesome-performance-audit
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.
awesome-seo-audit
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.
awesome-content-voice
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.
awesome-skills-purge
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.
awesome-security-audit
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.
awesome-pentest
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.
awesome-test-writing
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.
awesome-accessibility-audit
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.
awesome-database-audit
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.
awesome-git-commit-plan
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.
awesome-bug-fix
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.
awesome-code-review-feedback
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.
awesome-error-standards
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.
awesome-grammar-check
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.
awesome-logging-standards
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.
awesome-translate-ru-en
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.
awesome-api-design
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.
awesome-dependency-upgrade
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.
awesome-design-doc
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.
awesome-copywriting
Writes short product copy: headlines, titles, meta and store descriptions, buttons, empty states, error messages, subject lines, CTAs. Use when asked for such copy.
accessibility-audit
Audits UI and markup for accessibility (WCAG 2.1/2.2, keyboard, screen readers) and suggests concrete fixes. Use when checking a11y, before shipping a page or component, reviewing forms/modals/interactive UI, or when the user says 'accessibility', 'a11y', 'WCAG', 'screen reader', 'keyboard navigation', 'доступность'. Covers semantic HTML, focus management, labels, contrast, dynamic content, and WCAG 2.2 additions (target size, focus obscured, accessible authentication).
clean-markdown-human
Clean and line-edit Markdown documents for clear, specific, publication-ready prose. Use when asked to de-bloat, de-template, remove chatbot artifacts, fix vague wording, or make Markdown read like careful human editorial writing. Do not use to fabricate facts or bypass detectors.
code-review
Reviews diffs and PRs for correctness, security, and team standards, with confidence-scored findings in severity buckets (Critical / Suggestions / Nice to have). Use when reviewing a pull request, merge request, patch, or diff; before merging; after completing a feature; or when the user says 'review this PR', 'check this change', 'review my diff', 'сделай ревью'. Do not use for responding to review feedback you received (use receiving-code-review) or for docs-only and formatting-only changes.
code-surgeon
Repo-wide audit and cleanup of AI-like code noise — comments to a strict best-practice bar (delete redundant/narrating, condense bloated, fix stale or misleading, keep only load-bearing knowledge), plus a read-only audit mode and an opt-in refactor mode for vague names, dead/duplicated/speculative code, and over-abstraction — all strictly behavior-preserving and verified. Use whenever the user asks to clean up / prune / audit / condense comments, remove "obvious" or AI-generated comments, make code self-documenting or human-readable, de-slop vibe-coded files, apply a "comments only when necessary" or YAGNI/KISS pass, or says things like "чистка комментариев", "убери лишние комментарии", "comment hygiene", "de-comment", "почисти код". Also use when a code review found comment bloat or naming noise and the user wants it fixed repo-wide rather than file by file.
coding-standards
Universal coding standards: naming, structure, immutability, error handling, and type-safety patterns for consistent code. Use when starting a project or module, refactoring to team conventions, setting up lint/format rules, onboarding, or when the user says 'coding standards', 'naming conventions', 'code style'. Discovers and follows the project's own conventions first; these rules fill the gaps.
error-handling-patterns
Applies consistent error handling, logging, and user-facing messages: typed errors, operational-vs-programmer classification, API error envelopes, HTTP status mapping. Use when adding or refactoring error handling, designing an API error contract, reviewing failure paths, or when the user says 'error handling', 'consistent errors', 'обработка ошибок'.
humanizer-en
Use when: the user asks you to check, rewrite, humanize, or de-slop English text that shows signs of AI generation (ChatGPT, Claude, Gemini, Grok, DeepSeek, GPT-5, Qwen, Llama, any LLM). Trigger for requests like: 'humanize this', 'make it sound human / natural', 'remove the AI voice', 'this reads like a chatbot', 'AI detector for English', 'check for AI', 'de-slop', 'reduce AI-isms', remove clichés / filler / corporate jargon / emoji bullet lists 🚀 / gratuitous em-dashes / sycophantic tone / fabricated sources. Also when visible copy-paste chatbot markers are present: `:contentReference`, `?utm_source=chatgpt.com`, `oai_citation`, `grok_card://`, `vertexaisearch`, `turn0search`, `[cite_start]`, `[cite: 8]`. Do NOT use: text that is not in English, source code / scripts (even about NLP), legal documents (officialese is the genre), literary prose / poetry / résumés (there the em-dash, rhythm and compression are an authorial device).
logging-standards
Applies structured logging, levels, PII handling, and wide-event (canonical log line) patterns. Use when adding or reviewing logs, choosing log levels, designing request logging, after an incident where logs were insufficient or leaked data, or when the user says 'logging', 'log format', 'what should we log', 'логирование'.
public-client-leak-audit
Audit a public-facing client (browser extension, mobile/desktop app, SPA, CLI, SDK, or any open-sourced client that talks to a private backend) so its public surface stays self-contained and doesn't help attackers. Use when asked to review a repo for leaked backend internals, secrets, or abuse-enabling disclosure; to check that comments/docs/tests don't reveal server-side mechanics (rate limits, anti-abuse, quotas, test backdoors, infra/tech stack, DB/schema, env-var names); to scrub a client before open-sourcing or a store/app-store submission; or for client-side security hardening (permissions, IPC/message sender validation, auth-token handling, DOM/XSS sinks, build-time config, secret bundling). Triggers: 'audit for leaks', 'does this leak backend details', 'is this safe to make public', 'security review of the client/extension', 'what does our API disclose', 'harden the client'.
receiving-code-review
How to respond to code review feedback: verify before implementing, clarify unclear items, and push back with technical reasoning when needed. Use when receiving PR feedback or review comments. Applies to any team or culture.
security-audit
Audits code for common vulnerabilities: injection, secrets, auth, and dependency CVEs — with confidence-gated, evidence-backed findings mapped to CWE/OWASP. Use when reviewing security, before a release, after adding auth/payments/sensitive-data handling, or when the user says 'security review', 'security audit', 'check for vulnerabilities', 'is this secure'. Do not use for auditing what a public client discloses about a private backend — use public-client-leak-audit for that.
systematic-debugging
Debugs by building a runnable pass/fail reproduction, isolating the root cause, then fixing — no fixes without root cause first. Use when fixing bugs, investigating test/build failures, or when the user reports an error, crash, flaky behavior, or says 'debug this', 'why does X happen', 'не работает'. Use especially under time pressure or after several failed fix attempts. Do not use for feature work with no failing behavior to explain.
translate-ru-en
Translate Russian text of any kind into natural English while preserving every structural element, formatting marker, link, identifier, and the author's human voice. Use when translating Russian articles, docs, prose, fiction, marketing copy, technical content, transcripts, or any other Russian-language text to English; when mirroring a directory of Russian files into an English equivalent; or when the user asks to "translate to English", "convert to en", or "make an English version" of a Russian source.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.