New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Quality Engineering Zephyr Test Generation

by HoangNguyen0403 in HoangNguyen0403/agent-skills-standard

Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs.

MITAuto-check passedTesting & QA

Install Quality Engineering Zephyr Test Generation

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

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

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

At a glance

Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs.

  • Works in 4 steps: Analyze Requirements → Impact Analysis (run before any TC… → Draft Artifact → …
  • AC-to-test generation
  • SKILL.md covers Priority: P1 (HIGH), Workflow: Jira → Zephyr, Platform Rules and Naming & Filing, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Quality Engineering Zephyr Test Generation is an agent skill from HoangNguyen0403/agent-skills-standard. Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. create new), and draft correctly named test cases. Use for AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `evals/evals.json`, `references/impact_analysis.md` and `references/smartbear-api.md`).

It sits in Testing & QA, covering Test generation. 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

  • AC-to-test generation
  • Defer post-generation Jira linking and manual test-case quality review

Example prompts

  • “/quality-engineering-zephyr-test-generation”

Workflow steps

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

  1. Analyze Requirements
  2. Impact Analysis (run before any TC creation)
  3. Draft Artifact
  4. Create in Zephyr (after explicit user approval)

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 Zephyr Test Generation loads about 1.3k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 590 words of instructions outside code blocks.

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

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). 590 words, ~1,278 tokens.

Download SKILL.mdSave it as .claude/skills/quality-engineering-zephyr-test-generation/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
quality-engineering-zephyr-test-generation
description
Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. create new), and draft correctly named test cases. Use for AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.

Zephyr Test Generation Standards

Priority: P1 (HIGH)

Workflow: Jira → Zephyr

  1. Analyze Requirements:
  • Extract: Summary, ACs, Platform per AC row, Market, Components.
  • Fetch Jira with ?expand=renderedFields — HTML authoritative for platform colors: #00B8D9 = Web · #36B37E = Mobile · #FF991F = Web+Mobile
  • See Actor/Permission Matrix for role/market logic.
  • HALT on ambiguous AC per quality-engineering-test-plan-authoring scenario expansion: ultra-short AC, no expected behavior, bundled ACs, contradiction. Ask before drafting.
  1. Impact Analysis (run before any TC creation)
  • Step — Direct Lookup: Call Get Issue Link Test Cases with Jira issue key (e.g., {PROJECT}-{ID}).
  • Step B — Supplemental: If Step 0, search by [Module] and [Screen] keywords + check sibling issue links.
  • See Discovery Protocol for full chain.
  • Map each AC to coverage status:
  • Covered → ask user: skip or update to current format?
  • Partial → always propose NEW TC.
  • Not Covered → always create NEW TC.
  1. Draft Artifact:
  • Delete any existing zephyr_test_plan.md before writing.
  • Follow 4-section format in TC Format Reference exactly.
  • After writing: read back file and print full content in chat so user can review without opening it.
  • Ask for: review approval, handling of Covered ACs, and Zephyr Folder ID.
  1. Create in Zephyr (after explicit user approval)
  • Create Test Case (with customFields included — no separate Update needed) → Create Test Case Steps → Create Test Case Issue Link
  • For updates to existing TCs: fetch current steps via Get Test Case Steps, show before/after diff, wait for explicit approval, then Update Test Case.
  • Param contract per SmartBear API Notes.

Platform Rules

AC rowAction
Single row [ WEB + MOBILE ]ONE TC, Platform = "Web and Mobile", no platform prefix in name
Two rows same behavior, different platformsTWO TCs with Web_ / Mobile_ prefix — never merge

Naming & Filing

  • Name: Prefix Web_ / Mobile_ only when platform-exclusive; omit prefix for Web and Mobile.
  • Folder: Use exact Folder ID provided by user or specified in Technical Impact.
Role Mapping Rule
  • CRITICAL: If Acceptance Criteria uses generic terms like "user", "buyer", or "customer" in ordering/checkout context, it MUST mapped to ALL purchasing roles: ["Client user", "Client admin", "Internal sales rep", "External sales rep"]. not default to Client user.
Show full SKILL.md (251 more words)Show less

Anti-Patterns

  • No prefix omission: TC name sent to Zephyr API must include Web_ or Mobile_ prefix for platform-exclusive TCs — copy verbatim from artifact draft; omit prefix only when Platform = "Web and Mobile".
  • No Draft skip: Always set status = Draft; never automatically approve.
  • No flat folderId: Use "folder": {"id": X} in all PUT payloads.
  • No WEB+MOBILE split: One AC row = one TC with Platform "Web and Mobile".
  • No platform merge: Two AC rows, different platforms = two separate TCs.
  • No silent update: Show before/after diff; wait for explicit approval.
  • No lookup skip: Always run Step direct link lookup before supplemental search.
  • No stale artifact: Delete existing zephyr_test_plan.md before each run.
  • No coverage skip: Coverage Analysis table must open every artifact.
  • No ghost update: Update Zephyr TC whenever matching code changes.
  • No vague steps: Use specific observable outcomes — e.g., "System works" → "Banner 'Success' is visible".
  • No invented expected result: cite the AC or business rule, or tag ASSUMED and surface it for review.
  • No rephrased negatives: N and E scenarios must change a precondition or input, not the wording.
  • No generation on ambiguous AC: HALT and ask; a convincing TC must not hide a missing requirement.

