>
73
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its domain, lists specific capabilities, includes abundant natural trigger terms from the regulated manufacturing quality domain, and provides an explicit 'Use when...' clause. The description is comprehensive yet focused, making it highly distinguishable from other skills. The only minor note is the credential/authority claim ('15+ years experience') which is somewhat unnecessary filler but doesn't detract significantly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: quality control, non-conformance investigation, root cause analysis, corrective action, supplier quality management, NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. | 3 / 3 |
Completeness | Clearly answers both 'what' (quality control, NCR lifecycle, CAPA systems, SPC interpretation, audit methodology) and 'when' with an explicit 'Use when...' clause listing five specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a quality engineer would use: non-conformances, root cause analysis, CAPAs, SPC, NCR, supplier quality, FDA, IATF 16949, AS9100, audit. These are the exact terms users in regulated manufacturing would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting regulated manufacturing quality engineering with specific standards (FDA, IATF 16949, AS9100) and domain-specific terminology (NCR, CAPA, SPC). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
39%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a comprehensive quality engineering reference manual rather than a concise, targeted skill file. Its greatest strength is workflow clarity — the decision frameworks, escalation tables, and CAPA verification steps are well-structured with clear sequences and validation checkpoints. However, it is severely over-length, explains many concepts Claude already knows (SPC fundamentals, regulatory framework overviews, COQ model basics), and fails to split content into separate reference files, making it a poor fit for the SKILL.md format.
Suggestions
Reduce content by 60-70% by removing explanations of concepts Claude already knows (SPC basics, what 5 Whys is, COQ model definitions, regulatory framework overviews) and keeping only the decision-critical details and edge cases that add novel value.
Split detailed reference content (SPC chart selection, AQL sampling tables, regulatory framework specifics, supplier management details) into separate linked files like SPC_REFERENCE.md, SAMPLING_PLANS.md, and REGULATORY_REQUIREMENTS.md.
Add concrete, copy-paste-ready templates for NCR documentation, SCAR letters, and 8D reports with actual field structures rather than just describing what they should contain.
Remove the 'Role and Context' section entirely — Claude doesn't need to be told what tools quality engineers use or where they sit in the organization; focus on what to do, not who you are.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This is extremely verbose at ~400+ lines. It explains concepts Claude already knows well (what SPC is, what 5 Whys means, what FDA 21 CFR 820 covers, basic definitions of Cp/Cpk, what common vs special cause variation is). Much of this reads like a quality engineering textbook rather than actionable instructions that add novel knowledge. The Cost of Quality section, regulatory frameworks overview, and many definitional passages could be eliminated or drastically condensed. | 1 / 3 |
Actionability | The skill provides structured decision frameworks (NCR disposition logic, RCA method selection, escalation tables) and communication templates that are reasonably concrete. However, there is no executable code, no specific tool commands, and many instructions remain at the level of 'do this process' rather than providing copy-paste-ready artifacts like actual NCR forms, SCAR templates with fields, or specific queries for QMS systems. | 2 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints. The NCR lifecycle, CAPA effectiveness verification (4-step checklist), disposition decision logic (ordered sequence with clear gates), and supplier escalation ladder all have clear sequences with feedback loops (e.g., 'If recurrence occurs, the CAPA is not effective — reopen and re-investigate'). The escalation tables with timelines are well-structured. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files for detailed content. The entire regulatory framework section, SPC chart selection guide, AQL sampling details, and Cost of Quality model are all inline when they could easily be split into separate reference files. The 'Additional Resources' section at the end is vague and doesn't link to any actual files. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
Reviewed
Table of Contents