Agent skill

Quality Engineering Automation Health

by HoangNguyen0403 in HoangNguyen0403/agent-skills-standard

Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a releaseconfidence verdict.

MITAuto-check passedTesting & QA

Install Quality Engineering Automation Health

skills CLI
$ npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-automation-health -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HoangNguyen0403/agent-skills-standard quality-engineering-automation-health --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/quality-engineering/quality-engineering-automation-health .claude/skills/quality-engineering-automation-health && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
quality-engineering-automation-health
GitHub stars
572
Token cost
~861 tokens
SKILL.md length
391 words
Files
4 (incl. references)
Skills in repo
211
Repo updated
First seen
Licence
MIT

At a glance

Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a releaseconfidence verdict.

  • Works in 3 steps: Core workflows intact: the flows that… → No serious regression: the latest change… → Fast feedback: a developer learns what…
  • Judging suite value
  • SKILL.md covers Priority: P1 (HIGH), Mission, Three Questions and Four Metrics, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Quality Engineering Automation Health is an agent skill from HoangNguyen0403/agent-skills-standard. Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a releaseconfidence verdict. Use when judging suite value, ROI, or pre-release trust; not for writing or healing tests.

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `evals/evals.json`, `references/confidence-report-template.md` and `references/metrics-definitions.md`).

It sits in Testing & QA. The repository describes itself as: A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages. The licence is MIT.

When your agent uses it

  • Judging suite value
  • Pre-release trust
  • Not for writing

Example prompts

  • “Use the quality-engineering-automation-health skill to measure whether an automation suite builds release confidence via feedback-loop length, suite…”
  • “/quality-engineering-automation-health”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Core workflows intact: the flows that create revenue and user value still run end to end.
  2. No serious regression: the latest change did not break what was already stable.
  3. Fast feedback: a developer learns what they broke in minutes, not hours.

What it can do on your machine

Read from SKILL.md and the folder at commit b529c2d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quality Engineering Automation Health loads about 861 tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 80 tokens; SKILL.md has 391 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~861
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HoangNguyen0403/agent-skills-standard at commit b529c2d, republished under its MIT licence (© HoangNguyen0403). 391 words, ~861 tokens.

Download SKILL.mdSave it as .claude/skills/quality-engineering-automation-health/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
quality-engineering-automation-health
description
Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a release_confidence verdict. Use when judging suite value, ROI, or pre-release trust; not for writing or healing tests.

Quality Engineering: Automation Health

Priority: P1 (HIGH)

Mission

Automation exists to reduce ambiguity at release time, not to catch every bug. Finding bugs is testing's job; building confidence is automation's. Judge a suite by whether the team can deploy on Friday afternoon without fear.

Three Questions

A high-value suite answers all three with evidence:

  1. Core workflows intact: the flows that create revenue and user value still run end to end.
  2. No serious regression: the latest change did not break what was already stable.
  3. Fast feedback: a developer learns what they broke in minutes, not hours.

Four Metrics

MetricKeyQuestion it answers
Feedback loopfeedback_loop_minutesHow long from push to a trusted green or red?
Suite reliabilitysuite_reliability_pctWhen a run is red, does the team investigate or just re-run?
Release cadencerelease_cadenceDid automation let the team ship more often without more production risk?
Production escape rateprod_escape_rateHow many serious defects passed the whole pipeline and reached real users?

Formulas and data sources per CI provider live in Metrics Definitions.

Verdict

release_confidence: high | medium | low

  • high: all three questions answered yes with evidence; reliability at or above the team threshold; escape rate at or below baseline; feedback loop within target.
  • medium: one question lacks evidence, or reliability or feedback loop misses target while escapes stay at baseline.
  • low: any question answered no, a red run is not trusted, or escape rate rose after the last release.

Report with Confidence Report Template; feed release_confidence into test-loop, uat-signoff, and deploy-release handoffs.

Show full SKILL.md (137 more words)Show less

Anti-Patterns

  • No ranking by bug count: a suite that catches few bugs on CI usually means developers catch them locally first; that is success, not waste.
  • No deleting never-failing tests: a test that never fails is a safety net, not dead weight. It is what lets engineers refactor, bump dependencies, and change config without silent breakage.
  • No coverage % as the goal: coverage measures lines touched, not confidence earned.
  • No pass rate as health: a 99% pass rate with untrusted reds is worse than 95% the team believes.

Red Flags

"this test never fails, delete it" · "just re-run it, it's probably flaky" · "we found zero bugs so automation isn't paying off" · "coverage is 90%, we're safe". Each swaps a confidence question for a vanity number; re-frame with the Three Questions before acting.

References

© HoangNguyen0403, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/quality-engineering/quality-engineering-automation-health of HoangNguyen0403/agent-skills-standard.

  • SKILL.md
  • evals/evals.json
  • references/confidence-report-template.md
  • references/metrics-definitions.md

