Name: quality-nonconformance
Rating: 63.2 (1 reviews)
Author: administrakt0r

quality-nonconformance

Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/quality-nonconformance/SKILL.md

The canonical home for this skill is quality-nonconformance in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

85%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 thorough, highly actionable domain-expertise skill with clear sequenced workflows, validation checkpoints, and well-structured progressive disclosure into three reference files; its main weakness is re-explaining well-known quality frameworks Claude already knows.

Suggestions

Trim or condense explanations of widely-known frameworks (5 Whys mechanics, Ishikawa 6M, Western Electric rules, Juran COQ percentages) to the manufacturing-specific guidance that Claude would not already know.

Consider moving the SPC chart-selection and capability-index reference detail into decision-frameworks.md, keeping only the decision rule inline.

The duplicate 'When to Use' section at the end (lines 230-235) repeats the opening trigger guidance — consolidate to one location.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly domain-valuable, but it re-explains frameworks Claude already knows (5 Whys, Ishikawa 6M, SPC chart selection, Western Electric rules, Juran's COQ model), which is padding that could be trimmed.	3 / 5
Actionability	As an instruction-only skill it gives highly concrete guidance: specific regulatory clauses (21 CFR 820.90, IATF 16949 §8.7), numbered decision logic, template subject-line formats, and tables mapping triggers to actions with timelines and metric targets.	5 / 5
Workflow Clarity	Multi-step processes are clearly sequenced (NCR lifecycle, disposition decision logic 'first path that applies governs', CAPA effectiveness verification 1–4) with explicit validation checkpoints and feedback loops such as 'If recurrence occurs... reopen and re-investigate.'	5 / 5
Progressive Disclosure	The body summarizes edge cases, templates, and decision frameworks inline while pointing to three real one-level-deep reference files (edge-cases.md, communication-templates.md, decision-frameworks.md) with clear signaling and a consolidated Additional Resources section.	5 / 5
	Total	18 / 20 Passed

Description

65%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 distinctive, keyword-rich description that clearly stakes out its regulated-manufacturing quality niche, but it is framed as expertise rather than concrete actions and lacks an explicit 'Use when...' trigger clause.

Suggestions

Rewrite the opening as concrete actions, e.g. 'Investigates non-conformances, performs root cause analysis, manages CAPA, and audits supplier quality in regulated manufacturing.'

Add an explicit trigger clause such as 'Use when investigating product defects, managing CAPA, interpreting SPC data, or auditing supplier quality in regulated manufacturing.'

Include common acronym/synonym triggers (NCR, CAPA, RCA, SCAR, MRB) so the description matches how practitioners phrase requests.

Dimension	Reasoning	Score
Specificity	The description names the domain and several activities ('non-conformance investigation, root cause analysis, corrective action, and supplier quality management') but frames them as 'Codified expertise for...' rather than concrete actions Claude performs, so coverage is present but not action-oriented.	3 / 5
Completeness	It gives a clear 'what' (codified expertise across five quality domains) but provides no 'Use when...' trigger clause, so per the rubric a missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	It includes natural practitioner keywords ('non-conformance', 'root cause analysis', 'corrective action', 'supplier quality', 'regulated manufacturing') that users would actually say, though synonyms and acronym variants (CAPA, RCA, NCR) are absent.	4 / 5
Distinctiveness Conflict Risk	The niche — quality/non-conformance management in regulated manufacturing — is sharply defined and unlikely to trigger for unrelated skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/quality-nonconformance/SKILL.md
Commit: 57c135b

Reviewed: 2 days 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.