AB huawei-cloud-ascend-op-mfu-calculator
Calculate MFU (Machine FLOP Utilization) for operators like matmul/GEMM/FlashAttention on Ascend NPU, providing clear formulas and derivation process Use this skill when the user wants to: (1) calculate MFU for matrix operations, (2) analyze operator performance efficiency, (3) understand hardware utilization, (4) optimize operator implementation Trigger: user mentions "MFU", "machine flop utilization", "operator FLOPs", "matmul performance", "GEMM efficiency", "Ascend MFU", "算子MFU", "算力利用率", "矩阵乘效率", "GEMM性能", "FlashAttention性能"
Calculate MFU (Machine FLOP Utilization) for operators like matmul/GEMM/FlashAttention on Ascend NPU, providing clear formulas and derivation process Use this…
As a process B 70/100 · Nearly there — weak spots: result and completion, progress reporting
How to improve
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 70/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 20 steps, 2 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 727 tokens
- 100Running it twice. No mutating operations
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 535: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 20 items
- +4Reference files are cited in the instructions (1 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.