Open the folder on GitHubat commit b529c2d

Compare with similar skills

Quality Engineering Automation Health next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quality Engineering Automation Health compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quality Engineering Automation Health this skillHoangNguyen0403/agent-skills-standard572—~861Automated safety check: PassMIT
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Diagnosing Bugsfossasia/eventyay-interpretation1.6k32 repos~2.1kAutomated safety check: PassApache-2.0
TDDpietheinstrengholt/rssmonster56430 repos~906Automated safety check: PassMIT
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDDsanity-io/sanity6.4k20 repos~1kAutomated safety check: PassMIT

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed
  • Diagnosing Bugs

    fossasia/eventyay-interpretation

    Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 32 repos~2.1k tokens
    Testing & QAAuto-check passed
  • TDD

    pietheinstrengholt/rssmonster

    Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 30 repos~906 tokens
    Testing & QAAuto-check passed
  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed
  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Testing & QAAuto-check passed
  • Context Driven Development

    Ibrahim-3d/orchestrator-supaconductor

    A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…

    381 GitHub starsUsed in 9 repos~2.9k tokens
    Testing & QAAuto-check passed

More from HoangNguyen0403/agent-skills-standard

All 211 skills in this repo
  • Subagent-Driven Development

    HoangNguyen0403/agent-skills-standard

    Runs a multi-task implementation plan by sending each task to a fresh implementer subagent, reviewing it independently, then reviewing the whole branch.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • draw.io Architecture Diagramming

    HoangNguyen0403/agent-skills-standard

    Draws architecture diagrams as editable draw.io files from a JSON spec, with a fixed house style, one C4 level per diagram and evidence-tagged shapes.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Android Navigation 3 Guide

    HoangNguyen0403/agent-skills-standard

    Implements and migrates to Jetpack Navigation 3 in Compose: NavDisplay, typed route objects, a state-list back stack, deep links, multiple back stacks and dialog scenes.

    572 GitHub stars~687 tokensUpdated yesterday
    Auto-check passed
  • Angular HttpClient Standards

    HoangNguyen0403/agent-skills-standard

    Sets rules for Angular HTTP code: functional interceptors, typed requests, services that own every call, and httpResource for reactive data loading in Angular 17+.

    572 GitHub stars~652 tokensUpdated yesterday
    Auto-check passed
  • Angular Tooling

    HoangNguyen0403/agent-skills-standard

    Angular CLI usage, code generation, build configuration, and bundle optimization.

    572 GitHub stars~743 tokensUpdated yesterday
    Auto-check passed
  • Common Code Review

    HoangNguyen0403/agent-skills-standard

    Conduct high-quality, persona-driven code reviews. An agent skill from HoangNguyen0403/agent-skills-standard.

    572 GitHub stars~772 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Quality Engineering Automation Health

What does Quality Engineering Automation Health do?

Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a releaseconfidence verdict. Quality Engineering Automation Health is an agent skill from HoangNguyen0403/agent-skills-standard. Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a releaseconfidence verdict.

When should I use Quality Engineering Automation Health?

Quality Engineering Automation Health fits situations like: judging suite value; pre-release trust; not for writing.

How do I install Quality Engineering Automation Health in Claude Code?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-automation-health -a claude-code`. Or copy the skill folder (skills/quality-engineering/quality-engineering-automation-health in HoangNguyen0403/agent-skills-standard) into .claude/skills/quality-engineering-automation-health in your project. Claude Code loads it when a task matches its description.

How do I install Quality Engineering Automation Health in Codex?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-automation-health -a codex`. Or copy the skill folder (skills/quality-engineering/quality-engineering-automation-health in HoangNguyen0403/agent-skills-standard) into .agents/skills/quality-engineering-automation-health in your project. Codex loads it when a task matches its description.

Can I use Quality Engineering Automation Health in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-automation-health -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quality-engineering-automation-health, .gemini/skills/quality-engineering-automation-health, .github/skills/quality-engineering-automation-health and .opencode/skills/quality-engineering-automation-health in your project.

What does Quality Engineering Automation Health need to run?

SKILL.md names no scripts, command-line tools or credentials: Quality Engineering Automation Health is instructions for the agent only.

Does Quality Engineering Automation Health access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quality Engineering Automation Health safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quality Engineering Automation Health use?

Quality Engineering Automation Health is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quality Engineering Automation Health use?

About 861 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 922 tokens, read only when the agent opens those files.

What are the alternatives to Quality Engineering Automation Health?

Skills that share tags, products or a category with Quality Engineering Automation Health: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quality Engineering Automation Health?

HoangNguyen0403 (a GitHub user) maintains it in HoangNguyen0403/agent-skills-standard, which has 572 GitHub stars. The repository holds 211 skills in this directory. The repository was last updated on October 9, 2026.

Source: HoangNguyen0403/agent-skills-standard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.