review-interface

Define a precise output schema for standardized review result reporting.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/NetzSicht/Skill---W-S-Company --skill review-interface-netzsicht
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-interface
Source: https://github.com/NetzSicht/Skill---W-S-Company/tree/main/skills/review-interface
Command: npx skills add https://github.com/NetzSicht/Skill---W-S-Company --skill review-interface-netzsicht

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines and enforces a strict, exact output schema for review results (Interface C), ensuring consistency and auditability across evaluations.

Core Features & Use Cases

  • Structured evaluation: includes meta, summary, dimension ratings, slot-detail reviews, and action routing.
  • Quality gate readiness: enables consistent decision outcomes (APPROVED / REVISION / ABGELEHNT) during reviews.
  • Audit-friendly mappings: supports USP and objection mappings with clear traceability for internal reviews.

Quick Start

Structure every review output to conform to Interface C using the exact markdown layout described above.

Frequently Asked Questions about review-interface

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

FAQPage Schema
How do I standardize review outputs for quality gates and product-brief evaluations?▼

Standardize review outputs by applying a structured schema (Interface C) that enforces sections for meta, summary, dimension ratings, and slot details. This ensures consistency and auditability across product-brief evaluations and quality gates.

What is the best way to map USPs and objections during a slot-level assessment?▼

Mapping USPs and objections during a slot-level assessment requires an audit-friendly schema with clear traceability. Interface C provides dedicated sections for USP and objection mappings to ensure transparent internal reviews.

How does action routing work for review decisions like APPROVED, REVISION, or ABGELEHNT?▼

Action routing for review decisions like APPROVED, REVISION, or ABGELEHNT works through a defined decision workflow in the output schema. Interface C includes clear action routing to enable consistent quality gate readiness and standardized evaluation outcomes.

Can I use a structured markdown layout to enforce consistency in feedback processes?▼

Yes, you can enforce consistency in feedback processes using an exact markdown layout. Interface C defines a precise output schema that structures every review result to conform to a standardized format across the entire evaluation process.

When do I need a strict output schema for review results instead of free-text feedback?▼

You need a strict output schema for review results when you require auditability and consistent decision outcomes across multiple evaluators. Interface C replaces free-text feedback with structured sections to guarantee quality gate readiness.