excrtx-assess-interactive-audit

Runs moderated persona-driven audits of artifacts producing evidence-backed issue backlogs and GO/NO-GO verdicts.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-assess-interactive-audit-elderbernardi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: excrtx-assess-interactive-audit
Source: https://github.com/elderbernardi/exocortex.saas/tree/main/skills/excrtx-assess-interactive-audit
Command: npx skills add https://github.com/elderbernardi/exocortex.saas --skill excrtx-assess-interactive-audit-elderbernardi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Evaluating a real product, dataset, API, or skill under production-like conditions often produces ad-hoc, unverifiable feedback. This Skill standardizes the audit into a moderated, evidence-based process with owner-in-the-loop checkpoints, so every finding is reproducible, classified, and ready for a GO/NO-GO decision. ## Core Features & Use Cases - Two-persona audit loop: a first-person user driver exercises the real artifact surface while an expert observer scores explicit dimensions with P0–P3 severity. - Evidence and governance discipline: every finding cites captured evidence, external mutations follow Draft-First rules with tagged, logged, reversible actions, and uncertain verdicts are confirmed with the executive at finding-time. - Structured deliverables: generates PROMPT.md, TASKS.md, PROGRESS.jsonl, QUESTIONS.jsonl, an ISSUES.md backlog, persona experience narrative, expert critique, and a FINAL_REPORT.md with GO/NO-GO verdict. - Use Case: Before a beta release, ask for a UX and accessibility audit of your staging app; the Skill instantiates the audit template, runs both personas, captures screenshots and logs, and delivers a prioritized issue backlog with a release-readiness verdict. ## Quick Start Audit the staging build of my web app for UX and accessibility issues and give me a GO/NO-GO release verdict with an issue backlog.

Frequently Asked Questions about excrtx-assess-interactive-audit

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

FAQPage Schema
How do I run a UX audit with personas before a product release?▼

Use this Skill to instantiate the audit template, then run two personas: a first-person user driver performing real tasks and an expert observer scoring explicit dimensions. Every finding gets evidence, a P0–P3 severity, and a verdict, ending in a GO/NO-GO report.

What deliverables does an interactive audit produce?▼

The audit produces PROMPT.md, TASKS.md, PROGRESS.jsonl, QUESTIONS.jsonl, an artifacts folder with evidence, and four reports: ISSUES.md as the primary backlog, a persona experience narrative, an expert critique, and FINAL_REPORT.md with the GO/NO-GO verdict.

Can this audit skills, APIs, or datasets instead of UI?▼

Yes. The observer dimensions adapt per artifact type: correctness and freshness for data audits, contract conformance and error surfaces for API/CLI audits, and the D1–D5 skilljudge rubric for skill audits. The driver persona always exercises the real consumer surface.

How are external actions and mutations handled during an audit?▼

External actions such as sending messages, pushing branches, or deploying require a DRAFT first under Draft-First governance. Every authorized mutation is tagged with [AUDIT:slug], logged in PROGRESS.jsonl, and included in a cleanup checklist.

When should I not use an interactive audit?▼

Do not use it for simple code review, unit-test creation, bugfix execution, refactoring, brainstorming, or reading a document without producing an audit. Those tasks belong to specialized development or research skills.