willcoliveirawillcoliveira/qualiow-exploratory-testing-skills/skills/qa-knowledge-list/SKILL.md

qa-knowledge-list

Skill15 starsChanged 17 days agoMITView on GitHub

Browse and search the QA knowledge base. List entries by type, domain, or tag. Show changelog and stats. Use when user says: "list knowledge", "show heuristics", "what's in the knowledge base", "knowledge stats", "show changelog".

In this repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- qa-explore-cleanupSkill
- qa-explore-feedbackSkill
- qa-explore-mobileSkill
- qa-explore-quickSkill
- qa-explore-reportSkill
- qa-exploreSkill
- qa-gatherSkill
- qa-knowledge-addSkill
- qa-knowledge-listSkill
- qa-target-setupSkill
- qa-verify-backendSkill
- qa-explore-cleanupSkill
- qa-explore-feedbackSkill
- qa-explore-mobileSkill
- qa-explore-quickSkill
- qa-explore-reportSkill
- qa-exploreSkill
- qa-gatherSkill
- qa-knowledge-addSkill
- qa-target-setupSkill
- qa-verify-backendSkill

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Never paste a full entry into a session report or a website.
line 18
Very specific:
Never Read <data>/knowledge/manifest.yml or a release entry directly — --entry <id> returns one entry in full, and Grep answers a …
line 47
Very specific:
If the CLI is unavailable, say so and offer to Grep the manifest for what was asked rather than reading it whole.
line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Browse QA Knowledge Base

This skill is a thin wrapper around the qualiow CLI, which reads the base from <data>/knowledge/ plus any $PWD/data/knowledge/custom/*.yml. Resolve the qualiow prefix once per ${CLAUDE_SKILL_DIR}/../qa-explore/references/paths.md and write it literally.

Never paste a full entry into a session report or a website; the knowledge base is internal (${CLAUDE_SKILL_DIR}/../qa-explore/references/security-rules.md). Cite an entry by id in the ## Observations section of a session report instead — see ${CLAUDE_SKILL_DIR}/../qa-explore/references/output-contract.md.

Flag mapping

The user asks for	Run
everything	`qualiow list knowledge`
`--domain <id>`	`qualiow list knowledge --domain <id>`
`--tag <tag>`	`qualiow list knowledge --tag <tag>`
`--type <type>`	`qualiow list knowledge --type <type>`
`--entry <id>`	`qualiow list knowledge --entry <id>`
`--changelog`	`qualiow list knowledge --changelog`
`--stats`	`qualiow list knowledge --stats`

Flags combine; pass them through exactly as given. --type ∈ heuristic · technique · checklist · reference. The project's custom entries are listed in their own group.

qualiow list knowledge --domain fintech --tag security
qualiow list knowledge --entry heuristic-sfdipot

Rules

Print the command output verbatim. Do not re-order it, re-summarize it, or add entries from memory.
Never Read <data>/knowledge/manifest.yml or a release entry directly — --entry <id> returns one entry in full, and Grep answers a single-line question. The reasoning behind this is in ${CLAUDE_SKILL_DIR}/../qa-explore/references/delegation-rules.md.
If the CLI is unavailable, say so and offer to Grep the manifest for what was asked rather than reading it whole.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free