agentsclimarketplace

Review & quality

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

  • Pr review merge

    bjcoombs/ai-native-toolkit/skills/pr-review-merge Skill

    30★ repo

    Drive a single pull request to merge-ready across all five criteria (sync, CI, inline comments, conversation, threads), then smart-merge it. Source-agnostic library skill invoked by the /tm, /issues, /fix-pr, and /fix-develop commands and by marathon teammates. TRIGGER when a command or agent needs the PR review-to-green loop or the smart-merge (stale-bot-CR dismissal, auto-merge criteria, UNSTABLE/UNKNOWN handling, merge ordering), or when the user asks to take a PR to green/merge it.

  • Agent loops

    NickCrew/Claude-Cortex/skills/agent-loops Skill

    30★ repo

    Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Drives all work through atomic commits — each loop operates on the smallest complete, reviewable change. Defines the Code Change Loop, Test Writing Loop, Lint Gate, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Requires `cortex git commit` for all commits. Includes bundled provider-aware review scripts that keep same-model shell-outs as the last resort, plus a fresh-context Codex fallback for code review and test audit. Use this skill when starting any implementation task.

  • Ai tells review

    NickCrew/Claude-Cortex/skills/ai-tells-review Skill

    30★ repo

    Use when public prose still sounds machine-written after ai-tells-scan. Complements ai-tells-scan's mechanical pass with structural judgment: rhythm, hedging, rhetorical reflexes, and performative emphasis. Trigger on 'review for AI tells,' 'does this read AI,' 'strip the AI smell,' or 'make this less AI.'

  • Atomic commits

    NickCrew/Claude-Cortex/skills/atomic-commits Skill

    30★ repo

    Use this skill when a working tree contains uncommitted changes that need to be split into a sequence of atomic commits — typically after a long session, an agent hand-off, a rebase resolution, or anytime `git status` shows mixed work that was not committed as it landed. The skill assumes the agent has fresh context and did not author most of the diff, so it treats the working tree as evidence to investigate before grouping. Optimizes for `git bisect`: each commit is the smallest buildable and deployable unit, and no smaller. Uses `cortex git commit` for file-level commits and `cortex git patch --diff` when unrelated changes share a file.

  • Codex code review

    NickCrew/Claude-Cortex/skills/codex-code-review Skill

    30★ repo

    Automate code review remediation loops with the codex CLI. Requests reviews from codex, classifies findings by severity (P0-P4), fixes critical issues (P0/P1) through iterative cycles, defers quality improvements to backlog, and escalates after 3 review cycles. Use when working with code that needs structured remediation: 'codex review' in a request triggers this workflow.

  • Design critiquer

    NickCrew/Claude-Cortex/skills/design-critiquer Skill

    30★ repo

    Use this skill when reviewing, evaluating, or giving structured feedback on UI designs, wireframes, mockups, or design systems. Trigger phrases: 'critique this design', 'give feedback on my UI', 'review this wireframe', 'what's wrong with this design'. Do NOT use for writing code, implementing designs, or marketing material critique.

  • Design journey review

    NickCrew/Claude-Cortex/skills/design-journey-review Skill

    30★ repo

    Combined visual design and user journey review: color systems, typography, spacing, information density, visual hierarchy, workflow stages, emotional curve, friction points, and daily-use optimization. Use when evaluating how an interface looks, how it serves its user over time, and whether the design earns its space.

  • Doc architecture review

    NickCrew/Claude-Cortex/skills/doc-architecture-review Skill

    30★ repo

    Evaluate documentation information architecture: navigation paths, discoverability, progressive disclosure, cross-linking, and mental model alignment. This skill should be used when restructuring docs, adding new sections, or when users report difficulty finding information.

  • Doc claim validator

    NickCrew/Claude-Cortex/skills/doc-claim-validator Skill

    30★ repo

    Validate that claims in documentation match codebase reality. Extracts verifiable assertions (file paths, commands, function references, behavioral claims, dependencies) from markdown docs and checks them against the actual project. Use after code changes, before releases, or when docs feel untrustworthy.

  • Doc maintenance

    NickCrew/Claude-Cortex/skills/doc-maintenance Skill

    30★ repo

    Systematic documentation audit and maintenance. This skill should be used when documentation may be stale, missing, or misorganized — after feature work, refactors, dependency upgrades, or as a periodic health check. It prescribes folder structure for docs/ and manual/, dispatches haiku subagents for codebase/doc scanning, and routes doc creation to specialized agents (reference-builder, technical-writer, learning-guide) with docs-architect as quality gate.

  • Doc quality review

    NickCrew/Claude-Cortex/skills/doc-quality-review Skill

    30★ repo

    Assess documentation quality across readability, consistency, audience fit, and prose clarity. Produces a scored review with actionable findings. This skill should be used before releases, during doc reviews, or when documentation feels unclear or inconsistent.

  • Fact checker

    NickCrew/Claude-Cortex/skills/fact-checker Skill

    30★ repo

    Use this skill when verifying factual claims, checking accuracy of statements, or assessing the credibility of information. Trigger phrases: 'fact-check this', 'is this true', 'verify this claim', 'check if this is accurate'. Do NOT use for subjective opinions, legal or medical advice, or claims requiring real-time data or breaking news.

  • Finishing a development branch

    NickCrew/Claude-Cortex/skills/finishing-a-development-branch Skill

    30★ 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

  • Git ops

    NickCrew/Claude-Cortex/skills/git-ops Skill

    30★ repo

    Use when performing git operations or generating smart commit messages - provides safe git workflow guidance, validation checks, and conventional commit formatting.

  • Html seo review

    NickCrew/Claude-Cortex/skills/html-seo-review Skill

    30★ repo

    Audit static HTML files for on-page SEO, content quality, easy-win performance signals, and crawlability. This skill should be used when the user asks to review, audit, or check the SEO of one or more static HTML files — e.g., "review the HTML for SEO issues", "audit this landing page", "check SEO on these pages before I publish". Static HTML only — does not cover Jekyll/Hugo/Astro/Next.js source, off-page factors, or live-rendered Core Web Vitals.

  • Multi specialist review

    NickCrew/Claude-Cortex/skills/multi-specialist-review Skill

    30★ repo

    User-triggered multi-agent code review. Spawns 3-5 parallel specialist sub-agents that read actual source files, runs mechanical citation verification, and synthesizes a single review artifact. Use for PR-level changes, multi-commit ranges, or security-sensitive work where single-turn review is insufficient.

  • Receiving code review

    NickCrew/Claude-Cortex/skills/receiving-code-review Skill

    30★ 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

  • Requesting code review

    NickCrew/Claude-Cortex/skills/requesting-code-review Skill

    30★ repo

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches code-reviewer subagent to review implementation against plan or requirements before proceeding

  • Sharing skills

    NickCrew/Claude-Cortex/skills/sharing-skills Skill

    30★ repo

    Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository

  • Test review

    NickCrew/Claude-Cortex/skills/test-review Skill

    30★ repo

    Review test quality and audit test coverage for any module. This skill should be used when reviewing existing tests, auditing test gaps, writing new tests, or when asked to assess test health. It pipelines testing standards into the audit workflow to produce a prioritized gap report. The output is a report, not code — do not write test implementations until the report is reviewed.

  • Ui ux review suite

    NickCrew/Claude-Cortex/skills/ui-ux-review-suite Skill

    30★ repo

    User-triggered orchestrator that runs a comprehensive UI/UX review by coaching the user through four sibling skills as distinct lenses against one shared target, then synthesizing their findings into a single prioritized report. Composes user-journey-mapping (flow/funnel lens), ui-design-aesthetics (visual critique lens), interaction-design (state-coverage lens), and ux-review (usability-heuristics + WCAG lens). Resolves the review target once at suite start — the app/URL, the screens or flows under review, the viewports, and the user persona/goal — so every lens inherits the same scope and captured screenshots. Coaches rather than auto-runs — at each step it presents the next lens with its reframing prompt and an approval gate; the user invokes the sibling and confirms before moving on. Because the lenses overlap (ux-review already touches interaction and a11y), the suite scopes each lens to its distinct concern so the synthesis does not double-count. Produces one authored synthesis report — deduped findings grouped by severity and lens — not a navigation shell. Trigger on "run a full UX review," "comprehensive UI/UX review," "review this screen across all lenses," "do a complete design review," or when the user names two-or-more UI/UX lenses to coordinate. Not for running a single lens in isolation (invoke it directly), not for generating new UI (the generative siblings are reframed as critique here), and not for bypassing approval gates (this skill coaches, never autoruns).

  • Using git worktrees

    NickCrew/Claude-Cortex/skills/using-git-worktrees Skill

    30★ repo

    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

  • Ux interaction review

    NickCrew/Claude-Cortex/skills/ux-interaction-review Skill

    30★ repo

    Combined UX and interaction design review: usability heuristics, state coverage, feedback patterns, timing, keyboard behavior, error recovery, and progressive disclosure. Use when reviewing how an interface works mechanically and whether interactions are well-designed for use.

  • Ux review

    NickCrew/Claude-Cortex/skills/ux-review Skill

    30★ repo

    Multi-perspective UX review combining usability heuristics, WCAG accessibility checks, and interaction design analysis. Use when reviewing UI components before release, evaluating user flows for usability issues, conducting design critiques, or auditing accessibility compliance.

  • Verification before completion

    NickCrew/Claude-Cortex/skills/verification-before-completion Skill

    30★ 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

  • Wiring audit

    NickCrew/Claude-Cortex/skills/wiring-audit Skill

    30★ repo

    User-triggered audit that finds wiring drift between a project's UI surfaces and backend capabilities — orphan surfaces (UI calls endpoints/hooks/procedures that no longer exist), unwired capabilities (backend routes/exports that nothing surfaces), shape drift (both exist but contracts mismatch), method drift (URL matches, HTTP verb does not), validation drift (frontend vs backend rules diverged), permission drift (UI exposes what backend forbids or vice versa), stale labels (UI text references renamed backend concepts), and unsurfaced configuration (env vars or flags that gate behavior with no UI or CLI to control them). This skill should be used when the user asks to "audit our wiring," "find UI/backend drift," "find unwired capabilities," "find stale surfaces," "check for contract violations," "find unused endpoints," "find unused hooks," "what mismatches between UI and backend," or any similar request whose deliverable is a prioritized findings report rather than a descriptive snapshot. Generic across UI frameworks but optimized for React applications (hooks, fetch, react-query, SWR, tRPC, server actions, react-router, Next.js). Not for descriptive architectural snapshots (use architectural-analysis), security audits (use security-auditor), or performance audits (use the performance-optimization skills).

  • Constraint guided plan validator

    AnthonyAlcaraz/agentic-graph-rag-skills/skills/reasoning-planning/constraint-guided-plan-validator Skill

    30★ repo

    Validate a generated plan against extracted domain constraints AND the agent's capability model before execution (Ch5 Constraint-guided planning, Example 5-14, plus the DevOps hypothesis-formation capability filter). Scores the plan 0..1, returns structured per-step feedback so a planning node can refine when the score falls below threshold, and filters steps the agent is not authorized to perform (e.g. a step needing write access when the agent holds read-only monitoring). Forbidden-action and capability violations are HARD — a plan the agent cannot legally execute does not pass regardless of score. Use in regulated or capability-bounded environments where plans must respect business rules and operational authority before any action runs. NOT for free-form creative tasks with no constraints, NOT for validating execution results after the fact (this gates the plan, not the outcome), NOT as the constraint extractor itself (it consumes extracted constraints).

  • Loop pipeline router

    AnthonyAlcaraz/agentic-graph-rag-skills/skills/reasoning-planning/loop-pipeline-router Skill

    30★ repo

    The conditional-edge routing that turns a validate node into a bounded self-correcting loop (Ch5 Loop Pipeline + Error-handling strategies, Examples 5-6/5-9). Consumes a validation result, an error severity (correctable vs fundamental), and a retry budget, and returns exactly one of: proceed, refine (loop back with a remaining retry), fallback (alternative strategy once retries are exhausted), or terminate-with-partial (fundamental error). The finite retry budget is the explicit bound that prevents infinite loops. Use when first-attempt success is unrealistic and validation can identify correctable errors — plan refinement, documentation-gap re-requests, transient-failure recovery. NOT for strict sequential pipelines with no feedback (use a sequential pipeline), NOT for parallel branch reconciliation (that is a merge/tree concern), NOT as a substitute for the validator itself (this routes on the validator's output; it does not validate).

  • Graduated validation protocol

    AnthonyAlcaraz/agentic-graph-rag-skills/skills/self-evolution/graduated-validation-protocol Skill

    30★ repo

    The Ch7 safety envelope for a self-evolving agent: the RPO spine (Recursion, Provenance, Optimization) plus the Graduated Validation Protocol that gates what reaches production. Assigns every candidate change a risk tier and applies the matching scrutiny: Tier 1 canary (1% traffic, automatic rollback), Tier 2 staging gauntlet (multi-objective utility, passes only net-positive with no safety regression), Tier 3 airlock (sandboxed risk/reward report escalated for human approve/reject/modify). Also the entropy-collapse guard (Kepler dual-store): daily garbage collection of agent-generated Learnings once promoted, contradicted, or idle past a 30-day TTL. Use to gate a continuous self-evolution loop before candidate changes reach users. NOT for a one-off manual deploy (a single approval gate is enough), NOT for the diagnosis / attribution / intervention steps that produce the candidate (this validates the candidate, it does not generate it).

  • Code review

    tt-a1i/matt-skills-with-to-goal/skills/code-review Skill

    30★ repo

    Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

    The same file is in 12 other repositories

  • Grill me

    tt-a1i/matt-skills-with-to-goal/skills/grill-me Skill

    30★ repo

    A relentless interview to sharpen a plan or design.

    The same file is in 19 other repositories

  • Grill with docs

    tt-a1i/matt-skills-with-to-goal/skills/grill-with-docs Skill

    30★ repo

    A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

    The same file is in 19 other repositories

  • Prototype

    tt-a1i/matt-skills-with-to-goal/skills/prototype Skill

    30★ repo

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

    The same file is in 6 other repositories

  • Resolving merge conflicts

    tt-a1i/matt-skills-with-to-goal/skills/resolving-merge-conflicts Skill

    30★ repo

    Use when you need to resolve an in-progress git merge/rebase conflict.

    The same file is in 11 other repositories

  • Ad security reviewer

    saeed-vayghan/gemini-agent-skills/.gemini/skills/ad-security-reviewer Skill

    30★ repo

    Active Directory security specialist analyzing identity configuration, privileged group design, delegation, authentication policies, legacy protocols, and attack-surface exposure across enterprise domains.

  • Architect reviewer

    saeed-vayghan/gemini-agent-skills/.gemini/skills/architect-reviewer Skill

    30★ repo

    Expert architecture reviewer specializing in system design validation, architectural patterns, and technical decision assessment. Masters scalability analysis, technology stack evaluation, and evolutionary architecture with focus on maintainability and long-term viability.

  • Code reviewer

    saeed-vayghan/gemini-agent-skills/.gemini/skills/code-reviewer Skill

    30★ repo

    Expert code reviewer specializing in code quality, security vulnerabilities, and best practices across multiple languages. Masters static analysis, design patterns, and performance optimization with focus on maintainability and technical debt reduction.

  • Git workflow manager

    saeed-vayghan/gemini-agent-skills/.gemini/skills/git-workflow-manager Skill

    30★ repo

    Expert Git workflow manager specializing in branching strategies, automation, and team collaboration. Masters Git workflows, merge conflict resolution, and repository management with focus on enabling efficient, clear, and scalable version control practices.

  • Eks operation review

    aws-samples/sample-devops-agent-tools/skills/eks-operation-review Skill

    30★ repo

    Comprehensive Amazon EKS operational review aligned with the AWS EKS Best Practices Guide. Use this skill when a user asks to review, audit, or assess EKS clusters for best practices compliance, operational readiness, security posture, cost optimization, reliability, networking, scalability, or upgrade readiness. Triggers on requests like "EKS review", "EKS best practices audit", "EKS operational assessment", "review my EKS cluster", or "EKS health check".

  • Rds operation review

    aws-samples/sample-devops-agent-tools/skills/rds-operation-review Skill

    30★ repo

    Comprehensive Amazon RDS and Aurora operational review aligned with the AWS Well-Architected Framework and RDS/Aurora best practices. Use this skill when a user asks to review, audit, or assess RDS instances or Aurora clusters for best practices compliance, security posture, reliability, performance, cost optimization, backups, encryption, or operational readiness. Triggers on requests like "RDS review", "Aurora best practices audit", "database operational assessment", "review my RDS instance", "RDS health check", or "ORR for RDS".

  • Service quota check

    aws-samples/sample-devops-agent-tools/skills/service-quota-check Skill

    30★ repo

    Use this skill during any incident investigation, capacity planning, or operational troubleshooting when the issue may be caused by hitting AWS service limits. Activate when you observe throttling errors (ThrottlingException, TooManyRequestsException, LimitExceededException), resource creation failures, capacity-related alarms, or when a recommendation involves provisioning new AWS resources.

  • Recipe front review

    shinpr/codex-workflows/.agents/skills/recipe-front-review Skill

    30★ repo

    Frontend Design Doc compliance and security validation with optional auto-fixes using React-specific quality checks.

  • Recipe review

    shinpr/codex-workflows/.agents/skills/recipe-review Skill

    30★ repo

    Design Doc compliance and security validation with optional auto-fixes.

  • Superpowers git worktrees

    ItamarZand88/awesome-agent-conventions/conventions/skill-md/examples/dev-tooling/superpowers-git-worktrees Skill

    30★ repo

    A curated guide to convention files AI agents read, write, and act on: AGENTS.md, CLAUDE.md, SKILL.md, llms.txt, MCP configs, rules, and examples.

  • Superpowers requesting code review

    ItamarZand88/awesome-agent-conventions/conventions/skill-md/examples/dev-tooling/superpowers-requesting-code-review Skill

    30★ repo

    A curated guide to convention files AI agents read, write, and act on: AGENTS.md, CLAUDE.md, SKILL.md, llms.txt, MCP configs, rules, and examples.

  • Wshobson git advanced workflows

    ItamarZand88/awesome-agent-conventions/conventions/skill-md/examples/dev-tooling/wshobson-git-advanced-workflows Skill

    30★ repo

    A curated guide to convention files AI agents read, write, and act on: AGENTS.md, CLAUDE.md, SKILL.md, llms.txt, MCP configs, rules, and examples.

  • Deck review

    lool-ventures/founder-skills/founder-skills/skills/deck-review Skill

    29★ repo

    AI agent skills for high-velocity startup founders

    The same file is in 1 other repository

  • Financial model review

    lool-ventures/founder-skills/founder-skills/skills/financial-model-review Skill

    29★ repo

    AI agent skills for high-velocity startup founders

    The same file is in 1 other repository

  • Issue review

    DennisLiuCk/claude-plugin-marketplace/plugins/issue-review/skills/issue-review Skill

    no license29★ repo

    系統化的問題分析專家技能,自動協調五個專門代理進行深度問題分析。 適用於: - 使用者或 PM 報告的線上問題 - 開發團隊反映的技術問題 - 測試發現的 bug - 生產環境告警和異常

    The same file is in 6 other repositories

  • Wp ci qa

    mralaminahamed/wp-dev-skills/skills/wp-ci-qa Skill

    29★ repo

    Use when a pull request has QA failures, a "Testing Failed" label, or QA comments reporting broken features — reading QA feedback and PR comments, tracing root cause using root-cause-patterns.md, applying scoped conventional-commit fixes, swapping labels (Testing Failed to Need Testing), and posting a structured QA re-test comment. Triggers: "QA failed my PR", "Testing Failed label on my PR", "fix the QA comments on PR", "QA says feature X is broken", "post a re-test comment", "how do I respond to QA feedback", "CI is failing on my PR", "QA reopened the ticket", "update the PR label after fixing", "testing failed label", "QA comment says the button is broken", "phpcs failing in CI", "yarn lint error on the PR", "npm run build failing in CI", "root cause of the QA failure", "write a re-test instruction comment", "fix failing checks on this PR", "QA triage workflow", "phpcs prints nothing and exits 0", "composer run test produces no output", "phpstan workers keep crashing", "did my static checks actually run", "how do I tell a real pass from a broken tool", "compare test failures before and after my change". Not for: writing new features or opening a fresh PR — use `wp-github-flow`.

  • Wp freemius

    mralaminahamed/wp-dev-skills/skills/wp-freemius Skill

    29★ repo

    Use when integrating Freemius SDK into a WordPress plugin for monetisation — SDK bootstrap with fs_dynamic_init, feature gating with can_use_premium_code() / is__premium_only() / is_plan() / is_trial() / is_paying(), license management, free/pro dual-zip build using __premium_only__ file suffix, generating upgrade URLs with get_upgrade_url(), opt-in analytics dialog, multisite licensing, affiliate program, or debugging Freemius dashboard (Plans, Pricing, Licenses, Updates). Triggers: "add Freemius to my plugin", "gate this feature behind pro", "show the pricing page", "check if user has a license", "Freemius not initialising", "can_use_premium_code()", "is_plan()", "is_trial()", "is_paying()", "fs_dynamic_init", "my_plugin_fs()", "__premium_only__ file", "set up free and pro versions", "Freemius opt-in dialog", "trial period setup", "license key validation", "monetise my plugin", "get_upgrade_url()", "Freemius affiliate", "is_org_compliant", "Freemius SDK error", "free and premium zip", "Freemius multisite", "Freemius GlotPress translations". Not for: WooCommerce payments — use `wp-woocommerce`; WP.org trialware compliance — use `wp-org-submission`.

  • Wp github flow

    mralaminahamed/wp-dev-skills/skills/wp-github-flow Skill

    29★ repo

    Use when shipping work through GitHub — fixing a GitHub issue by URL/number, or committing and PR-ing uncommitted working-tree changes. Covers resolving ISSUE_REPO vs CODE_REPO, grouping changes into scoped conventional commits (type(scope): summary), branching from fresh origin/base, discovering labels via gh label list, opening PRs with gh pr create, cross-repo Closes footer, merging with --merge (never --squash), and re-syncing after merge. Triggers: "commit my changes", "commit scope by scope", "create a branch and PR", "open a PR for these changes", "fix issue #NNN", "debug this GitHub issue", "group my changes into commits", "push and open a PR", "what branch should I use", "conventional commit for this change", "close this issue with a PR", "write a PR description", "gh pr create", "gh issue view", "Closes footer", "branch name for this fix", "gh label list", "bugfix branch", "cross-repo close", "ISSUE_REPO vs CODE_REPO", "stale remote origin", "PR body template", "merge the open PR", "re-sync after merge", "sequential PRs". Not for: plugin version releases — use `wp-plugin-release`; WP.org SVN — use `wp-org-submission`.

  • Wp org submission

    mralaminahamed/wp-dev-skills/skills/wp-org-submission Skill

    29★ repo

    Use when submitting a WordPress plugin to the WP.org directory for the first time, deploying a new version via SVN (plugins.svn.wordpress.org trunk, tags, assets), fixing a reviewer rejection (17-issue catalog with exact reviewer quotes), writing or correcting readme.txt (Stable tag, Changelog, Upgrade Notice, Requires, Tested up to, External services), or preparing WP.org assets (banner-772x250.png, banner-1544x500.png, icon-128x128.png, icon-256x256.png, icon.svg, screenshot-N.png). Triggers: "submit my plugin to WP.org", "SVN deploy", "reviewer rejected my plugin", "fix WP.org review feedback", "how do I set up the SVN repo", "WP.org assets", "prepare my plugin for the directory", "what does the reviewer want", "Stable tag", "readme.txt requirements", "WP.org banner dimensions", "fix this reviewer comment", "plugin zip for submission", "svn commit trunk", "svn cp trunk tags", "reviewer says missing nonce", "reviewer says not prefixed", "reviewer says missing sanitization", "Upgrade Notice section", "External services section in readme", "submit.wordpress.org form", "icon.svg for WP.org". For WP.org guideline compliance review only, use `wp-plugin-directory-guidelines` instead.

  • Wp plugin audit

    mralaminahamed/wp-dev-skills/skills/wp-plugin-audit Skill

    29★ repo

    Use when auditing a WordPress plugin for security issues, code inconsistencies, or quality gaps — fans out parallel checks across four dimensions: A (version/metadata sync), B (naming/prefix/i18n), C (docs vs code), D (code conventions/security), verifies every finding with file:line references before reporting, and routes confirmed issues to the correct fix skill. Security patterns checked: XSS (missing esc_html/esc_attr), SQL injection (raw $wpdb), CSRF (missing nonce), missing capability checks, file upload validation, object unserialize, open redirect, path traversal, REST auth hardening. Triggers: "audit this plugin", "find inconsistencies in my plugin", "security review", "check my plugin for XSS", "is my escaping correct", "find missing nonces", "check capabilities in my plugin", "audit readme.txt", "find security issues", "plugin quality sweep", "are there SQL injection risks", "review my plugin before submission", "missing esc_html()", "raw wpdb query without prepare()", "missing current_user_can()", "unprotected AJAX handler", "plugin prefix inconsistency", "version out of sync", "i18n audit", "missing translator comment", "file upload not validated", "open redirect risk". Not for: PHPStan type analysis — use `wp-phpstan`; WP.org pre-submission checklist — use `wp-org-submission`.

  • Agami save correction

    AgamiAI/agami-core/plugins/agami/skills/agami-save-correction Skill

    no license29★ repo

    The trust layer between AI and your data. Turns your database schema - messy joins, undocumented tables, into a governed semantic model so AI answers with correct SQL and a receipt on every answer. Run it locally, or self-host a shared team server with Docker.

  • Doubt driven review

    pimenov/codex-first-skills-pack/skills/doubt-driven-review Skill

    no license29★ repo

    Runs an adversarial review gate for non-trivial or high-stakes decisions before they stand. Use when Codex is about to claim something is safe, correct, reversible, production-ready, scalable, idempotent, secure, or compliant; when work touches production, auth, permissions, secrets, billing, public APIs, migrations, irreversible cleanup, customer data, external agent CLIs, or unfamiliar code with meaningful blast radius; or when a confident answer would be cheaper to challenge now than to debug later.

  • Test driven development

    pimenov/codex-first-skills-pack/skills/test-driven-development Skill

    no license29★ repo

    Drives behavior changes through tests or explicit focused checks before implementation. Use when implementing new logic, fixing a bug, changing behavior, adding edge-case handling, modifying validation, refactoring behavior-sensitive code, or after debugging identifies a root cause that needs a regression guard. Also use when Codex is about to say a bug is fixed or behavior works but no proof exists yet.

  • Flag and release change

    launchdarkly/ai-tooling/skills/feature-flags/flag-and-release-change Skill

    no license29★ repo

    Drive a pull request's change end to end: decide it's flag-worthy, create the guarding flag, wire the new code path behind it on the PR branch, and record an automated release so the change ships safely when the PR merges. A portable orchestrator that composes should-flag-change, launchdarkly-flag-create, and flag-release. Keywords: flag a PR, wrap change in a flag, dark launch, kill switch, auto-release, automated rollout, end-to-end flag workflow.

  • Product design review

    sanky369/vibe-building-skills/skills/product-design/product-design-review Skill

    29★ repo

    Run an evidence-based product design and UI/UX review of a digital product (web, mobile, desktop) — heuristic evaluation, task walkthroughs, visual and interaction critique, and WCAG 2.2 AA accessibility checks. Use when the user says 'review my app/page/site', 'critique this UI', 'something feels off', 'why are users dropping off', 'audit our onboarding/checkout/dashboard', 'is this usable/accessible', or shares a URL, screenshot, Figma link, or codebase and asks what to improve — even if they never say 'design review'. Produces a Design Review Report: executive summary, prioritized findings table with evidence and severity, flow walkthroughs, accessibility blockers, and next steps routed to the skill that fixes each category.

  • Ethereum Address Validator

    nirholas/ethereum-wallet-toolkit/io.github.nirholas/validation-mcp-server MCP server

    no license29★ repo

    Validate Ethereum addresses, keys, checksums, keccak256 hashes, function selectors, ENS