Coverage wording

  • During impact analysis, map each AC to Covered, Partial, or Not Covered and check for duplicate test cases before drafting new ones.

Canonical response anchors

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

  • duplicate

  • impact analysis

  • no platform prefix

  • separate

  • Additional task-grounded exact anchors: Issue Link

© 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 5 other files (references) in skills/quality-engineering/quality-engineering-zephyr-test-generation of HoangNguyen0403/agent-skills-standard.

  • SKILL.md
  • evals/evals.json
  • references/impact_analysis.md
  • references/smartbear-api.md
  • references/tc_format.md
  • references/zephyr_schema.json

Open the folder on GitHubat commit b529c2d

Compare with similar skills

Quality Engineering Zephyr Test Generation 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 Zephyr Test Generation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quality Engineering Zephyr Test Generation this skillHoangNguyen0403/agent-skills-standard572—~1.3kAutomated safety check: PassMIT
Test Case Managementpetrkindlmann/qa-skills170—~5kAutomated safety check: PassMIT
Recommending Test Layersbitwarden/ai-plugins155—~2.4kAutomated safety check: PassCustom licence
Bug Retest Triagemirumee/nimara-ecommerce129—~888Automated safety check: PassBSD-3-Clause
Generate Test Planopenshift-eng/ai-helpers120—~1.6kAutomated safety check: PassApache-2.0
Writing Manual Test Casesbitwarden/ai-plugins155—~1.9kAutomated safety check: PassCustom licence

Similar skills

  • Test Case Management

    petrkindlmann/qa-skills

    Author and maintain MANUAL and hybrid test cases and suites in TestRail, Xray (Jira), Zephyr Scale, and Qase.

    170 GitHub stars~5k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed

  • Recommending Test Layers

    bitwarden/ai-plugins

    Official

    A skill your agent uses when deciding WHICH new tests a change needs and at WHICH layer each belongs, working from a Jira key, a Testmo CSV, an assessing-test-coverage report, a PR, or a feature…

    155 GitHub stars~2.4k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Bug Retest Triage

    mirumee/nimara-ecommerce

    Retest a reported defect on the live Nimara board (Jira project MS, board 74) and give it an evidence-backed verdict — still reproduces → Open, fixed → Done, blocked → leave In testing and ask.

    129 GitHub stars~888 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • 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

  • Writing Manual Test Cases

    bitwarden/ai-plugins

    Official

    A skill your agent uses when authoring NEW manual test cases in Gherkin format from a feature description, Jira ticket, acceptance criteria, PR, or design doc — the kind a QA engineer imports into…

    155 GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Emc

    aklofas/kicad-happy

    EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair…

    1.4k GitHub starsUsed in 1 repo~2.8k 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

Works with

Categories

Questions about Quality Engineering Zephyr Test Generation

What does Quality Engineering Zephyr Test Generation do?

Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. Quality Engineering Zephyr Test Generation is an agent skill from HoangNguyen0403/agent-skills-standard. Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs.

When should I use Quality Engineering Zephyr Test Generation?

Quality Engineering Zephyr Test Generation fits situations like: AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.

How do I install Quality Engineering Zephyr Test Generation in Claude Code?

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

How do I install Quality Engineering Zephyr Test Generation in Codex?

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

Can I use Quality Engineering Zephyr Test Generation 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-zephyr-test-generation -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-zephyr-test-generation, .gemini/skills/quality-engineering-zephyr-test-generation, .github/skills/quality-engineering-zephyr-test-generation and .opencode/skills/quality-engineering-zephyr-test-generation in your project.

What does Quality Engineering Zephyr Test Generation need to run?

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

Does Quality Engineering Zephyr Test Generation 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 Zephyr Test Generation 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 Zephyr Test Generation use?

Quality Engineering Zephyr Test Generation 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 Zephyr Test Generation use?

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

What are the alternatives to Quality Engineering Zephyr Test Generation?

Skills that share tags, products or a category with Quality Engineering Zephyr Test Generation: Test Case Management (petrkindlmann/qa-skills, 170 stars), Recommending Test Layers (bitwarden/ai-plugins, 155 stars), Bug Retest Triage (mirumee/nimara-ecommerce, 129 stars) and Generate Test Plan (openshift-eng/ai-helpers, 120 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quality Engineering Zephyr Test Generation?

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.