makinari-rol-judge-contract

Evaluates contract evidence to determine acceptance or rejection with placeholder resolution and escalation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluate contract-related evidence to determine acceptance or rejection.

Core Features & Use Cases

  • Per-flow judge for the contract workflow, enforcing a deterministic verdict based on evidence.
  • Rejects unresolved {{placeholders}} and requires an explicit acceptance match before progression.
  • Supports escalation after three failed attempts to obtain a valid acceptance.

Quick Start

Provide a contract-flow example with evidence containing placeholders to observe rejection when unresolved.

Frequently Asked Questions about makinari-rol-judge-contract

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

FAQPage Schema
How do I validate contract evidence to ensure unresolved placeholders are rejected?

Contract evidence validation requires checking for unresolved placeholders and rejecting submissions if they are found. This skill enforces placeholder resolution checks and requires an explicit acceptance match before progression.

What happens when contract acceptance matching fails multiple times during a review?

When contract acceptance matching fails repeatedly, the system triggers an escalation after three failed attempts to obtain a valid acceptance. This ensures unresolved contract flows do not proceed without valid evidence.

Can I use a deterministic judge to evaluate contract-related evidence automatically?

Yes, you can use a per-flow judge to enforce a deterministic verdict based on contract-related evidence. It evaluates the provided evidence to determine acceptance or rejection automatically.

How do I start testing a contract review workflow with placeholder validation?

To start testing contract review workflows, provide a contract-flow example with evidence containing placeholders. The system will reject the flow if the placeholders remain unresolved, demonstrating the validation mechanism.

Why does my contract workflow reject evidence even when the data seems correct?

Contract workflows reject evidence when it contains unresolved placeholders or fails to provide an exact acceptance match. The judge enforces strict evidence-to-claim matching before allowing any progression.

Does contract evidence evaluation work without resolving template placeholders?

No, contract evidence evaluation does not work without resolving template placeholders. The skill explicitly rejects unresolved placeholders and mandates their complete resolution before acceptance.