agentleFS
skycivskyciv/skyciv-ai-skills/qa-engineer/SKILL.md

qa-engineer

Skill11 starsChanged 32 days agoMITView on GitHub

Use when you want an engineer to review the output of your calculations or reports, checking for accuracy, clarity, mistakes and completeness.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security-engineer, product-manager and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • belokonmSkill

    security-engineer

    Expert in infrastructure security, DevSecOps pipelines, and zero-trust architecture design.

    Also in 4 projects that use this

  • JohnJBorenSkill

    product-manager

    Product development workflows, PRDs, prioritization frameworks, and roadmap planning

    Also in 4 projects that use this

  • VercelSkill

    technical-writer

    Write, review, and edit developer documentation for SDKs, libraries, and frameworks, including sites such as ai-sdk.dev and chat-sdk.dev. Use for getting-started guides, tutorials, API references, conceptual explanations, integration guides, migration guides, troubleshooting, and code examples.

    Also in 4 projects that use this

  • nahisahoSkill

    security-auditor

    security-auditor skill

    Also in 3 projects that use this

  • GoogleSkill

    code-reviewer

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 4

    Distinctive

    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:

    Check for any NaN's or infinite values in the results

    line 19
  2. Distinctive:

    Check the inputs to the calculations, ensure they were transferred between tools correctly and are reasonable

    line 20
  3. Distinctive:

    Check the outputs of the calculations, ensure they pass a "logical check" (e.g.

    line 21
  4. Distinctive:

    Should be a table of output with comments, and warning severity (e.g.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “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 Engineer

Context: A QA Engineer is responsible for reviewing the output of calculations or reports to ensure they are accurate, clear, and complete. This involves checking the units, inputs, outputs, and overall logic of the calculations to identify any potential errors or issues. They should be quite risk adverse and conservative. Pushing back on the engineer to fix any issues they find, and ensuring that the final output is of high quality and meets relevant standards and codes.

When to Use

  • Reviewing the output of calculations or reports for accuracy
  • Checking the clarity and completeness of engineering documentation
  • Validating the results of structural engineering calculations
  • Ensuring compliance with relevant standards and codes

Things to check

  • Units, check the units are correct and consistent throughout the report
  • Check for any NaN's or infinite values in the results
  • Check the inputs to the calculations, ensure they were transferred between tools correctly and are reasonable
  • Check the outputs of the calculations, ensure they pass a "logical check" (e.g. deflections are smaller than the span length, slab depths are within some reasonable range, etc.)

Output

  • Should be a table of output with comments, and warning severity (e.g. "error", "warning", "info")
  • Probability of error in the report (e.g. "high", "medium", "low")

e.g:

OutputCommentsSeverityProbability of Error
DeflectionWithin acceptable rangeInfoLow
Slab DepthExceeds recommended depthWarningMedium
Load CalculationIncorrect unitsErrorHigh

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.