agentsclimarketplace

Review & quality

19,181 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

  • Mistake review

    hwl668/Scientific-learning-skills-/skills/mistake-review Skill

    15★ repo

    适用于错题复盘和错误诊断。用户说做错了、答案不一样、为什么我错、粗心、同样错误反复出现,或提供原题/自己的解答/标准答案时使用。归类错因,提炼避免再错的方法,并用变式训练巩固。

  • Sendmux getting started

    Sendmux/skills/plugins/sendmux/skills/sendmux-getting-started Skill

    no license15★ repo

    Sendmux setup, skill installation, API key validation, agent access, secure agent credential-bundle storage, and first-call guidance. Use when the user wants to install Sendmux tooling or skills, check whether an smx_root_, smx_mbx_, or smx_agent_ credential works, choose MCP vs CLI vs SDK, connect an agent to Sendmux email, configure auth, self-register an agent, or make the first harmless Sendmux API call from an agent, terminal, or application.

    The same file is in 1 other repository

  • Sendmux getting started

    Sendmux/skills/skills/sendmux-getting-started Skill

    no license15★ repo

    Sendmux setup, skill installation, API key validation, agent access, secure agent credential-bundle storage, and first-call guidance. Use when the user wants to install Sendmux tooling or skills, check whether an smx_root_, smx_mbx_, or smx_agent_ credential works, choose MCP vs CLI vs SDK, connect an agent to Sendmux email, configure auth, self-register an agent, or make the first harmless Sendmux API call from an agent, terminal, or application.

    The same file is in 1 other repository

  • Cross checker

    a-ariff/ariff-claude-plugins/plugins/cross-checker/skills/cross-checker Skill

    14★ repo

    Verify every claim from multiple independent angles -- code, docs, tests, git history. Use when you need high confidence that something is correct before acting on it.

    The same file is in 2 other repositories

  • Plugin checker

    a-ariff/ariff-claude-plugins/plugins/plugin-checker/skills/plugin-checker Skill

    14★ repo

    Use this skill when asked to "validate plugin", "check plugin structure", "verify plugin", "audit plugin", "is my plugin correct", "plugin issues", or when troubleshooting plugin problems.

    The same file is in 5 other repositories

  • Verification before completion

    a-ariff/ariff-claude-plugins/plugins/verification-before-completion/skills/verification-before-completion Skill

    14★ repo

    Never claim completion without fresh verification evidence

    The same file is in 4 other repositories

  • Cc codex review

    codingSamss/all-my-ai-needs/platforms/claude/skills/cc-codex-review Skill

    no license14★ repo

    CC×Codex 交叉讨论。不确定性强的问题(事实核查 / 有争议或乐观的结论 / 重要技术决策)找 codex 交叉验证,避免单模型片面。关键词: 让codex看看, 跟codex讨论, codex审查, 帮我审查, review, 交叉讨论, battle, 发给codex, 继续讨论, 接着聊

  • Git ops

    codingSamss/all-my-ai-needs/platforms/claude/skills/git-ops Skill

    no license14★ repo

    Use when Sam asks Claude Code to create, rename, compare, commit, push, merge, promote, or clean up Git branches. Covers Sam's feature branch naming convention, safe Git pre-checks, JetBrains DontCommit handling, commit-message defaults, push and release promotion verification, branch rename upstream cleanup, branch sync comparison, and submodule/gitlink handling.

  • Git ops

    codingSamss/all-my-ai-needs/platforms/codex/skills/git-ops Skill

    no license14★ repo

    Use when Sam asks Codex to create, rename, compare, commit, push, merge, promote, or clean up Git branches. Covers Sam's feature branch naming convention, safe Git pre-checks, JetBrains DontCommit handling, commit-message defaults, push and release promotion verification, branch rename upstream cleanup, branch sync comparison, and submodule/gitlink handling.

  • Workshop critique

    Calliope-Editor/writing-skills/skills/critique/workshop-critique Skill

    14★ repo

    Runs a Milford/Clarion-style workshop critique on a chapter or short story — a group of distinct critiquers speaks in turn about what the piece is doing and where it's not working, while the author stays silent in the cone of silence. Use it when a writer wants a structured, multi-voice critique of a self-contained piece. It critiques; it never writes or rewrites the author's prose.

  • Layered architecture

    Amey-Thakur/AI-SKILLS/skills/architecture/layered-architecture Skill

    14★ repo

    Organize a system into layers with one permitted direction of dependency and enforce that direction mechanically at the import level. Use when a codebase is sliding toward tangled cross-references and you need a rule a linter can check, not a convention people forget.

  • Request validation

    Amey-Thakur/AI-SKILLS/skills/backend/request-validation Skill

    14★ repo

    Validate requests at the boundary with schemas, reject unknown fields, and return errors clients can act on. Use when hardening API input handling or standardizing validation across endpoints.

  • Architecture review board

    Amey-Thakur/AI-SKILLS/skills/big-tech-processes/architecture-review-board Skill

    14★ repo

    Run an Architecture Review Board that filters proposals by blast radius, reviews them through fixed lenses, issues binding decisions recorded as ADRs, and honors an appeals path. Use when a technical choice crosses team boundaries and needs a durable, accountable decision instead of hallway consensus.

  • Design critique

    Amey-Thakur/AI-SKILLS/skills/big-tech-processes/design-critique Skill

    14★ repo

    Run a design critique with a clear presenter contract, feedback rules that attack the work not the person, and captured decisions. Use when a designer brings work in progress to a group for structured feedback rather than approval.

  • Launch review

    Amey-Thakur/AI-SKILLS/skills/big-tech-processes/launch-review Skill

    14★ repo

    Run a launch review that gates a release behind a readiness checklist, named sign-offs, and a clear no-go authority. Use when a user-facing launch is about to ship and a bad release would be costly to walk back.

  • Open source review board

    Amey-Thakur/AI-SKILLS/skills/big-tech-processes/open-source-review-board Skill

    14★ repo

    Run an open source review board that gates incoming dependencies on license compatibility, sets the policy for contributing back, and requires a security review before adoption. Use when an organization needs consistent control over which OSS it pulls in and what it publishes.

  • Postmortem review board

    Amey-Thakur/AI-SKILLS/skills/big-tech-processes/postmortem-review-board Skill

    14★ repo

    Run an org-level board that grades incident postmortems against a quality bar, promotes cross-cutting fixes to owned work, and reads across incidents for trends. Use when your organization writes enough postmortems that reviewing them one at a time hides the systemic pattern.

  • Production readiness review

    Amey-Thakur/AI-SKILLS/skills/big-tech-processes/production-readiness-review Skill

    14★ repo

    Run a production readiness review that checks SLOs, runbooks, capacity, and dependencies before an on-call team agrees to own a service. Use when a service is about to be onboarded to a support rotation or handed from its builders to operators.

  • Code review comments

    Amey-Thakur/AI-SKILLS/skills/code-quality/code-review-comments Skill

    14★ repo

    Write review comments that land by labeling severity and separating genuine questions from directives. Use when leaving comments on a pull request or coaching someone on how theirs read.

  • Code review

    Amey-Thakur/AI-SKILLS/skills/code-quality/code-review Skill

    14★ repo

    Review code changes for correctness, security, and maintainability with severity-ranked, evidence-based findings. Use when asked to review a diff, a pull request, or a file before merge.

  • Guard clauses

    Amey-Thakur/AI-SKILLS/skills/code-quality/guard-clauses Skill

    14★ repo

    Flatten nested conditionals into early returns that handle edge cases up front and keep the main path unindented. Use when logic marches rightward into deep nesting.

  • Linting setup

    Amey-Thakur/AI-SKILLS/skills/code-quality/linting-setup Skill

    14★ repo

    Triage lint rules so bug-catchers are errors, style is left to the formatter, and every suppression carries a reason. Use when configuring a linter, taming warning noise, or setting a suppressions policy.

  • Pr authoring

    Amey-Thakur/AI-SKILLS/skills/code-quality/pr-authoring Skill

    14★ repo

    Shape pull requests a reviewer can actually hold in their head, through small size, a why-first description, and a self-review pass. Use when opening a pull request or preparing a change for review.

  • Git bisect

    Amey-Thakur/AI-SKILLS/skills/debugging/git-bisect Skill

    14★ repo

    Find the exact commit that introduced a regression by driving git bisect with an automated pass/fail script. Use when a behavior worked in an older build and you need the first bad commit out of hundreds, not a guess.

  • Branch strategy

    Amey-Thakur/AI-SKILLS/skills/git-collaboration/branch-strategy Skill

    14★ repo

    Choose a branching model, default to trunk-based with short-lived branches, and set protection rules. Use when establishing team git workflow or fixing long-lived-branch merge pain.

  • Commit messages

    Amey-Thakur/AI-SKILLS/skills/git-collaboration/commit-messages Skill

    14★ repo

    Write commit messages that explain change and intent so history stays useful. Use when committing work or asked to draft a commit message for a diff.

  • Git history hygiene

    Amey-Thakur/AI-SKILLS/skills/git-collaboration/git-history-hygiene Skill

    14★ repo

    Keep git history atomic, bisectable, and readable with curated commits and disciplined force-push. Use when commits are messy, history is hard to navigate, or bisect and blame mislead.

  • Git hooks automation

    Amey-Thakur/AI-SKILLS/skills/git-collaboration/git-hooks-automation Skill

    14★ repo

    Automate checks with git hooks that stay fast, with server-side enforcement and documented escape hatches. Use when setting up pre-commit checks or fixing hooks that developers routinely bypass.

  • Git workflow

    Amey-Thakur/AI-SKILLS/skills/git-collaboration/git-workflow Skill

    14★ repo

    Use git safely and legibly: branches, history, merges, conflicts, and recovery. Use when managing branches, cleaning history, resolving conflicts, or undoing mistakes.

  • Merge vs rebase

    Amey-Thakur/AI-SKILLS/skills/git-collaboration/merge-vs-rebase Skill

    14★ repo

    Choose merge or rebase by the history you want, use interactive rebase safely, and set a team policy. Use when deciding integration mechanics or resolving debates about git history style.

  • Pull request size

    Amey-Thakur/AI-SKILLS/skills/git-collaboration/pull-request-size Skill

    14★ repo

    Keep pull requests small through vertical slicing and stacking, because review quality and latency both collapse with size. Use when PRs are too big to review well or sit for days.

  • Cross validation

    Amey-Thakur/AI-SKILLS/skills/machine-learning/cross-validation Skill

    14★ repo

    Pick CV schemes that respect time and grouping, nest them for tuning, and read the variance, not just the mean. Use when data is too small for a single split or when validating tuning claims.

  • Agent code review loop

    Amey-Thakur/AI-SKILLS/skills/multi-agent-teams/agent-code-review-loop Skill

    14★ repo

    Run an author agent and a reviewer agent in a loop with a strict finding format, a mandatory verification pass, and a convergence rule that ends it. Use when you want agent-to-agent code review that improves the diff instead of spinning forever on style or re-flagging fixed issues.

  • Agent design review panel

    Amey-Thakur/AI-SKILLS/skills/multi-agent-teams/agent-design-review-panel Skill

    14★ repo

    Convene several reviewer agents with fixed distinct lenses, correctness, security, cost, and simplicity, then synthesize their verdicts into one. Use when a single review agent keeps missing whole classes of problems because it cannot hold every concern at once on a design or plan.

  • Agent release train

    Amey-Thakur/AI-SKILLS/skills/multi-agent-teams/agent-release-train Skill

    14★ repo

    Run release agents that draft the changelog, scan risk, verify the candidate, and gate publish behind a go/no-go check. Use when cutting a release and you want the boring parts automated and the risky parts caught before ship.

  • Literature review

    Amey-Thakur/AI-SKILLS/skills/research/literature-review Skill

    14★ repo

    Survey prior work systematically through search strategy, citation chasing, quality assessment, and synthesis. Use when entering a new domain or grounding a decision in what is already known.

  • Input validation

    Amey-Thakur/AI-SKILLS/skills/security/input-validation Skill

    14★ repo

    Validate untrusted input at every trust boundary with allowlists, canonicalization, and hard limits so malformed data never reaches logic. Use when accepting data from requests, files, uploads, or third-party APIs.

  • Security code review

    Amey-Thakur/AI-SKILLS/skills/security/security-code-review Skill

    14★ repo

    Read a diff for security by tracing attacker-controlled input to dangerous operations and checking every trust boundary it crosses. Use when reviewing code that handles input, queries, files, output rendering, or authorization.

  • Security review

    Amey-Thakur/AI-SKILLS/skills/security/security-review Skill

    14★ repo

    Review code for the vulnerabilities that actually get exploited, ranked by real risk with concrete attack scenarios. Use when reviewing changes that touch input handling, auth, secrets, files, queries, or network calls.

  • Unsafe code review

    Amey-Thakur/AI-SKILLS/skills/systems-languages/unsafe-code-review Skill

    14★ repo

    Audit unsafe blocks by verifying documented invariants, minimizing surface, and testing under sanitizers and Miri. Use when reviewing unsafe Rust, C/C++ interop shims, or any code that bypasses language safety.

  • Contract testing

    Amey-Thakur/AI-SKILLS/skills/testing/contract-testing Skill

    14★ repo

    Verify a service boundary with a consumer-driven contract that records the payload the caller actually reads and that both sides check in CI. Use when two services deploy independently and an unannounced response change would silently break the consumer.

  • Pact verification

    Amey-Thakur/AI-SKILLS/skills/testing/pact-verification Skill

    14★ repo

    Verify a provider against its consumers' recorded pacts in CI so a breaking API change fails before it ships. Use when independently deployed services share an HTTP contract and you want to catch breaks without end-to-end staging.

  • Test review

    Amey-Thakur/AI-SKILLS/skills/testing/test-review Skill

    14★ repo

    Review tests with the same rigor as production code, checking that assertions truly constrain behavior, that error and edge cases exist, and that no safety was quietly deleted. Use when reviewing a pull request that adds, changes, or removes tests.

  • Grill

    ngocsangyem/MeowKit/.claude/skills/grill Skill

    14★ repo

    Relentlessly interview the user about THEIR plan or design — one question at a time — resolving each branch of a decision tree until shared understanding. Claude is the interviewer; the user is the interviewee. Triggers on "grill me", "stress-test this plan", "get grilled on my design", "interrogate my plan". Checkpoints every answer to docs/knowledge/<slug>.md so progress survives a context-window reset. Flags knowledge the user cannot answer as a gap to chase. Do NOT use to PROPOSE solutions or compare approaches (→ mk:brainstorming). Do NOT use to validate "is this worth building?" (→ mk:office-hours). Do NOT use when Claude should ANSWER questions about the repo (→ mk:ask-me). Do NOT use for a one-shot review of an existing plan (→ mk:plan-ceo-review). Do NOT use to apply named reasoning lenses to findings (→ mk:elicit).

  • Improve codebase architecture

    ngocsangyem/MeowKit/.claude/skills/improve-codebase-architecture Skill

    14★ repo

    Use when surfacing architectural friction and proposing deepening refactors (shallow modules → deep modules) for testability and AI-navigability. Triggers on "improve architecture", "find deepening opportunities", "where is this codebase shallow", "architecture review". Emits structured candidates + precise patches; delegates ALL rendering to mk:preview. NOT for diagram/HTML rendering (see mk:preview); NOT for trade-off deliberation (see mk:party); NOT for plan critique (see mk:plan-ceo-review).

  • Jira dev

    ngocsangyem/MeowKit/.claude/skills/jira-dev Skill

    14★ repo

    Generate developer artifacts from Jira tickets via the jira-as wrapper: branch names, PR descriptions, parsed commits, commit/PR-to-issue links. Triggers: 'branch name for KEY', 'PR description for KEY', 'parse commits for issue keys', 'link PR to KEY'. NOT for executing git/gh commands directly (mk:ship); NOT for issue CRUD (mk:jira-issue).

  • Lint and validate

    ngocsangyem/MeowKit/.claude/skills/lint-and-validate Skill

    14★ repo

    Automatic quality control, linting, and static analysis after code modifications. Triggers on: lint, format, check, validate, types, static analysis. NOT for full build verification (see mk:verify); NOT for test coverage (see mk:testing).

  • Loop

    ngocsangyem/MeowKit/.claude/skills/loop Skill

    14★ repo

    Use when autonomously improving a measurable scalar metric through bounded, git-tracked iterations: modify one scoped change, verify, keep or revert. Triggers on /mk:loop, 'optimize coverage/bundle size/lint count', 'iterate until the metric improves'. NOT for subjective cleanup (see mk:cook), known-root-cause bugs (see mk:fix), behavioral grading (see mk:evaluate), or shipping (see mk:ship).

  • Plan ceo review

    ngocsangyem/MeowKit/.claude/skills/plan-ceo-review Skill

    14★ 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. Use AFTER a plan exists. For validating the idea itself before planning, use /mk:office-hours first.

  • Preview

    ngocsangyem/MeowKit/.claude/skills/preview Skill

    14★ repo

    Use when generating visual artifacts — explanations, diagrams, slides, or diff visualizations. Triggers on "explain X visually", "diagram this", "show as slides", "diff against main". NOT for rendering a plan as HTML (see mk:visual-plan), live media generation (see mk:multimodal), browser QA (see mk:qa), or plan critique (see mk:plan-ceo-review).

  • Resolving merge conflicts

    ngocsangyem/MeowKit/.claude/skills/resolving-merge-conflicts Skill

    14★ repo

    Resolve an in-progress git merge or rebase conflict end to end: read the conflict state, recover each side's original intent, resolve every hunk, run the project's checks, and prepare the merge/rebase for an explicitly approved finish. Use when asked to "resolve merge conflicts", "fix this rebase", "finish the merge", or when `git status` shows conflicted (unmerged) paths. NOT for the full ship pipeline that merges the base branch first (see mk:ship); NOT for debugging a runtime bug or test failure unrelated to a conflict (see mk:investigate / mk:fix).

  • Respond pr

    ngocsangyem/MeowKit/.claude/skills/respond-pr Skill

    14★ repo

    Triage reviewer comments on a GitHub PR with receiving-code-review discipline — verify each against the codebase, then accept/push-back/clarify, and optionally reply in-thread. Use when responding to received PR feedback. NOT for giving a review (see mk:review-pr); NOT for implementing the fixes (hand off to mk:fix).

  • Review pr

    ngocsangyem/MeowKit/.claude/skills/review-pr Skill

    14★ repo

    Reviews a GitHub PR with a single shallow correctness/security/breaking/AI-slop checklist and emits a verdict; optionally posts it via gh pr review. Use to review an external or teammate PR. NOT for deep pre-landing audit of your own diff (see mk:review); NOT for responding to received review comments (see mk:respond-pr).

  • Review

    ngocsangyem/MeowKit/.claude/skills/review Skill

    14★ repo

    Multi-pass structural code review with adversarial analysis, scope-aware dispatch, adversarial persona passes, and forced-finding protocol. Supports input modes: branch diff (default), PR number (#123), commit hash, pending changes (--pending). Use when asked to "review this PR", "code review", "pre-landing review", "check my diff", or "review #123". Proactively suggest when the user is about to merge or land code changes. NOT for behavioral verification against a running build (see mk:evaluate); NOT for post-implementation simplification (see mk:simplify).

  • Verify

    ngocsangyem/MeowKit/.claude/skills/verify Skill

    14★ repo

    Unified verification: build→lint→test→type-check→coverage. Use for 'is everything green', 'run all checks', 'verify build'. Auto-called by mk:cook. NOT for lint/format only (see mk:lint-and-validate); NOT for test-to-requirement coverage mapping (see mk:nyquist).

  • Visual plan

    ngocsangyem/MeowKit/.claude/skills/visual-plan Skill

    14★ repo

    Use when a plan directory (plan.md + phase-*.md) needs a visual review. By DEFAULT this drives the STRUCTURED visual-plan artifact (visual-plan/plan.json) via the mewkit visual-plan CLI — generate if absent, validate, open the local studio (view/edit), and export plan.html from the approved artifact. Pass --static for the legacy prompt-only single-file plan.html template render. Triggers on "render this plan", "visualize the plan", "open the plan studio", "make a shareable plan page", "plan.html". This is the canonical owner of plan-as-visual-review. NOT for plan critique or scope review (see mk:plan-ceo-review / mk:validate-plan), NOT for generic code/diagram/diff visuals (see mk:preview), NOT for live media generation (see mk:multimodal).

  • Mk grill

    ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/codex/root/.agents/skills/mk-grill Skill

    14★ repo

    Relentlessly interview the user about THEIR plan, one question at a time, until shared understanding. Checkpoints answers so progress survives a reset. Do NOT use to propose solutions.

  • Mk improve codebase architecture

    ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/codex/root/.agents/skills/mk-improve-codebase-architecture Skill

    14★ repo

    Surfaces architectural friction and proposes deepening refactors (shallow to deep modules). Renders via mk:preview. NOT for debate (mk:party); NOT for plan critique (mk:plan-ceo-review).

  • Mk jira dev

    ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/codex/root/.agents/skills/mk-jira-dev Skill

    14★ repo

    Generate dev artifacts from Jira tickets via jira-as: branch names, PR descriptions, parsed commits, PR-to-issue links. NOT running git/gh (mk:ship) or issue CRUD (mk:jira-issue).

  • Mk lint and validate

    ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/codex/root/.agents/skills/mk-lint-and-validate Skill

    14★ repo

    Linting and static analysis after code edits. Triggers on lint, format, check, validate, types. NOT for full build verification (mk:verify) or test coverage (mk:testing).