- name
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add paperclipai/paperclip --skill qa-acceptance -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add paperclipai/paperclip --skill qa-acceptance -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add paperclipai/paperclip --skill qa-acceptance -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add paperclipai/paperclip --skill qa-acceptance -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/paperclipai/paperclip/tree/HEAD/packages/skills-catalog/catalog/bundled/quality/qa-acceptanceFrom the publisher
Write acceptance criteria that a reviewer can run against the running app and decide pass or fail without asking the author. The criteria are the contract — automated tests cover correctness, QA covers feature-level behavior.
Each criterion is a single, independently-verifiable statement:
- **Given** <starting state>, **when** <action>, **then** <observable outcome>.
Example:
- **Given** a CSV export with 0 rows, **when** the user clicks Export, **then** the file downloads with only the header row and the UI shows "Exported 0 rows".
Avoid criteria that combine multiple whens or thens. Split them.
If a section is genuinely not applicable, write "N/A: " — do not silently omit.
Each criterion needs evidence on the verification pass:
"Looks good to me" without evidence is not a pass.
Return the validation plan with three sections:
The author owns turning failures into either fixes or accepted deferrals.
© 2026 Skills Rack.
---name: qa-acceptancedescription: Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases…---# packages/skills-catalog/catalog/bundled/quality/qa-acceptance/SKILL.mdFAQ
Download packages/skills-catalog/catalog/bundled/quality/qa-acceptance/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/paperclipai/paperclip.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.