makinari-test-agent

Automates validation and testing of worker agents, emitting a standardized test_results.json artifact.

1|Updated May 8, 2025
One-click install
npx skills add https://github.com/Uncodier/API --skill makinari-test-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: makinari-test-agent
Source: https://github.com/Uncodier/API/tree/main/src/skills/makinari-test-agent
Command: npx skills add https://github.com/Uncodier/API --skill makinari-test-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined framework to validate worker-agent tasks by formalizing when a step is complete and ensuring a canonical test_results.json artifact is produced for gatekeeping.

Core Features & Use Cases

  • Build, test, and validate worker agent workflows across frontend, backend, and content domains.
  • Artifact emission: always generate a standardized test_results.json at the repo root for makinari-fase-validacion.
  • Guardrails and reporting: codify the completion criteria, re-run on failures, and commit via automated tooling.

Quick Start

Run the mandated build and test steps to generate a valid test_results.json and push the completed work.

Frequently Asked Questions about makinari-test-agent

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

FAQPage Schema
How do I automate test validation and generate a test_results.json artifact for worker agents?

To automate test validation and generate a test_results.json artifact, you run mandated build and test steps to execute workflows, capture results, and emit a standardized JSON file at the repository root conforming to the validation schema.

What is a test playbook for worker agents and when do I need a standardized validation artifact?

A test playbook for worker agents is a disciplined framework formalizing when a task step is complete. You need a standardized validation artifact like test_results.json for gatekeeping and ensuring code works across frontend, backend, and content workflows.

How do I enforce completion criteria and emit structured test results for automated workflows?

You enforce completion criteria by applying execution rules that codify step completion, re-run on failures, and commit via automated tooling, producing a structured test_results.json artifact at the repository root for gatekeeping.

Does this test validation playbook work for frontend, backend, and content builds?

Yes, this test validation playbook works for frontend, backend, and content builds. It applies to any workflow where builds are executed, results are captured, and a standardized test_results.json artifact is emitted under the validation phase.

What are the limitations of relying on a standardized test_results.json artifact for quality assurance?

The limitation of relying on a standardized test_results.json artifact is that it strictly enforces execution rules and schema conformance, meaning workflows failing to produce this canonical file at the repository root cannot pass gatekeeping validation.