CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/quality-nonconformance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 well-structured domain skill with genuinely strong workflow sequencing, decision tables, and validation/feedback checkpoints — the workflow clarity is exemplary. Its weaknesses are redundancy: textbook restatements of RCA/SPC concepts Claude already knows, a duplicated 'When to Use' section, and core-knowledge bulk in SKILL.md that the bundle's reference files could absorb.

Suggestions

Trim the textbook restatements (Western Electric rules enumeration, SPC chart-selection table, Cp/Cpk definitions, 8D D0-D8 walkthrough) down to the non-obvious judgment — when each fails, what thresholds apply — and leave the rest to references.

Delete the duplicate 'When to Use' section at the end of the body; keep the single instance near the top.

Move the detailed 'Core Knowledge' subsections (SPC, incoming inspection, regulatory frameworks) into references/decision-frameworks.md, keeping SKILL.md as a tighter overview with the decision tables and escalation logic inline.

DimensionReasoningScore

Conciseness

The body is mostly efficient and dense with non-obvious specifics (thresholds, timelines, hour budgets), but several sections restate textbook knowledge Claude already has at length — e.g. the full Western Electric rules ('Rule 1: One point beyond 3σ... Rule 4: Fourteen consecutive points alternating up and down'), SPC chart selection (X-bar/R, I-MR, p/np/c/u charts), Cp/Cpk definitions, and the 8D D0-D8 walkthrough. The duplicated 'When to Use' section (lines 9-10 and 230-235) is pure padding. It is above a 2 because most tokens carry domain-specific judgment (red flags, regulatory citations, cost ratios) rather than filler.

3 / 5

Actionability

For an instruction-only skill the guidance is largely concrete: specific thresholds ('If rework cost exceeds 60% of replacement cost, scrap'), concrete CAPA examples ('Add torque verification step at Station 12 with calibrated torque wrench (±2%), documented on traveler checklist WI-4401 Rev C'), template subject lines with variables, and hour budgets for RCA methods. It is not a 5 because some sections are descriptive rather than instructive (the RCA method and regulatory-framework overviews tell you about methods rather than what to do), and there is no worked end-to-end example of applying the frameworks.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints and feedback loops: the NCR lifecycle mandates 'Containment actions must happen before root cause analysis begins'; the disposition logic is an ordered first-match decision list ('the first path that applies governs the disposition'); and the CAPA effectiveness verification section is a numbered checklist with an explicit error-recovery loop ('If recurrence occurs, the CAPA is not effective — reopen and re-investigate'). Escalation and inspection-adjustment tables add explicit trigger/action/timeline checkpoints.

5 / 5

Progressive Disclosure

The structure is good: all three referenced files exist, are exactly one level deep, and are clearly signaled both inline ('Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis') and in a consolidated 'Additional Resources' section. It falls short of 5 because the SKILL.md itself still carries substantial detail that belongs in the references (full SPC, incoming-inspection, and regulatory knowledge sections could largely live in decision-frameworks.md), and the duplicated closing 'When to Use' section is an organization gap.

4 / 5

Total

16

/

20

Passed

Description

66%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 solid, domain-specific description that clearly conveys what the skill covers, but it lacks any 'use when' trigger guidance and omits the acronym vocabulary (NCR, CAPA, SCAR, 8D, SPC) that practitioners most naturally use when reaching for this kind of help. Adding an explicit trigger clause would lift the two weakest dimensions (completeness and trigger coverage).

Suggestions

Append an explicit trigger clause, e.g. 'Use when investigating defects or process deviations, opening or managing NCRs/CAPAs, interpreting SPC data, or auditing supplier quality.'

Include the natural acronym terms practitioners say — NCR, CAPA, SCAR, 8D, MRB, SPC — so keyword matching catches real user phrasing.

Sharpen 'Codified expertise for...' into direct third-person actions (e.g. 'Investigates non-conformances, selects root-cause methods, defines MRB dispositions and CAPA actions') to push specificity toward 5.

DimensionReasoningScore

Specificity

The description lists several specific capability areas — 'non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing' — which goes beyond naming the domain. It falls short of anchor 5 because the areas are activity categories rather than crisply enumerated concrete operations, and coverage has gaps (no mention of NCR disposition, CAPA verification, SPC interpretation, or supplier audits).

4 / 5

Completeness

The 'what' is clearly stated ('Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management'), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the rubric caps completeness at 3 in that case. 'In regulated manufacturing' weakly implies a context but does not tell the user when to invoke the skill.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'quality control', 'non-conformance', 'root cause analysis', 'corrective action', 'supplier quality', 'regulated manufacturing' are all phrases a user in this domain would naturally say. It is not a 5 because common variations users actually use are missing — notably the acronyms NCR, CAPA, SCAR, 8D, and SPC, plus terms like 'defect investigation' and 'complaint handling'.

4 / 5

Distinctiveness Conflict Risk

The regulated-manufacturing quality niche is clear and mostly distinct, with domain-specific triggers like 'non-conformance' and 'supplier quality management'. It is not a 5 because 'root cause analysis' and 'corrective action' are generic phrases that also appear in incident-response, postmortem, and general problem-solving skills, creating minor overlap risk with closely related skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

skills/quality-nonconformance/SKILL.md

Reviewed

Table of Contents

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.