agentleFS
Sign inStart free
redicherediche/skills/qa/SKILL.md

qa

Skill3 starsChanged 36 days agoMITView on GitHub

Generates a practical QA checklist from the current conversation and goals. Use when the user asks for QA tasks, test checklists, validation steps, or simple step-by-step testing guidance.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep steps explicit and easy to follow.

    line 15
  2. Distinctive:

    Keep tasks small and independent so they can be completed one by one.

    line 17
  3. Distinctive:

    Prefer concise tasks over broad, combined tasks.

    line 22
  4. Distinctive:

    Use plain language and short steps.

    line 23
  5. Distinctive:

    Do not invent unrelated requirements.

    line 25

≈ “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

QA

Workflow

  1. Review the current conversation and identify the primary goals to verify.
  2. Convert each goal into one QA task with a clear, action-oriented title.
  3. For each QA task, provide a short step-by-step list of simple test actions.
  4. Keep steps explicit and easy to follow; avoid technical jargon unless required.
  5. Focus on practical verification outcomes (what to check and what should happen).
  6. Keep tasks small and independent so they can be completed one by one.

Output Rules

  • Base all QA tasks on the conversation context.
  • Prefer concise tasks over broad, combined tasks.
  • Use plain language and short steps.
  • Include expected result wording where useful.
  • Do not invent unrelated requirements.

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