Skills for QA and documentation work — write the test cases, audit the docs, fetch the pages. Install once, use them in Claude Code, ZCode, Cursor or Antigravity.

Tiếng Việt

Install

Claude Code — marketplace install, gets every skill in the repo:

claude plugin marketplace add xtieume/testcase
claude plugin install testcase@testcase-marketplace

ZCode — same flow, reading .zcode-plugin/:

zcode plugin marketplace add xtieume/testcase
zcode plugin install testcase@testcase-marketplace

Cursor / Antigravity — both read .agents/skills/ natively. Clone once, then symlink it into a project or copy it globally:

git clone https://github.com/xtieume/testcase.git

# project level (either editor)
ln -s "$(pwd)/testcase/.agents/skills" .agents/skills

# global
cp -R testcase/.agents/skills/* ~/.cursor/skills/              # Cursor
cp -R testcase/.agents/skills/* ~/.gemini/antigravity/skills/  # Antigravity

Any host, one skill only — copy the folder you want:

cp -R .agents/skills/<name> ~/.claude/skills/<name>

Skills trigger on natural language, or explicitly as /<name>.

Skills

Each name links to its SKILL.md, which is the reference for that skill — triggers, workflow, flags, scripts.

QA

Skill	Does	Trigger
🧪 testcase	Test cases from a requirement, attacks its own output for missed cases, then implements the automatable ones as runnable tests	"write test cases for…"
📋 docs-review	Audits docs against a spec: required vs actually written, with a citation per verdict	"review the docs against spec.md"

Data capture

Skill	Does	Trigger
📥 playwright-notion	Notion → markdown through a logged-in browser, when API token and Export are both unavailable	"download these Notion pages"

House rules

Conventions every skill here follows, so a new one is predictable before you open it:

• SKILL.md stays small. Detail goes in references/, loaded only when the task needs it.
• Review before returning. Skills that produce a deliverable end with an independent subagent pass that re-derives the work and attacks it, repeating until a round adds nothing.
• Scripts are stdlib. Python or Node, no install step unless the skill says otherwise; they lint the output rather than trusting it.
• Verdicts carry evidence. Any claim about a document or requirement cites the line it came from.

Setup beyond cloning, where a skill needs it:

cd .agents/skills/playwright-notion/scripts && npm install   # once

Adding a skill

Drop a folder into .agents/skills/<name>/ with a SKILL.md (frontmatter name + description), plus optional references/ and scripts/. No manifest edit: both plugin.json files point at the directory, not a list. Add a row to the table above and bump the skill count in the badge. Versions are not edited by hand: merging to main bumps all four manifests, tags the commit and publishes a release — feat: gives a minor bump, ! or BREAKING CHANGE a major one, anything else a patch.

Layout

.agents/skills/<name>/     SKILL.md + references/ + scripts/
.claude-plugin/            Claude Code manifests
.zcode-plugin/             ZCode manifests

License

MIT