.NET MAUI Release Readiness
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
A skill your agent uses when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA.
Install Release Testing Workflow
$ npx skills add naodeng/awesome-qa-skills --skill release-testing-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install naodeng/awesome-qa-skills release-testing-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/en/testing-workflows/release-testing-workflow .claude/skills/release-testing-workflow && rm -rf skills-srcUse ~/.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/
Install the "release-testing-workflow" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/release-testing-workflow into .claude/skills/release-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-testing-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/release-testing-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add naodeng/awesome-qa-skills --skill release-testing-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install naodeng/awesome-qa-skills release-testing-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/en/testing-workflows/release-testing-workflow .agents/skills/release-testing-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-testing-workflow" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/release-testing-workflow into .agents/skills/release-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-testing-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add naodeng/awesome-qa-skills --skill release-testing-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install naodeng/awesome-qa-skills release-testing-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/en/testing-workflows/release-testing-workflow .cursor/skills/release-testing-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-testing-workflow" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/release-testing-workflow into .cursor/skills/release-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-testing-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/naodeng/awesome-qa-skills.git --path skills/en/testing-workflows/release-testing-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add naodeng/awesome-qa-skills --skill release-testing-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install naodeng/awesome-qa-skills release-testing-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/en/testing-workflows/release-testing-workflow .gemini/skills/release-testing-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-testing-workflow" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/release-testing-workflow into .gemini/skills/release-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-testing-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install naodeng/awesome-qa-skills release-testing-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add naodeng/awesome-qa-skills --skill release-testing-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/en/testing-workflows/release-testing-workflow .github/skills/release-testing-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-testing-workflow" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/release-testing-workflow into .github/skills/release-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-testing-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add naodeng/awesome-qa-skills --skill release-testing-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install naodeng/awesome-qa-skills release-testing-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/en/testing-workflows/release-testing-workflow .opencode/skills/release-testing-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-testing-workflow" agent skill from https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/release-testing-workflow into .opencode/skills/release-testing-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-testing-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-testing-workflow- GitHub stars
- 243
- Token cost
- ~536 tokens
- SKILL.md length
- 248 words
- Files
- 33 (incl. scripts)
- Skills in repo
- 61
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA.
- Works in 4 steps: Read and follow… → Add release date, scope, freeze rules,… → After locating the T window, hand off by… → …
- You need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring
- SKILL.md covers When to Use, Workflow, Core Constraints and Progressive Disclosure, plus 2 more sections
- Triggers include release testing workflow and go/no-go QA
What it does
Release Testing Workflow is an agent skill from naodeng/awesome-qa-skills. Use this skill when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA.
Its SKILL.md is about 540 tokens, which your agent loads only when the skill is triggered. The skill folder holds 37 other files, including scripts (for example `README.md`, `agents/openai.yaml` and `evals/cases/basic-success.yaml`).
It sits in Product & Project Management, covering Feature launches and release readiness. The repository describes itself as: Awesome QA Skills is an open-source AI-native Quality Engineering skill system that helps engineering teams reason about, design, execute, evaluate, and continuously improve…
When your agent uses it
- You need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring
- Triggers include release testing workflow and go/no-go QA
Example prompts
- “/release-testing-workflow”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Read and follow prompts/release-testing-workflow.md (timeline, gates, Go/No-Go, handoffs).
- Add release date, scope, freeze rules, candidate build, and known defects that change decisions.
- After locating the T window, hand off by skill name per reference.md; invoke specialty type skills by name only.
- If input is incomplete, still draft a gate board and mark assumptions—never invent pass results.
What it can do on your machine
Read from SKILL.md and the folder at commit 52c4eaf. 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
Ships 1 file in scripts/, which the agent can run.
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
Release Testing Workflow loads about 536 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 248 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 248 words (~536 tokens).
“Chinese version： See the corresponding Chinese skill.”
- name
- release-testing-workflow
Files
SKILL.md and 32 other files (scripts) in skills/en/testing-workflows/release-testing-workflow of naodeng/awesome-qa-skills.
- SKILL.md
- 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/release-testing-workflow.md
- reference.md
- scripts
- … and 17 more
Open the folder on GitHubat commit 52c4eaf
Compare with similar skills
Release Testing Workflow 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Testing Workflow this skillnaodeng/awesome-qa-skills | 243 | — | ~536 | Automated safety check: Pass | Custom licence | |
| .NET MAUI Release Readinessdotnet/maui | 23k | — | ~15k | Automated safety check: Pass | MIT | |
| Release ValidationMesh-LLM/mesh-llm | 3.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Final Release Reviewopenai/openai-agents-python | 30k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Final Release Reviewopenai/openai-agents-js | 3.9k | — | ~4k | Automated safety check: Pass | MIT | |
| Acceptance Demo GeneratorChachamaru127/claude-code-harness | 3.2k | — | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
- Official
Release Validation
Mesh-LLM/mesh-llm
A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…
- Official
Final Release Review
openai/openai-agents-python
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
- Official
Final Release Review
openai/openai-agents-js
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
Acceptance Demo Generator
Chachamaru127/claude-code-harness
Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.
Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
More from naodeng/awesome-qa-skills
All 61 skills in this repoAccessibility Testing
naodeng/awesome-qa-skills
A skill your agent uses when you need to design accessibility testing against WCAG, keyboard navigation, and assistive technology scenarios; triggers include accessibility testing and a11y testing.
API Test Bruno
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate Bruno collections for executable regression; triggers include Bruno collections and Bruno API testing.
API Test Pytest
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate Pytest API automation; triggers include Pytest API tests and API automation with Pytest.
API Test Restassure
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate Rest Assured Java test classes; triggers include Rest Assured, RestAssured, and Java API automation.
API Test Supertest
naodeng/awesome-qa-skills
A skill your agent uses when you need to parse multi-format API definitions and generate executable Supertest scripts; triggers include Supertest, Node.js API testing, and Supertest automation.
API Testing
naodeng/awesome-qa-skills
A skill your agent uses when you need to design API test plans or cases for REST, GraphQL, or gRPC interfaces; triggers include API testing and API test cases.
Related
Categories
Questions about Release Testing Workflow
What does Release Testing Workflow do?
A skill your agent uses when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA. Release Testing Workflow is an agent skill from naodeng/awesome-qa-skills. Use this skill when you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA.
When should I use Release Testing Workflow?
Release Testing Workflow fits situations like: you need release-phase QA workflow from T-14 planning to go/no-go and post-release monitoring; triggers include release testing workflow and go/no-go QA.
How do I install Release Testing Workflow in Claude Code?
Run `npx skills add naodeng/awesome-qa-skills --skill release-testing-workflow -a claude-code`. Or copy the skill folder (skills/en/testing-workflows/release-testing-workflow in naodeng/awesome-qa-skills) into .claude/skills/release-testing-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Release Testing Workflow in Codex?
Run `npx skills add naodeng/awesome-qa-skills --skill release-testing-workflow -a codex`. Or copy the skill folder (skills/en/testing-workflows/release-testing-workflow in naodeng/awesome-qa-skills) into .agents/skills/release-testing-workflow in your project. Codex loads it when a task matches its description.
Can I use Release Testing Workflow 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 naodeng/awesome-qa-skills --skill release-testing-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-testing-workflow, .gemini/skills/release-testing-workflow, .github/skills/release-testing-workflow and .opencode/skills/release-testing-workflow in your project.
What does Release Testing Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Release Testing Workflow is instructions for the agent only.
Does Release Testing Workflow 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 Release Testing Workflow 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Release Testing Workflow use?
Release Testing Workflow has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Release Testing Workflow use?
About 536 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release Testing Workflow?
Skills that share tags, products or a category with Release Testing Workflow: .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Final Release Review (openai/openai-agents-js, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Testing Workflow?
naodeng (a GitHub user) maintains it in naodeng/awesome-qa-skills, which has 243 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on September 26, 2026.
Source: naodeng/awesome-qa-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.