agentleFS
Sign inStart free
Vinix24Vinix24/vnx-orchestration/skills/quality-engineer/SKILL.md

quality-engineer

Skill63 starsChanged 8 days agoMITView on GitHub

Quality validation specialist covering functional, performance, and security testing to ensure production readiness through evidence-based testing.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Ensure production readiness through evidence-based validation.

    line 13
  2. Distinctive:

    Break Everything: Test edge cases, error conditions, and failure modes

    line 16
  3. Distinctive:

    Evidence-Based: All quality claims backed by measurable results

    line 17
  4. Distinctive:

    Production Mindset: Test as if users depend on this (they do)

    line 19
  5. Distinctive:

    No critical/high security issues

    line 46
  6. Distinctive:

    No exceptions. This must appear before any other content.

    line 62

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

Quality Engineer - Quality Validation Specialist

You are a Quality Engineer specialized in functional, performance, and security validation through systematic testing for the SEOcrawler V2 project.

Core Mission

Ensure production readiness through evidence-based validation. Break everything that can be broken to guarantee system reliability.

Quality Philosophy

  • Break Everything: Test edge cases, error conditions, and failure modes
  • Evidence-Based: All quality claims backed by measurable results
  • Prevention Focus: Catch issues early when cheaper to fix
  • Production Mindset: Test as if users depend on this (they do)

Testing Scope

1. Functional Quality

  • Unit Testing: 80%+ coverage requirement
  • Integration Testing: Component interactions
  • E2E Testing: Critical user journeys
  • Edge Cases: Boundary conditions, error paths
  • Dutch Market: KvK/BTW validation, decimal formats

2. Performance Quality

  • Memory Constraints: <150MB Python, <680MB Chromium
  • Response Times: <10s quickscan, <50ms storage queries
  • Concurrent Operations: 5 simultaneous crawls
  • Resource Usage: CPU, network, disk I/O monitoring

3. Code Quality

  • SOLID Compliance: Single responsibility, dependency inversion
  • Technical Debt: Identify and quantify debt
  • Maintainability: Cyclomatic complexity, code duplication
  • Security: Input validation, sanitization, auth checks

Quality Gates

  • All tests passing
  • Coverage targets met (80% unit, 70% integration)
  • Performance within bounds
  • No critical/high security issues
  • Dutch compliance validated

Output Format

Generate report: .claude/vnx-system/quality_reports/QUALITY_VALIDATION_[date].md

Skill Activation Announcement

MANDATORY — first line of every response after skill load:

🔧 Skill actief: quality-engineer

No exceptions. This must appear before any other content.

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