Review & quality
19,016 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
samulee003/agentic-ppt-skills/skills/presentation-story-grill Skill
0★ repoPressure-tests an approved story against audience relevance, evidence interpretation, counter-cases, repeated slides, and conclusion quality. Use when the story-grill gate is current for a presentation project or when a router asks for a story opposition pass that may return passed, needs_revision: product-grill, or needs_revision: evidence.
Source command verify and submit
Erlemar/cayley-puzzles/.agents/skills/source-command-verify-and-submit Skill
no license0★ repoVerify an already-built submission CSV then submit to Kaggle.
dinaf2026-web/manuscript-editorial-suite-plugin/skills/manuscript-editorial-router Skill
0★ repoRoutes a broad or ambiguous editorial request to the right pass(es) in the Manuscript Editorial Suite. Use when the ask spans more than one kind of feedback or it's unclear which is wanted — "review my book", "give me editorial feedback", "is this ready", "go over this chapter", "full editorial pass", "what should I check". Picks among manuscript-publisher-critique, manuscript-continuity-audit, manuscript-fair-play-audit, manuscript-cinematic-scene-audit, manuscript-prose- immersion-audit, and manuscript-listing-critique, runs them in the right order for the book's genre, and hands off. Does not itself critique, score, or rewrite — it only dispatches.
The same file is in 1 other repository
dinaf2026-web/manuscript-editorial-suite-plugin/skills/manuscript-listing-critique Skill
0★ repoSales-listing critic for any book on Amazon KDP (and similar storefronts). Critiques (and, on request, rewrites) back-cover / jacket copy, the Amazon book description, categories, and keywords — the commercial surface that decides whether a browser clicks "buy". Use when the author says "critique the blurb", "review the back cover", "is this description good", "fix my Amazon listing", "rewrite my blurb", "check my categories and keywords", "would this sell", or "KDP listing review". For whole-story craft or an acquisitions verdict use manuscript-publisher-critique instead; this pass works only on selling copy and metadata, and never rewrites manuscript prose.
The same file is in 1 other repository
dinaf2026-web/manuscript-editorial-suite-plugin/skills/manuscript-publisher-critique Skill
0★ repoThe publisher's read for any manuscript — an acquisitions verdict plus a developmental craft breakdown, delivered as a scored report card graded against the markers of a great book in its genre (set by the project profile). Use for a single craft/acquisitions read of a scene, chapter, outline, full manuscript, or query: "publisher's read", "acquisitions verdict", "critique this", "score this", "grade this", "editor's letter", "would a publisher take this", "what's weak here", "read this like an editor". For a broad "review my book / full editorial pass" that may need several checks, use manuscript-editorial-router. NOT for canon checking (continuity-audit), mystery-fairness logic (fair-play-audit), line-level immersion (prose-immersion-audit), or blurb/listing copy (listing-critique). Diagnoses and scores; does not rewrite prose.
The same file is in 1 other repository
SkillMedev/remote-team-toolkit/skills/weekly-review Skill
0★ repoRuns a timeboxed weekly review - empty every inbox to a decision, audit every open commitment, and pick the 3-5 outcomes that define next week. Use when someone asks "walk me through a weekly review", "help me plan my week", "my task system feels stale and I don't trust it", or "I keep dropping commitments". Do NOT use for setting up the underlying capture-and-organize system itself - use gtd-system instead - or for tracking long-horizon personal goals with an accountability loop - use goals-accountability instead.
The same file is in 1 other repository
SkillMedev/security-compliance-hardening/skills/secure-code-review Skill
0★ repoReviews code for the security flaw classes that cause the most breaches - broken authorization and IDOR, injection, SSRF, mass assignment, and unsafe deserialization - and returns a short, focused findings list with concrete fixes. Use when someone asks "review this code for security issues", "is this endpoint safe", "check this PR for vulnerabilities", or is shipping auth logic, new API endpoints, file handling, or anything that touches untrusted input. Do NOT use for general code quality, style, or maintainability review - use code-review-checklist instead; for prioritizing findings a scanner already produced, use vulnerability-triage; for design-stage analysis before code exists, use threat-model-stride.
The same file is in 1 other repository
nsollazzo/skills/ship Skill
0★ repoTake a finished change from working tree to a green, mergeable PR by chaining simplify → verify → code-review → smart-commit → branch hygiene → PR → babysit. Use when the user says "ship", "ship it", "ship this", or wants the full clean→verify→review→commit→PR→green pipeline in one command. Default stops at approved + CI green + mergeable; does NOT merge unless --merge.
nsollazzo/skills/smart-commit Skill
0★ repoAutomatically cluster and commit git changes into logical groups with conventional commit messages. Use when: committing multiple unrelated changes, cleaning up work before PR, organizing messy commits, or when asked to "commit my changes", "smart commit", "organize commits", or "cluster commits".
Frog1205/OPC-Skills/skills/legal-review Skill
0★ repoOPC-Skills — AI 一人公司(One-Person Company)Claude Code 技能合集。一个人 + AI = 一支团队。战略/法务/内容/文档等虚拟部门,18 个开箱即用的 AI 技能。
opelpleple/meta-skills/pre-mortem Skill
0★ repoImagines the plan has already failed six months in the future, then works backwards to enumerate every reason why — surfacing risks that optimism and momentum normally hide. Use this skill when the user is finalizing a plan, launch, migration, hire, or big decision and asks "what could go wrong?", "review my plan", "what am I missing?", "poke holes before we commit", or is about to commit to something expensive or hard to reverse. Pairs with grill-me (which stress-tests at the start); pre-mortem assumes failure has happened and reasons backward.
usrrname/agent-skills/skills/gcm Skill
no license0★ repoGenerate conventional commit message from staged or unstaged changes
usrrname/agent-skills/skills/issue-plan-commit Skill
no license0★ repoReads from an existing issue, interprets expected outcomes, plans before making changes
Pr1m4lc0d3/KiSYSTEM/skills/kiss-debt-guard Skill
no license0★ repoUse when a repo needs an enforceable size/debt control rather than advice — installs a light, dependency-free size-budget audit script plus a config, and points to heavier guards (dead-code, duplicate-surface, test-debt, dependency-risk, doc-drift) when a repo warrants them. Use during KISS kickoff, or when files keep drifting over budget despite good intentions.
sdhilip200/api-warehouse/skills/connect Skill
0★ repoUse whenever the user wants to connect to an API, authenticate against an API, set up an API key safely, test or verify credentials, check whether an API is reachable, or prove connectivity before building a pipeline — even if they don't use the word "connect". Trigger contexts include: "set up auth", "configure my API key", "does my token work", "test my credentials", "can I reach this endpoint", or any request to confirm reachability before landing data.
sdhilip200/api-warehouse/skills/validate Skill
0★ repoUse whenever the user wants to validate or reconcile loaded data against the source API, check row counts or control totals, verify a load was complete, or confirm that warehouse data matches what the API returned — even if they don't say "validate". Trigger phrases include: "did everything land?", "check the counts", "reconcile the table", "verify the load", "compare API vs warehouse", "are the rows correct?", or any request to confirm that a loaded table matches its source.
aliasunder/agent-plugins/plugins/ship-check/skills/pr-monitor Skill
0★ repoPlugin marketplace for Claude Code and Claude Cowork — fresh-eyes code review agents, workflow orchestrators, and specialized skills
aliasunder/agent-plugins/plugins/ship-check/skills/pr-review Skill
0★ repoPlugin marketplace for Claude Code and Claude Cowork — fresh-eyes code review agents, workflow orchestrators, and specialized skills
aliasunder/agent-plugins/plugins/ship-check/skills/ship-check Skill
0★ repoPlugin marketplace for Claude Code and Claude Cowork — fresh-eyes code review agents, workflow orchestrators, and specialized skills
bahadirkisbet/bardak/plugins/bardak/skills/pipeline-verification Skill
0★ repoUse after any change, before calling it done or claiming it works — especially a change that touches shared code, a contract, or a user-visible path. Triggers whenever you are tempted to rely on unit tests alone.
bahadirkisbet/bardak/plugins/bardak/skills/verify-the-premise Skill
0★ repoUse whenever you are about to act on, suggest, or decide something that rests on an unverified assumption — a claim, a review finding, a doc or comment, a remembered API, a ticket, or your own belief about how the code behaves. The reflex: before acting on a belief, confirm it by reading, running, or tracing. Distinct from verifying that a finished change works end to end (that is pipeline-verification).
solidx86/intraday-trade/weekly-trade-review-skill Skill
no license0★ repoRuns a weekly review of the user's journaled intraday trades — a longitudinal accountability pass over the trade journal, not a fresh-trade critique. Use this skill whenever the user asks for a weekly review, week-end recap, or pattern summary of their journaled trades: "review my week", "weekly review", "how did I trade this week", "summarize my last N trades", "what patterns am I showing this week", "give me my week-end review", or just "weekly review" with no other context. Operates on the already-journaled trades in data/trade-journal/daily/<date>/ (written by the intraday-trade-mentor skill) — it does NOT take fresh chart screenshots; if the user wants a single trade critiqued, that's the intraday-trade-mentor skill. The review aggregates process grades and theme tags, surfaces recurring psychology, grades whether the user held last week's discipline order, then issues the next week's single discipline focus — drill-sergeant on accountability, head-coach on strategy. Persists each review to data/trade-journal/weekly/.
mbackschat/a12-dmtool-releases/skills/a12-dmtool Skill
0★ repoAuthor and validate A12 Kernel document models with the dmtool CLI — both a model's structure (fields, groups, type definitions, includes, config) and its validation rules. Use when a user (often a document modeller or business analyst) wants to create, edit, check, or understand an A12 document model — add or change fields and groups, factor out reusable includes, refactor structure, or author validation rules on it. Covers model creation, the structure edits and refactors (extract/move/rename), the rule envelope and error-scenario polarity, field-path references, per-row iteration, and the explore→compose→check loop.
cody-hutson/pmo-platform/operations/skills/artifact-lint Skill
no license0★ repoScans a project's generated-artifact surface (08-Generated/ + promoted folders) and runs five graph-integrity checks — orphan, sibling duplicate, stale draft, displaced content, version chain — reading the horizontal-lineage frontmatter (parent_artifact / sibling_topic / supersedes) so duplicate, orphaned, stale, or displaced generated content is surfaced for operator approval instead of silently accumulating. Read-and-recommend only — no automatic file moves or deletes. Triggers: "lint the generated artifacts", "check 08-Generated for duplicates", "scan for orphaned artifacts", "find stale drafts", "run artifact lint", "are there duplicate generated artifacts", "check the artifact lineage graph", "version-chain check the generated folder."
cody-hutson/pmo-platform/operations/skills/health-check Skill
no license0★ repoIntent-driven project-state drift auditor. Audits a single project for drift between its tracked state and its canonical sources (MCP + local), then emits a categorized 5-section punch list — Confirmed / Auto-Actionable / Decisions / Unknowns / Rollup-Diffs — that is never auto-applied. Eight modes: full (total sweep), timeline (date/milestone drift), attribution (owner drift), comms (comms-coverage drift), plan (one named plan), raid (RAID-log drift), sources (canonical-source inventory), rollup (project↔portfolio rollup compose/refresh). Invokable interactively as /health-check and schedulable for file output. Triggers: "health check this project", "is this project's state still accurate", "run a drift check", "check for stale dates", "audit the timeline", "check ownership drift", "are comms overdue", "did this plan land", "audit the RAID log", "are our sources current", "roll up to portfolio", "refresh this project's rollup", "did anything drift since last cycle", "is the tracked state current."
cody-hutson/pmo-platform/release/skills/build-reviewer Skill
no license0★ repoConducts final production-readiness review of any governed document pack — Copilot Builder Agent, PMO platform, or generic — using the shared review discipline (see `core/disciplines/review-discipline-principles.md`). Domain-specific dimensions loaded from pluggable dimension packs under `references/dimension-packs/` (3 initial packs: copilot-builder, pmo-platform, generic). Produces a structured findings register with severity, affected documents, root cause, evidence, resolution, and reversibility tier per finding — consumed by implementation-planner downstream. Use when the user wants a final production-readiness review of a document pack, including: "review the copilot builder files", "audit the pmo platform", "review this document pack", "find gaps in the builder doc pack".
cody-hutson/pmo-platform/release/skills/pmo-qa-lead Skill
no license0★ repoQA Lead Specialist — composes pmo-qa-auditor + build-reviewer into program-level QA leadership. Owns the system-level test strategy, binds acceptance scope to delivery readiness, governs defect disposition, and gates dev-testing — invoking the composed reviewers, never re-implementing them. Modes: Strategy · Acceptance · Defect-Governance · Dev-Test. Use when a release needs a QA-leadership read rather than a single review pass. Triggers: "what's the test strategy for this release", "does this meet the acceptance criteria", "is this acceptable to ship", "govern the defects on this release", "how should we disposition these findings", "gate the dev-testing on this PR", "run the dev-test quality gate", "QA-lead read on this release".
Pmo skill refiner selftest canary
cody-hutson/pmo-platform/release/skills/pmo-skill-refiner-selftest-canary Skill
no license0★ repoSmoke test for the pmo-skill-refiner factory — produced via the refiner's Create-New workflow during an AC demonstration. Reports the count of skill directories currently present in `release/skills/` and flags any that are missing from the `deploy.sh` per-module skill arrays (`OPERATIONS_SKILLS` / `RELEASE_SKILLS` / `CORE_SKILLS` / `CANARY_SKILLS`). Report-only (no decision-class outputs, no recommendations, no actions). Permanent fixture per ADR-04 (Stage 5 design for ) — functions as an always-on smoke test that detects factory regressions. Use when the user wants to check skill-roster consistency ("check the skill roster", "count tracked skills", "audit skill deployment drift", "verify skills/ folder matches deploy.sh", "are all my skills deployed").
cody-hutson/pmo-platform/release/skills/release-executor Skill
no license0★ repoExecutes approved release plans. Modes: Execute release · Verify release · Rollback release · Close release. Creates snapshots, applies file changes, closes IMP items, updates release log, runs verification, runs automated Stage 13 close-out. Requires an approved plan with Dry-Run Record. Triggers: "execute the release", "deploy v[X.Y]", "ship v[X.Y]", "verify the release", "rollback v[X.Y]", "go live with v[X.Y]", "close the release", "finalize v[X.Y]", "stage 13 close", "run the close-out", "automated close-out".
vipincode/exr-agent-skills/.claude/skills/frontend-code-review Skill
no license0★ repoReview frontend / client-side code (Next.js App Router, React, TypeScript, Tailwind + shadcn/ui, axios + Zod + TanStack Query + RHF) for correctness, component duplication, API-binding conformance, convention adherence, accessibility, and performance. Use whenever the user asks to review, audit, critique, or sanity-check frontend code — "review this component", "code review the products binding", "review my changes / this PR / the diff", "is this screen production-ready", "check this React code for issues". It reads the frontend ARCHITECTURE.md + MODULE_REGISTRY.md so it reviews against THIS project's conventions and flags components/hooks/utils that duplicate existing shared pieces or registry entries (DRY), plus bindings that bypass the BFF/axios/Zod/Query standard. Standalone and read-only — run anytime, never auto-chained, and it does not modify source unless explicitly asked to apply fixes. Tuned for frontend; NOT for backend/Express/Mongoose review (that is backend-code-review). This is static code review only — it does NOT run the app or confirm behavior at runtime; requests like "verify it works", "does it render", or "check my change actually works" are run/verify intent (/verify or /run), not review. Frontend / Next.js / React / component / API-binding scope only.
scoobydrew83/skills/plugins/coordinated-skills/skills/derisk-sequencer Skill
0★ repoTurn a validated idea into a risk-ordered sequence of experiments and build steps, with one hard rule — no product code is scheduled before the test that de-risks it. Use whenever someone has an idea worth building and asks what to do in what order — "what should I build first", "what order do I tackle this", "sequence this plan", "de-risk this roadmap", or presents a build plan that front-loads construction ahead of validation. The method lists the load-bearing assumptions, scores each by risk divided by cost-to-test, orders experiments cheapest-decisive first with kill-gates between them, places every build step after its unlocking test, and defers governance, breadth, and optimization until their gates clear — then emits an ordered sequence and a linter that flags build-before-its-test. Distinct from task-decomposition and overwhelm-breakdown (which collapse a big task to one next step for momentum) and agent-orchestration (which sequences build phases); this sequences de-risking ahead of building.
scoobydrew83/skills/plugins/coordinated-skills/skills/drift-check Skill
0★ repoAudit a set of related project documents for internal contradictions and drift from their stated mission, with a skeptical eye that distrusts suspiciously clean alignment. Use whenever the user points at multiple docs (spec, PLANNING.md, README, CLAUDE.md, .cursorrules, system prompt, TASK tracker, ADRs) and asks "are these consistent", "do my docs agree", "has my spec drifted", "check alignment", "is my README in sync", "audit my project for consistency", or shares a self-alignment/audit report. Especially trigger when documents should agree on the same facts (tech stack, metrics, feature lists, naming, architecture, tone) and the task is finding where they silently diverge, or where identical copy-pasted claims masquerade as validation. Lead with the real state of alignment and the biggest contradiction, never a vanity score. For cross-document consistency and mission-drift within a project's own materials, not verifying external claims (use reality-check) or choosing between options (use a council skill).
scoobydrew83/skills/plugins/coordinated-skills/skills/idea-validator Skill
0★ repoPressure-test whether an idea, product, or feature is worth building — BEFORE sinking days into it. Use whenever someone weighs building something and the real risk is the premise rather than the code. Triggers include "should I build X", "is this idea worth it", "validate this idea", "does this beat what already exists", "should this exist", "I'm about to build X", or mid-build "should I keep going or kill it". The method names the incumbent you must beat, ranks assumptions by risk × cost-to-test, attacks the cheapest riskiest one first, pre-registers kill criteria before any test, separates whether it's real from whether it's differentiated (real-but-commodity is a NO), and ends with a GO / NO-GO / CONDITIONAL-GO verdict plus scorecard. Trigger even on enthusiasm ("I have a great idea for…"), not just doubt. Distinct from reality-check (verifies an existing plan for hallucinations); this decides whether a thing should be built at all.
scoobydrew83/skills/plugins/coordinated-skills/skills/project-postmortem Skill
0★ repoGenerate an evidence-grounded project retrospective — pulled from git history and decision docs, not memory — that grades the project on separate dimensions, splits what went right from wrong, reduces the failure to its root ordering error, extracts transferable lessons for the next project, and names what survives. Use whenever a project ships, stalls, or gets sunset and someone wants the writeup — "post-mortem", "retrospective", "what went wrong with X", "we're sunsetting X, write it up", or mid-project "why did this go sideways". The method cites commit hashes or sources for every claim, builds a timeline of when validation happened vs building, separates pros from cons including uncomfortable symmetries, and ends with a per-dimension scorecard plus a what-survives list — then runs a check that fails any vanity scorecard or uncited narrative. Distinct from drift-check (audits live docs) and conductor-memory/session-bookend (capture session state for continuity); this extracts backward-looking lessons.
scoobydrew83/skills/plugins/coordinated-skills/skills/reality-check Skill
0★ repoPressure-test an AI-generated technical plan, recommendation set, setup guide, or tool/config list for hallucinations, factual errors, and unnecessary complexity, then verify the surviving claims against live sources before the user acts on them. Use whenever the user pastes recommendations, an implementation plan, a tooling/MCP/package list, install commands, or config and says "validate this", "fact-check this", "is this real/accurate", "did it hallucinate", "sanity-check this", "pressure-test this", "is this overkill", or asks whether a plan is feasible and worth doing. Especially trigger when the content looks AI-generated and is dense with checkable specifics (package names, repo URLs, CLI flags, file paths, versions, env vars, named "best-practice" patterns, time estimates) that could be fabricated. This is for VERIFYING the accuracy and practical value of an EXISTING plan, not for choosing between open options or deciding from scratch (use a decision/council skill for that).
BryceEWatson/claude-global-skills/global-review-loop Skill
0★ repoMine ALL of your local Claude history across EVERY project (both corpora — Claude Code CLI and Cowork local-agent-mode) for operator friction that recurs across MULTIPLE projects, then propose GLOBAL ~/.claude leverage (a CLAUDE.md rule, a new/edited global skill, a memory, or a settings hook) to fix it — each proposal reconciled against what already ships globally, self-validated by an adversarial /review-loop --mode claim loop, and recorded in a cross-run ledger so nothing is re-proposed, dismissed-twice, or shipped on its own say-so. DISTINCT FROM: signal-scan (one repo → that repo's .claude/ config), command-retro (Command's own logs → Command's queue), and transcript-analysis (ONE project, Cowork-only, proposes that project's CLAUDE.md candidates). This skill is the GLOBAL, cross-project layer: it only surfaces friction proven to recur across >=N DISTINCT projects (counted by cwd-PATH attribution only) and only ever proposes changes to ~/.claude. Invoke as /global-review-loop. Triggers: "what global rule should I add", "what recurs across my projects", "fleet-wide friction", "improve my global Claude config from how I actually work".
BryceEWatson/claude-global-skills/review-loop Skill
0★ repoDispatches a multi-agent review team over this session's work, runs an execution-grounded lint/test/build check, falsifies each finding against the diff, fixes load-bearing issues, and re-reviews until clean or the budget hits. Always records a commit-pinned verdict on the branch's open PR, so the review leaves a trail. Invoked manually or by the Stop hook after real work outside plan mode. `--mode claim` reviews an analytical conclusion against its primary sources instead of a diff.
BryceEWatson/claude-global-skills/seo-index-validation Skill
0★ repoValidate whether a DEPLOYED site is being crawled and indexed correctly, and diagnose plus fix why pages are not indexed. Use when a Google Search Console alert email arrives ("New reason preventing your pages from being indexed", "Not found (404)", "Page with redirect", "Discovered / currently not indexed", "Crawled / currently not indexed", "Soft 404"), when checking index health after a deploy, migration, or domain change, when a page will not appear in Google, or to confirm a prior indexing fix actually cleared in Search Console. It probes live HTTP (status codes, redirects, soft-404, canonical tags, sitemap) with curl, reads the GSC report via the browser, fixes at the correct layer (CDN or host setting, _redirects, a 404 page) under confirmation-gating, then schedules a lagged re-check. NOT for keyword research, content optimization, or backlinks. Triggers include "Search Console", "GSC", "not indexed", "404 in Search Console", "page with redirect", "soft 404", "validate indexing", "validate SEO", "why is my page not indexed", "did the indexing fix work".
search-atlas-group/amm-founding-circle/skills/prompt-injection-guard Skill
0★ repoProtect agent sessions from malicious or accidental instructions embedded in fetched web pages, documents, transcripts, issue text, screenshots, or logs.
search-atlas-group/amm-founding-circle/skills/python-style Skill
0★ repoPython code style and tooling rules — Ruff linter on every modification, --break-system-packages flag for Homebrew Python on macOS, python-dotenv for env loading (never source .env). Use proactively when editing any .py file or installing Python packages.
search-atlas-group/amm-founding-circle/skills/review-response-reputation Skill
0★ repoHandle a brand's review response workflow and reputation management program — draft specific, personalized responses to positive/neutral/negative reviews across Google, Yelp, Facebook, and industry-specific review platforms; design an FTC-compliant review generation program that asks for reviews without incentivizing sentiment; diagnose reputation threats (review bombing, fake-review campaigns, defamatory content); and establish a sustainable sentiment-tracking and response cadence. Hard-enforces FTC Consumer Reviews Rule (16 CFR Part 465, effective Oct 21, 2024) and platform TOS throughout — no fake reviews, no sentiment-gated incentives, no review suppression, no AI-pasted responses. Use this skill whenever a user asks about review responses, reputation management, review strategy, Google review replies, negative review handling, review generation, getting more Google reviews, handling a one-star review, review gating, or when GBP Competitor Audit flagged review volume, rating, freshness, or response rate as a gap. Chains opportunistically with brand-kit.md (tone of voice, business type, services) and gbp-competitor-audit.md (specific review gaps flagged with urgency). When a SearchAtlas MCP is connected, leverages SA tools (rank tracking, brand vault, GBP, OTTO, LLM Visibility) first before falling back to generic web search.
kumard3/lumbox-skills/email-for-ai-agents Skill
no license0★ repoPatterns and guidance for giving AI agents their own email - when an agent needs an inbox, how to handle OTP/2FA and verification links, and how agent-native email differs from transactional and OAuth-inbox APIs. Use when designing an agent that must sign up for services, verify identity, or correspond by email.
SkillMedev/database-performance/skills/migration-safety-checker Skill
0★ repoRewrite a schema migration into independently deployable, zero-downtime steps that never take a long-held blocking lock on a live table. Use when you are about to run an ALTER TABLE, CREATE INDEX, add a constraint, rename a column, or change a column type against a production database with live traffic. Do NOT use for greenfield table/column design with no rows yet - use database-schema instead; do NOT use for broad correctness/integrity review of a migration - use review-db instead.
The same file is in 1 other repository
SkillMedev/motion-video-direction/skills/social-video-formatter Skill
0★ repoReframe and export a finished video for social platforms - 9:16 ↔ 16:9 cropping, burned-in captions, a platform-native first frame, loop design, and per-platform specs (aspect, length, safe areas) for TikTok, Reels, Shorts, X, and LinkedIn. Use when someone says "make this vertical", "crop to 9:16", "format for TikTok/Reels/Shorts", "add captions/subtitles", "why is my video cut off on mobile", "resize for Instagram", or "export for social". Do NOT use when the question is about the storyboard or shot order before any video exists (use video-storyboard); the animation craft of how elements move (use motion-design-principles); animated word-by-word caption styling (use kinetic-typography); palette, contrast, or lighting (use motion-color-and-light); directing the product-demo content and screen choreography (use product-demo-director); or scoring, beat-syncing, or audio (use sound-and-music-sync) - this is the craft layer that decides WHAT to format for the feed, then hands a concrete spec to remotion-compose / remotion-render to author and export.
The same file is in 1 other repository
MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-devex Skill
0★ repoDeveloper-experience reviewer for the Karvey method. Walks the actual onboarding flow, measures time-to-hello-world, finds friction points and "docs lies". Plan-stage and live modes. Triggers include "karvey devex", "developer experience", "onboarding", "time to hello world", "fricción", "friction", "DX review".
MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-grill Skill
0★ repoPre-spec interrogation. Interviews the engineer relentlessly about their problem before writing any spec. Use at the start of every new feature or initiative — before karvey-init. Triggers include "grill me", "entrevístame", "interview me", "quiero especificar algo", "I want to spec something", "tengo una idea", "I have an idea", "necesito una feature", "I need a feature", "spec-driven", "SDD", "kiro", "gstack", "Garry Tan", "office hours", "producto 10 estrellas", "10-star product", "reframe", "PRD", "método de desarrollo", "development method".
MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-guard Skill
0★ repoSafety guardrails for the Karvey method. Installs/disables the opt-in enforcement hooks (git-flow + plan-gate), grants temporary override, and can edit-lock work to a single directory. Triggers include "karvey guard", "guardrails", "freeze", "edit lock", "activar hooks", "enable hooks", "bloquear cambios", "lock changes", "candado", "lock".
MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-health Skill
0★ repoCode quality dashboard for the Karvey method. Wraps type checker, linter, tests and dead-code detection into a weighted 0-10 score; tracks the trend over time. Triggers include "karvey health", "salud del código", "calidad de código", "quality score", "health dashboard".
MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-qa Skill
0★ repoQA code review in 8 dimensions (Security with OWASP Top 10 + STRIDE, Errors, Consistency, Impact, Env vars, Versioning, Second opinion cross-model, Visual audit vs design-spec). Creates REVISION_PR document, ClickUp tasks or PLAN.md entries. Notifies Google Chat. Triggers include "karvey qa", "code review", "revisión de código", "QA".
MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-second-opinion Skill
0★ repoIndependent cross-model code review for the Karvey method. Get an adversarial second opinion from a different AI model (e.g. Claude vs GPT/Codex/Gemini). Three modes: Review (PASS/FAIL), Challenge (adversarial), Consult. Triggers include "karvey second opinion", "segunda opinión", "cross-model review", "revisión independiente", "codex", "otro modelo".
SkillMedev/job-search-kit/skills/job-application Skill
0★ repoTailors a resume and writes a cover letter for one specific job description - mirroring JD keywords for ATS parsing, reordering bullets by relevance, quantifying impact, and reporting which JD keywords matched and which are missing. Use when someone asks "tailor my resume to this job", "write a cover letter for this posting", "will my resume pass the ATS", or shares a job description alongside their resume. Do NOT use for writing or restructuring a resume without a target job - use resume-writer instead; for critique of an existing resume, use resume-reviewer.
The same file is in 1 other repository
Sidsaladi9/persona-os/plugins/product-manager-os/skills/metrics-review Skill
0★ repoReviews product metrics with trend analysis and turns raw numbers into a scorecard with actions. Use when the user asks to "review our metrics", "run a weekly/monthly/quarterly metrics review", "why did signups drop", "why did this spike", "build a metrics scorecard", or "compare against target". Works with pasted numbers or a CSV; pulls from Amplitude/Mixpanel/GA if connected.
Sidsaladi9/persona-os/plugins/product-manager-os/skills/sql-queries Skill
0★ repoTranslates a product question into clean, correct SQL against a described schema and explains it line by line. Covers the core product-analytics patterns — funnels, retention and cohorts, DAU/MAU stickiness, and event counts — plus how to sanity-check the output. Use when you say "write me a query for", "how many users did X then Y", "what's our 7-day retention", "DAU/MAU by week", "build a funnel from signup to activation", or "is this number right?"
waseemnasir2k26/skynetlabs-all-claude-code/skills/client-delivery-and-planning/plan-ceo-review Skill
no license0★ repoCEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).
waseemnasir2k26/skynetlabs-all-claude-code/skills/client-delivery-and-planning/plan-eng-review Skill
no license0★ repoEng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance, observability, deployment. Walks through issues interactively with opinionated recommendations. CHANGELOG: 1.1.0 — Added §5 Observability & Debuggability and §6 Deployment & Rollout (folded down from plan-ceo-review and re-framed for "is this implementable safely?" lens vs CEO's "should we ship this?"). 1.0.0 — Initial release: Architecture, Code Quality, Tests, Performance.
waseemnasir2k26/skynetlabs-all-claude-code/skills/client-delivery-and-planning/review Skill
no license0★ repoPre-landing PR review. Analyzes diff against main for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.
waseemnasir2k26/skynetlabs-all-claude-code/skills/code-quality-and-review/caveman-review Skill
no license0★ repoUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
The same file is in 11 other repositories
waseemnasir2k26/skynetlabs-all-claude-code/skills/code-quality-and-review/code-audit-fanout Skill
no license0★ repoFive-way parallel code audit. User pastes a Python file / function / diff → orchestrator fans out 5 specialist sub-agents in ONE message, each reviewing a DIFFERENT axis (static analysis, library API correctness, standards/spec compliance, reproducibility, numerical correctness). Every finding MUST cite an exact URL + a quoted passage from the official documentation. Aggregator agent merges, dedupes, ranks by severity. Code returns reviewed 4-5 times before the user touches it. Trigger when user says: "audit this code", "review this diff", "debug this", "check my function", "find bugs", "/audit-code", "/code-audit-fanout", "fanout audit", or pastes a code block and asks for review. Auto-trigger heuristic: user pastes >20 lines of Python and asks for "review", "audit", "debug", "check", or "bug". HARD RULE: zero claims without a source. Every issue cites a URL to the official docs / paper / spec, plus the exact quoted passage. No hallucinated APIs, function signatures, or behaviors. If a specialist cannot verify a claim against a primary source, it must say "UNVERIFIED" and skip the finding.
waseemnasir2k26/skynetlabs-all-claude-code/skills/code-quality-and-review/fanout-ship Skill
no license0★ repoParallel multi-agent ship pattern. Decompose 1 parent task into N independent child tasks → spawn N background agents in isolated git worktrees → each opens PR targeting shared integration branch → smallest-first merge order with self-documenting rebase recipes → final PR integration → main. Collapses N×30min sequential work into ~30min wall-clock. Isolated blast radius (one agent crash ≠ kill others). Granular revert. Small review surface per PR. Background execution = no babysit. Trigger when user says: "fan out", "fanout", "split into N PRs", "parallel build", "parallel agents", "spawn N agents", "/fanout-ship", "ship in parallel", or pastes a parent issue + list of child tasks. Auto-trigger heuristic: task list ≥ 4 INDEPENDENT subtasks touching DISJOINT files, single repo, GitHub-hosted.
waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/browse Skill
no license0★ repoFast 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.