Agent skill

Quality Engineering Quality Assurance

by HoangNguyen0403 in HoangNguyen0403/agent-skills-standard

Write or review manual Zephyr test cases with 1-condition-per-TC granularity, ModuleAction on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification.

MITAuto-check passedTesting & QA

Install Quality Engineering Quality Assurance

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

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

GitHub CLI
$ gh skill install HoangNguyen0403/agent-skills-standard quality-engineering-quality-assurance --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-quality-assurance .claude/skills/quality-engineering-quality-assurance && 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-quality-assurance
GitHub stars
572
Token cost
~629 tokens
SKILL.md length
261 words
Files
4 (incl. references)
Skills in repo
211
Repo updated
First seen
Licence
MIT

At a glance

Write or review manual Zephyr test cases with 1-condition-per-TC granularity, ModuleAction on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification.

  • Works in 4 steps: Test Case Granularity → Naming Convention → Priority Levels → …
  • Test-case authoring and review
  • SKILL.md covers Priority: P1 (HIGH), 1. Test Case Granularity, 2. Naming Convention and 3. Priority Levels, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Quality Engineering Quality Assurance is an agent skill from HoangNguyen0403/agent-skills-standard. Write or review manual Zephyr test cases with 1-condition-per-TC granularity, ModuleAction on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification. Use for test-case authoring and review; defer Jira traceability, linking, and pushing cases to Zephyr.

