evaluator

Analyze build outputs and test results to verify code quality and security.

1|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/scottconverse/productteam --skill evaluator-scottconverse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evaluator
Source: https://github.com/scottconverse/productteam/tree/main/skills/evaluator
Command: npx skills add https://github.com/scottconverse/productteam --skill evaluator-scottconverse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure the correctness and quality of code produced within a product development pipeline by providing rigorous evaluation and verification.

Core Features & Use Cases

  • Code Verification: Analyzes builder-generated code and tests to confirm adherence to acceptance criteria.
  • Test Suite Analysis: Runs existing tests in a pre-configured environment to verify functionality.
  • Risk Identification: Detects missing deliverables, security issues, and architectural flaws.
  • Use Case: Use this Skill to validate a new feature implementation before integration, ensuring all requirements are met with verifiable evidence.

Quick Start

Use the evaluator to review the latest build output and run the test suite to verify code quality and compliance.

Frequently Asked Questions about evaluator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code quality and test coverage in a development pipeline?

Code quality and test coverage verification analyzes build outputs and test results to ensure compliance with acceptance criteria and specified standards. It checks builder-generated code for vulnerabilities, missing deliverables, and architectural flaws before integration.

What is skeptical verification of builder outputs in product pipelines?

Skeptical verification evaluates builder-generated code against acceptance criteria by running existing tests and analyzing outputs. It identifies security issues, missing deliverables, and architectural flaws to ensure product correctness and quality within development pipelines.

Do I need pre-installed testing frameworks to run code verification and risk identification?

Yes, pre-installed testing frameworks and code analysis tools are required. The verification process runs existing tests in a pre-configured environment to validate functionality, detect code vulnerabilities, and confirm adherence to specified standards.

How do I check for security vulnerabilities and missing deliverables before feature integration?

Security vulnerabilities and missing deliverables are detected by analyzing build outputs and test results. This verification confirms adherence to acceptance criteria and finds architectural flaws, ensuring all requirements are met with verifiable evidence before integration.

Can I use code review to validate test suite functionality in a pre-configured environment?

Yes, test suite validation runs existing tests within a pre-configured environment to verify functionality. The process analyzes builder-generated code, confirms compliance with acceptance criteria, and identifies security issues or architectural flaws.

What are the limitations of automated code review for security and compliance verification?

Automated verification relies on pre-installed testing frameworks and code analysis tools. It requires a pre-configured environment to run existing tests, meaning it cannot validate functionality or detect vulnerabilities without these dependencies properly set up beforehand.