quality-dashboard-design
Use this skill when you need evidence-bounded quality dashboard audiences, decision questions, panels, drill-downs, freshness, and alert boundaries; triggers include 质量仪表盘 and quality dashboard.
Install
npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/quality-dashboard-design
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart
git clone https://github.com/naodeng/awesome-qa-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole naodeng/awesome-qa-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Quality Dashboard Design
When to Use
- Use this skill when you need evidence-bounded analysis, design, or validation preparation for quality dashboard audiences, decision questions, panels, drill-downs, freshness, and alert boundaries.
- Use it to review a plan, result, or metric and turn the review into executable improvements.
- Use it when input is incomplete but a bounded first pass with assumptions, gaps, and human-decision boundaries is still useful.
Output Format Options
- Default to Markdown organized by domain risk, evidence state, priority, and boundary.
- When the user requests tables, CSV, JSON, or ticket fields, preserve the same finding fields, evidence, and decision boundaries.
- Before machine consumption, confirm the schema, enums, required fields, and evidence sources.
How to Use
- Read and follow
prompts/quality-dashboard-design.md, including its input audit, domain coverage, and output order. - Extract scope, environment, version, time window, constraints, success criteria, and available evidence, with attention to audience, decision question, panel, drill-down path, freshness and alerting.
- Separate confirmed facts, evidence-backed inferences, candidate recommendations, and Human decisions before ranking by risk and evidence strength.
- Turn high-risk items into preconditions, steps, expected behavior or decision criteria, required evidence, and a validation method.
- When input is incomplete, deliver a bounded first pass, state unsupported conclusions, and never present static material as execution evidence.
Reference Files
When calibrating domain outcomes, valid controls, or evidence gaps, read references/domain-decision-example.md for sanitized input, per-item oracles, and reproducible calculations.
Always read
prompts/quality-dashboard-design.md; it is the complete execution specification for this skill.For evaluation, read
evals/eval.yamland the matching cases underevals/cases/.Load
references/,examples/,scripts/, oroutput-formats.mdonly when those directories exist and the task needs them.
Domain Execution Essentials
- Map audience decisions to metrics, definitions/windows, source versions, actions and owners; available data alone must not decide what matters.
- Show numerator/denominator, refresh time and source status. Distinguish zero, null, NOT_RUN, BLOCKED and stale data; never fill gaps with zero or reuse stale green.
- Preserve P0 blockers and small high-risk groups in summaries. Overall pass rates cannot override individual blockers; aggregation follows project rules.
- Provide drill-down to run/obligation/defect evidence, refresh contracts and action triggers. Missing sources or gates yield design and gaps, not a current pass.
Core Constraints
- Keep the analysis focused on quality dashboard audiences, decision questions, panels, drill-downs, freshness, and alert boundaries; do not replace business owners or Human risk acceptance, exception approval, or release decisions.
- Never invent system behavior, fields, metrics, thresholds, data, root causes, execution records, or pass claims.
- Static design, plans, file presence, or a dry run retain their evidence state and cannot become proof of real execution.
- When evidence is insufficient, use pending confirmation, blocked, unassessed, or NOT_SCORED and give the smallest validation method.
- For production, privacy, or security work, use least privilege, masked data, mocks, dry runs, or isolation.
Delivery Checklist
- Covered audience, decision question, panel, drill-down path, freshness and alerting, with source, evidence state, and validation method for each.
- Separated facts, inferences, candidate recommendations, gaps, and Human decisions.
- Gave high-risk items P0/P1/P2/P3 or an equivalent priority, owner role, and close condition.
- Did not turn plans, static checks, or dry runs into test execution, all-passed, or release-approved claims.
- Stated residual risk, stop/escalation conditions, and next actions.
Common Pitfalls
- Listing checks without triggers, expected concerns, owner roles, close conditions, and evidence.
- Treating adjacent metrics or tool names as a complete quality dashboard judgment.
- Using unexplained numbers for false precision or writing correlation as causation.
- Refusing incomplete input, or pretending that incomplete evidence is conclusive.
Best Practices
- Start with paths most likely to cause business loss, quality regression, or decision blockage.
- Use the smallest verifiable experiment to reduce uncertainty and record conditions, versions, sources, and evidence.
- Make the Skill independently installable, executable, and reviewable by another engineer.
Files (awesome-qa-skills)
-
agents
-
openai.yaml 322 B
Loading…
-
-
evals
-
cases
-
basic-success.yaml 1.4 KB
Loading… -
domain-method-regression.yaml 1.4 KB
Loading… -
edge-incomplete-input.yaml 933 B
Loading… -
edge-scope-boundary.yaml 978 B
Loading…
-
-
fixtures
-
check-domain-decisions.sh 95 B
Loading… -
check_domain_decisions.py 3.7 KB
Loading… -
domain-oracle.json 155 B
Loading…
-
-
eval.yaml 489 B
Loading… -
local-rules.json 143 B
Loading… -
trigger-prompts.csv 593 B · in bundle
-
-
prompts
-
quality-dashboard-design.md 5.5 KB
Loading…
-
-
references
-
domain-decision-example.md 1.4 KB
Loading…
-
-
SKILL.md 5.3 KB
--- name: quality-dashboard-design description: Use this skill when you need evidence-bounded quality dashboard audiences, decision questions, panels, drill-downs, freshness, and alert boundaries; triggers include 质量仪表盘 and quality dashboard. license: PolyForm-Noncommercial-1.0.0 metadata: version: "1.0.0" compatibility: "" author: "Awesome QA Skills contributors" language: "en" category: "testing-types" source: "https://github.com/naodeng/awesome-qa-skills" license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0" --- # Quality Dashboard Design ## When to Use - Use this skill when you need evidence-bounded analysis, design, or validation preparation for quality dashboard audiences, decision questions, panels, drill-downs, freshness, and alert boundaries. - Use it to review a plan, result, or metric and turn the review into executable improvements. - Use it when input is incomplete but a bounded first pass with assumptions, gaps, and human-decision boundaries is still useful. ## Output Format Options - Default to Markdown organized by domain risk, evidence state, priority, and boundary. - When the user requests tables, CSV, JSON, or ticket fields, preserve the same finding fields, evidence, and decision boundaries. - Before machine consumption, confirm the schema, enums, required fields, and evidence sources. ## How to Use 1. Read and follow `prompts/quality-dashboard-design.md`, including its input audit, domain coverage, and output order. 2. Extract scope, environment, version, time window, constraints, success criteria, and available evidence, with attention to audience, decision question, panel, drill-down path, freshness and alerting. 3. Separate confirmed facts, evidence-backed inferences, candidate recommendations, and Human decisions before ranking by risk and evidence strength. 4. Turn high-risk items into preconditions, steps, expected behavior or decision criteria, required evidence, and a validation method. 5. When input is incomplete, deliver a bounded first pass, state unsupported conclusions, and never present static material as execution evidence. ## Reference Files - When calibrating domain outcomes, valid controls, or evidence gaps, read [references/domain-decision-example.md](references/domain-decision-example.md) for sanitized input, per-item oracles, and reproducible calculations. - Always read `prompts/quality-dashboard-design.md`; it is the complete execution specification for this skill. - For evaluation, read `evals/eval.yaml` and the matching cases under `evals/cases/`. - Load `references/`, `examples/`, `scripts/`, or `output-formats.md` only when those directories exist and the task needs them. ## Domain Execution Essentials 1. Map audience decisions to metrics, definitions/windows, source versions, actions and owners; available data alone must not decide what matters. 2. Show numerator/denominator, refresh time and source status. Distinguish zero, null, NOT_RUN, BLOCKED and stale data; never fill gaps with zero or reuse stale green. 3. Preserve P0 blockers and small high-risk groups in summaries. Overall pass rates cannot override individual blockers; aggregation follows project rules. 4. Provide drill-down to run/obligation/defect evidence, refresh contracts and action triggers. Missing sources or gates yield design and gaps, not a current pass. ## Core Constraints - Keep the analysis focused on quality dashboard audiences, decision questions, panels, drill-downs, freshness, and alert boundaries; do not replace business owners or Human risk acceptance, exception approval, or release decisions. - Never invent system behavior, fields, metrics, thresholds, data, root causes, execution records, or pass claims. - Static design, plans, file presence, or a dry run retain their evidence state and cannot become proof of real execution. - When evidence is insufficient, use pending confirmation, blocked, unassessed, or NOT_SCORED and give the smallest validation method. - For production, privacy, or security work, use least privilege, masked data, mocks, dry runs, or isolation. ## Delivery Checklist - [ ] Covered audience, decision question, panel, drill-down path, freshness and alerting, with source, evidence state, and validation method for each. - [ ] Separated facts, inferences, candidate recommendations, gaps, and Human decisions. - [ ] Gave high-risk items P0/P1/P2/P3 or an equivalent priority, owner role, and close condition. - [ ] Did not turn plans, static checks, or dry runs into test execution, all-passed, or release-approved claims. - [ ] Stated residual risk, stop/escalation conditions, and next actions. ## Common Pitfalls - Listing checks without triggers, expected concerns, owner roles, close conditions, and evidence. - Treating adjacent metrics or tool names as a complete quality dashboard judgment. - Using unexplained numbers for false precision or writing correlation as causation. - Refusing incomplete input, or pretending that incomplete evidence is conclusive. ## Best Practices - Start with paths most likely to cause business loss, quality regression, or decision blockage. - Use the smallest verifiable experiment to reduce uncertainty and record conditions, versions, sources, and evidence. - Make the Skill independently installable, executable, and reviewable by another engineer.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.