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

  • Name check

    Manzanita-Research/pedalboard/branding/skills/name-check Skill

    no license1★ repo

    Comprehensive artist name availability checker with parallel search agents that scan Spotify, Apple Music, Bandcamp, SoundCloud, Tidal, Subvert, YouTube Music, TikTok, Discogs, and MusicBrainz simultaneously. ALWAYS use this skill when a musician asks about a name — whether they say "is this name taken", "can I use this name", "check this band name", "would X be a good artist name", "any conflicts with this name", or anything about name availability, name conflicts, or choosing an artist/band/stage/project name. This skill has specialized subagents and a structured analysis workflow that produces much better results than ad-hoc searching. Use it even for indirect requests like "I'm thinking of calling my project X" or "we need a name for our band, what about X" — if there's a specific name mentioned and the user wants to know if it's safe to use, this skill applies.

  • Research

    drader/researcher_agent/skills/research Skill

    no license1★ repo

    Literature investigation, source verification, and synthesis for academic and professional research. 7 modes: brief (quick literature summary), full (comprehensive report), socratic (guided question-formulation dialogue), systematic (PRISMA 2020 review), verify (claim-by-claim fact-check), annotate (annotated bibliography), evaluate (critical review of one source). Engage when user asks about literature, research, fact-checking, evidence verification, systematic review, annotated bibliography, or guided research dialogue. Triggers: 'research X', 'literature on Y', 'fact-check this', 'systematic review', 'help me think through', 'evaluate this paper', 'annotated bibliography'.

  • Fact check

    jp-solumhealth/jpstack/fact-check Skill

    1★ repo

    14 opinionated skills for running a healthcare AI startup as a solo founder — daily briefings, PMF intelligence, sales coaching, conference pipelines, and content creation as slash commands

  • Prior auth review

    jp-solumhealth/jpstack/prior-auth-review Skill

    1★ repo

    Automate payer review of prior authorization (PA) requests. This skill should be used when users say "Review this PA request", "Process prior authorization for [procedure]", "Assess medical necessity", "Generate PA decision", or when processing clinical documentation for coverage policy validation and authorization decisions.

    The same file is in 4 other repositories

  • Site review

    jp-solumhealth/jpstack/site-review Skill

    1★ repo

    Comprehensive website SEO and conversion audit with built-in fact-checking. Technical SEO, tactical SEO, intake/lead form assessment, and CRO analysis. Use when asked to "review a site", "SEO audit", "check a website", "conversion audit", "site review", "website analysis", or "intake assessment".

  • Shaktra review

    im-shashanks/claude-plugins/shaktra/skills/shaktra-review Skill

    no license1★ repo

    Code Reviewer workflow — app-level code review and PR review with independent verification testing. Dispatches CR Analyzer agents across quality dimensions and produces evidence-based structured reports.

  • Finish branch

    Chrike/coding-agent-skills/skills/finish-branch Skill

    no license1★ repo

    Lightweight Claude Code skills for daily AI-assisted development workflows.

  • Reliability check

    Chrike/coding-agent-skills/skills/reliability-check Skill

    no license1★ repo

    Use when the user explicitly challenges the reliability of the agent's current or prior conclusion, evidence, source use, active stage, wrong direction, strategy or workflow drift, stale context, unsupported confidence, hallucination, guessing, source-vs-memory confusion, or example-vs-task confusion, or explicitly asks to reassess one of those concerns. Also use when the user says the agent used the wrong, missing, unread, or outdated source for its current or prior conclusion. Do not use for ordinary status questions, file-inventory questions, routine source-reading requests, general uncertainty, ordinary strategy or approach preference changes, or preventive stage reminders without a stated reliability concern.

  • Review and finish

    Chrike/coding-agent-skills/skills/review-and-finish Skill

    no license1★ repo

    Use when the user explicitly asks to review code, assess or address review or PR feedback, verify whether completed software work is done, fixed, passing, or ready, or check a development artifact before sending or shipping. Also use before a done claim for completed changes affecting persisted data or migrations, authentication, authorization, permissions, public compatibility contracts, concurrency, transactions, or destructive behavior. Do not use for ordinary progress summaries, implementation-only requests, high-risk terminology without a completion claim, or an explicitly invoked bundled `/code-review`.

  • Plan review

    KonH/ClaudeTools/plugins/k/skills/plan-review Skill

    1★ repo

    Review a dated plan under docs/specs/ for missing steps, wrong assumptions, or guideline violations before implementation begins.

  • Pr

    KonH/ClaudeTools/plugins/k/skills/pr Skill

    1★ repo

    Create a pull request for the current branch

  • Version check

    scagogogo/versions-skills/skills/version-check Skill

    1★ repo

    Check boolean properties of version numbers — type checks (IsBeta, IsStable, IsRC, etc.) and comparison predicates (IsNewerThan, IsOlderThan, IsBetween). Use for CI/CD conditionals, shell script exit-code checks, and programmatic version filtering.

  • Plan ceo review

    Yesterday-AI/ytstack/skills/plan-ceo-review Skill

    1★ repo

    Challenge premise, scope, and ambition via four modes: SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, SCOPE REDUCTION. Auto-detects mode: concept-mode reviews a pitch (OFFICE-HOURS.md) before any scaffolding exists; milestone-mode reviews a committed milestone (M###-CONTEXT.md + M###-ROADMAP.md) before slicing. Use concept-mode right after office-hours to stress-test the pitch; use milestone-mode after plan-milestone and before slice-milestone. Thin ytstack wrapper around the vendored gstack plan-ceo-review procedure.

  • Plan eng review

    Yesterday-AI/ytstack/skills/plan-eng-review Skill

    1★ repo

    Review execution approach for feasibility, architecture, data flow, edge cases, test coverage, performance, and security risks. Auto-detects mode: concept-mode reviews a pitch (OFFICE-HOURS.md) for technical feasibility before any scaffolding; milestone-mode reviews slice-plans (M###-S##-PLAN.md) before plan-task. Use concept-mode optionally after plan-ceo-review to sanity-check the pitched approach; use milestone-mode after slice-milestone to lock architecture before implementation. Thin ytstack wrapper around the vendored gstack plan-eng-review procedure.

  • Verification before completion

    Yesterday-AI/ytstack/skills/verification-before-completion Skill

    1★ repo

    Run verification commands and confirm output before claiming work is complete. Evidence before assertions. Thin ytstack wrapper around the vendored superpowers verification-before-completion procedure, injecting the current task's verification command. Use before commit, before PR, before summarize-task, before any 'done' claim.

  • Browse

    Yesterday-AI/ytstack/vendor/gstack/browse Skill

    1★ repo

    Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence. Use when asked to "open in browser", "test the site", "take a screenshot", or "dogfood this". (gstack)

  • Canary

    Yesterday-AI/ytstack/vendor/gstack/canary Skill

    1★ repo

    Post-deploy canary monitoring. Watches the live app for console errors, performance regressions, and page failures using the browse daemon. Takes periodic screenshots, compares against pre-deploy baselines, and alerts on anomalies. Use when: "monitor deploy", "canary", "post-deploy check", "watch production", "verify deploy". (gstack)

  • Codex

    Yesterday-AI/ytstack/vendor/gstack/codex Skill

    1★ repo

    OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via codex review with pass/fail gate. Challenge: adversarial mode that tries to break your code. Consult: ask codex anything with session continuity for follow-ups. The "200 IQ autistic developer" second opinion. Use when asked to "codex review", "codex challenge", "ask codex", "second opinion", or "consult codex". (gstack) Voice triggers (speech-to-text aliases): "code x", "code ex", "get another opinion".

  • Cso

    Yesterday-AI/ytstack/vendor/gstack/cso Skill

    1★ repo

    Chief Security Officer mode. Infrastructure-first security audit: secrets archaeology, dependency supply chain, CI/CD pipeline security, LLM/AI security, skill supply chain scanning, plus OWASP Top 10, STRIDE threat modeling, and active verification. Two modes: daily (zero-noise, 8/10 confidence gate) and comprehensive (monthly deep scan, 2/10 bar). Trend tracking across audit runs. Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review". (gstack) Voice triggers (speech-to-text aliases): "see-so", "see so", "security review", "security check", "vulnerability scan", "run security".

  • Design review

    Yesterday-AI/ytstack/vendor/gstack/design-review Skill

    1★ repo

    Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use /plan-design-review. Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish". Proactively suggest when the user mentions visual inconsistencies or wants to polish the look of a live site. (gstack)

  • Devex review

    Yesterday-AI/ytstack/vendor/gstack/devex-review Skill

    1★ repo

    Live developer experience audit. Uses the browse tool to actually TEST the developer experience: navigates docs, tries the getting started flow, times TTHW, screenshots error messages, evaluates CLI help text. Produces a DX scorecard with evidence. Compares against /plan-devex-review scores if they exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to "test the DX", "DX audit", "developer experience test", or "try the onboarding". Proactively suggest after shipping a developer-facing feature. (gstack) Voice triggers (speech-to-text aliases): "dx audit", "test the developer experience", "try the onboarding", "developer experience test".

  • Guard

    Yesterday-AI/ytstack/vendor/gstack/guard Skill

    1★ repo

    Full safety mode: destructive command warnings + directory-scoped edits. Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems. Use when asked to "guard mode", "full safety", "lock it down", or "maximum safety". (gstack)

    The same file is in 1 other repository

  • Health

    Yesterday-AI/ytstack/vendor/gstack/health Skill

    1★ repo

    Code quality dashboard. Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter), computes a weighted composite 0-10 score, and tracks trends over time. Use when: "health check", "code quality", "how healthy is the codebase", "run all checks", "quality score". (gstack)

  • Gstack openclaw ceo review

    Yesterday-AI/ytstack/vendor/gstack/openclaw/skills/gstack-openclaw-ceo-review Skill

    1★ repo

    Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.

    The same file is in 1 other repository

  • Plan ceo review

    Yesterday-AI/ytstack/vendor/gstack/plan-ceo-review Skill

    1★ repo

    CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. (gstack)

  • Plan design review

    Yesterday-AI/ytstack/vendor/gstack/plan-design-review Skill

    1★ repo

    Designer's eye plan review — interactive, like CEO and Eng review. Rates each design dimension 0-10, explains what would make it a 10, then fixes the plan to get there. Works in plan mode. For live site visual audits, use /design-review. Use when asked to "review the design plan" or "design critique". Proactively suggest when the user has a plan with UI/UX components that should be reviewed before implementation. (gstack)

  • Plan devex review

    Yesterday-AI/ytstack/vendor/gstack/plan-devex-review Skill

    1★ repo

    Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".

  • Plan eng review

    Yesterday-AI/ytstack/vendor/gstack/plan-eng-review Skill

    1★ repo

    Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

  • Qa only

    Yesterday-AI/ytstack/vendor/gstack/qa-only Skill

    1★ repo

    Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

  • Review

    Yesterday-AI/ytstack/vendor/gstack/review Skill

    1★ repo

    Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes. (gstack)

  • Ship

    Yesterday-AI/ytstack/vendor/gstack/ship Skill

    1★ repo

    Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)

  • Golden

    Yesterday-AI/ytstack/vendor/gstack/test/fixtures/golden Skill

    1★ repo

    Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)

  • Finishing a development branch

    Yesterday-AI/ytstack/vendor/superpowers/skills/finishing-a-development-branch Skill

    1★ repo

    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

    The same file is in 10 other repositories

  • Receiving code review

    Yesterday-AI/ytstack/vendor/superpowers/skills/receiving-code-review Skill

    1★ repo

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    The same file is in 28 other repositories

  • Requesting code review

    Yesterday-AI/ytstack/vendor/superpowers/skills/requesting-code-review Skill

    1★ repo

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    The same file is in 11 other repositories

  • Using git worktrees

    Yesterday-AI/ytstack/vendor/superpowers/skills/using-git-worktrees Skill

    1★ repo

    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

    The same file is in 13 other repositories

  • Verification before completion

    Yesterday-AI/ytstack/vendor/superpowers/skills/verification-before-completion Skill

    1★ repo

    Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

    The same file is in 40 other repositories

  • Gst

    yokeloop/yoke/deprecated/gst Skill

    1★ repo

    Shows development status in the repository: branch, uncommitted changes, recent commits, diff vs main, hot files, semantic summary. Used when a developer writes "status", "gst", "git status", "what's going on", "repo state", "show changes".

  • Gca

    yokeloop/yoke/skills/gca Skill

    1★ repo

    Git staging and commit with smart file grouping. Activated when the user writes "commit", "gca", "make a commit", "commit changes".

  • Grill docs

    yokeloop/yoke/skills/grill-docs Skill

    1★ repo

    Docs-aware grilling: interrogates the user's plan one question at a time AND maintains the domain glossary (.yoke/context.md) and architecture decision records (.yoke/adr/) inline as decisions crystallise. Used to stress-test a plan against the project's language and documented decisions; for a plain interview that writes no files, use grill. Activates when the user writes "grill-docs", "grill with docs", "grill and update the glossary", "grill and write ADRs", "stress-test against the glossary", "challenge my plan and capture decisions".

  • Grill

    yokeloop/yoke/skills/grill Skill

    1★ repo

    Interviews the user one interactive question at a time about a plan or design, walking each branch of the decision tree to a shared understanding; every question offers a recommended answer. A read-only interview that writes no files — for the variant that also captures terminology and decisions into .yoke/context.md and ADRs, use grill-docs. Activates when the user writes "grill", "grill me", "poke holes in this", "interrogate my design", "challenge my plan", "stress-test my plan", "interview me about this".

  • Review

    yokeloop/yoke/skills/review Skill

    1★ repo

    Finds problems in code, fixes them and produces a report. Used when the user writes "review", "code review", "find issues", "find bugs", "check code", "code analysis", "prepare a report", "what's wrong with the code".

  • Quality review tickets

    Ludovic33Fr/product-ai-toolbox/skills/quality-review-tickets Skill

    1★ repo

    Utiliser la veille de chaque cérémonie de refinement pour pré-réviser un ou plusieurs tickets de backlog. Produit un tableau des critères manquants par dimension, un test INVEST argumenté, des scénarios edge cases en Given/When/Then, et la liste des dépendances détectées.

  • Quarterly review pm

    Ludovic33Fr/product-ai-toolbox/skills/quarterly-review-pm Skill

    1★ repo

    Utiliser trimestriellement pour préparer la revue d'un PM managé sur la base de données factuelles et de la grille de maturité IA. Produit une synthèse factuelle, un score de maturité IA, les zones de progression et stagnation, les questions à poser et les objectifs proposés.

  • Deploy check

    claude-hangar/claude-hangar/core/skills/deploy-check Skill

    1★ repo

    Deployment readiness check for Docker/Traefik projects. Use when: "deploy check", "deployment check", "ready for deployment", "deploy-check", "before deploy", "production ready".

  • Favicon check

    claude-hangar/claude-hangar/core/skills/favicon-check Skill

    1★ repo

    Favicon/app icon completeness check. Use when: "favicon", "icon check", "app icon", "icons".

  • Freshness check

    claude-hangar/claude-hangar/core/skills/freshness-check Skill

    1★ repo

    Pipeline source freshness check (frameworks, tools, standards). Use when: "freshness", "update check", "is everything current", "check versions".

  • Git hygiene

    claude-hangar/claude-hangar/core/skills/git-hygiene Skill

    1★ repo

    Git repository hygiene check. Stale branches, large files, commit conventions. Use when: "git cleanup", "git hygiene", "clean up branches", "git-hygiene", "stale branches", "git cleanup".

  • Inline review

    claude-hangar/claude-hangar/core/skills/inline-review Skill

    1★ repo

    Quick self-review checklist after code changes. Lightweight alternative to adversarial-review. Use when: "review my changes", "self-review", "quick review", "check my work", or automatically after significant edits.

  • Review team

    claude-hangar/claude-hangar/core/skills/review-team Skill

    1★ repo

    Launch parallel code review agents for comprehensive multi-perspective review. Use when: "review team", "full review", "multi-review", "review-team".

  • Safety guard

    claude-hangar/claude-hangar/core/skills/safety-guard Skill

    1★ repo

    3-mode protection system for autonomous agent runs. Careful (confirm risky ops), Freeze (restrict writes to directory), Guard (combined). Use when running autonomous loops or untrusted agent tasks.

  • Verification loop

    claude-hangar/claude-hangar/core/skills/verification-loop Skill

    1★ repo

    Pre-PR verification pipeline with plan validation, build, types, lint, test, security, diff review, and consistency checks. Verification gate — use before creating a PR or merging.

  • Double loop execution reviewer

    limerickgds/dashi-skills/skills/double-loop-execution-reviewer Skill

    1★ repo

    A double-loop learning execution review skill. Reviews the execution history after a task is completed and turns it into a concise retrospective, handoff, or improvement memo. Use this whenever a coding, writing, research, planning, debugging, or operational task has just finished; whenever files, commands, tests, or deliverables were produced; whenever the user asks to summarize what was done, review the execution, create a handoff, capture lessons learned, or prepare for the next iteration; and especially when the user needs not only a summary of what happened, but a judgment about whether the original goal, assumptions, success criteria, or working rules should change before the next pass. If there is execution evidence in the conversation, err on the side of using this skill instead of waiting for the user to ask explicitly.

  • Editorial git committer

    limerickgds/dashi-skills/skills/editorial-git-committer Skill

    1★ repo

    Use when users want to commit changes, improve a commit message, split mixed changes into logical commits, clean up recent local history, remove accidentally committed files, squash or reword recent local commits, or generally sort out a local Git mess before review or a PR.

  • Lint

    odere-pro/claude-wiki-pages-plugin/skills/lint Skill

    1★ repo

    Read-only audit of vault/wiki/ for structural and provenance drift. Reports Errors, Warnings, and Info per the lint rules in vault/CLAUDE.md. Trigger when the user says "lint the vault", "audit the wiki", "check for broken links", "run a health check on the wiki", or invokes /claude-wiki-pages:lint directly. Does not repair anything — that is /claude-wiki-pages:fix.

  • Review

    odere-pro/claude-wiki-pages-plugin/skills/review Skill

    1★ repo

    Review drafted wiki pages and promote or reject them. Trigger when the user wants to "review proposals/drafts", "approve/reject a draft", check what a local model produced, or invokes /claude-wiki-pages:review. Operates on vault/_proposed/; promotion runs under a git checkpoint and then chains the maintenance loop. The human-in-the-loop gate for any drafted content.

  • Swing research

    SURFLIN2030/swing-skills/skills/swing-research Skill

    1★ repo

    Deep research with cross-verification and source tiering. Use when investigating technologies, comparing tools, fact-checking claims, evaluating architectures, or any task requiring verified information. Triggers on "조사해줘", "리서치", "research", "investigate", "fact-check", "비교 분석", "검증해줘".

  • Swing review

    SURFLIN2030/swing-skills/skills/swing-review Skill

    1★ repo

    Devil's Advocate stress-testing for code, architecture, PRs, and decisions. Surfaces hidden flaws through structured adversarial analysis with metacognitive depth. Use for high-stakes review, stress-testing choices, or when the user wants problems found deliberately. NOT for routine code review (use engineering:code-review). Triggers on "스트레스 테스트", "stress test", "devil's advocate", "반론", "이거 괜찮아", "문제 없을까", "깊은 리뷰", "critical review", "adversarial".

  • Caio review

    timdevai/proteus/skills/community/from-alireza/c-level-advisor/c-level-agents/skills/caio-review Skill

    1★ repo

    /cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.

  • Cco review

    timdevai/proteus/skills/community/from-alireza/c-level-advisor/c-level-agents/skills/cco-review Skill

    1★ repo

    /cs:cco-review <plan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring.