Marketplace for trusted AI agent skills

Skill Detail

Run agentic quality engineering checks with Agentic QE

Configure Agentic QE in a repository so a coding agent can generate tests, inspect coverage gaps, investigate flaky behavior, and report reviewable quality evidence.

Code Quality & ReviewMulti-Framework
Code Quality & Review Multi-Framework Security Reviewed
⭐ 495 GitHub stars ⬇ 44.8k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill run-agentic-quality-engineering-checks-with-agentic-qe Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
View source Documentation
At a glance
Tools required
Node.js 22.13.0 or newer, npm 10 or newer, the agentic-qe CLI, and a supported coding-agent client such as Claude Code, Codex CLI, GitHub Copilot, Cursor, Cline, OpenCode, Kiro, Roo Code, Windsurf, or Continue.dev
Install & setup
Run npm install -g agentic-qe, then cd into the target repository and run aqe init –auto. Add client-specific setup flags such as –with-codex, –with-cursor, or –with-all-platforms when needed, then verify with aqe health.
Author
Dragan Spiridonov / proffesor-for-testing
Publisher
Open Source Project
Last updated
Oct 9, 2026
Quick brief

Use Agentic QE when a team wants a coding agent to perform structured quality-engineering work close to the codebase. The operator installs the AQE CLI, initializes project configuration, connects the supported agent client, then asks for narrow tasks such as generating tests for a changed service, prioritizing coverage gaps by risk, investigating flaky failures, or coordinating a release quality assessment. The expected output is not just generated test code; it includes rationale, executed checks when available, unresolved risks, and evidence the human can inspect.

How it works

What this skill actually does

Invoke this instead of asking a general coding assistant to write tests from scratch when the quality task needs a repeatable QE surface, MCP-backed project context, framework-specific test output, and explicit review boundaries. The scope boundary is repository quality engineering through AQE commands, skills, agents, and client setup. It is not a generic QA product card, a test framework listing, or a claim that an agent can replace human release judgment.