Its SKILL.md is about 630 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/TDD_FEEDBACK.md` and `references/test_case_standards.md`).

It sits in Testing & QA, covering Test generation and QA and bug reports. It works with Jira. 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

  • Test-case authoring and review
  • Defer Jira traceability
  • Pushing cases to Zephyr

Example prompts

  • “/quality-engineering-quality-assurance”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Test Case Granularity
  2. Naming Convention
  3. Priority Levels
  4. References

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 Quality Assurance loads about 629 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 261 words of instructions outside code blocks.

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

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). 261 words, ~629 tokens.

Download SKILL.mdSave it as .claude/skills/quality-engineering-quality-assurance/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
quality-engineering-quality-assurance
description
Write or review manual Zephyr test cases with 1-condition-per-TC granularity, Module_Action on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification. Use for test-case authoring and review; defer Jira traceability, linking, and pushing cases to Zephyr.

Quality Assurance Standards

Priority: P1 (HIGH)

1. Test Case Granularity

  • 1 Test Case = 1 Condition on 1 Screen.
  • Split Screens: "Order Details" & "Item Details" separate.
  • Split Conditions: "Config " & "Config B" separate.
  • No "OR" Logic: Each TC must test single, distinct path.

2. Naming Convention

  • Pattern: Platform_Module_Action on Screen when Condition (e.g., Web_Order_Verify... or Mobile_Order_Verify...)
  • Rule: Only include Web_ or Mobile_ prefix if requirement exclusive to one platform. Omit prefix if it supports Both.
  • Example: Order_Verify payment term on Item Details when Toggle is OFF (Supports Both)

3. Priority Levels

Use priority rationale to justify each classification:

  • High: Critical path, blocker bug.
  • Normal: Standard validation, edge case.
  • Low: Cosmetic, minor improvement.

4. References

Anti-Patterns

  • No Broad TCs: "Verify order flow works" — too broad; every TC must cover exactly 1 condition on 1 screen
  • No Shared TCs (Divergent): Testing Web and Mobile behavior in single TC when behavior diverges — split into separate TCs per platform
  • No Incomplete Naming: Order_Verify page — name must follow full pattern: Module_Action on Screen when Condition
  • No Priority Inflation: Marking cosmetic spacing bug as High priority — reserve High for critical path blockers only

Review wording

  • Call out naming violations explicitly when a test case breaks the naming convention, then split it into separate TCs with one condition on one screen.

Canonical response anchors

When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:

  • naming violations
  • 1 Test Case = 1 Condition
  • High: Critical path
  • Low: Cosmetic
  • Module_Action on Screen when Condition
  • No "OR" Logic
  • Split into separate TCs
  • priority rationale

© 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-quality-assurance of HoangNguyen0403/agent-skills-standard.

  • SKILL.md
  • evals/evals.json
  • references/TDD_FEEDBACK.md
  • references/test_case_standards.md

Open the folder on GitHubat commit b529c2d

Compare with similar skills

Quality Engineering Quality Assurance 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 Quality Assurance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quality Engineering Quality Assurance this skillHoangNguyen0403/agent-skills-standard572—~629Automated safety check: PassMIT
Generate Test Planopenshift-eng/ai-helpers120—~1.6kAutomated safety check: PassApache-2.0
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Test Planquran/quran.com-frontend-next1.9k—~1.4kAutomated safety check: PassNone
Identify Fragile SystemsBuilderIO/agent-native7.1k—~957Automated safety check: PassNone
Atmos Testscloudposse/atmos1.4k—~1.9kAutomated safety check: PassApache-2.0

Similar skills

  • Generate Test Plan

    openshift-eng/ai-helpers

    Generate a comprehensive manual testing guide from a Jira issue, GitHub PR URLs, or both.

    120 GitHub stars~1.6k tokensUpdated 4 days ago
    Testing & QAAuto-check passed
  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Test Plan

    quran/quran.com-frontend-next

    Generates a comprehensive testing plan based on the current branch changes or a specific PR.

    1.9k GitHub stars~1.4k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • Identify Fragile Systems

    BuilderIO/agent-native

    Nightly refactor review: find the systems the last day's commits hit hardest, use three weeks of history to tell fragile from fast-moving, write a plan per systemic fix, and file deduplicated Jira…

    7.1k GitHub stars~957 tokensUpdated today
    Testing & QAAuto-check passed
  • Atmos Tests

    cloudposse/atmos

    Author Atmos smoke tests, post-deployment stack checks, and integration tests using type: test, HTTP assertions, shell or script/interpreter checks, require gates, parallel dependencies, matrix…

    1.4k GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Exploratory Test

    tobihagemann/turbo

    Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus usability observations through a UX lens…

    408 GitHub stars~2k tokensUpdated 2 days ago
    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

Works with

Categories

Questions about Quality Engineering Quality Assurance

What does Quality Engineering Quality Assurance do?

Write or review manual Zephyr test cases with 1-condition-per-TC granularity, ModuleAction on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification. Quality Engineering Quality Assurance is an agent skill from HoangNguyen0403/agent-skills-standard. Write or review manual Zephyr test cases with 1-condition-per-TC granularity, ModuleAction on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification.

When should I use Quality Engineering Quality Assurance?

Quality Engineering Quality Assurance fits situations like: test-case authoring and review; defer Jira traceability; pushing cases to Zephyr.

How do I install Quality Engineering Quality Assurance in Claude Code?

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

How do I install Quality Engineering Quality Assurance in Codex?

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

Can I use Quality Engineering Quality Assurance 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-quality-assurance -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-quality-assurance, .gemini/skills/quality-engineering-quality-assurance, .github/skills/quality-engineering-quality-assurance and .opencode/skills/quality-engineering-quality-assurance in your project.

What does Quality Engineering Quality Assurance need to run?

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

Does Quality Engineering Quality Assurance 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 Quality Assurance 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 Quality Assurance use?

Quality Engineering Quality Assurance 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 Quality Assurance use?

About 629 tokens (SKILL.md is roughly 2.5k 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 716 tokens, read only when the agent opens those files.

What are the alternatives to Quality Engineering Quality Assurance?

Skills that share tags, products or a category with Quality Engineering Quality Assurance: Generate Test Plan (openshift-eng/ai-helpers, 120 stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Test Plan (quran/quran.com-frontend-next, 1.9k stars) and Identify Fragile Systems (BuilderIO/agent-native, 7.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quality Engineering Quality Assurance?

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.