Review & quality
19,178 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
lantisprime/claude-sdlc/skills/domain-expert Skill
3★ repoUse this skill during /plan (between scope validation and writing the plan artifact) to inject domain-specific context, gap questions, and regulatory concerns into the plan. Triggers automatically when the plan skill evaluates the task and scope.md against the domain registry in domains/_index.json using semantic judgment — no keyword list required. Produces a ## Domain context section in the plan artifact. Also triggers when the human says "add domain context", "what are the domain concerns here", or "check domain rules".
lantisprime/claude-sdlc/skills/security-review Skill
3★ repoUse this skill to review code changes for security concerns before they merge. Covers input validation, authentication and authorization, secrets handling, injection surfaces (SQL, command, template, prompt), unsafe APIs and dependencies, sensitive data handling, and output encoding. Runs against the current diff (NOT the whole codebase) so findings stay relevant to the change at hand. Trigger proactively whenever the diff touches auth, routing, data access, user input, template rendering, external calls, or dependency files. Also runs as part of the /review and /ship commands.
broomva/skills/skills/cadence/drift-check Skill
3★ repoCompares stated priorities against where time and effort actually went, and produces a strategy drift report. Uses git log, vault priorities, and project docs to detect misalignment. Use when the user says "drift check", "am I on track", "priority alignment", "where did my time go", "strategy drift", or wants to audit focus vs intention.
broomva/skills/skills/cadence/weekly-review Skill
3★ repoScans the vault for updates from the past week, surfaces what changed, and flags what needs attention. Produces a structured weekly review. Use when the user says "weekly review", "week in review", "what happened this week", "weekly summary", "end of week review", or at the end of a work week.
broomva/skills/skills/governance/cross-review Skill
3★ repobstack P20 — Cross-Model Adversarial Review Gate. The model that wrote the code cannot be the final judge of the code. Before substantive PRs merge, fire a cross-model adversarial gate — different evaluator than writer, anti-slop scoring ≥7/10, max 3 fix rounds, verdict logged in PR. Three strata: (A) Codex CLI cross-vendor for true different-model verdict, (B) fresh-context subagent under devils-advocate brief, (C) composed existing adversarial-review skills always parallel. Use cross-review when: (1) about to push a substantive PR (>200 LOC OR public API OR multi-file OR governance-class), (2) reviewing a draft plan/design before implementation, (3) auditing a feature spec against single-model blind spots, (4) integrating with the /autonomous skill's pre-push gate. Triggers on 'cross-review', 'P20', 'adversarial review', 'anti-slop', 'cross-model gate', 'different evaluator', 'devils advocate gate', 'self-review prohibition'.
broomva/skills/skills/governance/dogfood Skill
3★ repoPer-bstack-P11 reflex 7+16 — explicitly trigger the Dogfood Plan + per-stack cookbook + Dogfood Receipt sequence. Auto-detects the tech stack from repo signals (Cargo.toml + src-tauri/ → tauri-sidecar; next.config.* → nextjs; app.json + expo → expo-rn; Cargo.toml solo → rust-cli; openapi.* or REST framework deps → rest-api; mcp.{json,yaml} → mcp-server), loads the matching cookbook entry from bstack/references/dogfood-patterns.md (broomva/bstack ≥ 0.13.0), produces a six-row Dogfood Plan (entry surface · driver · evidence · smoke · end-to-end · receipt anchor), optionally executes via the named surfaces (Interceptor mandatory for visual deploy verification; gstack, cliclick, screencapture, curl+jq, xcrun simctl compose per stack), and produces the final receipt with binary anti-rationalization check. Three subcommands: /dogfood (full sequence — plan → execute → receipt), /dogfood plan (plan only), /dogfood receipt (receipt only, assumes plan exists in PR body or AGENTS.md). Inherits from broomva/bstack: cookbook, P11 discipline, stack-detection algorithm. Composes with broomva/autonomous (which fires this implicitly at reflex 7+16) — use /dogfood directly for narrower scope (small changes, exploration, pre-merge verification gate without full pipeline). USE WHEN dogfood, dogfood this, dogfood plan, dogfood receipt, validate as user, exercise the change, click through the app, /dogfood, P11 receipt, exercise like a user would, did I actually click it, prove this works for a user, interaction evidence, deploy verification. NOT FOR running CI checks (use /p9), batch headless automation (use Browser skill), or scientific-method experiment framing (use Science skill).
broomva/skills/skills/orchestration/governed-autonomy-loop Skill
3★ repoTurn any work-queue + any enforcement pipeline into a self-driving, self-healing, human-minimal autonomy loop with a control-systems safety envelope. A prose-defined governor closes a feedback loop over the queue, drives isolated worktree arcs to Done, is metacognitive (defers when the runtime can't support the act, escalates only when genuinely blocked, self-heals when the block clears), and NEVER performs the irreversible act itself — it delegates every merge/deploy/publish to an isolated arc gated by adversarial review + a policy gate + a server-side aggregate check. The controller is a markdown prompt interpreted fresh each tick; a thin tested shell (tick.sh) only schedules, locks, and logs. The skill SCAFFOLDS + GOVERNS a new loop instance: the invariant spine stays fixed, four adapters (tracker / irreversible-act + enforcement / runtime / partition) are per-instance, the deterministic core (scheduler, in-flight fold, reseed gate, config + denylist validation) is extracted into tested scripts, and the latent decisions stay prose with scenario evals. Generalizes the proven broomva ticket-dispatch governor (BRO-1740 + BRO-1833). USE WHEN setting up an autonomous ticket/PR/deploy loop, standing up a governor that drives a queue unattended, building a self-merging arc pipeline, adding a metacognitive control loop over background agents, or the user says "governed autonomy loop", "autonomy loop", "self-driving loop", "ticket-dispatch governor", "loopcast", "loop-caster", "set up an autonomous governor". NOT FOR a single in-session autonomous task (use /autonomous), a one-shot background watcher (use P9 wait), or a cross-session single-agent restart loop with no queue (use P12 persist) — this is the external-trigger, across-session, queue-driven, irreversible-act-gated quadrant.
broomva/skills/skills/research/checkit Skill
3★ repoIngest-and-integrate an artifact someone points at with a terse, deliberately under-articulated directive — "check this out", "lets research this", "look into this", "wdyt" — followed by a URL, repo, paper, file, image, or pasted document. Infers the actual request from a fully-contextualized frame (who is asking + what they're working on + what's already known) WITHOUT bouncing a clarifying question back, then runs the pipeline: contextualize → deep research (verify every source) → analyze → connect → document the finding → suggest ranked next steps. The artifact ends up metabolized into knowledge and action, not left as a one-paragraph summary. Composes existing research/search/memory tools; it does not reimplement them. USE WHEN: check this out, checkit, /checkit, lets research this, research this, look into this, dig into this, wdyt, what do you think of this, found this, take a look + an artifact; or whenever an artifact is shared with an underspecified ask. NOT FOR: retrospective "what have I been doing repeatedly" (a discovery/look-back task); fully-specified artifact asks ("summarize this PDF in 3 bullets", "fix the bug in this file" — answer directly). Triggers on those phrases + a shared artifact.
broomva/skills/skills/strategy/strategy-critique Skill
3★ repoReads a strategy doc and writes a red-team critique with gaps, risks, and missing assumptions. Adopts an adversarial but constructive stance. Use when the user says "strategy critique", "red team this", "critique my strategy", "find the holes", "stress test this plan", "what am I missing", or provides a strategy document for review.
broomva/skills/skills/video/creative-review Skill
3★ repoMeta-review skill for validating generated creative assets (videos, images, designs) against a reference style brief. Extracts frames, compares against style criteria, scores adherence, and produces actionable feedback for iteration. Self-improving feedback loop: each review refines the style brief for the next generation. Use when: (1) reviewing a generated video against a reference style, (2) validating visual quality of AI-generated content, (3) scoring style adherence of a Remotion composition, (4) comparing before/after creative iterations, (5) building a self-improving creative pipeline. Triggers on: 'review video', 'check style', 'creative review', 'style adherence', 'compare to reference', 'validate video', 'review reel', 'quality check'.
aneja5/forge-skills/skills/code-review-and-quality Skill
3★ repoUse when a task is complete and ready for review, when reviewing a PR, when validating an implementation against its contract, when checking quality before merging, or when a five-axis quality gate is needed before approving code.
aneja5/forge-skills/skills/cross-validation Skill
3★ repoUse when user says "validate this", "get feedback", "cross-validate", "what are we missing", when seeking external review before committing to major decisions, when stress-testing a design with senior reviewers, or when reviewer responses need to be synthesized into actionable changes.
aneja5/forge-skills/skills/git-workflow Skill
3★ repoUse when committing work, creating branches, preparing PRs, resolving merge conflicts, when grouping related changes into commits, when cleaning up history before merging, or when deciding what should be a separate commit vs squashed.
TimboGP/timbogp-marketplace/plugin/lean-coach/skills/investor-pitch Skill
3★ repoThis skill should be used when the user wants to rehearse or stress-test a fundraising pitch — "play an investor", "let's practice my pitch", "be a skeptical VC and grill me", "pitch practice", "what would an investor ask?", "is my traction story convincing?", or prepping for an angel/seed meeting. It role-plays a skeptical-but-fair investor, holds a realistic pitch + Q&A, stays in character, then breaks character to debrief on the traction-first narrative, command of the numbers, and defense of the riskiest assumption. It can also just prep a pitch or critique a deck without role-play. Writes to .lean/pitch/.
Tanq16/claudex/skills/review-code Skill
no license3★ repoUse when reviewing existing code against development skill best practices — orchestrates multi-agent domain reviews for thoroughness
ProjAnvil/MindForge/skills/en/git-guru Skill
3★ repoExpert Git skills covering interactive rebase, worktree management, reflog recovery, bisect debugging, advanced workflows, commit message best practices, and clean history management. Use this skill when needing advanced Git operations, cleaning commit history, managing multiple worktrees, recovering lost commits, debugging with bisect, or implementing sophisticated Git workflows.
ProjAnvil/MindForge/skills/zh-cn/git-guru Skill
3★ repoGit 大师技能,涵盖交互式变基、工作树管理、reflog 恢复、bisect 调试、高级工作流、提交信息最佳实践和清晰的历史管理。使用此技能进行高级 Git 操作、清理提交历史、管理多个工作树、恢复丢失的提交、使用 bisect 调试或实现复杂的 Git 工作流时使用。
mryll/skills/skills/codex-review Skill
3★ repoIterative code review and planning discussion between the local agent and Codex CLI. Orchestrates an automatic back-and-forth debate where both agents discuss findings, architecture decisions, or implementation plans until reaching consensus. Codex CLI runs READ-ONLY and never modifies files; model and reasoning effort come from the user's local Codex config. Supports plan mode: when the local agent has a plan ready, Codex evaluates and iterates on it before implementation, producing an updated consensus plan. Use when the user asks to review with codex, analyze with codex, discuss code with codex, iterate with codex, consult codex, ask codex, review the plan with codex, validate plan with codex, or any Codex CLI request for code review, architecture review, plan review, or implementation strategy. Does NOT trigger on non-code topics like diet, fitness, writing, life decisions, or general strategy; use codex-discuss for those.
mryll/skills/skills/explain-pr Skill
3★ repoExplain a GitHub Pull Request (PR) or GitLab Merge Request (MR) to the user in plain, easy-to-understand language: WHAT was done, WHY/what for, and HOW — with the relevant code snippets embedded. Invoke this proactively and automatically right after creating or finishing a PR/MR (e.g. after running `gh pr create`, `glab mr create`, or pushing a branch and opening a PR/MR), even if the user did not explicitly ask for an explanation. Also use whenever the user asks to explain, summarize, walk through, recap, or 'tell me what you did' about a PR/MR or the changes in a branch. Works with any coding agent and relies on the local git diff, so it does NOT require gh/glab to function. Do NOT use for unrelated code reviews, bug hunting, or writing the PR/MR description itself — this skill only explains finished work back to the user.
weiting-tw/MAGI-System/skills/magi-review Skill
no license3★ repo三機(Claude/Gemini/Codex)平行審查代碼,評估邏輯、品質、安全漏洞後投票共識
blakecyze/kanso/skills/kanso-pr Skill
3★ repoUse when the user asks to write a pull request description, open a PR, draft PR notes, or summarise a branch for review.
edfenton/claude-skills/ios/ios-code-review Skill
3★ repoReview iOS code for compliance with standards, NFRs, and security policy.
edfenton/claude-skills/ios/ios-design-review Skill
3★ repoVisual design review of iOS screens against ios-styleguide.
edfenton/claude-skills/mern/mern-code-review Skill
3★ repoReview MERN code for compliance with standards, NFRs, and security policy.
edfenton/claude-skills/mern/mern-deps Skill
3★ repoCheck and update dependencies safely with security audits and test verification.
edfenton/claude-skills/mern/mern-design-review Skill
3★ repoVisual design review using Playwright screenshots against mern-styleguide.
edfenton/claude-skills/nean/nean-code-review Skill
3★ repoReview NEAN code for compliance with standards, NFRs, and security policy.
edfenton/claude-skills/nean/nean-deps Skill
3★ repoCheck and update dependencies safely with security audits and test verification.
edfenton/claude-skills/nean/nean-design-review Skill
3★ repoVisual design review using Playwright screenshots against nean-styleguide.
edfenton/claude-skills/shared/github-hooks Skill
3★ repoSet up local Git hooks for pre-commit validation (lint, format, tests, secrets). Integrates with mern-scaffold, nean-scaffold, and iOS projects.
edfenton/claude-skills/shared/github-merge-stack Skill
3★ repoMerge stacked feature branches from Ralph into main, preserving full feature history. Handles PR base updates, sequential squash merges, and branch cleanup.
edfenton/claude-skills/shared/shared-review-workflow Skill
3★ repoSeverity definitions, approval gate protocol, and fix constraints shared across all review and test skills.
bitwise-media-group/skills/plugins/python/skills/python-project Skill
3★ repoScaffold and modernize a Python project with uv. Sets up the src/ layout; a pyproject.toml on uv's native uv_build backend; runtime deps plus a dev dependency group (PEP 735) pinning developer tooling like ruff, ty (or pyright), and pytest; a committed uv.lock and pinned interpreter; a thin __main__ entry point; and a Makefile whose pr target runs the full local gate. Use when: creating a new Python project, package, library, or CLI with uv; creating or configuring a pyproject.toml; choosing a build backend (uv_build) or dependency layout; restructuring an existing repo to the src/ layout; migrating from pip/requirements.txt, poetry, or pipenv onto uv; setting up a dev dependency group or pinning Python dev tools (ruff, ty or pyright, pytest); or adding Makefile targets (pr, fmt, lint, typecheck, test, build) to a Python codebase. Not for writing functions, type hints, tests, or publishing to PyPI — those are separate Python skills.
bitwise-media-group/skills/plugins/python/skills/python-release Skill
3★ repoRelease engineering for Python projects on uv — static versioning in pyproject.toml exposed via importlib.metadata, building the sdist and wheel with uv build, publishing to PyPI with uv publish via Trusted Publishing (OIDC, no token), tag-triggered GitHub Actions releases, CI running ruff/ty (or pyright)/pytest with SHA-pinned actions, and Dependabot coverage for uv and Actions. Use when releasing or publishing a Python package to PyPI, running uv build to make a wheel and sdist, running uv publish, configuring Trusted Publishing or a tag-triggered release workflow, writing a GitHub Actions CI workflow that runs ruff format/ruff check/ty (or pyright)/pytest for a uv project, versioning a package, or adding Dependabot coverage for uv and GitHub Actions to a Python repo.
bitwise-media-group/skills/plugins/python/skills/python-style Skill
3★ repoModern Python house style: ruff is the single formatter and linter (replacing black, isort, flake8, pylint, pyupgrade) with an opinionated lint select set, plus idioms ruff cannot enforce — pathlib over os.path, module-level logging instead of print, specific chained exceptions, dataclasses for data, comprehensions and context managers. Use when formatting, linting, reviewing, or refactoring Python code or improving its idiomatic style; setting up, configuring, or running ruff (in pyproject.toml or replacing black/isort/flake8/pylint), or choosing which ruff lint rules to enable; converting print to logging, fixing exception handling, choosing pathlib vs os.path, or otherwise shaping errors, logging, file I/O, or data structures in Python. Not for type annotations, docstrings, tests, project/uv scaffolding, or non-Python languages.
bitwise-media-group/skills/plugins/python/skills/python-testing Skill
3★ repoPython test authoring and review with pytest. Use when writing, adding, generating, or reviewing Python tests or unit tests for a function, module, or class; running pytest or a single test (the -k flag and other invocation flags for a Makefile or CI); parametrizing test cases into the table-driven pattern; setting up pytest fixtures or using the built-in tmp_path, monkeypatch, or capsys; choosing between hand-written fakes and mock objects; asserting a function raises with pytest.raises; or adding property-based or fuzz tests to a Python parser, encoder, or validator with Hypothesis. Covers pytest conventions, fixtures, parametrization, fakes vs mocks, error-path testing, and Hypothesis property testing. Not for non-Python test frameworks (Jest, Go testing), type hints, ruff/linting, or scaffolding a project.
bitwise-media-group/skills/plugins/python/skills/python-typing Skill
3★ repoPython static typing and type annotations, checked with a static type checker — ty (Astral) or pyright (Microsoft/Pylance). Use when adding, writing, or reviewing type hints or annotations on Python functions, methods, parameters, or return values; adding return type annotations across a module; fixing or resolving Python type errors; making a function or class generic with a type parameter; modernizing hints to X | None instead of Optional, A | B instead of Union, and built-in list[]/dict[] generics; choosing between Protocol and ABC for an interface or using typing.Self and PEP 695 syntax; or setting up, configuring, or running ty or pyright under [tool.ty] or [tool.pyright] in pyproject.toml, migrating from mypy, and wiring a type-check step into the dev gate or CI. For Python code only — not TypeScript, Go, or other languages, not runtime isinstance checks, formatting, or test-writing.
bitwise-media-group/skills/plugins/terraform/skills/terraform-validate Skill
3★ repoFormat and validate Terraform code with the fmt / init / validate / tflint loop. Use after editing any .tf file, before committing Terraform changes, when asked to lint, format, validate, or check Terraform modules and root configurations, or when setting up tflint for a repository.
bitwise-media-group/skills/plugins/workflow/skills/workflow-commit Skill
3★ repoCommit changes the way a sandboxed agent must — write Conventional Commit messages and, because commit signing fails inside the sandbox, hand the real commit off through a generated commit.sh script. Inside a git worktree, commit normally (unsigned) and emit a commit.sh that re-signs the range; in the main checkout, do not commit at all — emit a commit.sh containing the exact git add and git commit invocations for the user to run. Use when committing changes, creating a git commit, staging and committing work, writing or formatting a commit message, splitting changes into separate commits, or when an agent or sandbox cannot sign commits and must hand the commit off to the user. Not for pushing, opening or merging pull requests, rebasing or amending existing history, tagging releases, or non-git version control.
CODE-SAURABH/OpenSkills/code-reviewer Skill
3★ repoReview code changes for bugs, security issues, performance problems, and style before shipping. Use when the user asks for a code review, wants to check a diff or PR, needs a second opinion on implementation, or says "review this", "check this code", or "is this safe to ship".
CODE-SAURABH/OpenSkills/commit-message Skill
3★ repoWrite clean Conventional Commits messages and pull request descriptions from staged changes or diffs. Use when the user asks to write a commit message, commit their changes, describe a PR, open a pull request, summarise a branch, or says "write a commit", "create a PR", "what should I call this commit", or "draft my PR description".
CODE-SAURABH/OpenSkills/plan-ceo-review Skill
3★ repoCEO and founder-lens strategic plan review. Use when the user wants to evaluate a feature or product idea from a business perspective, challenge scope, find the 10-star product inside the request, assess user value and competitive moat, or run a strategic review before engineering begins.
CODE-SAURABH/OpenSkills/plan-design-review Skill
3★ repoDesign plan review skill — rate and improve a UI design plan before implementation. Use when the user has a plan, wireframe, or design description for a UI feature and wants a senior designer to rate each design dimension 0-10, explain what a 10 looks like, detect AI slop, and edit the plan to reach that quality before any code is written.
CODE-SAURABH/OpenSkills/plan-eng-review Skill
3★ repoEngineering plan review skill — architecture, data flow, edge cases, and test plan before coding begins. Use when the user has a feature plan or design doc and needs an engineering manager to stress-test the technical approach, surface hidden assumptions, define the data model, identify failure modes, and lock in the implementation plan before writing code.
CODE-SAURABH/OpenSkills/sre-canary Skill
3★ repoPost-deploy monitoring and canary verification skill. Use when the user has just deployed and wants to verify production health, watch for console errors or performance regressions, run a post-deploy monitoring loop, or validate that a canary deployment is stable before rolling out to 100% traffic.
CODE-SAURABH/OpenSkills/webapp-testing Skill
3★ repoAutomated end-to-end web application testing using Playwright. Use when the user wants to write automated tests for a web app, test frontend functionality, verify UI behaviour programmatically, debug interactions in a browser, capture screenshots of a running app, check for console errors, or test a user flow from login to completion.
MuhammedZohaib/patchman/plugins/patchman/skills/business-logic-review Skill
3★ repoReview an authorized application for business-logic vulnerabilities, workflow abuse, approval bypasses, replay conditions, quota circumvention, plan enforcement bugs, and state-transition errors. Use for billing, invites, approvals, refunds, admin actions, and multi-step workflows.
MuhammedZohaib/patchman/plugins/patchman/skills/pr-diff-review Skill
3★ repoReview an authorized pull request diff for security regressions. Use when changes modify trust boundaries, auth logic, data-access scope, file handling, logging, headers, or secrets.
MuhammedZohaib/patchman/plugins/patchman/skills/query-review Skill
3★ repoReview an authorized codebase for ORM misuse, N+1 query patterns, authorization-after-fetch bugs, raw SQL risks, cache key collisions, and missing tenant scopes. Use for data-access layers and security-adjacent performance pitfalls.
MuhammedZohaib/patchman/skills/api-review Skill
3★ repoReview an authorized API surface for access control, mass assignment, schema validation, rate limiting, SSRF, error leakage, webhook verification, and unsafe defaults. Use for REST, GraphQL, RPC, and webhook handlers.
MuhammedZohaib/patchman/skills/auth-review Skill
3★ repoPerform a defensive review of authentication and authorization flows in an authorized codebase. Use for login, session, MFA, OAuth, password reset, cookie security, JWT validation, impersonation, privilege checks, and object-level access control.
MuhammedZohaib/patchman/skills/business-logic-review Skill
3★ repoReview an authorized application for business-logic vulnerabilities, workflow abuse, approval bypasses, replay conditions, quota circumvention, plan enforcement bugs, and state-transition errors. Use for billing, invites, approvals, refunds, admin actions, and multi-step workflows.
MuhammedZohaib/patchman/skills/pr-diff-review Skill
3★ repoReview an authorized pull request diff for security regressions. Use when changes modify trust boundaries, auth logic, data-access scope, file handling, logging, headers, or secrets.
MuhammedZohaib/patchman/skills/query-review Skill
3★ repoReview an authorized codebase for ORM misuse, N+1 query patterns, authorization-after-fetch bugs, raw SQL risks, cache key collisions, and missing tenant scopes. Use for data-access layers and security-adjacent performance pitfalls.
VersoXBT/claude-recommended-skills/code-quality-review Skill
3★ repoPerform structured code reviews enforcing quality standards, naming conventions, architecture patterns, and team agreements. Use when the user says 'review this code', 'code review', 'check quality', 'review my PR', 'what's wrong with this', 'improve this code', 'review before merge', 'peer review', or 'audit this'. Also triggers on 'code quality', 'review standards', 'enforce conventions', 'tech debt check', 'lint review', or when user completes a significant code change.
VersoXBT/claude-recommended-skills/product-verification Skill
3★ repoTest, validate, and verify that code changes produce correct product behavior. Use when the user says 'verify this works', 'test the feature', 'check the output', 'does this actually work', 'validate the behavior', 'smoke test', 'QA this', 'acceptance test', or 'make sure it works end to end'. Also triggers on 'product verification', 'behavior validation', 'functional check', 'integration verification', 'sanity check', or after completing a feature implementation.
kelpi-ai/google-ads-skills/skills/conversion-tracking-checker Skill
3★ repoDecide whether Google Ads conversion data is trustworthy enough for optimization by checking goals, action settings, duplicates, and campaign use. Use before changing bids, budgets, or performance targets.
genfeedai/skills/bundles/all/skills/channel-validator Skill
3★ repoValidate channel focus against the One Channel Rule before adding more platforms or tactics. Triggers on channel sprawl, platform focus, right-channel questions, and expansion readiness.
genfeedai/skills/bundles/all/skills/content-reviewer Skill
3★ repoReview and score content quality across six dimensions with actionable feedback. Triggers on "review this content", "score this post", "check content quality", "review my copy", "is this post ready to publish", "critique this content".
genfeedai/skills/bundles/all/skills/expert-validator Skill
3★ repoScore existing expert positioning against Attractive Character, origin story, Big Domino, New Opportunity, authority signals, and differentiation. Triggers on validating positioning, messaging, authority, expert narrative, and personal brand angle.