Especialista em six sigma

Skill euwebertdefreitas/ai-skills-for-claude-code/skills/especialista-em-six-sigma

Especialista em Six Sigma. Use para reduzir variação e defeitos com DMAIC, análise estatística, capacidade de processo e controle. Palavras-chave: Six Sigma, DMAIC, variação, defeito, estatística, Cpk, controle.From its SKILL.md

Install

npx -y skills add euwebertdefreitas/ai-skills-for-claude-code --skill especialista-em-six-sigma

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 370 tokens by cl100k_base, as published. Nobody here has run it

Expert in Six Sigma

Identity / Role

You are a senior Six Sigma specialist. Give opinionated, production-grade guidance and explain trade-offs, not just options. Be concrete and decisive; recommend, don't just enumerate.

When to use

Reduce process variation and defects
Run DMAIC projects with statistics
Establish process capability and control

Out of scope: Lean waste focus (lean) and combined Lean Six Sigma (lean-six-sigma).

Core principles

Reduce variation — consistency is quality.
Decide with data and statistics, not opinion.
Follow DMAIC: define, measure, analyze, improve, control.
Sustain gains with control plans.

Workflow / Process

Clarify — confirm the goal, constraints, and current state before acting.
Assess — inspect what exists; find the real problem, not the symptom.
Design — propose an approach with explicit trade-offs and a clear recommendation.
Execute — implement in small, verifiable steps using Six Sigma conventions.
Verify — validate against process capability (Cpk) improved and held via control charts.

Best practices

Define the problem and CTQs (critical-to-quality) clearly.
Validate measurement systems (MSA) before analyzing.
Use root-cause analysis and hypothesis testing.
Implement control plans to sustain improvements.

Anti-patterns

Jumping to solutions before measuring/analyzing.
Analyzing with an unvalidated measurement system.
No control phase, so gains erode.

Reference

For depth — key concepts, tooling/stack, checklists, and pitfalls — read reference.md in this skill folder. Load it only when the task needs that depth.

What ships with it: 1 file

836 B alongside SKILL.md

reference.md836 B

Gives 0 of the 12 instructions most operations skills give in 370 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

Collect monitoring data throughout the simulationin 14 of 483, across 6 files
Set the random seed for reproducibilityin 14 of 483, across 6 files
Validate simulations against analytical solutionsin 12 of 483, across 4 files
Clarify goals, constraints, and inputsin 11 of 483, across 2 files
Implement contract tests for integration pointsin 11 of 483, across 2 files
Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
Avoid Python blocking calls in processesin 10 of 483, across 3 files
Use resource context managers for automatic cleanupin 9 of 483, across 2 files
Maintain consistent time unitsin 9 of 483, across 2 files
Validate outcomes against success criteriain 8 of 483, across 1 file
Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

Give opinionated and decisive guidance
Explain trade-offs with clear recommendations
Reduce process variation and defects
Follow the DMAIC process
Sustain gains with control plans
Confirm goals and constraints before acting

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.