evaluator

Evaluate code against QA checklists and emit PASS/FAIL verdicts.

Updated Nov 26, 2025
One-click install
npx skills add https://github.com/neyrojasj/smart-agent --skill evaluator-neyrojasj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evaluator
Source: https://github.com/neyrojasj/smart-agent/tree/main/.github/skills/evaluator
Command: npx skills add https://github.com/neyrojasj/smart-agent --skill evaluator-neyrojasj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-execution QA evaluation is tedious and error-prone; this skill automates checking results against QA checklists and captures actionable learnings to improve procedures and documentation.

Core Features & Use Cases

  • Evaluate code against post-execution QA checklists and emit PASS/FAIL verdicts with evidence
  • Track iteration history and surface learnings to update skills, docs, and context
  • Generate learning proposals after plan completion for continuous improvement

Quick Start

Trigger the evaluator after a completed plan to generate a verdict and improvement proposals.

Frequently Asked Questions about evaluator

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

FAQPage Schema
How do I automate post-execution QA checklist evaluation for code?

Post-execution QA checklist evaluation is automated by checking completed code results against validation criteria to emit structured PASS or FAIL verdicts with supporting evidence. It surfaces actionable insights to drive continuous improvement.

What is the best way to track iteration history and learnings across multiple skills?

Tracking iteration history and learnings across multiple skills is achieved by capturing post-execution validation results and generating learning proposals after plan completion. This updates skills, docs, and context for continuous improvement.

How do I generate learning proposals after a plan-to-code cycle finishes?

Learning proposals after a plan-to-code cycle are generated by triggering automated evaluation against QA checklists upon plan completion. This captures actionable learnings to improve procedures, documentation, and future iterations.

Can I integrate post-execution validation into a continuous learning loop?

Post-execution validation integrates into continuous learning loops by applying automated checklist evaluations after code execution. It surfaces structured verdicts and iteration history to update skills, docs, and context dynamically.

Why does manual post-execution QA fail to surface actionable insights?

Manual post-execution QA fails to surface actionable insights because it is tedious and error-prone. Automating the evaluation of QA checklists captures structured verdicts and learnings efficiently to improve procedures and documentation.

Do I need dependencies to evaluate code against post-execution QA checklists?

Evaluating code against post-execution QA checklists requires no external dependencies. The automation runs independently to check results, emit PASS or FAIL verdicts, and track iteration history for learning extraction.