3.6천건 · 관련도순
This skill should be used when the user asks to "analyze skill quality", "evaluate this skill", "review skill quality", "check my skill", or "generate quality report". Evaluates local skills across description quality, content organization, writing style, and structural integrity.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
VS-Enhanced Evidence Quality Appraiser - Prevents Mode Collapse with context-adaptive quality assessment Enhanced VS 3-Phase process: Avoids automatic tool application, delivers research-specific evaluation strategies Use when: appraising study quality, assessing risk of bias, grading evidence Triggers: quality appraisal, RoB, GRADE, Newcastle-Ottawa, risk of bias, methodological quality
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Filter reads by quality scores, length, and N content using Trimmomatic and fastp. Apply sliding window trimming, remove low-quality bases from read ends, and discard reads below thresholds. Use when reads have poor quality tails or require minimum quality for downstream analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Combined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a generated Scenario image needs a quality check or a brand-brief compliance verdict before it ships: pass/warn/fail scoring, on-brand review against a configured brief, QA gating a batch, pricing or refreshing a stored verdict, or iterating a generation until it clears the gate. Keywords: quality gate, quality check, QA, verdict, brief compliance, on-brand, brand brief, pass fail, score, review, asset_quality_gate_run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech. Use for management reviews, quality objectives and KPIs, quality culture, and Notified Body / FDA inspection prep per ISO 13485 Clause 5.5.2.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply requirement quality principles when generating or validating feature specifications. Enforces feature completeness, scenario structure, AC verifiability, feature independence, and implementation slice quality. Use when writing feature specs, validating existing requirements, or when the user mentions 'validate this spec', 'check this feature', 'requirement quality', 'is this spec complete', or 'requirement-quality'. This skill governs the craft of writing individual feature specifications — not technical design (see design-blueprint), not implementation (see code-forge).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run AI agent and LLM evaluations in CI/CD pipelines — automated quality gates that fail the build when AI output quality drops. Use when someone asks to "test my AI agent", "add evals to CI", "catch prompt regressions", "compare models", "evaluate LLM output quality", "set up AI quality gates", or "benchmark my agent before deploying". Covers eval frameworks (Cobalt, Promptfoo, Braintrust), LLM-as-judge scoring, threshold-based assertions, and GitHub Actions integration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate data quality in CSV/Excel files for vehicle insurance platform. Use when checking required fields, validating data formats, detecting quality issues, or generating quality reports. Mentions "validate", "check fields", "data quality", "missing values", or "quality score".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-language code quality validation (Python, JS/TS, Shell, SQL) — formatting, linting, type-checking, complexity analysis with auto language detection. Use when checking code quality or running linters. Trigger on "lint", "type-check", "quality check", "run the linters", "check code quality".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when user asks to "audit tooling", "recommend tools", "quality stack", "what tools am I missing", "setup eslint", "setup detekt", "add coverage", "add ruff", "configure CI quality pipeline", "scan project tools", "tooling audit", "android tooling", "android quality", "compose testing", "kmp testing", or "screenshot testing".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
工程ごとの完了判定、品質ゲート、証跡、標準検証コマンド、例外運用を設計するスキル。 実装完了・テスト実施・品質確認完了・出荷可能を分離し、再利用可能な gate matrix を作る。 「全OK」「完了」などの曖昧な完了表現を排除し、証跡に基づく退出条件を定義する。 Use when defining Definition of Done, quality gates, exit criteria, release readiness gates, evidence requirements, exception handling, or standardized verification commands. Covers: definition of done, quality gate, exit criteria, release readiness, 完了判定, 品質ゲート. Distinct from project-completeness-scorer (which scores) -- this skill designs the gates and criteria themselves.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
品質ゲート（lint・型チェック・テスト）を実行し、必須ゲート通過を機械可読な結果で返す。Triggers on: '/quality-check', '品質チェック', 'QCして', 'quality gate'
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Iteratively detects and auto-fixes technical debt in a codebase using three quality criteria from debt-analysis references: conditional branch simplification, encapsulation, and separation of concerns. Applies fixes directly to code, runs existing tests to verify no regressions, re-analyzes, and loops until all high-severity issues are resolved or max iterations (5) reached. Use this skill when you want to automatically improve code quality with real code changes, reduce technical debt systematically, or clean up code to meet quality standards. Trigger on phrases like "fix technical debt", "clean up code quality", "refactor and fix issues", "improve code quality automatically", "apply debt fixes", "fix code problems", "eliminate debt".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[51] EXECUTE. Commitment to maximum quality work with 150% coverage. Use when you need the highest quality output for critical tasks, complex problems, important decisions, or when standard work isn't enough. Triggers on "maximum quality", "150% mode", "full quality", "critical task", or when you explicitly want AI to work at its best.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
앱 개발을 계획·구현·평가 에이전트로 나누고, 실행 중인 앱의 화면과 기능을 검증하며 설정한 품질 기준이나 반복 횟수 상한까지 수정을 이어 갑니다.
Review source code for readability, complexity, duplication, and maintainability without changing files. Receive a structured report with prioritized issues, refactoring suggestions, positive findings, and estimates of technical debt—the work needed to address accumulated code problems.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review blog posts, product descriptions, and landing pages for SEO content quality. Check whether they answer readers' search needs, support claims with evidence, show relevant authorship, and offer specific details, then identify areas to rewrite or expand.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build repeatable evaluations for AI agent responses, tool choices, and multi-step tasks. Use reference datasets and scoring criteria to compare changes, detect quality regressions, and set automated checks that must pass before deployment.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.