BF rohoon-6sigma
Rohoon Six Sigma professional support. Based on AIAG-VDA SPC Manual, MSA Manual, and Six Sigma/Lean methodology. Provides: DMAIC/DMADV tools, SPC control charts, process capability indices (Pm/Pmk, Pp/Ppk, Cp/Cpk), MSA analysis (GR&R/Bias/Linearity/Stability), DOE (Full/Partial Factorial/RSM/Taguchi), FMEA, 5S/VSM, and more. For automotive quality management, process optimization, supplier assessment.
As a process F 34/100 · Will not run — References files that are not bundled: references/AIAG_VDA_Standard_EN_Format.pdf, references/AIAG_VDA_Standard_ZH_Format.pdf
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 37. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Rohoon Six Sigma professional support. Based on AIAG-VDA SPC Manua… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/AIAG_VDA_Standard_EN_Format.pdf - warning
missing-refreference to a missing file: references/AIAG_VDA_Standard_ZH_Format.pdf
Process rating: all ten parameters 34/100
- 0Tools and files. 2 referenced file(s) missing: references/AIAG_VDA_Standard_EN_Format.pdf, references/AIAG_VDA_Standard_ZH_Format.pdf
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 4576 tokens
- 100Steps. 154 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -280 emoji in the instructions: noise for the model
- -32 of 25 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 404: enough signal without eating the budget
- +4Structure: 55 headings
- +3Step-by-step instructions: 154 items
- +4Has examples (14 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 52.