agentsclimarketplace

Review & quality

19,040 rows, by stacks then stars

1,766 of these skill files have been read, by 1,273 distinct authors, and what they tell an agent counted. What Review & quality authors agree on, and what they forbid

  • Design accessibility review

    rakibulism/agent-skills-os/skills/design-accessibility-review Skill

    2★ repo

    Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.

    The same file is in 3 other repositories

  • Design design critique

    rakibulism/agent-skills-os/skills/design-design-critique Skill

    2★ repo

    Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.

    The same file is in 3 other repositories

  • Engineering code review

    rakibulism/agent-skills-os/skills/engineering-code-review Skill

    2★ repo

    Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.

    The same file is in 2 other repositories

  • Marketing brand review

    rakibulism/agent-skills-os/skills/marketing-brand-review Skill

    2★ repo

    Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before/after fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.

    The same file is in 2 other repositories

  • Mathematician

    rakibulism/agent-skills-os/skills/mathematician Skill

    2★ repo

    Solve and prove with mathematical rigor — model a problem precisely, choose a strategy, construct a valid proof or derivation, and verify the result. Covers proof technique, problem-solving heuristics, mathematical modeling of real situations, and careful checking. Use this skill whenever the user wants to prove a statement, solve a hard math/logic problem, model something quantitatively, derive a formula, check a mathematical argument for errors, or reason carefully about quantities, structure, probability, or optimization — and wants correctness with the reasoning shown, not just an answer.

  • Ux expert rakibulism

    rakibulism/agent-skills-os/skills/ux-expert-rakibulism Skill

    2★ repo

    Review UI screens, dashboards, modals, tables, and flows as a UX expert speaking in "rakibulism" — Rakibul's curated professional communication style for client-facing design feedback. Use this skill whenever the user uploads a UI screenshot or design and asks to find UX issues, review a screen, critique a design, comment on a file, or give client-facing feedback. Also trigger when the user says "review this", "find issues", "comment on this", "tell it like me", "rakibulism", or wants feedback written as designer-to-client comments that will be fixed later in a design pass.

  • Ux ui designer

    rakibulism/agent-skills-os/skills/ux-ui-designer Skill

    2★ repo

    Design and critique end-to-end user experiences and interfaces — flows, information architecture, layout, visual hierarchy, and interaction patterns. Produces concrete artifacts (flows, wireframe specs, UI critiques) an engineer or designer can act on. Use this skill whenever the user is designing or reviewing a screen, app, website, dashboard, form, onboarding, checkout, navigation, modal, or settings page, or says things like "how should this flow," "make it more intuitive," "reduce friction," "improve the UX," "review this UI," or "design the interface" — even if they don't say "UX" or "UI" explicitly.

  • Visual polish reviewer

    rakibulism/agent-skills-os/skills/visual-polish-reviewer Skill

    2★ repo

    Review UI screenshots or code for visual polish — alignment, spacing rhythm, typography, color contrast, shadows, borders, and micro-details that separate "fine" from "feels great". Produces a prioritized punch list of fixes with concrete CSS/token changes. Use when the user says the UI "feels off", asks for a polish pass, or wants a design QA before shipping.

  • Flightline

    IamK77/Skill/skills/engineering/flightline Skill

    2★ repo

    Set up or harden a project's engineering process so quality has an automated floor instead of depending on anyone's discipline — version control & branching, code style, code review, CI/CD, and dependency/build management — tuned for a world where agents write much of the code and have no self-discipline to fall back on. Use when the user is bootstrapping or improving a team's workflow, choosing a branching strategy, setting up CI/CD or pre-commit hooks, defining a code-review process, enforcing lint/format, managing dependencies or reproducible builds, or fixing onboarding. Triggers on "set up CI", "git workflow / branching strategy", "how should we do code review", "add pre-commit hooks", "our builds aren't reproducible", "make this project team-ready".

  • Bulwark

    IamK77/Skill/skills/surface/bulwark Skill

    2★ repo

    The 1-to-N lens for a frontend system that is already alive: the enemy is no longer building, it is ENTROPY — boundaries eroded by one "just this once" cross-import at a time, and the two graphs (component tree vs data dependency) drifting apart. Use when a frontend is in maintenance/scaling, onboarding more people, or showing rot (every change touches everything, the global store keeps growing, only one person dares touch the core). The one move: make the architecture SELF-ENFORCING, so it doesn't depend on everyone remembering the rules — because at scale they won't. Triggers on "the codebase is getting hard to change", "enforce architecture / module boundaries", "lint rules for imports / layering", "circular dependency", "this abstraction is everywhere / should I delete it", "dead code / unused exports / stale feature flags", "Conway's law / team structure", "design system / Storybook / component library", "onboarding / how long until a new hire ships". There is no exit; it is a steady state.

  • Securecoder fix

    nerdy-krishna/securecoder/skills/security/securecoder-fix Skill

    2★ repo

    Remediate findings from a previous /securecoder-scan run. Pre-flight (clean-tree, branch, backup) + per-fix loop (LLM SEARCH/REPLACE → syntax check → re-scan → commit) + automatic rollback on any verification failure. Supports severity multi-select, by-finding-ID targeting, interactive one-by-one mode, and a --restore action to roll back a previous fix run.

  • Securecoder review

    nerdy-krishna/securecoder/skills/security/securecoder-review Skill

    2★ repo

    Fast diff-scoped security review of staged or uncommitted changes. Pre-commit gate. Runs SAST + scoped LLM compliance on the diff only — cost proportional to change size, not repo size. Optional pre-commit hook installation for SAST-only blocking-mode.

  • Cross model review

    F-e-u-e-r/opus-pack/skills/cross-model-review Skill

    2★ repo

    Get an adversarial review from a DIFFERENT model family before a load-bearing merge/ship — the mechanized form of "the author is not the judge" when the strongest independent lens is another model, not just a fresh-context subagent of your own. Load when about to merge/ship load-bearing work (code, or a load-bearing plan/spec/doctrine doc), or when the user asks to get an external/second model to review. Do NOT load for routine changes a same-model fresh-context critic covers (delegation-and-review §3), for routine copy/marketing/user-facing prose, or as a way to skip reproducing findings yourself.

  • Delegation and review

    F-e-u-e-r/opus-pack/skills/delegation-and-review Skill

    2★ repo

    Rules for delegating work to subagents and judging what comes back — when to spawn vs. do it yourself, how to write a dispatch packet, how to review agent-produced changes without rubber-stamping, when to retry vs. change approach vs. ask the user, and how to hand off long-running work across sessions. Load when about to spawn a subagent or write a dispatch prompt, when fanning out parallel work, when the diff you are reviewing was produced by an agent, or when work will outlive this session. Do NOT load for small single-context tasks — just do those under operational-rigor.

  • Ground truth gates

    F-e-u-e-r/opus-pack/skills/ground-truth-gates Skill

    2★ repo

    Build executable verification gates (golden set, replay corpus, project checks) so "it works" becomes a checked fact instead of a claim. Load when changing any LLM-judgment step (classify/extract/route/prompt), refactoring logic that processes real logged data, designing tests for a fix, setting up a commit/ship gate for a project, designing a runtime guard (a hook, validator, or auth check) and its fail direction, or when you are about to trust a passing test that has never been shown able to fail. Also the reference for what "proof gate" means in delegation-and-review packets. Do NOT load for one-off scripts or exploratory spikes — plain operational-rigor covers those.

  • Pr writer vp

    VectorPeak/vectorpeak-agent-skills/dev-skills/pr-writer-vp Skill

    2★ repo

    Manage the user's external GitHub PR workflow from project name to fork/clone, multi-agent bug hunting, PR-value validation, formal PR creation, reviewer feedback, and detailed PR comment section expansion. Use when the user asks to fork or clone a GitHub project, find small fixable PR opportunities, launch multi-agent source review, evaluate whether a candidate is real and PR-worthy, create or update a formal PR, expand a specified section in the first PR comment, or align with project PR templates and contribution rules.

  • Profile readme vp

    VectorPeak/vectorpeak-agent-skills/dev-skills/profile-readme-vp Skill

    2★ repo

    Trigger and verify VectorPeak's personal GitHub profile README automation. Use when the user asks to manually run, rerun, test, check, or validate the VectorPeak/VectorPeak profile README GitHub Actions workflow, especially the Update profile README workflow or update-profile.yml.

  • Job contract review vp

    VectorPeak/vectorpeak-agent-skills/job-skills/job-contract-review-vp Skill

    2★ repo

    Review job-related contracts or pasted contract text for red flags, warnings, protective clauses, missing protections, fairness score, and negotiation suggestions. Use when the user provides PDF, DOCX, TXT, MD, RTF, or pasted text for employment agreements, offer letters, NDAs, contractor agreements, freelance agreements, internship agreements, non-competes, severance terms, or asks for practical contract risk review.

  • Github clippings vp

    VectorPeak/vectorpeak-agent-skills/knowledge-skills/github-clippings-vp Skill

    2★ repo

    Convert one or many GitHub repository, pull request, issue, discussion, commit, or code URLs into structured LLM_wiki GitHub raw-corpus Markdown. Use when the user invokes $github-clippings-vp, provides GitHub URL batches, asks to save GitHub material into 01.raw/10.GitHub, build GitHub source cards, organize repo/PR/issue URLs, or create engineering-case notes for later LLM/code-agent reference.

  • Elenchus plan

    alexvtejeda/elenchus/skills/elenchus-plan Skill

    no license2★ repo

    Use when you have an approved spec (or firm requirements) for a multi-step build and want the implementation plan itself stress-tested before you execute it — "write the plan and have the council check it", "verify this plan against the spec", "turn this spec into a plan I can trust", or the writing-plans stage of the Elenchus pipeline. The plan/verification front end over the elenchus-council engine. NOT for stress-testing a build PREMISE that isn't settled yet (that's elenchus-build), NOT for authoring plan craft from scratch with no council (that's plain writing-plans), and NOT for verifying a finished implementation in the browser (that's finishing-implementation-elenchus).

  • Finishing implementation elenchus

    alexvtejeda/elenchus/skills/finishing-implementation-elenchus Skill

    no license2★ repo

    Use when a frontend feature has been implemented and you want to verify it actually works in the running browser against its spec/plan — then fix what doesn't — before calling it done. Triggers: "verify my implementation works", "check the frontend against the spec", "did I actually build everything", "finish and verify this feature", "run the finishing pass". The post-execution stage of the Elenchus pipeline. NOT for stress-testing a build premise (elenchus-build), NOT for writing or verifying a plan (elenchus-plan), and NOT a code-style review.

  • Mcp server review

    selic/skills/skills/mcp-server-review Skill

    2★ repo

    Review an MCP (Model Context Protocol) server for tool-design quality: tool naming and granularity, description/annotation accuracy, input schema strictness, output token budgets, error handling, and role/permission safety. Produces a prioritized findings list, not a rewrite. Use when reviewing, auditing, or hardening an MCP server or its tool definitions. Triggers on: review my MCP server, audit MCP tools, MCP tool design, are my tool descriptions good, MCP server quality.

  • Code review

    shikanime-labs/skills/skills/workflow/code-review Skill

    2★ repo

    A curated catalog of self-improved agent skills for Hermes and compatible agents

  • Email review

    Ken-Technology/cold-email-skills/email-review Skill

    2★ repo

    Review cold email copy for quality, compliance with critical copy rules, and client preferences. Use after email-copywriting completes to validate and improve email sequences. Scores emails 1-5 and outputs emails_v2.md when score >= 4.5. If score < 4.5, provides revision feedback for email-copywriting to iterate. Triggers on "review emails", "check email copy", or when invoked by campaign-planning/campaign-strategy workflows.

  • Backlog refine

    carinyaparc/skills/skills/backlog-refine Skill

    2★ repo

    Use to groom an existing backlog or judge whether a breakdown is ready to commit to — reprioritise, split oversized epics or stories, re-estimate, defer misaligned items, and check sprint readiness of docs/product/backlog.md or docs/work/{epic}/tasks.md. Triggers on "groom the backlog", "refine the backlog", "is this sprint-ready", "are these stories ready", "reprioritise", "this epic is too big", "clean up the backlog". Amends in place and reports a verdict. Do NOT use to create a backlog or write new stories and tasks (tasks), plan a sprint (sprint-planning), review a finished sprint (sprint-retro), or verify an epic against its acceptance criteria (validate).

  • Code review fix

    carinyaparc/skills/skills/code-review-fix Skill

    2★ repo

    Use when the user wants to address, action, or fix findings from a code review — their own working diff reviewed by code-review, a reviewer's comments on a PR or MR, or a pasted list of issues. Triggers on "fix the review findings", "address the review feedback", "action the blocking issues", "apply the review comments". Optionally scoped to an action tier (blocking, warning, all). Makes targeted, behaviour-preserving changes, runs the project's validation suite, and commits in logical units. Do NOT use to perform a review (code-review), to implement new work or features (implement), to address UX or design-fidelity findings (ux-design-review), or to open a PR/MR (merge-request).

  • Code review

    carinyaparc/skills/skills/code-review Skill

    2★ repo

    Carinya Parc Agent Skills

  • Docs review

    carinyaparc/skills/skills/docs-review Skill

    2★ repo

    Use when the user wants a set of documents reviewed — a docs folder, a wiki, a handbook, a repo's markdown, or any collection of written material. Checks that each document is well written and well structured, that boundaries between documents are clear with no duplication, and that the set is consistent and cohesive. Triggers on "review the docs", "are these docs any good", "is our documentation consistent", "do these docs overlap", "audit the documentation". Works on any doc set in any format or tool. Read-only: produces a report and changes nothing. Do NOT use to write or amend a document, to review code (code-review), or to review rendered UI (ux-design-review).

  • Implement

    carinyaparc/skills/skills/implement Skill

    2★ repo

    Use when the user wants to implement a task in code against an approved design.md and docs/work/{epic}/tasks.md. Triggers on "implement CHK01-01", "build this task", "write the code for this story". Reads the design and acceptance criteria, writes code and tests, runs the project's full validation suite, and commits in logical units. Do NOT use for code review (code-review), addressing review feedback (code-review-fix), changing how existing UI looks or behaves (ux-design-fix), writing tasks (tasks), or writing a design (design).

  • Merge request babysit

    carinyaparc/skills/skills/merge-request-babysit Skill

    2★ repo

    Use when the user wants an already-open merge request or pull request driven to a merge-ready state — watching CI, fixing objective check failures, triaging review threads, and syncing merge conflicts until all checks are green and nothing is unresolved. Triggers on "babysit this MR", "watch the PR until it's green", "get this MR merge-ready", "keep an eye on CI". Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Never merges. Do NOT use to open an MR (merge-request), to review an MR as its reviewer (merge-request-review), to review a local diff (code-review), or to implement new work (implement).

  • Merge request review

    carinyaparc/skills/skills/merge-request-review Skill

    2★ repo

    Use when the user is the reviewer of a merge request or pull request and wants it reviewed and the verdict published to the provider — inline comments on the right lines, threads resolved or replied to, and an approve / request-changes / comment decision. Handles first reviews and re-review rounds after the author pushes. Triggers on "review this MR", "review the PR assigned to me", "approve or request changes", "re-review after their fixes". Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Do NOT use to review your own working diff before opening an MR (code-review), to open or babysit an MR (merge-request), or to implement changes (implement).

  • Merge request

    carinyaparc/skills/skills/merge-request Skill

    2★ repo

    Use when the user wants to open a merge request or pull request for the current branch, with a generated title, description, labels, and reviewer suggestions. Triggers on "open a PR", "raise an MR", "create a pull request", "put this branch up for review". Resolves change context and provider, discovers the repo's MR/PR template, composes a size-adaptive description, pushes, and creates the MR. Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise, and plain git as a last resort. Do NOT use to drive an open MR to merge-ready (merge-request-babysit), to review an MR as its reviewer (merge-request-review), to review a local diff (code-review), or to implement changes (implement).

  • Ux design review

    carinyaparc/skills/skills/ux-design-review Skill

    2★ repo

    Carinya Parc Agent Skills

  • Validate

    carinyaparc/skills/skills/validate Skill

    2★ repo

    Use when the user wants final epic completion sign-off: every task in docs/work/{epic}/tasks.md verified against Gherkin AC and roadmap phase exit criteria. Triggers on "validate CHK01", "is this epic done", "sign off the epic". Builds an acceptance matrix with evidence, updates task and epic status, and produces a validation report. Do NOT use for PR or branch code review (code-review), writing tasks (tasks), sprint retrospective (sprint-retro), or drafting the breakdown (tasks) or design.

  • Grill me

    bogdanbaciu21/skills/grill-me Skill

    2★ repo

    Interview the user one question at a time to resolve every open branch of a plan or decision before implementation. Use when the user says "grill me", "/grill-me", "interview me", "stress-test this plan", "poke holes", "push back on this", or asks for hard questions before committing to an approach. Also use proactively before plan mode when the user's request has unresolved design branches, ambiguous scope, or hidden assumptions. Do NOT use to test the user's knowledge of a subject — that's `quiz-me`. Do NOT use for code review or post-implementation critique. Adapted from Matt Pocock's grill-me skill.

  • Boundary review

    jukrap/ai-agent-playbook/skills/architecture/boundary-review Skill

    2★ repo

    Use when reviewing architecture boundaries, FSD layers, DDD modules, monorepo package ownership, dependency direction, or cross-module coupling.

  • Request validation error contract

    jukrap/ai-agent-playbook/skills/backend/request-validation-error-contract Skill

    2★ repo

    Use when changing backend request parsing, validation, error responses, exception mapping, or client-visible failure contracts.

  • Analytics instrumentation review

    jukrap/ai-agent-playbook/skills/data/analytics-instrumentation-review Skill

    2★ repo

    Use when reviewing tracking plans, event schemas, analytics instrumentation, funnels, cohorts, experiments, attribution, consent, or downstream metric impact.

  • Analytics reporting review

    jukrap/ai-agent-playbook/skills/data/analytics-reporting-review Skill

    2★ repo

    Use when reviewing metrics, dashboards, reports, KPI definitions, chart/table consistency, analytics queries, segmentation, freshness, or reporting caveats.

  • Data contract lineage review

    jukrap/ai-agent-playbook/skills/data/data-contract-lineage-review Skill

    2★ repo

    Use when reviewing dataset contracts, data lineage, source-of-truth ownership, freshness targets, schema/grain changes, or downstream consumer impact.

  • Data pipeline review

    jukrap/ai-agent-playbook/skills/data/data-pipeline-review Skill

    2★ repo

    Use when reviewing analytics pipelines, ETL jobs, batch processing, data contracts, quality checks, dashboards, or reporting datasets.

  • Knowledge retrieval pipeline review

    jukrap/ai-agent-playbook/skills/data/knowledge-retrieval-pipeline-review Skill

    2★ repo

    Use when reviewing document ingestion, parsing, chunking, metadata, deduplication, embeddings, vector stores, retrieval quality, citations, or stale RAG/search indexes.

  • Query performance review

    jukrap/ai-agent-playbook/skills/database/query-performance-review Skill

    2★ repo

    Use when reviewing slow SQL, reporting queries, dashboard queries, API list/detail queries, exports, aggregates, joins, sort/pagination, full scans, N+1 patterns, or index choices.

  • Ci quality gate

    jukrap/ai-agent-playbook/skills/delivery/ci-quality-gate Skill

    2★ repo

    Use when deciding CI quality gates before merge, release, handoff, or publication.

  • Git worklog guardrails

    jukrap/ai-agent-playbook/skills/delivery/git-worklog-guardrails Skill

    2★ repo

    Use when staging files, committing, pushing, preparing PR text, release notes, or worklogs in a repository with local-only files or careful branch policy.

  • Test verification strategy

    jukrap/ai-agent-playbook/skills/delivery/test-verification-strategy Skill

    2★ repo

    Use when planning, reviewing, or repairing verification strategy, test scope, contract/manual checks, coverage gaps, risk-based selection, or release confidence.

  • Deployment release check

    jukrap/ai-agent-playbook/skills/devops/deployment-release-check Skill

    2★ repo

    Use when preparing, reviewing, or troubleshooting releases, deploys, rollbacks, feature flags, changelogs, package artifacts, migration gates, or post-deploy checks.

  • Frontend accessibility review

    jukrap/ai-agent-playbook/skills/frontend/frontend-accessibility-review Skill

    2★ repo

    Use when reviewing or changing keyboard access, focus management, semantics, forms, dialogs, menus, announcements, contrast, reduced motion, or accessible interaction states.

  • Interactive media 3d review

    jukrap/ai-agent-playbook/skills/frontend/interactive-media-3d-review Skill

    2★ repo

    Use when implementing or reviewing Three.js, WebGL, canvas, SVG, chart, map, animation, video, or media-heavy interactive UI surfaces.

  • Commit worklog guardrails

    jukrap/ai-agent-playbook/skills/git/commit-worklog-guardrails Skill

    2★ repo

    Use when staging files, writing commits, pushing branches, opening PRs, preparing release notes, or recording worklogs with local-only doc constraints.

  • Legacy risk check

    jukrap/ai-agent-playbook/skills/legacy/legacy-risk-check Skill

    2★ repo

    Use when changing legacy code that may affect global state, shared CSS/JS, common selectors, templates, forms, API contracts, build output, or deployment behavior.

  • Offline sync review

    jukrap/ai-agent-playbook/skills/mobile/offline-sync-review Skill

    2★ repo

    Use when changing or reviewing mobile offline mode, local cache, durable queues, sync jobs, conflict resolution, retries, idempotency, or network transition behavior.

  • Requirements prd scope review

    jukrap/ai-agent-playbook/skills/project/requirements-prd-scope-review Skill

    2★ repo

    Use when turning vague requests into PRDs, scope boundaries, acceptance criteria, or open questions.

  • Review work light

    jukrap/ai-agent-playbook/skills/quality/review-work-light Skill

    2★ repo

    Use when doing a lightweight review of recent implementation work, local diffs, or a completed change before handoff without starting a blocking multi-agent review process.

  • Style quality review

    jukrap/ai-agent-playbook/skills/quality/style-quality-review Skill

    2★ repo

    Use when reviewing or improving UI styling, responsive behavior, CSS structure, design polish, layout overflow, or visual regressions without product changes.

  • Dependency supply chain review

    jukrap/ai-agent-playbook/skills/security/dependency-supply-chain-review Skill

    2★ repo

    Use when changing dependencies, lockfiles, SBOMs, licenses, containers, package scripts, provenance, or vulnerability remediation.

  • License notice review

    jukrap/ai-agent-playbook/skills/security/license-notice-review Skill

    2★ repo

    Use when reviewing licenses, notices, attribution, vendored code, copied snippets, generated artifacts, redistribution scope, or compliance evidence.

  • Security review

    jukrap/ai-agent-playbook/skills/security/security-review Skill

    2★ repo

    Use when reviewing secrets, authentication, authorization, input validation, dependency risk, sensitive data flow, or threat-model changes.

  • Git commit push

    ainova-systems/intelligence-dev-packs/packs/core/skills/git-commit-push Skill

    2★ repo

    Verify, review, and push pending work as one milestone commit

  • Git create release

    ainova-systems/intelligence-dev-packs/packs/core/skills/git-create-release Skill

    2★ repo

    Cut a release: version, changelog, tag, and release object — policy-driven across trunk/gitflow and tag-only/full