Daily Testing Workflow Agent Skill

Use this skill when you need a day-by-day QA routine including planning, execution, bug reporting, and end-of-day wrap-up; triggers include daily testing workflow and daily QA routine.

9k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

144

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/naodeng/awesome-qa-skills --skill daily-testing-workflow

What comes with it

34 566 bytes besides the instruction

README.md

agents/openai.yaml

evals/cases/basic-success.yaml

evals/cases/edge-gates-handoff.yaml

evals/cases/edge-incomplete-input.yaml

evals/eval.yaml

output-templates/template-csv.csv

output-templates/template-excel.tsv

output-templates/template-json.json

output-templates/template-markdown.md

output-templates/template-word.md

output-templates/template-xmind.md

prompts/daily-testing-workflow.md

reference.md

scripts/batch_convert_templates.py

scripts/convert_formats.py

scripts/convert_output_formats.py

scripts/convert_to_csv.py

scripts/convert_to_excel.py

scripts/convert_to_json.py

scripts/convert_to_markdown.py

scripts/convert_to_word.py

scripts/convert_to_xmind.py

scripts/parse_csv.py

scripts/parse_excel.py

scripts/parse_formats.py

scripts/parse_json.py

scripts/parse_markdown.py

scripts/parse_output_formats.py

scripts/parse_word.py

scripts/parse_xmind.py

The instruction itself

7 sections, as written by the author

Daily Testing Workflow

中文版： See the corresponding Chinese skill.

When to Use

Need a one-day QA cadence: morning plan, execution, defects, EOD wrap-up.
Need stage gates and handoffs to type skills—not a single isolated testing task.

Workflow

Read and follow prompts/daily-testing-workflow.md (stages, gates, handoffs, output structure).
Add only context that changes the result: day scope, environment, constraints, risks, carryover defects.
After locating the stage, hand off by skill name per reference.md; no relative-path links to other skill internals.
If input is incomplete, draft a usable day plan and mark assumptions and gaps.

Core Constraints

Own phases and gates; hand full cases/strategy/reports to type skills.
Prioritize by risk; gates must be checkable.
Separate confirmed facts from assumptions.
Do not invent missing details; no relative-path links to other skill files.

Progressive Disclosure

Before producing output, read and follow prompts/daily-testing-workflow.md.
For step ↔ handoff skill mapping: read reference.md.
When deep-diving a stage: invoke the matching type skill (e.g. bug-reporting); do not expand full artifacts here.
When a template fits: use matching files under output-templates/.

Pre-delivery Checklist

[ ] Followed the main prompt’s output structure
[ ] Includes today’s scope/won’t-do, gate status, priority queue, next skill
[ ] High-risk items have explicit priority
[ ] Did not invent details the user did not provide
[ ] Assumptions and gaps are marked

Common Pitfalls

Do not turn the daily workflow into a functional-testing encyclopedia.
Do not leave work forever “in progress” without exit criteria.
Do not hand off multiple equal primary skills at once.
Do not pretend execution succeeded on a red environment.

Other skills for the same job

different authors, same section of the catalogue

Webapp Testing

by anthropics

vendor ×12

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

6k tokens scripts

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens

Test Driven Development

by w95

×7

Use when implementing any feature or bugfix, before writing implementation code

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

10k tokens scripts

Verification Before Completion

by ZhanlinCui

×6

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.

Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.

19k tokens

How to use it

Copy the folder

Take naodeng/daily-testing-workflow from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.