skills.rest
Uncodier
UncodierCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

makinari-rol-judge-task

Validate MAKINARI task flows for tool-call presence and matching acceptance tokens.

1|Updated May 8, 2025
Search Tags:#automation#task#acceptance#tool-call#flow-validation#makinari
One-click install
npx skills add https://github.com/Uncodier/API --skill makinari-rol-judge-task
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: makinari-rol-judge-task
Source: https://github.com/Uncodier/API/tree/main/src/skills/makinari-rol-judge-task
Command: npx skills add https://github.com/Uncodier/API --skill makinari-rol-judge-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate MAKINARI task and automation flows by ensuring at least one tool-call is recorded and acceptance tokens match.

Core Features & Use Cases

  • Enforces a minimal contract for flow evaluations, requiring at least one tool-call.
  • Verifies acceptance tokens align with expected outcomes in transcripts.
  • Supports both task-focused and automation-style MAKINARI workflows for end-to-end validation.

Quick Start

Provide a flow transcript to the judge and confirm it contains at least one tool-call with acceptance tokens that match.

Frequently Asked Questions about makinari-rol-judge-task

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

FAQPage Schema
How do I validate task flow transcripts to ensure tool execution occurred?▼

Task flow validation checks that at least one tool-call is recorded and acceptance tokens match expected outcomes. Provide a flow transcript to confirm it contains a tool-call with acceptance tokens that align, passing the minimal contract enforced by the judge.

What is the minimal contract required for automation flow acceptance checks?▼

Automation flow acceptance requires verifying at least one tool-call is present in the transcript and that acceptance tokens match. This minimal contract ensures runtime events and evidence of tool execution align with expected automation outcomes.

How do I verify acceptance tokens align with tool-call records in MAKINARI workflows?▼

Verifying acceptance tokens in MAKINARI workflows involves checking that recorded tool-call evidence matches the expected acceptance tokens in the transcript. The judge evaluates this alignment to confirm the automation flow meets its required outcomes.

Can I use this validation for both task-focused and automation-style MAKINARI workflows?▼

Yes, this validation supports both task-focused and automation-style MAKINARI workflows for end-to-end validation. It evaluates transcripts containing runtime events, tool execution evidence, and acceptance checks across both workflow types.

Why does my automation flow fail validation when no tool-call is recorded?▼

Automation flow validation fails without a recorded tool-call because the minimal contract requires at least one tool-call to be present. The judge enforces this requirement to ensure there is evidence of tool execution before matching acceptance tokens.

Related Skills

Explore More Software Engineering Skills→
raydocsraydocs

flow-next-work

Automates e2e execution of Flow epic tasks with built-in validation and reporting.

Community
Advanced
Imad-OuteImad-Oute
2

mh-coo-client-offboarding

Manage client offboarding transitions from accepted to handed-off engagement states.

Community
Advanced
pwv-vcpwv-vc
6

voice-e2e-test

Automate end-to-end voice call validation from initiation to report generation.

Official
Advanced
minh2004pdminh2004pd
18

adk-wiki-trace

Trace MemRAG wiki tool invocation failures and validate tool registration.

Community
Advanced