Cxc Qa

Community

lidge-jun

cxc-qa

Use for manual web, TUI, CLI, API and desktop QA. Triggers: smoke test, visual QA, screenshot check, CJK clipping, 수동 QA, 실제로 되는지 확인, 동작 확인, 직접 돌려봐.

Overview

Publisher	lidge-jun
Repository	`codexclaw`
Skill name	`cxc-qa`
Stars	51
Forks	10
Bundled files	9
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
9 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by lidge-jun on GitHub. Read the source before you install it.

Installation

Install the Cxc Qa AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/lidge-jun/codexclaw/tree/main/plugins/codexclaw/skills/qa
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/lidge-jun/codexclaw.git /tmp/codexclaw
mkdir -p .claude/skills
cp -r /tmp/codexclaw/plugins/codexclaw/skills/qa .claude/skills/cxc-qa

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cxc Qa in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cxc Qa on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cxc Qa is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

cxc-qa — Manual Surface QA Gate

Prove a built surface works by DRIVING it, not by inferring from green tests. No scenario closes on a status string; it closes on a captured artifact from a real surface, an adversarial pass, and a teardown receipt. Everything in this skill is E7 discipline (agent-followed, not hook-enforced); the one shipped E2 touchpoint is noted in §7.

Completion proof: dev verification gate (FAMILY-PROOF-01). Every PASS points at a non-empty artifact you (or your dispatched QA worker) captured THIS round.

2. Surface detection + faithful channels

State the exact surface and invocation BEFORE running each scenario. Use the channel faithful to the surface — CLI output parsed from the wrong layer is not evidence of the layer you changed:

Surface	Faithful channel	Artifact
HTTP API	`curl -i` (headers + body) — scenarios in `references/http-api-qa.md`	response capture
CLI	real invocation, stdout/stderr split + exit code — discipline in `references/cli-tui-qa.md`	terminal capture
TUI	tmux session at FIXED dims — mechanics in `references/cli-tui-qa.md`, visual rubric in `references/visual-qa.md`	plain + ANSI captures
Web UI	browser screenshot at a STATED viewport, read via `view_image` — workflow in `references/visual-qa.md`	screenshot(s)
Desktop GUI	computer-use + screenshots (per-app approval; never drive terminals/Codex itself)	screenshots + action log; native panels, menu-bar popups and approval prompts follow `dev-devops` `native-desktop-acceptance.md` §10 and `macos-system-approvals.md`

Tool choice for the browser/CU rows follows the shared portable browser policy; the inspect -> act -> re-inspect protocol applies. Data-shaped behavior may use parsed CLI/data output as its channel.

Modular References

Read the matching row before the governed action.

Condition	Reference
Choosing QA ownership or closing PABCD C	Scope and binding
Recording any scenario verdict or aggregate receipt	Evidence contract
Driving scenarios and reviewing artifacts	Adversarial classes and oracle passes
Finishing any QA pass	Teardown receipts
ANY visual surface verdict (web UI, TUI, desktop GUI)	Visual rubric
HTTP API surface scenarios	Wire-driving procedure
CLI or TUI surface scenarios	Session mechanics
Choosing browser/CU tools	Portable browser routing (QA-TOOL-LADDER-01)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Cxc Qa AI skill do?

Use for manual web, TUI, CLI, API and desktop QA. Triggers: smoke test, visual QA, screenshot check, CJK clipping, 수동 QA, 실제로 되는지 확인, 동작 확인, 직접 돌려봐.

Why use Cxc Qa on TypingMind?

Because you install it once and use it with any model. Cxc Qa is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cxc Qa in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/lidge-jun/codexclaw/tree/main/plugins/codexclaw/skills/qa. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Cxc Qa?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cxc Qa?

As many as you like. As long as a model supports skills, you can use Cxc Qa with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cxc Qa AI skill free?

Yes. It is published on GitHub by lidge-jun under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Channel Message Flows

openclaw

OrganizationPopular

Use when running QA Lab channel message flow evidence.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Clawdtributor

Clawtributor PRs here, last week or another window: discover conversation refs, recheck GitHub, rank by impact.

Control Ui E2e

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

cxc-qa — Manual Surface QA Gate

2. Surface detection + faithful channels

Modular References

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now