Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →griddynamics/qa-structure
To resolve QA session paths, identifiers/slugs, and state-file shape
Passed 15 of 19 test cases with the skill, and 6 of 19 without it.
and 10 more in the full report
11 fixed6 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
The API test configuration is missing and needs to be gathered interactively. Which asset should be loaded to conduct the interview?
| Checked | Without skill | With skill |
|---|---|---|
| Reads assets/api-aqa-config-interview.md | Missed | Passed |
The instructions your model reads when the skill loads.
<qa_structure>
<when_to_use_skill>
Use when you need to create the QA session folder, resolve or name an artifact path, derive the {IDENTIFIER} / <test-name> slug, or seed/read the QA state file. This is the single source for WHERE QA artifacts live -- not for HOW to author or analyze them. Use TMS, Issue Tracker, and Wiki as the roles; TestRail, Jira, and Confluence are canonical examples only.
</when_to_use_skill>
<core_concepts>
references/api-aqa-layout.md (backend API) XOR READ SKILL FILE references/ui-aqa-layout.md (UI/E2E) -- canonical paths + each flow's slug authority, guards, and state-file fields live there.state, index, and the flow's own *-state name.{IDENTIFIER}: if unresolvable even after one user attempt, stop, record the gap in the flow's state file, ask once -- never fabricate or guess.## Phase Completion Status (8 rows) + per-phase append blocks; each phase appends only its own delta.gain.json.sdlc is the primary SDLC-provider configuration. Merge it with explicit user input, recognizable provider URLs/handles, and available integrations; ask only when evidence conflicts or remains unresolved.references/config-schema.md only when loading/validating that run artifact.<resources>.</core_concepts>
Router -- READ SKILL FILE for the one your current step needs (point-of-use, never all at once):
| When you need to… | Command |
|---|---|
resolve API-AQA paths, {IDENTIFIER} derivation, or the QA state-file shape | READ SKILL FILE references/api-aqa-layout.md |
resolve UI-AQA paths, the <test-name> slug rules, the page-sources contract, or the UI-AQA state-file shape | READ SKILL FILE references/ui-aqa-layout.md |
load or validate the API-AQA per-run config keys (keys + consumer + accepted N/A forms) | READ SKILL FILE references/config-schema.md |
| write the API-AQA project-config file | READ SKILL FILE assets/api-aqa-project-config-template.md |
| run the user interview when the config is missing | READ SKILL FILE assets/api-aqa-config-interview.md |
| seed the UI-AQA state file | READ SKILL FILE assets/ui-aqa-state-template.md |
The API-AQA state-file seed and the API-AQA per-run initial-data skeleton are tiny + always-needed, so they stay inline in the consuming step rather than as assets -- avoids extra reads on the critical path.
<anti_patterns>
test cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.