workflow-cp4

Validates operator performance against requirement targets using HAP scores or msprof profiling data.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/WangWindow/CANN-BatchMatMulMaxsum --skill workflow-cp4-wangwindow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-cp4
Source: https://github.com/WangWindow/CANN-BatchMatMulMaxsum/tree/main/.agents/skills/workflow-cp4
Command: npx skills add https://github.com/WangWindow/CANN-BatchMatMulMaxsum --skill workflow-cp4-wangwindow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It provides QA with an objective acceptance standard for the CP4 performance checkpoint, determining whether an Ascend C operator's measured performance meets the targets declared in the requirements document, based on data rather than subjective judgment. ## Core Features & Use Cases - Dual evaluation modes: Mode A uses evaluation-set HAP scores (default threshold ≥ 0.5) as the final verdict; Mode B compares self-collected msprof op metrics (latency, bandwidth, AI Core utilization) against quantified targets. - Bottleneck verification: Requires bottleneck-dimension decomposition (compute / move-in / move-out / scalar) and cross-checks measured bottlenecks against the development plan's predictions, flagging contradictions. - Leverage assessment gate: When targets are unmet, it enumerates untried optimization levers and excludes disproven directions before deciding whether to roll back or recommend closing as a known limitation. - Use Case: After functional acceptance of a BatchMatmulMaxSum operator, QA loads this skill to run the evaluation set, compare HAP scores per case against the threshold, verify mandatory optimization items landed, and produce a structured CP4 performance acceptance report. ## Quick Start Load the workflow-cp4 skill and run the CP4 performance acceptance for the operator submission, producing a pass/fail report with bottleneck analysis.

Frequently Asked Questions about workflow-cp4

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run CP4 performance acceptance for an Ascend C operator?

Run the evaluation set with run_evaluation.sh for Mode A to get HAP scores, or collect msprof op profiling data for Mode B. Then compare measured metrics against requirement targets, verify shape coverage, and produce the CP4 acceptance report.

What is the difference between Mode A and Mode B performance evaluation?

Mode A uses the evaluation set's HAP score as the final verdict, with a default threshold of 0.5 meaning performance is not below baseline. Mode B compares self-collected metrics like latency, bandwidth, and AI Core utilization against quantified targets in the requirements document.

What happens when performance targets are not met?

The skill requires a leverage assessment gate before rollback: list untried optimization levers matched to the measured bottleneck, exclude directions with prior negative results, then either roll back for optimization or conclude with a recommendation to close as a known limitation.

Can the CP4 checkpoint accept sub-threshold performance as a known limitation?

No, accepting unmet targets exceeds this checkpoint's authority. It can only issue a 'fail, recommend closure' conclusion with evidence of exhausted implementation-level optimization, leaving the final decision to the user.

Why is performance data judged incomplete without bottleneck decomposition?

The acceptance criteria require a breakdown of compute, move-in, move-out, and scalar shares to lock the measured bottleneck dimension. Without this decomposition, the data cannot be cross-checked against the development plan's bottleneck predictions.