quality-nonconformance

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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, expert-grade reference that is highly actionable with concrete thresholds, templates, and gated decision logic. Its weaknesses are an atmospheric opening paragraph and a monolithic single-file structure with no progressive disclosure into reference files.

Suggestions

Move the regulatory-frameworks detail, escalation tables, and communication templates into reference files (e.g., references/REGULATORY.md, references/TEMPLATES.md) and link them from a concise overview, improving progressive disclosure and token efficiency.

Trim the 'Role and Context' atmospheric framing ('You sit at the intersection of...', 'Your judgment calls directly affect...') to the concrete scope statements Claude needs to act.

Add per-step validation checkpoints to the top-level 'How It Works' sequence so the summary workflow matches the rigor of the detailed sub-frameworks.

Dimension	Reasoning	Score
Conciseness	Most content is high-value domain expertise Claude does not already know (8D steps, AS9100 §8.7.1, Western Electric rules, capability thresholds), but the opening 'Role and Context' paragraph and atmospheric lines like 'You sit at the intersection of...' add framing Claude could do without.	3 / 5
Actionability	Guidance is concrete and copy-paste-ready: explicit thresholds (Cpk ≥ 1.33, rework > 60% of replacement cost, 90-day monitoring), literal template subject lines, named regulatory clauses, and decision-logic sequences covering the common cases — fully actionable for an instruction skill.	5 / 5
Workflow Clarity	Detailed sub-frameworks carry explicit validation checkpoints and feedback loops (CAPA effectiveness verification with 'reopen and re-investigate', gated disposition logic), but the top-level 'How It Works' summary sequence lists steps without per-step checkpoints, leaving a minor gap.	4 / 5
Progressive Disclosure	The skill ships no bundle files (references/, scripts/, assets/ absent) and the ~260-line body inlines material that could live in separate references (regulatory frameworks, escalation tables, templates); headers make it navigable, but content that should be separate is inline with no external references signaled.	3 / 5
	Total	15 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states capabilities and gives an explicit 'Use when' trigger list tied to natural user phrasing. The only soft spot is a few specialized acronyms (CAPA, SPC) that not every user would utter verbatim.

Suggestions

Add plain-language synonyms alongside the acronyms in the 'Use when' clause (e.g., 'corrective and preventive action (CAPA)' and 'statistical process control (SPC)') so non-specialist users trigger it naturally.

Consider trimming the credentialing phrase 'Informed by quality engineers with 15+ years experience' — it reads as marketing and adds no activation value.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities across the domain — 'non-conformance investigation, root cause analysis, corrective action, and supplier quality management' plus 'NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology' — giving comprehensive coverage rather than a single action.	5 / 5
Completeness	It explicitly answers both 'what' (codified expertise for QC, NCR investigation, RCA, corrective action, supplier quality) and 'when' ('Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'Use when' clause supplies natural phrases users would say ('investigating non-conformances', 'performing root cause analysis', 'interpreting SPC data'), but CAPA/SPC are specialized jargon a non-expert may not voice, leaving a few common-synonym gaps.	4 / 5
Distinctiveness Conflict Risk	The regulated-manufacturing quality niche (NCR/CAPA/SPC/audit) is clearly bounded with distinct triggers unlikely to fire for unrelated skills, giving minimal conflict risk despite the mildly marketing-toned 'codified expertise' framing.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/quality-nonconformance/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.