aming-claw-ue-review

Audit Aming Claw flows against ue_audit.v1 for visibility gaps.

26|5|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/amingclawdev/aming-claw --skill aming-claw-ue-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aming-claw-ue-review
Source: https://github.com/amingclawdev/aming-claw/tree/main/skills/aming-claw-ue-review
Command: npx skills add https://github.com/amingclawdev/aming-claw --skill aming-claw-ue-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Governance teams reviewing Aming Claw flows need a structured, auditable evaluation against the bundled ue_audit.v1 contract to ensure visibility of user requests and state across ordinary builder scenarios.

Core Features & Use Cases

  • Intent-focused review: Evaluate hierarchy, object visibility, status visibility, next actions, terminology, error states, feedback, accessibility, and device compatibility.
  • Audit-output driven decisions: Produce machine-readable findings with severity, evidence refs, recommendations, and acceptance impact; support pass, pass_with_followups, or block decisions.
  • Fallback governance: If an external UE skill is unavailable, rely on the bundled governance profile and record the expert source in the audit output.

Quick Start

Review the current user-facing Aming Claw flows against ue_audit.v1 and generate a compliant audit report.

Frequently Asked Questions about aming-claw-ue-review

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

FAQPage Schema
How do I audit UE governance gaps in user-facing flows?

To audit UE governance gaps, evaluate user-facing flows against the ue_audit.v1 contract to surface visibility issues across hierarchy, object status, next actions, terminology, and error states. This generates machine-readable findings with severity levels and evidence references for compliance tracking.

What is a UE audit for user experience flow governance?

A UE audit is a structured evaluation that applies the ue_audit.v1 contract to ordinary builder flows, ensuring clear visibility of user requests and state transitions across the flow lifecycle. It enforces compliance by requiring the recording of the expert source in the audit output.

How do I generate a compliance audit report for user-facing flows?

Generate a compliance audit report by reviewing current user-facing flows against the ue_audit.v1 standard. The output produces machine-readable findings with severity, evidence refs, recommendations, and acceptance impact, supporting pass, pass_with_followups, or block decisions.

Can I review UE compliance without an external audit tool?

Yes, you can review UE compliance without external tools by relying on the bundled governance profile. This fallback mechanism enforces the ue_audit.v1 contract and requires recording the expert source directly in the audit output to maintain governance visibility.

What dimensions does a UE visibility review cover?

A UE visibility review covers hierarchy, object visibility, status visibility, next actions, terminology, error states, feedback, accessibility, and device compatibility. These dimensions ensure comprehensive governance of user-facing flows across the entire flow lifecycle.

What limitations exist when applying fallback governance to UE audits?

The main limitation of fallback governance is the reliance on the bundled expert source only when external UE skills are unavailable. While it still enforces the ue_audit.v1 contract, the scope is restricted to ordinary builder flows where request and state visibility matter.